Dear Scott, in message <[EMAIL PROTECTED]> you wrote: > > Well, the device tree is a mechanism for communicating from the firmware > to the kernel, and if we could control the firmware better we'd just make > it set the pins properly to begin with. :-)
Is this just a comment, or do you oppose Heiko's suggestion? Other uses of the device tree seem possible and reasonable, too. For example, we can use the device tree to configure the firmware (U-Boot in this case). Using the device tree to describe the pin configuration of the hardware sounds easier to me than hard-coding it in some source (or header) file - no matter if this is in the kernel and/or in the firmware. What do you think? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] A quarrel is quickly settled when deserted by one party; there is no battle unless there be two. - Seneca _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev