From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "Andrew Lunn" <andrew@lunn.ch>, "Jan Jacobs" <hpjcon@mweb.co.za>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] AT91SAM and I2C
Date: Sun, 06 Jan 2008 21:28:00 -0000 [thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJMEPIMHAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <20080106211211.GU3023@lunn.ch>
-----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
next prev parent reply other threads:[~2008-01-06 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 21:02 Jan Jacobs
2008-01-06 21:12 ` Andrew Lunn
2008-01-06 21:28 ` Laurie Gellatly [this message]
2008-01-07 9:39 ` Tom Deconinck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OBEELMDOHGDFDEMJCJCJMEPIMHAA.laurie.gellatly@netic.com \
--to=laurie.gellatly@netic.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=hpjcon@mweb.co.za \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).