From: Dan Malek <dmalek@jlc.net>
To: Cort Dougan <cort@persephone.cs.nmt.edu>
Cc: Paul Mackerras <paulus@cs.anu.edu.au>,
Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>,
bh40@calva.net, tmrini@ntplx.net,
linuxppc-dev@lists.linuxppc.org
Subject: Re: irq cleanup
Date: Tue, 05 Jan 1999 00:33:15 -0500 [thread overview]
Message-ID: <3691A41B.5BB09E15@jlc.net> (raw)
In-Reply-To: Pine.LNX.3.96.990104184703.27992A-100000@persephone.cs.nmt.edu
Cort Dougan wrote:
> Right, that's the plan.
>
> }To support PCI or ISA devices that interrupt on the MBX
> }you would need to modify irq.c to support a multilevel interrupt
> }scheme. The 8259 would interrupt on one of the 8xx interrupt
> }controller levels, then you would have to process all 8259
> }interrupts.
Are there other systems designed like this with a multilevel
interrupt controller? It's not hard to imagine, although I have
never seen one before the MBX. This is one reason I didn't
spend any effort when I did the iniitial port. It seemed like
lots of work for a single board not likely to use them
-- Dan
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-05 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-31 21:43 irq cleanup Cort Dougan
1999-01-04 1:37 ` Dan Malek
1999-01-05 1:48 ` Cort Dougan
1999-01-05 5:33 ` Dan Malek [this message]
1999-01-05 9:05 ` Geert Uytterhoeven
1999-01-05 21:06 ` Cort Dougan
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=3691A41B.5BB09E15@jlc.net \
--to=dmalek@jlc.net \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=bh40@calva.net \
--cc=cort@persephone.cs.nmt.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@cs.anu.edu.au \
--cc=tmrini@ntplx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.