From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fed1rmmtao05.cox.net (fed1rmmtao05.cox.net [68.230.241.34]) by ozlabs.org (Postfix) with ESMTP id 5CD322BC0F for ; Thu, 14 Oct 2004 07:18:50 +1000 (EST) Date: Wed, 13 Oct 2004 14:18:47 -0700 From: Matt Porter To: "VanBaren, Gerald (AGRE)" , "Robert P. J. Day" , Embedded PPC Linux list Message-ID: <20041013141847.D21277@home.com> References: <065ACD8E84315E4394C835E398C8D5EB865270@COSSMGMBX02.email.corp.tld> <20041013132613.A21277@home.com> <20041013211428.GB28349@gate.ebshome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20041013211428.GB28349@gate.ebshome.net>; from ebs@ebshome.net on Wed, Oct 13, 2004 at 02:14:28PM -0700 Cc: Subject: Re: "I2C" versus "IIC" List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Oct 13, 2004 at 02:14:28PM -0700, Eugene Surovegin wrote: > On Wed, Oct 13, 2004 at 01:26:13PM -0700, Matt Porter wrote: > > On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote: > > > 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. > > > > It's been related to me several times that this is the reason why > > most implementers refer to their interface/bus as IIC in > > documentation. > > Yeah, the most "extreme" variant being "two-wire serial interface", > without even mentioning I2C or IIC. I see "two-wire serial interface" on a lot of devices. That one is awfully popular. :) > You need some familiarity with bus protocol to figure out that this is > really I2C :). Yup. -Matt