Repository navigation
odyssey: native 2560x1440 (QHD) desktop on VPro/Odyssey - #782
Draft
sebastjan-rijavec wants to merge 1 commit into
Draft
sebastjan-rijavec wants to merge 1 commit into
sebastjan-rijavec wants to merge 1 commit into
Conversation
Model a 2560x1440 scanout on the Odyssey (VPro) board and widen the shared host framebuffer so the V12 drives a native QHD desktop matching a 1440p monitor. The tallest format IRIX ships is 1920x1200, so the guest also needs a custom 2560x1440 video timing (built on-box with vfc: 50 Hz / ~200 MHz, which fits VPro_Board.def's 202.6 MHz ceiling; 60 Hz is physically impossible there). Board / scanout: - Add ODSY_MAX_WIDTH/HEIGHT (2560x1440), distinct from the 1280x1024 boot/reset size. The display FIFO clamps the guest's channel request to this max; the rasterizer's poly_marks plane and clip/fill extents are sized to it. - Update the display-channel test: 1920x1200 and 2560x1440 present at full size; a larger request is clamped per axis. Host display: - Raise disp::FB_STRIDE 2048 -> 2560 and route the shared GL present path through it: the GlCompositor output texture, the prebuilt-frame upload and readback, the status-bar texture/buffer, save_screenshot, and the screen quad UVs. Odyssey and O2 copy into the shared screen via FB_STRIDE and so track it automatically. Known limitation: Newport (ng1/*) and GR2 still index their own buffers with a literal 2048 and are deliberately NOT updated here; with the wider stride their display is sheared and several of their unit tests fail. The machines that use the wide path -- Tezro (Odyssey) and O2 (o2gfx) -- are verified rendering a clean 2560x1440 desktop. Co-Authored-By: Mildroid <>
Owner
|
add stride reporting to common layer and incorporate sam's display buffer reallocation schemes? we can be more flexible there and reallocate on mode change? #781 |
Author
|
we can and we should get vfo files i reckon. Yes to the rest. |
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.
What
Lets the Odyssey (VPro / V12) board drive a native 2560×1440 IRIX desktop that fills a 1440p monitor, instead of being capped at 2048 wide.
Verified end-to-end on Tezro (IP35, V12) running IRIX 6.5.22:
gfxinfo:Managed 2560x1440,Video Output 2560x1440_50vpro mem:scan-out (PB&J) 2560x1440, stride 160 tilesBecause the tallest video format IRIX ships is 1920×1200, the guest also needs a custom 2560×1440 timing, built on-box with
vfc(50 Hz / ~200 MHz — underVPro_Board.def's 202.6 MHz ceiling; 60 Hz is physically impossible there) and selected withsetmon.Changes
Board / scanout
ODSY_MAX_WIDTH/HEIGHT(2560×1440), distinct from the 1280×1024 boot/reset size. The display FIFO clamps the guest's channel request to this max; the rasterizer'spoly_marksplane and clip/fill extents are sized to it.Host display
disp::FB_STRIDE2048 → 2560 and route the shared GL present path through it: theGlCompositoroutput texture, the prebuilt-frame upload and readback, the status-bar texture/buffer,save_screenshot, and the screen-quad UVs. Odyssey and O2 copy into the shared screen viaFB_STRIDEand track it automatically.Newport (
ng1/*) and GR2 still index their own buffers with a literal2048and are deliberately not updated here. With the wider shared stride their display is sheared and several of their unit tests fail, socargo test --workspaceis red. Only the machines that use the wide path — Tezro (Odyssey) and O2 (o2gfx) — are verified.A merge-ready version would either thread a per-screen stride through
Rex3Screen(Newport stays 2048, Odyssey/O2 go 2560) or convert Newport/GR2's literals (incl. the REX3 JIT stride constant and the corpus tests) toFB_STRIDE. Opening as a draft to discuss which direction is preferred before doing that wider sweep.