[U-Boot-Users] Using a second I2C interface
r-woodruff2 at ti.com
Tue May 16 15:27:01 CEST 2006
I've can post a diff to some code we use to do this. I didn't look at
it to closely, but it has worked well. Select a device, then standard
commands go to it.
> A clean design should allow to switch I2C busses usign a command;
> additionally, I think we should try to stay backward-compatible with
> the existing code. Eventually this is not too difficult: similar to
> the "ide" or "usb" commands we could create a new command "i2c
> device" which takes as argument the number of the I2C bus which shal
> become the current (= active) bus. Then all existing I2C related
> commands can be left unchanged (and "i2c device" without arguments
> should of course print the ID of the current bus).
> In parallel, existing I2C commands could be changed to migrate to a
> new "i2c" group of commands: "imd" would become "i2c md", "imw"
> becomes "i2c mw", "iprobe" becomes "i2c probe", etc. For some (long)
> transition period old and new commands could be provided in parallel
> (at least optionally). Later, the old syntax could be dropped.
> Best regards,
> Wolfgang Denk
> Software Engineering: Embedded and Realtime Systems, Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Ever try. Ever fail. No matter. Try again. Fail again. Fail better.
> -- S. Beckett
> Using Tomcat but need to do more? Need to support web services,
> Get stuff done quickly with pre-integrated technology to make your job
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
More information about the U-Boot