linux-kernel - Re: [sodaville] [PATCH 02/11] x86: Add device tree support

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: <4D21F718.8010600@linux.intel.com>
Date:	Mon, 03 Jan 2011 08:19:36 -0800
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Grant Likely <grant.likely@...retlab.ca>
CC:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>, x86@...nel.org,
	linux-kernel@...r.kernel.org, sodaville@...utronix.de,
	Rob Landley <rob@...dley.net>,
	devicetree-discuss@...ts.ozlabs.org
Subject: Re: [sodaville] [PATCH 02/11] x86: Add device tree support

On 01/03/2011 08:05 AM, H. Peter Anvin wrote:
> On 12/30/2010 12:58 PM, Grant Likely wrote:
>>
>> Right, but in all of those cases a boot wrapper provides the same
>> functionality with better flexability, such as being able to provided
>> the dtb image(s) at install time instead of compile time.
>>
> 
> Assuming the boot wrapper is written correctly.  I have seen a number of
> cases in which it was not, and it being "already locked into firmware"
> and not changeable.
> 
> It's a nice theory.  And in theory, theory and practice agree.
> 

By the way, this is the same reason we also allow the initramfs and even
the command line to be compiled in.

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