linux-kernel - Re: RFC: PCI quirks update for 2.6.16

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:	Thu, 7 Dec 2006 11:37:03 -0500
From:	Alan Cox <alan@...hat.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Daniel Drake <dsd@...too.org>, Alan Cox <alan@...hat.com>,
	Chris Wedgwood <cw@...f.org>, Daniel Ritz <daniel.ritz@....ch>,
	Jean Delvare <khali@...ux-fr.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Linus Torvalds <torvalds@...l.org>,
	Brice Goglin <brice@...i.com>,
	"John W. Linville" <linville@...driver.com>,
	Bauke Jan Douma <bjdouma@...all.nl>,
	Tomasz Koprowski <tomek@...rowski.org>, gregkh@...e.de,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: RFC: PCI quirks update for 2.6.16

On Thu, Dec 07, 2006 at 03:57:56PM +0100, Adrian Bunk wrote:
> Looking at Alan's patch in -mm, it seems the best current solution for 
> 2.6.16 is to go back to the pre-2.6.16.17
>   DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
> and revisit this after Alan's patch was released with 2.6.20?

If you want 2.6.16.* not to risk any reversions of good behaviour then I'd agree
I'm pretty sure the new code is right cool and wonderful *BUT* it may not be
of course and it may also break broken bioses differently 8(
-
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/