From: Jesper Skov <jskov@redhat.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: Grant Edwards <grante@visi.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] hal_default_isr undefined
Date: Tue, 02 Jan 2001 06:27:00 -0000 [thread overview]
Message-ID: <otae9aghbq.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <3A37DCBA.3DD3708B@redhat.com>
>>>>> "Jonathan" == Jonathan Larmour <jlarmour@redhat.com> writes:
Jonathan> You're right. I suppose the issue is that all the ARM
Jonathan> platforms in eCos support virtual vectors now, so there's no
Jonathan> need to support ones that don't, in theory. Perhaps it would
Indeed. In the MIPS HAL we have appropriate cruft in place to support
both.
I hope to get rid of all such cruft as we get all targets converted to
use virtual vectors.
Grant, did I see you mention RedBoot support on your target? You'll
need virtual vectors for that to happen. Just a forewarning :)
Jesper
next parent reply other threads:[~2001-01-02 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001212120553.A14609@visi.com>
[not found] ` <3A37D11F.5FF55FFB@redhat.com>
[not found] ` <20001213140730.A17131@visi.com>
[not found] ` <3A37DCBA.3DD3708B@redhat.com>
2001-01-02 6:27 ` Jesper Skov [this message]
2001-01-02 7:38 ` Grant Edwards
2001-01-02 7:42 ` 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=otae9aghbq.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
--cc=jlarmour@redhat.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).