From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, Chris Wedgwood <cw@f00f.org>,
greg@kroah.com, dsd@gentoo.org, jeff@garzik.org, harmon@ksu.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add SATA device to VIA IRQ quirk fixup list
Date: Wed, 26 Jul 2006 13:45:53 +0100 [thread overview]
Message-ID: <1153917954.29975.22.camel@bastov.localdomain> (raw)
In-Reply-To: <1153874577.7559.36.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
Hi, Alan
But can we know if dev->irq is XT-PIC ? or not ?
or could we know if IO_APIC or LOCAL_APIC is enabled or
not ?
on linux-2.6.17/drivers/pci/quirks.c
* we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
* interrupts delivered properly.
*/
static void quirk_via_irq(struct pci_dev *dev)
{
u8 irq, new_irq;
I want put here something like: if ( dev->irq != XT-PIC) return and
don't quirk this dev.
else
new_irq = dev->irq & 0xf;
pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
On Wed, 2006-07-26 at 01:42 +0100, Alan Cox wrote:
> A few comments
>
> "The legacy IDE is using IRQ 14 or 15 not PCI"
>
> This is half correct - V-Link is not involved in this case, however the
> legacy IRQs are configurable and steerable via func 0 reg 0x4C for some
> chips. If this has been set by a weirdass bios (bits 3-0 not 0x0100 for
> the 8233C varies for others) then we've never supported it.
>
>
> I have full IRQ routing info for some of the VIA chips and it varies by
> chip how this all works.
>
> The 8233/8233C routes via register 0x4C/0x4D of function 0 for internal
> devices and via 0x55->0x57 (polarities on 0x54) for PCI interrupts. The
> devices use the IRQ number not line. Also to add fun the 8233C has a
> 3com nic part that does this...
>
> There are then a seperate set of register mappings for SCI and for ISA
> IRQ mapping.
>
> There is an errata with the internal devices of the 8235 and earlier
> which can be used to detect them fairly well. Only the low four bits of
> 0ffset 0x3C are writable not the full IRQ value.
>
>
> Some later chips use bits to indicate PIC v APIC routing.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-07-26 12:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 9:52 Daniel Drake
2006-07-14 11:08 ` Jeff Garzik
2006-07-14 11:40 ` Daniel Drake
2006-07-14 11:51 ` Jeff Garzik
2006-07-14 12:15 ` Daniel Drake
2006-07-14 12:51 ` Sergey Vlasov
2006-07-14 13:20 ` Daniel Drake
2006-07-14 14:43 ` Andrew Morton
2006-07-14 15:42 ` Chris Wedgwood
2006-07-14 16:01 ` Scott J. Harmon
2006-07-14 16:17 ` Daniel Drake
2006-07-14 16:16 ` Chris Wedgwood
2006-07-14 16:24 ` Daniel Drake
2006-07-14 16:33 ` Chris Wedgwood
2006-07-14 16:51 ` Daniel Drake
2006-07-14 16:48 ` Sergio Monteiro Basto
2006-07-14 17:06 ` Daniel Drake
2006-07-14 17:21 ` Sergey Vlasov
2006-07-14 15:46 ` Sergio Monteiro Basto
2006-07-14 16:13 ` Chris Wedgwood
2006-07-15 0:10 ` Sergio Monteiro Basto
2006-07-16 14:09 ` Daniel Drake
2006-07-16 18:31 ` Greg KH
2006-07-17 0:34 ` Chris Wedgwood
2006-07-25 4:40 ` Andrew Morton
2006-07-26 0:42 ` Alan Cox
2006-07-26 12:45 ` Sergio Monteiro Basto [this message]
2006-07-26 13:59 ` Daniel Drake
2006-07-26 14:06 ` Sergio Monteiro Basto
2006-07-26 14:31 ` Daniel Drake
2006-07-26 15:11 ` Sergio Monteiro Basto
2006-07-26 22:14 ` Sergio Monteiro Basto
2006-07-14 23:58 ` Chris Wedgwood
2006-07-14 19:26 Brown, Len
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=1153917954.29975.22.camel@bastov.localdomain \
--to=sergio@sergiomb.no-ip.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--cc=jeff@garzik.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®