From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Karsten Wiese <annabellesgarden@yahoo.de>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH,RFC] quirks for VIA VT8237 southbridge
Date: Tue, 16 Aug 2005 18:20:16 +0100 [thread overview]
Message-ID: <1124212816.20707.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200508160949.10607.bjorn.helgaas@hp.com>
On Maw, 2005-08-16 at 09:49 -0600, Bjorn Helgaas wrote:
> On Tuesday 16 August 2005 9:26 am, Karsten Wiese wrote:
> > What about the following version?
> > quirk_via_686irq() only works on pci_devs that are part of the 686.
> > Sooner or later there'll be more VIA southbridge types, which will
> > not need quirk_via_irq() like the 8237.
>
> Do you have VIA spec references to support this? I had a quick
> look, but couldn't find anything specific about which VIA devices
> need the quirk and which don't.
PCI interrupt line routing is used for all V-Bus devices. Thats all
devices in any way on an internal bus of the north or south bridge. The
quirk is harmless when applied to other devices.
Note the description of the quirk is still wrong
> > * For these devices, this register is defined to be 4 bits wide.
> > * Normally this is fine. However for IO-APIC motherboards, or
> > * non-x86 architectures (yes Via exists on PPC among other places),
> > * we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
> > * interrupts delivered properly.
The interrupt line field is used to indicate the ISA type IRQ or the
APIC pin used for the IRQ delivery. See the data sheet.
The & 0x0F is the old hack used to get the ISA type IRQ line in use from
the IRQ number.
Alan
next prev parent reply other threads:[~2005-08-16 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 15:10 [PATCH,RFC] quirks for VIA VT8237 southbridge Karsten Wiese
2005-08-13 16:04 ` Grant Coady
2005-08-13 16:34 ` Karsten Wiese
2005-08-13 16:41 ` Jeff Garzik
2005-08-13 21:06 ` Grant Coady
2005-08-15 22:31 ` Bjorn Helgaas
2005-08-16 15:26 ` Karsten Wiese
2005-08-16 15:49 ` Bjorn Helgaas
2005-08-16 17:20 ` Alan Cox [this message]
2005-08-18 12:36 ` Karsten Wiese
2005-08-18 13:57 ` Alan Cox
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=1124212816.20707.5.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=annabellesgarden@yahoo.de \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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