linux-kernel - Re: PCI card initialisation at boot

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 11 Nov 2007 17:43:13 -0600
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Keith Chew <keith.chew@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: PCI card initialisation at boot

On Sun, Nov 11, 2007 at 04:46:44PM +0000, Alan Cox wrote:
> Linux by default uses the BIOS resource assignments. It doesn't know
> where those came from other than "the BIOS".

Slightly tangential, but I'm starting to hear requests to have the OS
re-assign resources when it might make better sense.  For example, if
you have a graphics card with a 1GB memory allocation, the BIOS may
assign it into address ranges below 4GB because it doesn't know
if the OS will be 32-bit or 64-bit capable.  But, it would be
beneficial to have it located above 4GB, and to fill in the (new) hole
below 4GB with RAM.  Linux right now doesn't have a way to do this.
It will assign resources for cards that the BIOS left unassigned, but
won't intentionally move resources.

-- 
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
-
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/