From: mod+linuxppc-dev@MissionCriticalLinux.com
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Changes to gt64260 interrupt support code
Date: Wed, 02 Jan 2002 16:11:10 -0500 [thread overview]
Message-ID: <200201022111.QAA18195@missioncriticallinux.com> (raw)
>The ppc64 port has an array of virtual irq's which is used to index to
>the real irq. In the interests of easy debugging (eg when drivers print
>out their irq number) the virtual irq is kept identical to the actual
>whenever possible.
>
>arch/ppc64/prom.c sets up the map (virt_irq_to_real_map), and
>arch/ppc64/xics.c (the interrupt controller) uses it.
Simple translation of irqs doesn't really solve the
problem; a general solution would provide us with the
ability to initialize and service interrupt requests
routed through multiple, nested, heterogeneous
controllers no matter what the HW designers were
smoking when they laid out the system. See earlier
posts to this list for good discussion on this topic.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-01-02 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 21:11 mod+linuxppc-dev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-02 19:18 Changes to gt64260 interrupt support code Michael O'Donnell
2001-12-27 17:44 mod+linuxppc-dev
2002-01-02 18:30 ` Troy Benjegerdes
2002-01-02 20:04 ` hollis
2002-01-02 22:26 ` Mark A. Greer
2002-01-02 23:23 ` Troy Benjegerdes
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=200201022111.QAA18195@missioncriticallinux.com \
--to=mod+linuxppc-dev@missioncriticallinux.com \
--cc=linuxppc-dev@lists.linuxppc.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).