From: Jon Loeliger <jdl-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: [Fwd: Re: [U-Boot-Users] using a flat device tree to drive u-boot config]
Date: Tue, 29 Jul 2008 09:27:11 -0500 [thread overview]
Message-ID: <488F28BF.6030902@freescale.com> (raw)
-------- Original Message --------
Subject: Re: [U-Boot-Users] using a flat device tree to drive u-boot config
Date: Mon, 28 Jul 2008 13:59:21 -0500
From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Ben Warren <biggerbadderben-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
CC: u-boot-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Users <u-boot-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>, Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Ben Warren wrote:
> Uh, yeah. I like the idea of a central repo for hardware info, and
> the device tree concept is good. My point is that the syntax, while
> concise and exact, can be intimidating. Just look at the amount of
> traffic on the mailing lists of people that don't understand what all
> the fields mean when specifying IRQs etc. Anything we can do to make
> it less so for noobies is a good thing for everybody.
Sure, no argument there -- enhancing the dts syntax with symbolic
constants, computational expressions, and macros should make things like
interrupt specifiers and maps a lot clearer.
-Scott
next reply other threads:[~2008-07-29 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 14:27 Jon Loeliger [this message]
[not found] ` <488F28BF.6030902-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-07-30 1:19 ` [Fwd: Re: [U-Boot-Users] using a flat device tree to drive u-boot config] David Gibson
[not found] ` <20080730011908.GB19216-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-07-30 21:15 ` Jon Loeliger
[not found] ` <4890D9DA.1010603-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2008-07-31 1:15 ` David Gibson
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=488F28BF.6030902@freescale.com \
--to=jdl-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
/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