linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linuxppc-dev@ozlabs.org, jgarzik@pobox.com
Subject: Re: [PATCH] Fix Maple PATA IRQ assignment.
Date: Mon, 01 Jan 2007 21:15:32 +0000	[thread overview]
Message-ID: <1167686134.18169.3.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20070101212236.34526225@localhost.localdomain>

On Mon, 2007-01-01 at 21:22 +0000, Alan wrote:
> On Mon, 01 Jan 2007 19:31:15 +0000
> David Woodhouse <dwmw2@infradead.org> wrote:
> > There's probably a better way to do this -- especially if we observe
> > that the _only_ case in which this seemingly-generic
> > "pci_get_legacy_ide_irq()" function returns anything other than 14 and
> > 15 for primary and secondary respectively is the case of the AMD8111 on
> > the Maple board -- couldn't we handle that with a special case in the
> > pata_amd driver, or perhaps with a PCI quirk for Maple to switch it into
> > native mode during early boot and assign resources properly?
> 
> There are lots of platforms where the primary/secondary address depends
> upon the board/architecture. PPC actually has functions for this in the
> machine specific goo used by the old driver for one example
> > 
> > Signed-off-by: David Woodhouse <dwmw2@infradead.org>
> 
> NAK: Alan Cox <alan@redhat.com>
> 
> Please reuse the existing PPC methods that drivers/ide calls into.

Er, that would be pci_get_legacy_ide_irq(), which is what I _have_ used.

As I said, the Maple board is the _only_ user, across all architectures
and all PowerPC platforms, of pci_get_legacy_ide_irq(). And the AMD74xx
driver is the only driver which calls it -- for Maple. Hence the
suggestion that perhaps there's a better way to do it.

-- 
dwmw2

  reply	other threads:[~2007-01-01 21:15 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
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 [this message]
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=1167686134.18169.3.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).