From: Olof Johansson <olof@lixom•net>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>,
microblaze-uclinux@itee•uq.edu.au
Subject: Re: Refactor booting-without-of.txt
Date: Mon, 15 Oct 2007 12:40:59 -0500 [thread overview]
Message-ID: <20071015174059.GA17387@lixom.net> (raw)
In-Reply-To: <fa686aa40710151014q5e151ea9w3f589d9e89e95905@mail.gmail.com>
Hi,
On Mon, Oct 15, 2007 at 11:14:44AM -0600, Grant Likely wrote:
> On 10/15/07, Olof Johansson <olof@lixom•net> wrote:
> >
> > The flat device tree is, in spite of what some people would like it to be,
> > not open firmware, nor is it the same as their bindings. So I think we'd
> > be doing ourselves a disservice by continuing to associate them together.
> > All it would take is a rename of the directory, unfortunately i don't
> > have any suggestions on better names though.
>
> I think I need to stick with the of prefix. All the support API in
> include/linux/of_* is prefixed with "of_" already, so convention is
> established.
>
> How about Documentation/of-device-tree?
Sounds good to me, even though it doesn't really address the original
OF separation comment. :)
Maybe it's enough to document the difference between the linux-specific
flat device tree bindings and classic 1275-style bindings in the top
readme in that directory. Either way, it's not worth arguing over,
your suggestion is good enough.
> > Looks reasonable. The other way to cut it would be to slice along vendor
> > boundaries, but I think I like the functional partitioning you suggested
> > better.
>
> I think vendor partitioning makes sense for non-common devices that
> don't easily fit into a particular mold (soc glue nodes come to mind).
> Other than that, the functional partitioning
> lets us start with defining common property usage for a given device
> type and follow up with device specific properties.
Yep, it could always be added down the road in case it's needed.
-Olof
next prev parent reply other threads:[~2007-10-15 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:08 Refactor booting-without-of.txt Grant Likely
2007-10-15 16:55 ` Olof Johansson
2007-10-15 17:14 ` Grant Likely
2007-10-15 17:40 ` Olof Johansson [this message]
2007-10-16 2:38 ` David Gibson
2007-10-16 3:02 ` Grant Likely
2007-10-16 3:24 ` David Gibson
2007-10-16 17:24 ` Stephen Neuendorffer
2007-10-16 19:39 ` Grant Likely
2007-10-16 17:13 ` Stephen Neuendorffer
2007-10-16 17:17 ` Grant Likely
2007-10-31 15:44 ` Yoder Stuart-B08248
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=20071015174059.GA17387@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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