<br><br><div class="gmail_quote">On Tue, Jan 22, 2013 at 2:54 PM, Dennis Gilmore <span dir="ltr"><<a href="mailto:dennis@ausil.us" target="_blank">dennis@ausil.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
El Tue, 22 Jan 2013 14:15:57 -0600<br>
Jon <<a href="mailto:jdisnard@gmail.com">jdisnard@gmail.com</a>> escribió:<br>
<div><div class="h5">> On Tue, Jan 22, 2013 at 1:51 PM, Paul Whalen <<a href="mailto:pwhalen@redhat.com">pwhalen@redhat.com</a>><br>
> wrote:<br>
><br>
> ><br>
> > Summary of discussion from #fedora-arm<br>
> > --------------------------------------<br>
> ><br>
> > Dennis Gilmore will be creating a kernel-dtb subpackage for the 3.7<br>
> > kernel, using 'make dtb' during the kernel build.<br>
> ><br>
> > The plan is to pull in the 3.7 dtb's into our 3.6 based F18 RC1<br>
> > release. We will<br>
> > only be including the DTB's where needed, for Trimslice and<br>
> > vexpress which do not<br>
> > boot without a DTB. The Pandaboard will boot the 3.7 without use of<br>
> > a DTB, and Highbank<br>
> > provides it's own.<br>
> ><br>
> > For a full summary of the testing:<br>
> ><br>
> > <a href="https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/Kernel_Testing#kernel-3.7.3-201.jcm1.fc18" target="_blank">https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/Kernel_Testing#kernel-3.7.3-201.jcm1.fc18</a><br>
> ><br>
> > Paul<br>
> > _______________________________________________<br>
> > arm mailing list<br>
> > <a href="mailto:arm@lists.fedoraproject.org">arm@lists.fedoraproject.org</a><br>
> > <a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/arm</a><br>
><br>
><br>
><br>
><br>
> I get DTB working on the panda by the following code:<br>
><br>
> # wget <a href="http://ausil.us/dtb/omap4-panda.dtb" target="_blank">http://ausil.us/dtb/omap4-panda.dtb</a> -o /root/omap4-panda.dtb<br>
><br>
> #<br>
> cat /boot/vmlinuz-3.6.10-6.fc18.armv7hl.omap /root/omap4-panda.dtb<br>
> > /root/foo.zimg<br>
><br>
> # mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e<br>
> 0x80008000 -n "3.6.10-6-DTB" -d /root/foo.zimg /boot/uboot/uImage-dtb<br>
><br>
> # rm -i /root/foo.zimg<br>
><br>
> # sed -i -e 's|\(uImage\)|\1-dtb|s' /boot/uboot/uEnv.txt<br>
><br>
> That makes an appended DTB style kernel image, and results in<br>
> /proc/device-tree<br>
><br>
><br>
<br>
</div></div>appending the dtb seems to work fine for a pandaboard, i've never<br>
personally had a pandaboard boot when loading the dtb separately<br>
<br>
Dennis<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.19 (GNU/Linux)<br>
<br>
iEYEARECAAYFAlD+/KAACgkQkSxm47BaWffdIACeMwMqcgH55FeGACEllmJVq66w<br>
IdAAn0TzGyXXQOQB78CrL3LxqQFhEwH9<br>
=Myby<br>
-----END PGP SIGNATURE-----<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div><br></div><div>Bellow is how to create an appended kernel for trimslice.</div><div>This was working on the older U-Boot 2010.09-1.03-00006-ga52694f firmware.</div>
<div><br></div><div><br></div><div><div># wget <a href="http://ausil.us/dtb/tegra20-trimslice.dtb">http://ausil.us/dtb/tegra20-trimslice.dtb</a> -O /boot/tegra20-trimslice.dtb</div><div># cat /boot/vmlinuz-3.6.10-6.fc18.armv7hl.tegra /boot/tegra20-trimslice.dtb > /root/blah.zimg</div>
<div># mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "3.6.10-6-DTB" -d /root/blah.zimg /boot/uImage-dtb</div><div><br></div><div># cat <<-EOF > /boot/boot.cmd.appended-dtb.mmc</div>
<div>setenv bootargs console=ttyS0,115200n8 root=/dev/mmcblk0p3 ro rootwait</div><div>ext2load mmc 0:1 4880000 uInitrd</div><div>ext2load mmc 0:1 4080000 uImage-dtb</div><div>bootm 4080000 4880000</div><div>EOF</div><div>
<br></div><div># mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "appended-dtb 3.6.10-6" -d /boot/boot.cmd.appended-dtb.mmc /boot/boot.scr.appended-dtb.mmc</div><div># cp -f /boot/boot.scr /boot/boot.scr_before_appended</div>
<div># cp -f /boot/boot.scr.appended-dtb.mmc /boot/boot.scr</div></div><div><br></div><div><br></div><div>Not sure the old firmware used here is able to able to load a DTB.</div><div>This test is nothing special, just wanted to ensure consumers of older trimslice with older firmware would somehow be able to load a DTB.</div>
<div>Of course we might want to consider the idea of encouraging the users to update firmware.</div><div><br></div><div>Also this firmware provides all the memory of the device:</div><div><div># grep MemTotal /proc/meminfo </div>
<div>MemTotal: 1029300 kB</div></div><div><br></div></div>-- <br><br>-Jon Disnard<div>irc: masta</div><div>fas: parasense</div>