From: Gary Thomas <gary@mlbassoc.com>
To: Evgeniy Dushistov <dushistov@mail.ru>
Cc: John Dallaway <john@dallaway.org.uk>,
Daniel Helgason <dhelgason@shaw.ca>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>,
Martin Laabs <martin.laabs@mailbox.tu-dresden.de>
Subject: Re: Getting Atmel AT91SAM9 into eCos
Date: Tue, 23 Feb 2010 16:53:00 -0000 [thread overview]
Message-ID: <4B840808.1090208@mlbassoc.com> (raw)
In-Reply-To: <20100223100104.GA15310@rain>
On 02/23/2010 03:01 AM, Evgeniy Dushistov wrote:
> On Tue, Feb 23, 2010 at 09:26:15AM +0000, John Dallaway wrote:
>> 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.
>>
>
> Actually, I and Filip Navara implemented AT91SAM7X and at91sam9263
> support for qemu, one of the most recent version can be found here:
> git://github.com/Dushistov/qemu_at91sam9263.git
> It can run linux, freertos, ecos.
>
> So if there is interest, I can create binaries of qemu for linux OS,
> so maintainers who have sam7 hardware, but have no sam9, or
> vice versa, or completly have no development boards can run
> and test eCos.
How do you configure Qemu to run eCos on these platforms?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-02-23 16:53 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
2010-02-23 9:58 ` Evgeniy Dushistov
2010-02-23 16:53 ` Gary Thomas [this message]
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=4B840808.1090208@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dhelgason@shaw.ca \
--cc=dushistov@mail.ru \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--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).