From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Dan Malek <dan@embeddededge.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH and RFC] Remove request_8xxirq
Date: Thu, 20 Jun 2002 23:16:50 +0200 [thread overview]
Message-ID: <20020620211651.0A6811030B@denx.denx.de> (raw)
In-Reply-To: Your message of "Thu, 20 Jun 2002 13:34:55 PDT." <20020620203455.GG16052@opus.bloom.county>
In message <20020620203455.GG16052@opus.bloom.county> Tom Rini wrote:
>
> The following two patches remove request_8xxirq and redesign how we
> handle interrupts. There's patches both against 2.5 (For inclusion
> first, mainly for comment tho) and for 2.4 (which has been tested but is
> intended for inclusion much later, probably 2.4.21 time-frame).
>
> The new interrupt handling scheme allows all 8xx interrupt handlers to be
> installed via the standard request_irq() function. This required a
> "flattened" representation of the interrupt vectors from all interrupt
> controllers so that we can uniquely identify any interrupt source with a
> single integer. The interrupt vector numbers used by request_irq() are:
>
> request_irq vector interrupt source
> ------------------ ----------------
> 0 - 15 SIU interrupt vectors 0 to 15
> 16 - 47 CPM interrupt vectors 0 to 31
> 48 - 63 8259 interrupt vectors 0 to 15 (MBX only)
...
> The bulk of this work was done by Andy Lowe and then moved up to current
> kernels and expanded slightly by myself.
Isn't this more or less the same idea as presented by Wolfgang
Grandegger more than half a year ago? See
> Date: Sun, 28 Oct 2001 23:04:48 +0100
> From: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
> To: Tom Rini <trini@kernel.crashing.org>
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Multi-level CPM Interrupts
By then there was a common agreement that it was a bad idea from the
beginning (although we need and use it for RTAI anyway).
It's amusing to see how ideas get recycled again and again.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A conservative is a man who believes that nothing should be done for
the first time. - Alfred E. Wiggam
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-20 21:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 20:34 [PATCH and RFC] Remove request_8xxirq Tom Rini
2002-06-20 21:04 ` Dan Malek
2002-06-20 21:39 ` Tom Rini
2002-06-20 22:03 ` Dan Malek
2002-06-20 16:58 ` Benjamin Herrenschmidt
2002-06-20 22:34 ` Tom Rini
2002-06-20 21:16 ` Wolfgang Denk [this message]
[not found] <20020620214551.GI16052@opus.bloom.county>
2002-06-20 21:58 ` Wolfgang Denk
[not found] ` <20020620221016.GK16052@opus.bloom.county>
[not found] ` <3D12F667.30902@bluewin.ch>
2002-06-24 17:00 ` Tom Rini
2002-06-24 17:49 ` Dan Malek
2002-06-24 17:59 ` Tom Rini
[not found] ` <3D1793E1.3030509@bluewin.ch>
[not found] ` <20020624224100.GL3489@opus.bloom.county>
2002-06-25 0:03 ` Dan Malek
[not found] <3D124DF4.6060505@embeddededge.com>
2002-06-20 22:02 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-06-21 2:32 Andy Lowe
2002-06-21 4:35 ` Dan Malek
2002-06-21 4:54 ` Andy Lowe
[not found] <15635.16331.965632.877856@argo.ozlabs.ibm.com>
2002-06-23 16:54 ` Stephan Linke
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=20020620211651.0A6811030B@denx.denx.de \
--to=wd@denx.de \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 NNTP newsgroup(s).