From: John Dallaway <john@dallaway.org.uk>
To: Daniel Helgason <dhelgason@shaw.ca>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>,
Evgeniy Dushistov <dushistov@mail.ru>
Cc: Martin Laabs <martin.laabs@mailbox.tu-dresden.de>
Subject: Re: Getting Atmel AT91SAM9 into eCos
Date: Tue, 23 Feb 2010 09:26:00 -0000 [thread overview]
Message-ID: <4B839F37.50904@dallaway.org.uk> (raw)
In-Reply-To: <1266877649.3024.105.camel@localhost.localdomain>
Hi Daniel, Evgeniy and eCos maintainers
Daniel Helgason wrote:
> I have seen many messages on the eCos mailing lists about getting
> AT91SAM9 support into eCos. I'm writing directly to you in hopes of
> getting some movement on this. I know this is off the mailing list but I
> wanted to get initial input directly from people whose opinions I have
> come to respect before I add yet another message to the mailing list
> about this subject.
[ snip ]
> If there was ever a time to consider pushing the AT91SAM9 devices into
> eCos, this could be it! I am asking you for your thoughts on how to
> proceed from here. Thanks!
I am not an expert on ARM7/ARM9 differences but there are several eCos
maintainers who have experience with multiple ARM variants and are well
positioned to review the AT91SAM9 patch. I do not think motivation
should be an issue here. We all wish to see eCos move forward and
AT91SAM9 support is clearly very good for the project.
My main concern is that we don't break eCos support for older ARM
platforms in the process of improving the hardware abstraction for
future platform ports.
Is there an eCos maintainer with the necessary ARM expertise who can
volunteer for the review of this contribution? Ref:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
John Dallaway
eCos maintainer
next parent reply other threads:[~2010-02-23 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1266877649.3024.105.camel@localhost.localdomain>
2010-02-23 9:26 ` John Dallaway [this message]
2010-02-23 9:58 ` Evgeniy Dushistov
2010-02-23 16:53 ` Gary Thomas
2010-02-23 17:50 ` Evgeniy Dushistov
2010-03-08 13:11 ` John Dallaway
2010-03-08 13:54 ` Jonathan Larmour
2010-03-08 15:59 ` John Dallaway
2010-03-09 2:00 ` Sergei Gavrikov
2010-03-09 16:30 ` Jonathan Larmour
2010-03-09 16:25 ` Jonathan Larmour
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=4B839F37.50904@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=dhelgason@shaw.ca \
--cc=dushistov@mail.ru \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=martin.laabs@mailbox.tu-dresden.de \
/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).