Follow

For a legacy structure like the Intel GDT that has grown over many decades, or for ease of hardware implementation like the RISC-V it makes sense. But for a purely software parsed structure like the HDMI EDID, why would you do this?

@th Hm..What's your complaint? I don't understand the problem. :D

@th needless bitpinching in design leads to hours wasted in debugging the implementation, but the designers must feel really clever!

@th well, at least it's documented. (below is from the RF transceiver I'm working with)

@th Everything about HDMI makes more sense once you understand it as first a *restraint*, and only second as a means of moving images from point A to point B.

HDMI's mission is, "Under no circumstances display something unpermitted; all other considerations secondary; crew expendable."

The EDID thing probably falls out of that on the basis of: the kind of people who would willingly work on the design of such a system are terrible engineers, technically and ethically compromised.

@jwz @th It’s much simpler: HDMI is built on the ruins of VGA.

@frumble @jwz @th

I mean, those bit mingling things look like a 10-bit extension of a pre-existing 8-bit thing, although that doesn't explain why the LSBs come first.

@jwz @th wow id assumed hdcp was tacked onto hdmi not its original goal

@glassresistor @th HDCP actually predates HDMI since it was a party of DVI as well. But really HDCP is the purpose of HDMI, they are inseparable.

@jwz @th the better solution is called SDI (all versions of it)
Sign in to participate in the conversation
(void *) social site

(void*)