The most interaction I've personally had with I2C was poking my monitor to determine the layout necessary to get DDC/CI control working. Nothing was terribly well documented, but at the protocol...
The most interaction I've personally had with I2C was poking my monitor to determine the layout necessary to get DDC/CI control working. Nothing was terribly well documented, but at the protocol level at least, everything seemed surprisingly well supported, and I was able to figure out which bytes mapped to which display features without too much difficulty.
However, I never would've guessed that it might be possible to use I2C to overwrite the EDID information like that. I don't know why that wouldn't be made read only, it seems like it'd be pretty easy to render the device unusable and maybe even bricked by poking that stuff the wrong way.
The most interaction I've personally had with I2C was poking my monitor to determine the layout necessary to get DDC/CI control working. Nothing was terribly well documented, but at the protocol level at least, everything seemed surprisingly well supported, and I was able to figure out which bytes mapped to which display features without too much difficulty.
However, I never would've guessed that it might be possible to use I2C to overwrite the EDID information like that. I don't know why that wouldn't be made read only, it seems like it'd be pretty easy to render the device unusable and maybe even bricked by poking that stuff the wrong way.