> -----Original Message----- > From: linuxppc-embedded-bounces at ozlabs.org > [mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of > Eugene Surovegin > Sent: Wednesday, October 13, 2004 3:34 PM > To: Robert P. J. Day > Cc: Embedded PPC Linux list > Subject: Re: "I2C" versus "IIC" > > On Wed, Oct 13, 2004 at 02:26:23PM -0400, Robert P. J. Day wrote: > > > > i was just about to rename some of my variables and macros to be > > consistent with what i *thought* was the standard nomenclature of > > "IIC" as opposed to "I2C". just checked include/asm-ppc, > and grepped > > for case-insensitive instances of both strings ... oh, god. > there's > > really no preferred usage, is there? > > Philips' documentation uses I2C, not IIC, so I guess this is > _official_ name of the _bus_. > > Some vendors (like IBM in their 4xx parts) use IIC to name > I2C _interface_ to distinguish it from I2C _bus_ (they > specifically mention this in the chip manual). > > For example, in the corresponding 4xx driver I used "iic" > because it was written for IBM IIC _interface_. > > -- > Eugene.
Just to mess with your minds... I2C is a trademark of Philips Electronics N.V. so that is probably not the best choice from a legalistic point of view. gvb ****************************************** The following messages are brought to you by the Lawyers' League of IdioSpeak: ****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************
