linux-kernel - Re: [RFC] which drivers need to map ROM BARs?

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: <200805140958.14646.jbarnes@virtuousgeek.org>
Date:	Wed, 14 May 2008 09:58:14 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Gary Hade <garyhade@...ibm.com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org
Subject: Re: [RFC] which drivers need to map ROM BARs?

On Wednesday, May 14, 2008 9:20 am Gary Hade wrote:
> > > that boot option will get rid of that ROM BAR for all devices...
> > > big system could use several graphical cards that need ROM BAR and
> > > several cards that don't need ROM BAR.
> >
> > Correct, not a perfect solution but better than we have right now.
>
> ...but don't let this comment make you think that I am not in
> favor of something like you are suggesting.  I am interested
> in getting the 'pci=norom' change into mainline quickly but it
> is obviously less than ideal for the long term.
>
> Jesse, any idea how many different devices absolutely need
> memory allocated for their expansion ROMs?

Well video devices are one obvious type.  Beyond that you'd have to audit the 
drivers in the tree looking for ones that map the ROM BAR (iirc qla1280 did 
this?).

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