From: Andrew Lunn <andrew@lunn.ch>
To: John Eigelaar <jeigelaar@yahoo.co.uk>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: AT91RM9200-EK Port
Date: Wed, 29 Jun 2005 19:50:00 -0000 [thread overview]
Message-ID: <20050629194949.GD8479@lunn.ch> (raw)
In-Reply-To: <pan.2005.06.29.07.53.50.90555@yahoo.co.uk>
On Wed, Jun 29, 2005 at 09:53:51AM +0200, John Eigelaar wrote:
> On Wed, 29 Jun 2005 16:19:59 +1000, stewart hamilton wrote:
>
> > Hi John
> >
> > I know its early days yet. But as we are just about to embark on an
> > evaluation of ecos on the
> > AT91RM9200-EK board and have no previous ecos experience, was wondering how
> > your port to this board is going
> >
> > Regards
> > Stewart
>
> Stewart,
>
> I haven't actually started yet. I have spent the last two days inspecting
> the ARM HAL structure. The AT91RM9200 present a bit of a conundrum - it is
> a an at91 part as well as an arm9 part. At this point I am not sure
> whether to start it as an at91 variant and use the stuff from the arm9 HAL
> as well, or start with an arm9 platfrom and just use the at91 variants a e
> reference. At this point in time I am leaning towards the arm9 starting
> point just because stuff like cahces and MMU controllers has already been
> used in these platforms.
I beleave eCosCentric have already a port for the AT91RM9200. Maybe
they could share there experiance. Did they use the at91 var or the
arm9 var?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-06-29 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 6:20 stewart hamilton
2005-06-29 8:06 ` John Eigelaar
2005-06-29 19:50 ` Andrew Lunn [this message]
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=20050629194949.GD8479@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=jeigelaar@yahoo.co.uk \
/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).