linux-kernel - VIA IRQ quirk, another (embarrassing) suggestion.

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, 3 Sep 2006 22:55:02 -0700
From:	Chris Wedgwood <cw@...f.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>, greg@...ah.com,
	harmon@....edu, Daniel Drake <dsd@...too.org>,
	Len Brown <len.brown@...el.com>
Subject: VIA IRQ quirk, another (embarrassing) suggestion.

On Mon, Sep 04, 2006 at 01:44:08AM -0400, Jeff Garzik wrote:

> 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'll also point out that I was told (very indirectly, those with
definitive knowledge please speak up) that VIA claimed the recommended
way to deal with these chipset problems is to use ACPI...

However, we know in some cases ACPI doesn't work as-is under Linux,
but apparently does under Windows.  In many cases though it does
appear to suffice.

When chasing down why it doesn't work on other main boards someone who
is ACPI knowledgeable claimed that in the past VIA got their ACPI
wrong, so we need to figure out what ACPI specific quirk windows is
using if we go that route.

It would be really nice if someone from VIA could come forward on this
matter.

Now, failing that, Jeff, what about if we try to use ACPI to detect if
the PCI device is on-board or a plug-in card?  If we did and ignored
them would that satisfy you?

Yes, I know this is yet-another horrible heuristic and might not work
in all cases, but I think we need to aim to get the majority of
systems broken working pretty promptly.  As Andrew said, this really
is quire embarrassing right now.

-- 
VGER BF report: H 0.3996
-
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/