[09:34] <ali1234> ogra_: so, u-boot can dump a fdt in memory. this is the diff between the dtb put in memory by broadcom, vs loading the same dtb with u-boot: http://paste.ubuntu.com/13111353/
[10:15] <ogra_> ali1234, well, pretty much the cmdline .... overlays would show up there too i guess
[10:15] <ali1234> i didn't load any overlays but yeah they would
[10:15] <ali1234> but the serial number/mac stuff is in there too
[10:16] <ali1234> i reckon u-boot is capable of even loading overlays
[10:16] <ali1234> and even parameters
[10:17] <ali1234> it would need a really big script though
[10:41] <ogra_> i dont mind big scripts .... :)
[10:42] <ogra_> the question is, can uboot pverwrite 0x100 after you already loaded the blob fdt from there
[10:42] <ali1234> sure, of course
[10:42] <ali1234> it's just memory
[10:42] <ogra_> well, i guess it can ... the question is can it re-read from there rather
[10:42] <ogra_> or does it fall over if you call the fdt command twice
[10:43] <ali1234> no, absolutely not
[10:43] <ogra_> perfect
[10:43] <ali1234> you can load a fdt, extract stuff from it, load a new one and insert stuff into it
[10:43] <ali1234> you can even have more than one in memory at once if you like
[10:43] <ogra_> so you can read the cmdline stuff and then overwrite with your own dtb
[10:43] <ali1234> you just change the active one with fdt <addr>
[10:43] <ali1234> *fdt addr <addr>
[10:44] <ali1234> and you can store the values into variables
[10:45] <ogra_> sure, thats what i do already when loading the initial dtb