Skip to content

docs: what the display shows on the VisionFive 2, read back - #34

Merged
jwinarske merged 1 commit into
mainfrom
the-display-read-back-on-the-visionfive-2
Nov 18, 2026
Merged

jwinarske merged 1 commit into
mainfrom
the-display-read-back-on-the-visionfive-2

Conversation

@jwinarske

Copy link
Copy Markdown
Owner

With frames no longer waited for (#33), what the VisionFive 2's display shows was read back with --capture and compared with the same frames drawn offscreen on the board.

  • text_churn: ten captures in one run, each matching one offscreen frame with no pixel off by more than one level in 255
  • counter: driven by Tab and Enter written to the keyboard's event node, counts to 3, captured in a ripple and at rest

The capture is the buffer the CRTC is showing, not the panel, and no terminal switch was tried; both docs say so.

- m4-status: ten captures of text_churn with frames not waited for, each one of the run's frames drawn offscreen on the board to one level in 255; counter driven through the keyboard's event node, captured in a ripple and at rest
- m4-exit: the open item says what was read back and what was not, the panel itself and a terminal switch
- review: docs only; the capture is the CRTC's buffer, and says so

Signed-off-by: Joel Winarske <joel.winarske@linux.com>
@jwinarske
jwinarske merged commit 91ae127 into main Nov 18, 2026
11 checks passed
@jwinarske
jwinarske deleted the the-display-read-back-on-the-visionfive-2 branch November 18, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant