From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2131 invoked by alias); 6 Jan 2008 21:02:32 -0000 Received: (qmail 2064 invoked by uid 22791); 6 Jan 2008 21:02:19 -0000 X-Spam-Check-By: sourceware.org Received: from ctb-mesg-1-1.saix.net (HELO ctb-mesg-1-1.saix.net) (196.25.240.79) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 06 Jan 2008 21:01:57 +0000 Received: from jan03 (unknown [41.246.105.75]) by ctb-mesg-1-1.saix.net (Postfix) with SMTP id 91EC2CE45 for ; Sun, 6 Jan 2008 23:01:53 +0200 (SAST) Message-ID: <009701c850a7$5ceb63b0$c800a8c0@jan03> From: "Jan Jacobs" To: Date: Sun, 06 Jan 2008 21:02:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook Express 6.00.2900.3138 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: [ECOS] AT91SAM and I2C X-SW-Source: 2008-01/txt/msg00006.txt.bz2 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? 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 must state that I am new to ecos and the AT91SAM7x, so if I ask stupid questions humour me :) Cheers Jan -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss