From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.237]) by ozlabs.org (Postfix) with ESMTP id 71ED2DDE29 for ; Thu, 15 Nov 2007 06:26:22 +1100 (EST) Received: by nz-out-0506.google.com with SMTP id i1so263750nzh for ; Wed, 14 Nov 2007 11:26:20 -0800 (PST) Message-ID: <9e4733910711141126k1bb896caoe40fb7204237fa85@mail.gmail.com> Date: Wed, 14 Nov 2007 14:26:19 -0500 From: "Jon Smirl" To: "Scott Wood" Subject: Re: I2C on mpc8248 / device tree In-Reply-To: <20071114175630.GA4547@loki.buserror.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <9e4733910711131556r23a38780q39baf15d85c0bd85@mail.gmail.com> <9AADA2CE-A7F0-4C88-BFCF-08D6C8DC09E0@kernel.crashing.org> <20071114175630.GA4547@loki.buserror.net> Cc: linuxppc-dev@ozlabs.org, Alan Bennett List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 11/14/07, Scott Wood wrote: > On Wed, Nov 14, 2007 at 10:49:13AM -0700, Alan Bennett wrote: > > ERk. > > So if I needed to read values from four i2c devices (raw access would be > > fine) and I need to get this working in a few days, how would you suggest I > > proceed? Kernel = 2.6.23+. > > > > Do I need to start from scratch? > > > > Start by using Jon's patch (or are the 5200 i2c and the cpm2 i2c > > completely incompatible?) > > Start with the cpm i2c driver that Jochen Friedrich posted to > linuxppc-embedded. Sorry about the confusion I thought the mpc82xx chips had the same i2c core as the mpc52xx but I was not correct. > > -Scott > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > -- Jon Smirl jonsmirl@gmail.com