When HN users recommended it
1 HN user recommended this in 2022, in one comment.
20072026
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
1 HN user recommended this in 2022, in one comment.
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
Seems you have separate RGBHV on the monitor side. See
[·] https://en.wikipedia.org/wiki/Component_video
To get that from your PI's HDMI you'd need something like
[·] https://www.amazon.com/Portta-3-5mm-Audio-Converter-support/...
and then something like this
[·] https://www.monoprice.com/product?p_id=562
Then you'd construct a custom Modeline like described in
[·] http://howto-pages.org/ModeLines/ &
[·] https://tldp.org/HOWTO/Framebuffer-HOWTO/
for I guess 1280x1024@60Hz? Maybe you don't even need to, because that is a common VESA resolution(SXGA) which should be provided anyways? So by setting this as fixed resolution by whichever means at startup, it could work. Maybe there are a even a few different ones to choose from, with slightly different timings, polarities. Or you could change that at the monitor itself. The second pdf from your link suggests that. I mean if the picture is rolling slowly up or down, or something like that.
I don't use PIs, so I don't know how the firmware works, which modes it supports, and how this all interacts with that videocore-thing, nowadays.
But that you'd need the converter gadgets and cable from there is obvious.