linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, jgarzik@pobox.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] Fix Maple PATA IRQ assignment.
Date: Tue, 02 Jan 2007 08:23:14 +1100	[thread overview]
Message-ID: <1167686594.23340.139.camel@localhost.localdomain> (raw)
In-Reply-To: <1167683166.22068.378.camel@pmac.infradead.org>

On Mon, 2007-01-01 at 20:26 +0000, David Woodhouse wrote:
> On Tue, 2007-01-02 at 07:10 +1100, Benjamin Herrenschmidt wrote:
> > 
> > I'm not sure you can switch it to native mode in sw... worth double
> > checking though. All boards based on 8111 on powerpc have this problem,
> > I think. What of the js20 and js21 with IBM firmware ? Or does it have
> > the ide strapped to native mode ?
> 
> No idea, but it doesn't implement ppc_md.pci_get_legacy_ide_irq(). Only
> Maple does -- maybe the others actually manage to route it to IRQ 14 and
> 15?

Not with the new IRQ numbering scheme in which only a 8259 can get
those. Thus it must be native.

> Perhaps we could do that on Maple too -- after all, IRQ numbers in Linux
> are just a fiction which don't have to match the hardware documentation
> in any way.

I suppose I could add a function to hard-code a mapping but that would
have a few issues with the way I do virtual IRQs... I really assume that
1 to 15 are reserved for 8259. But we can hack it... I'd rather not
though and keep a hook for IDE etc...

There's another problem which is PCI IDE cards with the chip in legacy
mode... I've seen all sort of HW horrors in the area (like routing them
to INT#A and INT#B on a single function, sic....) or there's also the
case of the VIA chipset in pegasos which claims to be native mode but
routes IDE IRQs to 14 and 15 and not PIRQ...

Ben.

  reply	other threads:[~2007-01-01 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 19:31 [PATCH] Fix Maple PATA IRQ assignment David Woodhouse
2007-01-01 20:10 ` Benjamin Herrenschmidt
2007-01-01 20:26   ` David Woodhouse
2007-01-01 21:23     ` Benjamin Herrenschmidt [this message]
2007-01-01 20:44   ` Segher Boessenkool
2007-01-01 21:33     ` Benjamin Herrenschmidt
2007-01-01 22:17       ` Segher Boessenkool
2007-01-01 20:42 ` Segher Boessenkool
2007-01-01 20:56   ` David Woodhouse
2007-01-01 21:22 ` Alan
2007-01-01 21:15   ` David Woodhouse
2007-01-01 21:34     ` Alan
2007-01-01 21:43       ` David Woodhouse
2007-01-02  0:17         ` Benjamin Herrenschmidt
2007-01-02  0:18 ` Benjamin Herrenschmidt
2007-01-26 22:28 ` Jeff Garzik

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=1167686594.23340.139.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.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).