> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Grant Likely > Sent: Monday, October 15, 2007 11:09 AM > To: linuxppc-dev; [EMAIL PROTECTED] > Subject: Refactor booting-without-of.txt > > 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. >
I agree in principle with what your are proposing. One other thing to consider-- as has been publicly announced in several forums, a committee in power.org (including several folks on this thread) is working on a standard called the ePAPR which in general is attempting to standardize the base set of requirements and boot conventions that apply to the flat device tree. There will not be much device specific stuff to start with. The ePAPR document is actually quite far a long and is well beyond the 'idea' stage. The one point is that we hope that the device tree with be useful for other embedded OSes beyond Linux. So long term, I think this documentation should be pulled out of the kernel source and put on a public wiki that is not tied directly to Linux. What you are proposing is a good start... Stuart _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
