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 11:55:05 -0500 [thread overview]
Message-ID: <20071015165505.GA16040@lixom.net> (raw)
In-Reply-To: <fa686aa40710150908o55d1f5d2t264cbb8ed800a12f@mail.gmail.com>
On Mon, Oct 15, 2007 at 10:08:44AM -0600, Grant Likely wrote:
> Adding the Linux expected device tree bindings to
> booting-without-of.txt seems to be getting a little unwieldy. Plus
> with more than one arch using the device tree (powerpc, sparc &
> microblaze) the device tree bindings aren't necessarily powerpc only
> (the Xilinx devices certainly fall in this category).
>
> Anyone have comments about splitting the expected device tree bindings
> out of booting-without-of.txt into a separate directory?
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.
> Perhaps something like this; each file contains common bindings for
> the type of device and device specific properties:
>
> Documentation/of/
> Documentation/of/README - Description of the purpose and layout of
> this directory
> Documentation/of/net.txt - network device bindings (eth, MDIO, phy, etc)
> Documentation/of/serial.txt - serial device bindings
> Documentation/of/misc.txt - anything that doesn't fit anywhere else yet.
> Documentation/of/soc/* - System on chip stuff that doesn't fit will
> into established device types; possibly a separate file for each chip.
> Documentation/of/usb.txt - usb blah blah blah
> Documentation/of/whatever - you get the picture.
>
> Thoughts?
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.
-Olof
next prev parent reply other threads:[~2007-10-15 16:49 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 [this message]
2007-10-15 17:14 ` Grant Likely
2007-10-15 17:40 ` Olof Johansson
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=20071015165505.GA16040@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