linux-kernel - Re: PCI MAINTAINER change

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:	Mon, 21 Apr 2008 09:18:50 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz,
	pcihpd-discuss@...ts.sourceforge.net, mingo@...hat.com,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: PCI MAINTAINER change

On Mon, 21 Apr 2008, Jesse Barnes wrote:
> 
> And now I get to figure out just how much trouble I've gotten myself into...

Mwhahahaaa! Sucker. You'll find out.

The good news is that most of the time, the PCI code works fine. The bad 
news is that when it doesn't work, it's usually due to something *really* 
odd, like some magic motherboard device that has magic resources that 
aren't part of the standard PCI resource set and that clash with some of 
our resource allocation.

And they don't show up in the PnP lists because Windows never put anything 
that could clash with them, so there was no reason for the BIOS engineers 
to bother.

IOW, it's usually almost totally undebuggable crud like "driver X doesn't 
work on my machine", and then it turns out that it only happens on that 
particular motherboard that is totally identical to all other motherboards 
_except_ for that BIOS table not having the right reserved IO regions.

.. and then there's the pluggable PCI stuff, of course. I'm not sure 
whether you took that over too. That's a whole different set of issues.

			Linus
--
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/