From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@mvista.com>
Cc: Wolfgang Grandegger <wg@denx.de>,
Tom Rini <trini@kernel.crashing.org>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Multi-level CPM Interrupts
Date: Wed, 31 Oct 2001 22:19:44 +0100 [thread overview]
Message-ID: <20011031211949.C52D411269@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 29 Oct 2001 10:01:45 EST." <3BDD6F59.7070301@mvista.com>
In message <3BDD6F59.7070301@mvista.com> Dan Malek wrote:
>
> Wolfgang Grandegger wrote:
...
> > I have incorporated the CPM into the multilevel interrupt structure
> > on the 8xx.
>
> Why?
...
> Why is this good?
It seems you did not real until the end of Wolfgang's message; he wrote:
| it easily allows RTAI users to use CPM interrupts.
We need this for RTAI, and I don't see any problems with it.
> Please leave the 8xx/CPM interrupt stucture alone, and add some /proc
Would you please explain why you think the proposal is bad? ANd what
is your recommendation for RTAI, then?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It took him several minutes to understand any new idea put to him,
and this is a very valuable trait in a leader, because anything any-
one is still trying to explain to you after two minutes is probably
important and anything they give up after a mere minute or so is al-
most certainly something they shouldn't have been bothering you with
in the first place. - Terry Pratchett, _Reaper Man_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-10-31 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BDD6F59.7070301@mvista.com>
2001-10-31 21:19 ` Wolfgang Denk [this message]
2001-11-01 18:16 ` Multi-level CPM Interrupts Dan Malek
2001-11-01 18:28 ` Wolfgang Denk
2001-11-01 19:36 ` Wolfgang Grandegger
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=20011031211949.C52D411269@denx.denx.de \
--to=wd@denx.de \
--cc=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
--cc=wg@denx.de \
/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 NNTP newsgroup(s).