From: Matt Sealey <matt@genesi-usa.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: how to handle pata_via when controller not in fully-pci-native mode (two irqs?)
Date: Sat, 23 Jun 2007 10:33:46 +0100 [thread overview]
Message-ID: <467CE8FA.2040304@genesi-usa.com> (raw)
In-Reply-To: <20070623103349.23cad9b7@the-village.bc.nu>
Alan Cox wrote:
> On Sat, 23 Jun 2007 01:26:06 +0100
>
> The simplest way is probably to load the pci class and programming
> interface bits correctly for the device to match how your IRQ setup has
> been arranged. See page 78 of the VIA 8231 spec if you have it, and load
> the programming class in the boot firmware or in a PCI header quirk)
Ah so the correct way *is* to change the PCI class? I don't think we're
going to be publishing such a thing in the firmware (sadly) but this could
be done in a platform fixup for sure, then? Or a Forth script in the
firmware... hmm.. that sounds pretty easy actually.
--
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations
next prev parent reply other threads:[~2007-06-23 9:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 0:26 how to handle pata_via when controller not in fully-pci-native mode (two irqs?) Matt Sealey
2007-06-23 4:23 ` Jeff Garzik
2007-06-23 9:33 ` Alan Cox
2007-06-23 9:33 ` Matt Sealey [this message]
2007-06-23 9:53 ` Alan Cox
2007-06-23 10:11 ` Matt Sealey
2007-07-03 7:33 ` Tejun Heo
2007-07-03 8:11 ` Matt Sealey
2007-07-03 9:21 ` Tejun Heo
2007-07-03 12:44 ` Matt Sealey
2007-07-03 12:17 ` Alan Cox
2007-07-03 12:32 ` Matt Sealey
2007-07-03 13:38 ` Alan Cox
2007-07-03 13:41 ` Matt Sealey
2007-07-03 13:53 ` Jeff Garzik
2007-07-03 14:00 ` Matt Sealey
2007-07-03 15:08 ` Jeff Garzik
2007-07-03 13:53 ` Alan Cox
2007-07-03 13:54 ` Matt Sealey
2007-07-04 8:55 ` Tejun Heo
2007-07-04 19:08 ` Matt Sealey
2007-07-05 2:28 ` Tejun Heo
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=467CE8FA.2040304@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.