public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] using a flat device tree to drive u-boot config
Date: Mon, 28 Jul 2008 12:32:55 -0500	[thread overview]
Message-ID: <488E02C7.5000106@freescale.com> (raw)
In-Reply-To: <f8328f7c0807281028u76d692bbt75f4ae953afc09ed@mail.gmail.com>

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

  reply	other threads:[~2008-07-28 17:32 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 15:07 [U-Boot-Users] using a flat device tree to drive u-boot config Kumar Gala
2008-07-28 17:28 ` Ben Warren
2008-07-28 17:32   ` Scott Wood [this message]
2008-07-28 17:35     ` Ben Warren
2008-07-28 17:43       ` Scott Wood
2008-07-28 18:05         ` Ben Warren
2008-07-28 18:59           ` Scott Wood
2008-07-29  8:26           ` André Schwarz
2008-07-29  8:41             ` Wolfgang Grandegger
2008-07-29  9:09               ` André Schwarz
2008-08-03  1:10         ` Jerry Van Baren
2008-07-29 16:41     ` Timur Tabi
2008-07-28 17:40 ` Grant Likely
2008-07-28 18:17   ` Kumar Gala
2008-07-28 19:07     ` Scott Wood
2008-07-29  7:54     ` Haavard Skinnemoen
2008-07-28 18:13 ` Wolfgang Grandegger
2008-07-28 18:19   ` Kumar Gala
2008-07-29 14:30     ` Jon Loeliger
2008-07-29 15:51       ` Robert Schwebel
2008-07-29 15:51 ` Robert Schwebel
2008-07-29 16:46 ` Timur Tabi
2008-08-03  1:58   ` Jon Smirl
2008-08-03  7:51     ` Wolfgang Denk
2008-08-03 12:57       ` Jon Smirl
2008-08-03 15:47         ` Wolfgang Denk
2008-08-03 17:49           ` Timur Tabi
2008-08-03 19:06             ` Grant Likely
2008-08-03 20:08               ` Timur Tabi
2008-08-04  8:08                 ` Albert ARIBAUD
2008-08-04  7:16               ` Jens Gehrlein
2008-08-03 19:45             ` Wolfgang Denk
2008-08-04 14:33               ` Timur Tabi
2008-08-04 15:31                 ` Wolfgang Denk
2008-08-04 15:36                   ` Timur Tabi
2008-08-03 20:47         ` Andrew Dyer
2008-08-04 15:02       ` Jon Smirl
2008-08-04 15:05         ` Timur Tabi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=488E02C7.5000106@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox