B+ disable ID_EEPROM

[Richard-TX]

I have an existing application that uses both I2C buses on a model B. Since the B+ has redefined the other I2C bus, this is an issue. I understand the whole HAT idea, but this hardware application could not possibly be a HAT.

Since my application has no provision for an EEPROM nor would it benefit from it, is there some way that I can reconfigure the firmare/kernel so that the ID_EEPROM I2C bus is converted to a general purpose I2C bus?

If I have to, I am willing to rebuild the Linux kernel/firmware so that I regain the use of the 2nd I2C bus. I just need some help or guidance in this regard.

Thanks

[ShiftPlusOne]

I think it was decided that there will be a 'classic mode' config option, but you should be able to just add bcm2708.vc_i2c_override=1 to cmdline.txt and use it like you normally would. The firmware will check for an attached eeprom first, but that shouldn't affect your device.

[Richard-TX]

Well, that certainly helps. Is there any documentation or source tree that I can look at regarding the scan at boot for the eeprom?

Depending on what the reading of the EEPROM does, It may be possible that the addition of an EEPROM could help.

[ShiftPlusOne]

I don't think that's a thing that happens yet.

[Richard-TX]

hmmm. I guess I will have to wait and see what, if anything, will happen in the future. Thanks for the info.

richard