From: Andrew Lunn <andrew.lunn@ascom.ch>
To: david.barrass@geo-track.co.uk
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: eCos for AVR32
Date: Tue, 29 Aug 2006 17:05:00 -0000 [thread overview]
Message-ID: <20060829170535.GP27259@donkey.ma.tech.ascom.ch> (raw)
In-Reply-To: <Vdbpe5k6.1156870826.7636130.david.barrass@geo-track.co.uk>
On Tue, Aug 29, 2006 at 05:00:26PM +0000, david.barrass@geo-track.co.uk wrote:
> Hi,
>
> I am currently playing with a development kit for the Atmel AVR32
> processor which is running Linux. I was wondering if you know whether
> anyone is working on a port of eCos to this architecture.
Not that i know of. It might be worth asking on the ecos-discuss
mailing list.
> If not, I
> would be interested in doing the port. Where do the porting/CVS useage
> guidelines live?
There is a HAL porting guide as part of the main reference manual:
http://ecos.sourceware.org/docs-latest/ref/hal-porting-guide.html
And there is information about anoncvs access at:
http://ecos.sourceware.org/anoncvs.html
Andrew
prev parent reply other threads:[~2006-08-29 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 17:00 david.barrass
2006-08-29 17:05 ` 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=20060829170535.GP27259@donkey.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=david.barrass@geo-track.co.uk \
--cc=ecos-maintainers@ecos.sourceware.org \
/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).