From: "Andy Voelkel" <andy@bushtaxi.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] porting ECOS to an Atmel AT91RM9200 eval board
Date: Sat, 07 May 2005 02:36:00 -0000 [thread overview]
Message-ID: <E1DUCt7-0000IV-00@mail.aemf.org> (raw)
In-Reply-To: <1115423292.31725.ezmlm@ecos.sourceware.org>
I'm an experienced embedded systems and DSP programmer but am completely new
to ECOS (and ARM). I'm trying ascertain how difficult and time consuming it
will be to get ECOS up and running on an Atmel AT91RM9200 eval board. I am
particularly concerned about how long it will take to get Ethernet drivers
and a TCP/IP stack up and running.
Can anyone help me with this question and point in the direction of any good
information resources?
Thanks!
- Andy Voelkel
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2005-05-07 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1115423292.31725.ezmlm@ecos.sourceware.org>
2005-05-07 2:36 ` Andy Voelkel [this message]
2005-05-08 0:05 ` Daniel Morris
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=E1DUCt7-0000IV-00@mail.aemf.org \
--to=andy@bushtaxi.com \
--cc=ecos-discuss@sources.redhat.com \
/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).