On Fri, Mar 31, 2017 at 10:18:05AM +0300, Çağlar Kilimci wrote: > 2017-03-31 10:02 GMT+03:00 Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > > On Fri, Mar 31, 2017 at 09:54:56AM +0300, Çağlar Kilimci wrote: > >> Hello, > >> > >> > I should have never implemented this freeing of the stored device tree. > >> > There are too many pointers in the code to nodes of this tree. Please > >> > do not use this free/load device tree feature for state. > >> > >> Sure, I usually avoid using it. Here I use to test it if it is able to > >> read the dtb or not? Apparently, it "can" read and parse it but at the > >> boot stage, it does not care. > >> > >> > So you edited > >> > the devicetree in the barebox source code, built a new binary with it > >> > and started it. Now when you enter "of_dump /state@0" you should > >> > see the state node you created. Is that what happens? > >> > >> No, not at all. I could not any sign of state (or state@0). > >> barebox@Phytec phyCORE AM335x:/ of_dump /state@0 > >> Cannot find nodepath /state@0 > >> of_dump: No such file or directory > > > > Ok, here's your problem. I assume you edited > > arch/arm/dts/am335x-phytec-phycore-som.dts, right? Could you send the > > diff to that file (or to the one you edited)? There must be something > > wrong here. > > Actually, I was using arch/arm/boot/dts/am335x-phycore-som.dtsi in the > linux-ti kernel and the diff is: Ok, when you're changing the Linux dts then barebox of course doesn't know about this. > > Let me edit "arch/arm/dts/am335x-phytec-phycore-som.dts" and try it. Yes, please. That sounds better. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
