From: Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
To: Scott Moore <smoore@powerfile.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Notification of changes required for CPU support
Date: Wed, 29 Aug 2007 19:29:00 -0000 [thread overview]
Message-ID: <20070829192912.GA24434@grumpf.hope-2000.org> (raw)
In-Reply-To: <BC0348D2176B4C4EA0CBB50AEFDBD9670B11D6D4@MI8NYCMAIL14.Mi8.com>
On Wed, Aug 29, 2007 at 02:46:32PM -0400, Scott Moore wrote:
> Right now, I am just hacking up the lpc2xxx series to get our stuff
> running without regard for lpc21xx and lpc22xx backwards compatibility.
>
> Hey, blame Phillips for creating an incompatibility in their own
> series.
Is this the only incompatibility?
AFAIK the lpc23xx series uses a ARM9 core and has more (different)
on-chip peripherals and memory. I have currently no clue about that, but
I think that supporting the lpc23xx in a different tree would make sense
iff there more incompatibilities than just the interrupt stuff.
But renaming the lpc2xxx in lpc21xx_lpc22xx is something I wouldn't do.
I would just leave it as it is, adding a new CPU without disturbing any
old once.
--
%SYSTEM-F-ANARCHISM, The operating system has been overthrown
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-08-29 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 12:03 [ECOS] timer alarm or any timer in Redboot Jacob Avraham
2007-08-29 12:53 ` Andrew Lunn
2007-08-29 18:48 ` [ECOS] Notification of changes required for CPU support Scott Moore
2007-08-29 19:00 ` Gary Thomas
2007-08-29 19:08 ` Scott Moore
2007-08-29 19:29 ` Hans Rosenfeld [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=20070829192912.GA24434@grumpf.hope-2000.org \
--to=rosenfeld@grumpf.hope-2000.org \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=smoore@powerfile.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).