public inbox for
 help / color / mirror / Atom feed
From: John Dallaway <>
To: Richard Rauch <>
Cc: eCos development list <>
Subject: Re: Port to Atmel ARM9 Microcontroller SAM9G4
Date: Thu, 04 Mar 2010 08:36:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <AD91E7C0F6F84C248A600E00067869A5@DESKTOPITRGMBH>

Hi Richard

> I want to announce a development project. It is an eCos port to the Atmel's
> ARM9 microcontroller family, in particular a port to the SAM9G45.
> It is planned to contribute the result of the project to the eCos
> repository.
> I would be very glad to get some response, whether the planned port is of
> common interest!

A port to the AT91SAM9G45 is undoubtedly of value to the eCos community.
Thank you for announcing your plans early. This helps other members of
the community in their own planning.

We do need to be careful about merge work here. There is a patch from
Evgeniy Dushistov which provides support for the AT91SAM9236-EK board
and also re-organises the ARM7/ARM9 abstraction:

I would say that it makes sense to base any further work off a
repository with this patch applied. However, the patch is still subject
to review.

Would you like the maintainers to register your project? Details at:

John Dallaway
eCos maintainer

  parent reply	other threads:[~2010-03-04  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 21:12 Richard Rauch
2010-03-04  7:18 ` Jürgen Lambrecht
2010-03-04  9:38   ` AW: Port to Atmel ARM9 Microcontroller SAM9G45 Richard Rauch
2010-03-07 17:33     ` Stanislav Meduna
2011-01-17 11:57       ` Mapping of ARM Architecture to Repository Richard Rauch
2011-01-17 16:22         ` John Dallaway
2010-03-04  8:36 ` John Dallaway [this message]
2010-03-04  9:44   ` AW: Port to Atmel ARM9 Microcontroller SAM9G45 Richard Rauch

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).