From: Jeff Garzik <jeff@garzik.org>
To: Matt Sealey <matt@genesi-usa.com>
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 00:23:25 -0400 [thread overview]
Message-ID: <467CA03D.9060908@garzik.org> (raw)
In-Reply-To: <467C689E.3050800@genesi-usa.com>
Matt Sealey wrote:
> Just bringing this up again as it's about that time of year.
>
> There's an issue with some Via southbridges (the only notable and confirmed
> example I have being the VT8231 on the PegasosPPC) which can be configured
> such that they report that they are in "PCI Native Mode", but in fact handle
> (and report) legacy ATA interrupts through the ISA Bridge configuration.
pata_via calls ata_pci_init_one(), which supports the two-interrupt
legacy configuration just fine. The two-interrupt configuration is
normal for a majority of pata_* drivers (and a few others), and has been
working for years.
It sounds like you need to upgrade your BIOS to fix the requisite PCI
config register, or need to add a PCI quirk for your platform, so that
libata two-irq code will automagically start working for you.
Jeff
next prev parent reply other threads:[~2007-06-23 4:23 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 [this message]
2007-06-23 9:33 ` Alan Cox
2007-06-23 9:33 ` Matt Sealey
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=467CA03D.9060908@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=matt@genesi-usa.com \
/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.