**** BEGIN LOGGING AT Thu Nov 05 03:00:15 2015
Nov 05 09:34:04 <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/
Nov 05 10:15:21 <ogra_> ali1234, well, pretty much the cmdline .... overlays would show up there too i guess
Nov 05 10:15:35 <ali1234> i didn't load any overlays but yeah they would
Nov 05 10:15:59 <ali1234> but the serial number/mac stuff is in there too
Nov 05 10:16:17 <ali1234> i reckon u-boot is capable of even loading overlays
Nov 05 10:16:26 <ali1234> and even parameters
Nov 05 10:17:08 <ali1234> it would need a really big script though
Nov 05 10:41:41 <ogra_> i dont mind big scripts .... :)
Nov 05 10:42:11 <ogra_> the question is, can uboot pverwrite 0x100 after you already loaded the blob fdt from there
Nov 05 10:42:18 <ali1234> sure, of course
Nov 05 10:42:24 <ali1234> it's just memory
Nov 05 10:42:35 <ogra_> well, i guess it can ... the question is can it re-read from there rather
Nov 05 10:42:53 <ogra_> or does it fall over if you call the fdt command twice
Nov 05 10:43:03 <ali1234> no, absolutely not
Nov 05 10:43:09 <ogra_> perfect
Nov 05 10:43:22 <ali1234> you can load a fdt, extract stuff from it, load a new one and insert stuff into it
Nov 05 10:43:29 <ali1234> you can even have more than one in memory at once if you like
Nov 05 10:43:31 <ogra_> so you can read the cmdline stuff and then overwrite with your own dtb
Nov 05 10:43:36 <ali1234> you just change the active one with fdt <addr>
Nov 05 10:43:55 <ali1234> *fdt addr <addr>
Nov 05 10:44:14 <ali1234> and you can store the values into variables
Nov 05 10:45:07 <ogra_> sure, thats what i do already when loading the initial dtb
**** BEGIN LOGGING AT Thu Nov 05 23:50:44 2015
**** ENDING LOGGING AT Fri Nov 06 02:59:58 2015