From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Cc: Sven.Dickert@planb.de, davidm@amberdata.demon.co.uk,
geert@linux-m68k.org, hollis@austin.ibm.com, paubert@iras.es
Subject: Re: RFC: i8259.c cleanup
Date: Wed, 7 Nov 01 14:55:43 PST [thread overview]
Message-ID: <0111072255.AA06565@ivan.Harhan.ORG> (raw)
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> That address is passed by board-specific code to the generic OpenPIC code
> during OpenPIC initialization.
What does it have to do with OpenPIC? It's the 8259 code, if it's changed to
use interrupt acknowledge, that will need this information.
> So s/an openpic/another interrupt controller/.
>
> There's no single reason why you can't pass a magic interrupt acknowledge
> address to the initialization code for the Adirondack interrupt controller.
>
> Well, this assumes you have generic `building block' interrupt controller code
> that can be cascaded arbitrarily by board-specific code.
Well, if/when you change the 8259 code to use interrupt acknowledge, you'll
have to provide an interface allowing ports to tell it how to do it. When that
happens I'll make the Adirondack and K2 ports provide this information.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-07 22:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 22:55 Michael Sokolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 23:04 RFC: i8259.c cleanup Michael Sokolov
2001-11-07 23:00 Michael Sokolov
2001-11-07 22:43 Michael Sokolov
2001-11-07 21:22 Michael Sokolov
2001-11-07 21:26 ` Geert Uytterhoeven
2001-11-07 21:13 Michael Sokolov
2001-11-07 21:22 ` Geert Uytterhoeven
2001-11-07 20:31 Michael Sokolov
2001-11-07 4:43 Michael Sokolov
2001-11-07 6:31 ` Dag Nygren
2001-11-07 7:00 ` Dan Malek
2001-11-07 7:09 ` Dag Nygren
2001-11-07 6:38 ` Dan Malek
2001-11-06 23:15 hollis
2001-11-07 6:37 ` Dan Malek
2001-11-07 9:31 ` Geert Uytterhoeven
2001-11-07 9:40 ` Gabriel Paubert
2001-11-07 9:38 ` Gabriel Paubert
2001-11-07 17:06 ` hollis
2001-11-07 17:17 ` Geert Uytterhoeven
2001-11-07 21:17 ` Gabriel Paubert
2001-11-07 22:01 ` hollis
2001-11-07 20:46 ` Val Henson
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=0111072255.AA06565@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=Sven.Dickert@planb.de \
--cc=davidm@amberdata.demon.co.uk \
--cc=geert@linux-m68k.org \
--cc=hollis@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iras.es \
/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).