linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: hollis@austin.ibm.com
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Changes to gt64260 interrupt support code
Date: Wed, 2 Jan 2002 14:04:59 -0600	[thread overview]
Message-ID: <20020102200459.GG469@austin.ibm.com> (raw)
In-Reply-To: <20020102123046.U25200@altus.drgw.net>


On Wed, Jan 02, 2002 at 12:30:46PM -0600, Troy Benjegerdes wrote:
>
> We **REALLY** need a better way to deal with cascaded 8259's than adding
> an offset.. I think Dan Malek had some good ideas on what to do about
> this, but I don't know that anyone has got any currently running code that
> solves this problem nicely.

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.

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-01-02 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 17:44 Changes to gt64260 interrupt support code mod+linuxppc-dev
2002-01-02 18:30 ` Troy Benjegerdes
2002-01-02 20:04   ` hollis [this message]
2002-01-02 22:26 ` Mark A. Greer
2002-01-02 23:23   ` Troy Benjegerdes
  -- strict thread matches above, loose matches on Subject: below --
2002-01-02 19:18 Michael O'Donnell
2002-01-02 21:11 mod+linuxppc-dev

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=20020102200459.GG469@austin.ibm.com \
    --to=hollis@austin.ibm.com \
    --cc=hozer@drgw.net \
    --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).