linux-kernel - Re: 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]

Message-ID: <44FBD91B.2080600@garzik.org>
Date:	Mon, 04 Sep 2006 03:43:23 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chris Wedgwood <cw@...f.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: Re: VIA IRQ quirk, another (embarrassing) suggestion.

Chris Wedgwood wrote:
> 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.

It's not a question of me being satisfied or embarrassed.  The only 
question is what works for all cases.

My guess is that we need more complex logic to detect which devices are 
truly on-board.

Unfortunately for us, PCI cards with VIA SATA or VIA ethernet exist, so 
we cannot continue the current scheme of device ID enumeration either.

	Jeff



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