From: Rafael RodrÃÂguez Velilla <rrv@tid.es>
To: Aron <aron_lu@kimo.com.tw>, ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] porting process
Date: Thu, 15 Feb 2001 06:12:00 -0000 [thread overview]
Message-ID: <3A8BE268.D93117ED@tid.es> (raw)
In-Reply-To: <20010215031750.UCSS24090.n16-svc.kimo.com@k12.svc.kimo.com.tw>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Aron wrote:
> 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?
Tell us a little about your project. ¿Which processor are you using? ¿which devices?
You should try to make a platform port (if your hardware allows it) so your platform can be quickly
adapted to new architecture upgrades.
My personal experience about porting (I'm actually porting an ARM variant, platform porting) is that
the first thing you have to modify is memory layout. Then try to make as soon of posible your target talk
(via serie, via display, via leds... no iterrupts, just polling)...
... tell us about your hardware.
--
Rafael RodrÃguez Velilla rrv@tid.es
Telefónica I+D http://www.tid.es
Telf: +34 - 91 337 4270
prev parent reply other threads:[~2001-02-15 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 19:18 Aron
2001-02-15 6:12 ` Rafael RodrÃguez Velilla [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=3A8BE268.D93117ED@tid.es \
--to=rrv@tid.es \
--cc=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).