summaryrefslogtreecommitdiffstats
path: root/wiki/FAQ.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-08 18:30:14 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-08 18:30:14 -0500
commitdf332e75fc70f81430b146ccb23481f80b89e8d3 (patch)
tree9c9b41adb256742c5720ca474e90a344df2b6a13 /wiki/FAQ.md
parent6cd260b87557e881af1e47f82ff3f0df79d30e44 (diff)
downloadopen-iov-df332e75fc70f81430b146ccb23481f80b89e8d3.tar.gz
open-iov-df332e75fc70f81430b146ccb23481f80b89e8d3.zip
vgsp-disp: map class 0xc57b to its real control window (window-imm)
The header labelled 0xc57b CURSOR and mapped it to the cursor-PIO block at 0x6d8000+n*0x1000, but 0xc57b is the immediate-mode window class whose control window is 0x690000+(n+32)*0x1000 = 0x6d0000+n*0x1000 (0xc57a is the PIO cursor channel, valid=0). The engine therefore polled the wrong window for every 0xc57b channel: their PUT was never seen, no UPDATE ever completed, and r1638's GZDoom-triggered mode set left X spinning in an RM ioctl after the window-imm flip. Rename the constants (WINDOW_IMM 0xc57b, CURSOR_PIO 0xc57a) and return the correct control offsets; cursor-PIO keeps 0x6d8000+n*0x1000.
Diffstat (limited to 'wiki/FAQ.md')
0 files changed, 0 insertions, 0 deletions