Conversation
Contributor
|
So /dev/ttyS1 should be COM2 on windows? My emulator uses COM1, COM2 ... |
Owner
Author
I'm not sure your question here, but the general idea is to map "COM1" (/dev/ttyS0) to the host Terminal, and "COM2" (/dev/ttyS1) to the emulator MS mouse. Then set MOUSE_PORT=/dev/ttyS1. If it is not possible to attach COM1 to the host terminal, that is still OK, you can still attach the emulator mouse to COM2, right? |
Contributor
|
mouse says /dev/ttyS0 |
Contributor
|
does not work. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed in ghaerr/microwindows#106 with @toncho11, the
mousecommand will now display the mouse port being used when started.In addition, Nano-X will display the mouse port on startup. Properly configured, this "message" will display on either /dev/ttyS0 when running on QEMU, or /dev/console otherwise. Because nano-X clears the screen to graphics mode, the mouse message may be erased quickly and not be seen (along with any other error or informative messages). For this reason, it is recommended that emulators set the mouse port to /dev/ttyS1 (along with MOUSE_PORT=/dev/ttyS1) and console output to /dev/ttyS0 so that messages can be seen.
Here's a pre-built image with both fixes for testing.
fd2880.img.zip