From: Rutger Hofman <rutger@cs.vu.nl>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] eCos upgrade from pre-2.0 to CVS: painless!
Date: Fri, 16 Feb 2007 16:45:00 -0000 [thread overview]
Message-ID: <45D5DF00.60307@cs.vu.nl> (raw)
Hi eCos developers,
a short time ago I upgraded from a pre-2.0 (just) version of eCos that
came bundled with our XScale development board, to the anonymous CVS
version of eCos. It was as good as painless to port our vendor's changes
to recent eCos -- the /only/ snag was in the Legacy JFFS2 layer, which
seemed hardly used. Porting the .ecc was also painless: I threw out a
few apparently deprecated stanzas, and the tool succeeded in creating a
correct new .ecc for me.
Kudos and many thanks for such a good and API-wise stable development
system!
Rutger Hofman
VU Amsterdam
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-02-16 16:45 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=45D5DF00.60307@cs.vu.nl \
--to=rutger@cs.vu.nl \
--cc=ecos-discuss@ecos.sourceware.org \
/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).