Re: [Ltib] Hardcoded 'ppc' strings in Ltibutils.pm

[Stuart Hughes]

Hi Andreas,

Thanks for finding that, the 68k guys must have missed it (I think they only just moved to u-boot?).

I've checked in the following change that should fix it:

Index: bin/Ltibutils.pm
===================================================================
RCS file: /sources/ltib/ltib/bin/Ltibutils.pm,v
retrieving revision 1.13
diff -u -r1.13 Ltibutils.pm
--- bin/Ltibutils.pm    4 Apr 2008 15:48:10 -0000       1.13
+++ bin/Ltibutils.pm    16 Sep 2008 17:00:58 -0000
@@ -650,7 +650,7 @@
 rm -f vmlinux.gz.uboot

 mkimage -n 'Linux for $pcf->{PLATFORM}' \\
-        -A ppc -O linux -T kernel -C gzip \\
+        -A $pcf->{LINTARCH} -O linux -T kernel -C gzip \\
         -d $vmlinuz $outpath
 TXT
     return 1;
@@ -846,7 +846,7 @@
 then
     echo "creating a uboot ramdisk image: rootfs.ext2.gz.uboot"
     mkimage -n 'uboot ext2 ramdisk rootfs' \\
-        -A ppc -O linux -T ramdisk -C gzip \\
+        -A $pcf->{LINTARCH} -O linux -T ramdisk -C gzip \\
         -d $tdir/rootfs.ext2.gz $tdir/rootfs.ext2.gz.uboot
 fi
 if [ "$pcf->{DEPLOYMENT_JFFS2}" = "y" ]


Regards, Stuart

On Tue, 2008-09-16 at 09:17 -0700, address@hidden wrote:
>     
>     Hi guys,
>     
>     I'm using the new mcfv4e ltib release and found a couple of hard coded strings in bin/Ltibutils.pm
>     They are all related to building a u-boot image, using mkimage. For instance, line 852: mkimage -n 'uboot ext2 ramdisk rootfs' \\ -A ppc -O linux -T ramdisk -C gzip \\
>     The new u-boot(1.3.3) will complain about the architecture not being m68k.
>     
>     I've changed it from ppc to m68k on my end but I'm sure there is a better, more generic approach.
>     
>     Best,
>     Andreas
>     
>     
>     ConMed Linvatec
>     7416 Hollister Ave.
>     Goleta, CA 93117
>     
>     http://www.conmed.com