[fedora-arm] Distributing DTB's for Fedora 18 RC1

[Jon]

On Tue, Jan 22, 2013 at 2:54 PM, Dennis Gilmore <dennis at ausil.us> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> El Tue, 22 Jan 2013 14:15:57 -0600
> Jon <jdisnard at gmail.com> escribió:
> > On Tue, Jan 22, 2013 at 1:51 PM, Paul Whalen <pwhalen at redhat.com>
> > wrote:
> >
> > >
> > > Summary of discussion from #fedora-arm
> > > --------------------------------------
> > >
> > > Dennis Gilmore will be creating a kernel-dtb subpackage for the 3.7
> > > kernel, using 'make dtb' during the kernel build.
> > >
> > > The plan is to pull in the 3.7 dtb's into our 3.6 based F18 RC1
> > > release. We will
> > > only be including the DTB's where needed, for Trimslice and
> > > vexpress which do not
> > > boot without a DTB. The Pandaboard will boot the 3.7 without use of
> > > a DTB, and Highbank
> > > provides it's own.
> > >
> > > For a full summary of the testing:
> > >
> > >
> https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/Kernel_Testing#kernel-3.7.3-201.jcm1.fc18
> > >
> > > Paul
> > > _______________________________________________
> > > arm mailing list
> > > arm at lists.fedoraproject.org
> > > https://admin.fedoraproject.org/mailman/listinfo/arm
> >
> >
> >
> >
> > I get DTB working on the panda by the following code:
> >
> > # wget http://ausil.us/dtb/omap4-panda.dtb -o /root/omap4-panda.dtb
> >
> > #
> > cat /boot/vmlinuz-3.6.10-6.fc18.armv7hl.omap  /root/omap4-panda.dtb
> > > /root/foo.zimg
> >
> > # mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e
> > 0x80008000 -n "3.6.10-6-DTB" -d /root/foo.zimg  /boot/uboot/uImage-dtb
> >
> > # rm -i /root/foo.zimg
> >
> > # sed -i -e 's|\(uImage\)|\1-dtb|s' /boot/uboot/uEnv.txt
> >
> > That makes an appended DTB style kernel image, and results in
> > /proc/device-tree
> >
> >
>
> appending the dtb seems to work fine for a pandaboard, i've never
> personally had a pandaboard boot when loading the dtb separately
>
> Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlD+/KAACgkQkSxm47BaWffdIACeMwMqcgH55FeGACEllmJVq66w
> IdAAn0TzGyXXQOQB78CrL3LxqQFhEwH9
> =Myby
> -----END PGP SIGNATURE-----
>
>

Bellow is how to create an appended kernel for trimslice.
This was working on the older U-Boot 2010.09-1.03-00006-ga52694f  firmware.


# wget http://ausil.us/dtb/tegra20-trimslice.dtb  -O
/boot/tegra20-trimslice.dtb
# cat /boot/vmlinuz-3.6.10-6.fc18.armv7hl.tegra
 /boot/tegra20-trimslice.dtb > /root/blah.zimg
# 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

# cat <<-EOF > /boot/boot.cmd.appended-dtb.mmc
setenv bootargs console=ttyS0,115200n8 root=/dev/mmcblk0p3 ro rootwait
ext2load mmc 0:1 4880000 uInitrd
ext2load mmc 0:1 4080000 uImage-dtb
bootm 4080000 4880000
EOF

# 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
# cp -f /boot/boot.scr /boot/boot.scr_before_appended
# cp -f /boot/boot.scr.appended-dtb.mmc  /boot/boot.scr


Not sure the old firmware used here is able to able to load a DTB.
This test is nothing special, just wanted to ensure consumers of older
trimslice with older firmware would somehow be able to load a DTB.
Of course we might want to consider the idea of encouraging the users to
update firmware.

Also this firmware provides all the memory of the device:
# grep MemTotal /proc/meminfo
MemTotal:        1029300 kB

-- 

-Jon Disnard
irc: masta
fas: parasense
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/arm/attachments/20130122/fceb23b7/attachment.html>