On 08/05/2013 06:17 PM, Brendan Conoboy wrote:
On 08/05/2013 03:14 PM, Stephen Warren wrote:
Related, all of this pre-supposes that the DTBs are stored in the filesystem and installed via distro packages. On some systems (Calxeda?), I believe they're provided by firmware (i.e. are stored in flash), so are already in memory by the time e.g. U-Boot runs, and hence have no disk location.
They can still have a disk location- you just might not want to load the thing. Really, if all vendors would simply embed the dtb into their firmware that would be ideal. It's not happening, though.
Well, is there a recommended standard for doing this? And a follow-up on allowing for overrides or fix-ups to be done easily? I've done some poking about how to have more data be done as part of factory programming and it's both possible and something that they want to understand what's coming in, and have it be something that's know roughly at the start of the process, rather than the end (so we have some way to go, in terms of conversion in the kernel).