vnc improvements #673
Draft
vnc improvements #673
Conversation
This file contains 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.
working on making VNC perform better by supporting lower bit depth pixel formats and implementing partial screen updates (as well as trying to plumb faux-relative mouse, but that will likely split into a separate PR later).
in service of making oxidecomputer/omicron#5342 viable.
support for tighter pixel formats relies on oxidecomputer/rfb#12
low bit-rate desktop (8-bit RGB 3:3:2) on display:
a partial update gone wrong during development, but that's illustrative of partial screen-damage updates existing at all:
