On Wed, Jun 19, 2013 at 07:02:00AM -0300, Ezequiel Garcia wrote: > > Verifying the DT is setup this way and aborting if it is not seems > > like a good idea.. > > I agree it's a nice idea, but I'm not too sure how to accomplish this > in a simple and generic way. There's nothing in the DT that allows you > to know which of the ranges entries correspond to the BootROM, unless you go > through each of the entries comparing against the known target ID and > attribute.
I think you need to have a defined compatible string for the bootrom, use one of the of_find.. functions to locate the node, then translate the regs to get a CPU address, ensure it is the right base and size.. > You could also do a 'of_find_node_by_name(NULL, "bootrom");' but the > binding no longer requires to even have any children for the window. You'll need to define a bootrom binding. There is not a lot of sense in including things in the DT if the kernel can't find them and use them. Jason _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss