From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fed1rmmtao01.cox.net (fed1rmmtao01.cox.net [68.230.241.38]) by ozlabs.org (Postfix) with ESMTP id 7AAC52BDA0 for ; Thu, 14 Oct 2004 06:26:16 +1000 (EST) Date: Wed, 13 Oct 2004 13:26:13 -0700 From: Matt Porter To: "VanBaren, Gerald (AGRE)" Message-ID: <20041013132613.A21277@home.com> References: <065ACD8E84315E4394C835E398C8D5EB865270@COSSMGMBX02.email.corp.tld> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <065ACD8E84315E4394C835E398C8D5EB865270@COSSMGMBX02.email.corp.tld>; from Gerald.VanBaren@smiths-aerospace.com on Wed, Oct 13, 2004 at 02:18:03PM -0600 Cc: Embedded PPC Linux list 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: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. -Matt