public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rafael Rodríguez Velilla <rrv@tid.es>
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Porting...
Date: Tue, 18 Jul 2000 09:13:00 -0000	[thread overview]
Message-ID: <3974812B.E9026910@tid.es> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

  Hello,
   I'm starting to work with ecos, and I'm going to port it to a chip
based on an ARM7TDMI, it is called microPP (from microPay Phone)
   The port is for a custom design that we have developed at Telefónica
I+D, so it's a very singular platform and I suppose that nobody else
than me is going to be interested in the port, anyway I would want to
work with the philosophy of eCos, I want to have an eCos package that
using something like "ecosconfig new microPP " generates all the
working-directory adjusted to microPPs requirements. Which is the
recommended reading for doing this? Is there something written so I can
know how to change eCos in order to satisfy my needs taking into account
that I'd want to be able to apply future modifications of eCos directly
to my new porting?


   Another question. Has anybody worked with an ARM7TDMI with an
MMU(ARM710 or something  like that)? Does eCos or gcc takes this feature
into account?

--
Rafael Rodríguez Velilla        rrv@tid.es
Telefónica I+D          http://www.tid.es
Telf: 34 - 1 - 91 337 4270



             reply	other threads:[~2000-07-18  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-18  9:13 Rafael Rodríguez Velilla [this message]
2000-07-18 10:00 ` Jonathan Larmour
2000-09-19 10:24 Rafael Rodríguez Velilla
2000-09-25  3:00 ` Jesper Skov
2000-09-25  1:57   ` Rafael Rodríguez Velilla
2000-09-25  6:10     ` Jesper Skov

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=3974812B.E9026910@tid.es \
    --to=rrv@tid.es \
    --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).