linux-kernel - Re: [git pull] PCI changes for 2.6.34

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: <alpine.LFD.2.00.1003010803360.3616@localhost.localdomain>
Date:	Mon, 1 Mar 2010 08:05:55 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Yinghai Lu <yinghai@...nel.org>
cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] PCI changes for 2.6.34  - pci rom rom fail list

On Sun, 28 Feb 2010, Yinghai Lu wrote:
> 
> [PATCH] pci: don't reassign to ROM res if it is not going to be enabled
> 
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>

Yes, this makes my setup work again.

I'm still nervous that it will cause problem on some _other_ machines 
(because of not knowing that some bridge is transparent and then trying to 
re-allocate things unnecessarily and causing chaos), but at least it seems 
to be ok on this machine.

So I do have this nagging feeling that we'll still end up having to do 
this whole "reassign PCI buses" thing as a kernel command line option and 
default to not doing it, but let's give it a chance.

		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/