From: "Grant Likely" <grant.likely@secretlab.ca>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>,
microblaze-uclinux@itee.uq.edu.au
Subject: Refactor booting-without-of.txt
Date: Mon, 15 Oct 2007 10:08:44 -0600 [thread overview]
Message-ID: <fa686aa40710150908o55d1f5d2t264cbb8ed800a12f@mail.gmail.com> (raw)
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?
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?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next reply other threads:[~2007-10-15 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:08 Grant Likely [this message]
2007-10-15 16:55 ` Refactor booting-without-of.txt Olof Johansson
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=fa686aa40710150908o55d1f5d2t264cbb8ed800a12f@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).