From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19310 invoked by alias); 6 Jan 2008 21:28:24 -0000 Received: (qmail 19301 invoked by uid 22791); 6 Jan 2008 21:28:24 -0000 X-Spam-Check-By: sourceware.org Received: from netic.com (HELO netic.com) (208.131.130.247) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 06 Jan 2008 21:28:05 +0000 Received: from piii550 (60-242-91-36.static.tpgi.com.au [60.242.91.36]) by netic.com (8.12.11.20060308/8.12.11) with SMTP id m06LS1fC031509; Sun, 6 Jan 2008 14:28:02 -0700 From: "Laurie Gellatly" To: "Andrew Lunn" , "Jan Jacobs" Cc: Date: Sun, 06 Jan 2008 21:28:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20080106211211.GU3023@lunn.ch> X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] AT91SAM and I2C X-SW-Source: 2008-01/txt/msg00008.txt.bz2 -----Original Message----- From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Andrew Lunn Sent: Monday, 7 January 2008 8:12 AM To: Jan Jacobs Cc: ecos-discuss@ecos.sourceware.org Subject: Re: [ECOS] AT91SAM and I2C On Sun, Jan 06, 2008 at 11:01:51PM +0200, Jan Jacobs wrote: > Hi All, > > I need an I2C (TWI) driver for the AT91SAM7X. I have started doing > something, but want to find out if somebody has done one or has any advice? >I think somebody is working on such a driver. It was mentioned last >month. Take a look in the mail archive. > Secondly, I think there might be a flaw with the I2C IO package. > If the device you communication to does not use internal addressing (RTC, > Sensor, etc) then the I2C IO API works. > If the device requires internal addressing (EEPROM) I do not see how that > gets conveyed via the I2C IO API? >I don't really follow. Do you want to make it look like the EEPROM is >memory mapped? Jan, When you talk to a EEPROM then part of the I2C message is a command followed by the memory address then the data is exchanged all across teh I2C bus. You should see this in the Datasheet. (apologies for duplicate message Andrew). ...Laurie:{) -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss