Re: [RFC] Best practices for hardware shipping device trees

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, Aug 14, 2013 at 10:57:36PM -0400, Nicolas Pitre wrote:
> On Wed, 14 Aug 2013, Tom Rini wrote:
> > On 08/14/2013 08:37 PM, Nicolas Pitre wrote:
> > > On Wed, 14 Aug 2013, Tom Rini wrote:
[snip]
> Well, the hard guideline should require that the DTB be updateable and 
> not linked with nor generated by the bootloader or firmware.  That 
> implies some storage separate from the bootloader but this doesn't need 
> to be a filesystem.

Wait, what!?

Much as I think a bunch of the current problems have been caused by
being overly keen to push the dtb into firmware, we shouldn't *ban*
the original Open Firmware model of the device tree, where it is
generated by the firmware and consumed by the OS.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

Attachment: pgpxJMn0tAEdQ.pgp
Description: PGP signature


[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux