I have a bad feeling about swiping the CRT I2C. It kind of leaves
a needless landmine for video driver authors who would prefer to
unify their code (XO and non-XO hardware) as much as possible.
Suppose a video driver attempts E-DDC. Is it going to confuse
some non-compliant I2C device or actually h
A question about I2C bus assignments on Gen 1.5 has come up.
We have three I2C buses available: SMB, VPD, and CRT.
We have four potential devices that want an I2C interface:
1. the clock generator (addr 0xD2/D3)
2. the DCON (has had problems w. I2C communication in the past)
3. the Camera (addr
