linux-kernel - Re: VIA IRQ quirk fixup only in XT-PIC mode Take 3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 03 Sep 2006 09:52:24 -0400
From:	Daniel Drake <dsd@...too.org>
To:	Jeff Garzik <jeff@...zik.org>
CC:	Andrew Morton <akpm@...l.org>, sergio@...giomb.no-ip.org,
	bjorn.helgaas@...com, linux-kernel@...r.kernel.org,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Chris Wedgwood <cw@...f.org>, greg@...ah.com, harmon@....edu,
	Len Brown <len.brown@...el.com>
Subject: Re: VIA IRQ quirk fixup only in XT-PIC mode Take 3

Jeff Garzik wrote:
> Andrew Morton wrote:
>> There's a similar patch in -mm: 
>> pci-quirk_via_irq-behaviour-change.patch. Does that work for you?
> 
> And then, we return to:
> 
> Some installations have VIA products on a PCI card.  We cannot assume 
> that all PCI_VENDOR_ID_VIA devices are on-board devices with the special 
> VIA PIC on-chip routing (the thing quirk_via_irq tweaks).

I'm not sure whether you are commenting on my patch 
(pci-quirk_via_irq-behaviour-change.patch), or Sergio's, but just to 
clarify:

My patch includes a hack that detects the presence of a VIA southbridge, 
and only applies quirks if a southbridge is present.

This isn't perfect, as someone could insert a VIA PCI card into a 
VIA-based motherboard and the PCI card would get quirked, but it's the 
most accurate solution which has been proposed so far.

If the southbridge detection hack is acceptable, there is no reason why 
it could not be combined with Sergio's patch.

Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/