Hi Wolfram, On Tue, Sep 8, 2015 at 7:53 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: > >> Yes, now a HD-ready TV is hooked up. It should give you something over >> EDID. Let me know when you're done and I'll move things back. > > 'No EDID data' says bootlog. Also, all 0 when reading that i2c client > address afterwards. I don't see or sense anything suspicious with the > I2C transfers itself from remote. Did you use the DRM/KMS modetest program to display stuff on the HDMI monitor? To trigger the error case you need to a couple of steps - just booting the kernel does not trigger things. The EDID provided by the HDMI monitor is read out by the HDMI encoder chip that in turn is connected over I2C to the SoC. I believe the connection between the HDMI monitor and the HDMI encoder chip works ok, but the bits between the HDMI encoder chip and the I2C master on the SoCs may need some more attention. > And could you maybe install a local TFTP server on your next images? :) This was done by Geert earlier. Lets discuss details over IRC! Thanks, / magnus -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
