From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Mon, 28 Jul 2008 12:32:55 -0500
Subject: [U-Boot-Users] using a flat device tree to drive u-boot config
In-Reply-To: <f8328f7c0807281028u76d692bbt75f4ae953afc09ed@mail.gmail.com>
References: <A8499417-7011-4DFA-B453-B6C05EC6AEAB@kernel.crashing.org>
	<f8328f7c0807281028u76d692bbt75f4ae953afc09ed@mail.gmail.com>
Message-ID: <488E02C7.5000106@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Ben Warren wrote:
> On Mon, Jul 28, 2008 at 8:07 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>> One topic that come up during OLS in discussions and u-boot BOF was
>> the idea of driving u-boot configuration from a device tree instead of
>> from "config.h".  I was wondering if anyone has actually looked at
>> doing this.
>>
> This sounds like an interesting idea, having a central repo for all
> hardware information.  A big problem I see is that while device-tree
> syntax may make sense to Linux kernel propellerheads, to the average
> Joe it's mind-numbing.  Config files are ugly, but at least IMHO are
> easy to figure out.

I find a device tree much easier to figure out than a tangled mess of 
header files, #defines, and #ifdefs...

-Scott