From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id E6BAADDE21 for ; Thu, 15 Nov 2007 07:21:56 +1100 (EST) In-Reply-To: <9e4733910711141126k1bb896caoe40fb7204237fa85@mail.gmail.com> References: <9e4733910711131556r23a38780q39baf15d85c0bd85@mail.gmail.com> <9AADA2CE-A7F0-4C88-BFCF-08D6C8DC09E0@kernel.crashing.org> <20071114175630.GA4547@loki.buserror.net> <9e4733910711141126k1bb896caoe40fb7204237fa85@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <679CE66E-DA80-45B6-BC44-DBC23A00B4A4@kernel.crashing.org> From: Kumar Gala Subject: Re: I2C on mpc8248 / device tree Date: Wed, 14 Nov 2007 14:21:34 -0600 To: Jon Smirl 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 Nov 14, 2007, at 1:26 PM, Jon Smirl wrote: > 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. the 8241 and 8245 have it, but they are the only ones. - k