Other than that quibble, I agree that burning the blob into the
firmware
so that the firmware must be recompiled and reburned to change the
blob
is very undesirable.
I thought the device tree was *supposed* to be an interface between the
firmware and the kernel? What if the firmware produces the tree
dynamically? What if the firmware itself depends on having the device
tree
in order to operate?
Sure. But in the case where the firmware just passes the
kernel some fixed blob, it is easier for everyone to include
that blob with the kernel instead.
Segher
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
