>>>>> Why the phandle redirection? Why not just put the firmware blob into >>>>> a property in the QE node, or as a subnode? >>>> >>>> Because there might be multiple QE devices on a single chip, and each >>>> will need to upload the same firmware. So instead of embedding the >>>> firmware multiple times, just embed it once, and have a pointer. >>> >>> You're messing up the binding because of a (perceived) deficiency in >>> the DTB format? > > Huh? Who says anything about messing up?
I do; I consider that indirection thing (and putting firmware blobs in the device tree at all, but to a lesser extent) as making a mess of your device binding. Let's forget that I do not like putting a firmware blob in the device tree if you can at all avoid that; Grant is on that already. As far as I can see, you want that indirection node so that you safe space in the DTB. With real OF it is trivial to not have multiple copies of the data if you want a few properties with the same data. There is no reason this could not be done in DTB as well (and some way in DTS to express that, or maybe the tools could auto-detect it, whatever). Or you could just zip the DTB. >> That is a good question. Why is it necessary to pass the blob via the >> tree? > > Because sometimes the firmware is needed before networking or serial I/O > can function. Can't you link it into the kernel then? Seems a better place for it to me. Of course you said something about GPL, heh. Segher _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
