From: "Aron"<aron_lu@kimo.com.tw>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] porting process
Date: Wed, 14 Feb 2001 19:18:00 -0000 [thread overview]
Message-ID: <20010215031750.UCSS24090.n16-svc.kimo.com@k12.svc.kimo.com.tw> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
I recently try to port eCos on new target
When I do the job, what should I note?
anyone who has porting experience can tell
me roughly steps?
Architecture HAL/Platform HAL
I read the eCos online porting guide.
I still don't understand the porting process of Architecture HAL. Should I try to edit vector.S first?
thank you.
--------------------------------------------------------------------
©_¼¯¹q¤l«H½c¡E·¾³q¤ÃÂ¥@ˆ http://mail.kimo.com.tw
< ºô ¸ô ¥à ¬¡¡Eºà ¦b ©_ ¼¯ > http://www.kimo.com.tw
next reply other threads:[~2001-02-14 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 19:18 Aron [this message]
2001-02-15 6:12 ` Rafael RodrÃguez Velilla
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=20010215031750.UCSS24090.n16-svc.kimo.com@k12.svc.kimo.com.tw \
--to=aron_lu@kimo.com.tw \
--cc=ecos-discuss@sourceware.cygnus.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).