From: "amassa@san.rr.com" <amassa@san.rr.com>
To: ottawaguy81@yahoo.com
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] RE: General ecos porting question
Date: Tue, 14 Oct 2003 23:55:00 -0000 [thread overview]
Message-ID: <265000-2200310214235538608@M2W027.mail2web.com> (raw)
When you start porting, it is usually best to select a platform that is
close to your new platform. Typically porting RedBoot is the first step to
get the eCos HAL running on the target hardware. Then you can move to
developing an eCos application.
You can also find additional information, and slightly different than the
documentation on the eCos site, about porting eCos in the Embedded Systems
Programming magazine article here:
http://www.embedded.com/story/OEG20011220S0059
Chapter 13 of the book "Embedded Software Development with eCos" also
contains detailed information on porting along with the example
modifications necessary.
Hope this helps,
Anthony
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
reply other threads:[~2003-10-14 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=265000-2200310214235538608@M2W027.mail2web.com \
--to=amassa@san.rr.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=ottawaguy81@yahoo.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).