From: "Christophe Coutand" <ccoutand@stmi.com>
To: "Sergei Gavrikov" <sergei.gavrikov@gmail.com>,
"John Dallaway" <john@dallaway.org.uk>
Cc: <ecos-patches@ecos.sourceware.org>
Subject: RE: AT91 ADC support
Date: Thu, 27 May 2010 14:16:00 -0000 [thread overview]
Message-ID: <D6050C555CC56940A7AF32652283027602EAC8A5@mail2.STMIRV01.COM> (raw)
In-Reply-To: <alpine.DEB.2.00.1005271643220.28208@sg-desktop.local>
Hi,
I originally made it for AT91SAM7S and AT91SAM7X but at the last minute
I saw that Atmel was using the same ADC for AT91M55800A, AT91SAM9X etc..
so I renamed it to AT91. I thought this would be more future proof.
It remains true that I have not compiled / tested it for anything else
than AT91SAM7S / AT91SAM7X.
I can specify which AT91 supports it and update the var_io.h when
definition are missing.
Regards,
Christophe
-----Original Message-----
From: Sergei Gavrikov [mailto:sergei.gavrikov@gmail.com]
Sent: 27. mai 2010 15:52
To: John Dallaway
Cc: Christophe Coutand; Sergei Gavrikov;
ecos-patches@ecos.sourceware.org
Subject: Re: AT91 ADC support
On Thu, 27 May 2010, John Dallaway wrote:
> Hi Christophe and Sergei
>
> Christophe, is your ADC driver applicable to all AT91 parts with
on-chip
> ADC in theory?
>
> Sergei, if so, we should add the new package to all the relevant
target
> records in ecos.db: at91sam7sek, at91sam7xek, sam7ex256, eb55, phycore
Hi John,
First I tried to build the driver for AT91 'phycore' target and it was
not possible to build it because in AT91 var_io.h some ADC defines
included by a condition:
...
#elif defined (CYGHWR_HAL_ARM_AT91SAM7)
#include <pkgconf/hal_arm_at91sam7.h>
...
So, it seemed for me that's AT91SAM7 related driver. I have no
experience with AT91 CPU set. May be Christophe enlighten us?
Thanks for your point. It seems I must dive in AT91 datasheets.
Sergei
> John Dallaway
> eCos maintainer
>
next prev parent reply other threads:[~2010-05-27 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 9:40 Christophe Coutand
2010-05-27 13:42 ` John Dallaway
2010-05-27 13:52 ` Sergei Gavrikov
2010-05-27 14:16 ` Christophe Coutand [this message]
2010-05-27 14:47 ` John Dallaway
2010-05-27 15:44 ` Christophe Coutand
2010-05-27 16:08 ` John Dallaway
2010-05-27 16:37 ` Kurt Siedenburg
2010-05-27 16:37 ` Sergei Gavrikov
2010-05-27 19:49 ` Christophe Coutand
2010-05-27 21:44 ` Sergei Gavrikov
2010-05-29 10:24 ` Sergei Gavrikov
2010-05-29 13:10 ` John Dallaway
2010-05-30 10:34 ` Sergei Gavrikov
2010-05-30 12:40 ` Christophe Coutand
2010-05-30 13:46 ` Sergei Gavrikov
2011-02-22 11:33 ` John Dallaway
2010-05-27 21:37 ` Christophe Coutand
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=D6050C555CC56940A7AF32652283027602EAC8A5@mail2.STMIRV01.COM \
--to=ccoutand@stmi.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=sergei.gavrikov@gmail.com \
/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).