* [ECOS] Re: AT91RM9200-EK Port
@ 2005-06-29 6:20 stewart hamilton
2005-06-29 8:06 ` John Eigelaar
0 siblings, 1 reply; 3+ messages in thread
From: stewart hamilton @ 2005-06-29 6:20 UTC (permalink / raw)
To: ecos-discuss
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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ECOS] Re: AT91RM9200-EK Port
2005-06-29 6:20 [ECOS] Re: AT91RM9200-EK Port stewart hamilton
@ 2005-06-29 8:06 ` John Eigelaar
2005-06-29 19:50 ` Andrew Lunn
0 siblings, 1 reply; 3+ messages in thread
From: John Eigelaar @ 2005-06-29 8:06 UTC (permalink / raw)
To: ecos-discuss
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.
Please keep in touch, might be nice to share the experience.
John
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ECOS] Re: AT91RM9200-EK Port
2005-06-29 8:06 ` John Eigelaar
@ 2005-06-29 19:50 ` Andrew Lunn
0 siblings, 0 replies; 3+ messages in thread
From: Andrew Lunn @ 2005-06-29 19:50 UTC (permalink / raw)
To: John Eigelaar; +Cc: ecos-discuss
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-29 19:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-29 6:20 [ECOS] Re: AT91RM9200-EK Port stewart hamilton
2005-06-29 8:06 ` John Eigelaar
2005-06-29 19:50 ` Andrew Lunn
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).