Guess the NuBus card
- Thread starter slomacuser
- Start date
Yes interesting resolution I tought it would be something like 1152 x 870
The memory dump shows the framebuffer at offset 0 which has a B&W checkerboard pattern that is 128 bytes wide = 1024 pixels, 769 lines.
The decldata is 4K at offset 0x30000 (192K)
The decldata uses 2 of the 4 byte lanes so its actual data is 2K.
The decldata repeats 16 times until offset 256K where the framebuffer exists again.
This 256K window repeats 64 times in the 16 MB slot window except for some small differences.
- They may be scan line counters or stuff like that which changes rapidly - or maybe they're just floating values.
The corners of the framebuffer show square instead of rounded corners? Your photo does not show the corners of the display.
Attached the SlotsParse output. It's a very small amount of data. Just one vendor info, one driver, and one display resolution.
The decldata is 4K at offset 0x30000 (192K)
The decldata uses 2 of the 4 byte lanes so its actual data is 2K.
The decldata repeats 16 times until offset 256K where the framebuffer exists again.
This 256K window repeats 64 times in the 16 MB slot window except for some small differences.
- They may be scan line counters or stuff like that which changes rapidly - or maybe they're just floating values.
The corners of the framebuffer show square instead of rounded corners? Your photo does not show the corners of the display.
Attached the SlotsParse output. It's a very small amount of data. Just one vendor info, one driver, and one display resolution.
It's a 1bit card - I'd suspect the photo is of the output from a different source.
