|
|
|
|
|
|
by 10000truths
1029 days ago
|
|
|
Mere speculation on my part, since I have no familiarity with the HDMI or DisplayPort protocols: 1. Windows/macOS might have a "quirks table" that hardcodes fixes for spec-violating devices. 2. Windows/macOS might ignore some reported EDID values and derive their own when they determine that the display behaves differently from what is reported (e.g. by recording response packet timings). |
|
|
Even modern packetized display interfaces like DisplayPort are still fundamentally a one-way firehose for the pixel data. There's no provision for acknowledging or retransmitting data packets, and forward error correction is optional. The bidirectional sideband channels used for stuff like EDID are not timing-sensitive like the pixel data stream.