ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Ltib] YAFFS2 tool/deployment method


From: Newell, James C.
Subject: RE: [Ltib] YAFFS2 tool/deployment method
Date: Fri, 18 Sep 2009 17:24:20 -0400

The .spec file references a 03 patch that wasn’t included in the email.

 

From: address@hidden [mailto:address@hidden On Behalf Of Peter Barada
Sent: Friday, September 18, 2009 1:03 PM
To: address@hidden
Subject: [Ltib] YAFFS2 tool/deployment method

 

Attached are components containing a new mkyaffs2image tarball, patches and .spec file that can deal with a device table, and can be used by LTIB to create a YAFFS2 root filesystem image as a new YAFFS2 deployment method.

The following patch to current LTIB CVS should get it running (my LTIB version is based on version 8.4.1 and hacked up pretty hard so YMMV):

 
address@hidden:~/work/logic/cvs-ltib/ltib$ cvs diff -up .
Index: bin/Ltibutils.pm
===================================================================
RCS file: /sources/ltib/ltib/bin/Ltibutils.pm,v
retrieving revision 1.27
diff -u -p -r1.27 Ltibutils.pm
--- bin/Ltibutils.pm  14 Sep 2009 09:39:16 -0000     1.27
+++ bin/Ltibutils.pm  18 Sep 2009 16:53:00 -0000
@@ -682,6 +682,10 @@ if [ "$pcf->{DEPLOYMENT_JFFS2}" = "y" ]
 then
     rm -f $tdir/rootfs.jffs2
 fi
+if [ "$pcf->{DEPLOYMENT_YAFFS2}" = "y" ]
+then
+    rm -f $tdir/rootfs.yaffs2
+fi
 if [ "$pcf->{DEPLOYMENT_CRAMFS}" = "y" ]
 then
     rm -f $tdir/cramfs.*
@@ -876,6 +880,12 @@ then
     mkfs.jffs2 -n $pad_opt -D $dev_tab -U $endian -e $pcf->{DEPLOYMENT_ERASE_BLOCK_SIZE} -d $stage -o $tdir/rootfs.jffs2
     ln -sf $tdir/rootfs.jffs2 $tdir/rootfs_image
 fi
+if [ "$pcf->{DEPLOYMENT_YAFFS2}" = "y" ]
+then
+    mkfs.yaffs2 -r -p $stage/etc/passwd -N -D $dev_tab $endian $stage $tdir/rootfs.yaffs2;
+    ln -sf $tdir/rootfs.yaffs2 $tdir/rootfs_image
+fi
+fi
 if [ "$pcf->{DEPLOYMENT_CRAMFS}" = "y" ]
 then
     mkfs.cramfs -q -D $dev_tab $endian $stage $tdir/rootfs.cramfs
Index: config/platform/host/ltib.preconfig
===================================================================
RCS file: /sources/ltib/ltib/config/platform/host/ltib.preconfig,v
retrieving revision 1.3
diff -u -p -r1.3 ltib.preconfig
--- config/platform/host/ltib.preconfig      27 Aug 2009 08:31:14 -0000     1.3
+++ config/platform/host/ltib.preconfig      18 Sep 2009 16:53:00 -0000
@@ -378,6 +378,7 @@ CONFIG_X11_NONE=y
 # CONFIG_PKG_XORG_X11_TWM is not set
 # CONFIG_PKG_XTERM is not set
 # CONFIG_PKG_YAFFS_UTILS is not set
+CONFIG_PKG_MKYAFFS2IMAGE=y
 # CONFIG_PKG_ZAPTEL is not set
 # CONFIG_PKG_ZLIB is not set
 
Index: config/userspace/deployment.lkc
===================================================================
RCS file: /sources/ltib/ltib/config/userspace/deployment.lkc,v
retrieving revision 1.4
diff -u -p -r1.4 deployment.lkc
--- config/userspace/deployment.lkc  14 Sep 2009 09:39:16 -0000     1.4
+++ config/userspace/deployment.lkc  18 Sep 2009 16:53:00 -0000
@@ -15,6 +15,11 @@ choice 
         help
             build a jffs2 flash filesystem image
 
+    config DEPLOYMENT_YAFFS2
+        bool "yaffs2"
+        help
+            build a yaffs2 flash filesystem image
+
     config DEPLOYMENT_RAMDISK
         bool "ext2.gz ramdisk"
         help
@@ -51,6 +56,7 @@ endchoice
 
 config SYSCFG_DEPLOYMENT_STYLE
     string
+    default YAFFS2     if DEPLOYMENT_YAFFS2
     default JFFS2      if DEPLOYMENT_JFFS2
     default RAMDISK    if DEPLOYMENT_RAMDISK
     default CRAMFS     if DEPLOYMENT_CRAMFS
@@ -113,7 +119,7 @@ config SYSCFG_READONLY_FS
     default n
 
 config SYSCFG_TMPFS_SIZE
-    depends SYSCFG_READONLY_FS || DEPLOYMENT_JFFS2
+    depends SYSCFG_READONLY_FS || DEPLOYMENT_JFFS2 || DEPLOYMENT_YAFFS2
     string "tmpfs size"
     default "512k"
     help
@@ -124,10 +130,10 @@ config SYSCFG_TMPFS_SIZE
        from the total available RAM to the system.
 
 config SYSCFG_RAM_DIRS
-    depends SYSCFG_READONLY_FS || DEPLOYMENT_JFFS2
+    depends SYSCFG_READONLY_FS || DEPLOYMENT_JFFS2 || DEPLOYMENT_YAFFS2
     string "Place these dirs in writable RAM"
     default "/tmp /etc /var" if SYSCFG_READONLY_FS
-    default "/tmp /var"      if DEPLOYMENT_JFFS2
+    default "/tmp /var"      if DEPLOYMENT_JFFS2 || DEPLOYMENT_YAFFS2
     help
        Flash may only be erased a finite number of times (of the order
        of 100000 times for a NOR device).  If you deploy to Flash,
@@ -256,7 +262,7 @@ config DEPLOYMENT_STRIP_MORE
         .ko are stripped like this.
 
 config DEPLOYMENT_PADDING_KB
-    depends ! DEPLOYMENT_NFS && ! DEPLOYMENT_JFFS2
+    depends ! DEPLOYMENT_NFS && ! DEPLOYMENT_JFFS2 && ! DEPLOYMENT_YAFFS2
     default "0"
     string "Allocate extra space (Kbytes)"
     help
Index: config/userspace/packages.lkc
===================================================================
RCS file: /sources/ltib/ltib/config/userspace/packages.lkc,v
retrieving revision 1.34
diff -u -p -r1.34 packages.lkc
--- config/userspace/packages.lkc    3 Sep 2009 09:14:53 -0000      1.34
+++ config/userspace/packages.lkc    18 Sep 2009 16:53:00 -0000
@@ -3527,6 +3527,12 @@ config PKG_YAFFS_UTILS
       This package contains YAFFS file system utilities to create YAFFS
       image and partition.
 
+config PKG_MKYAFFS2IMAGE
+    bool "mkyaffs2image"
+    help
+        mkfs.yaffs2 utility to create YAFFS2 image of directory
+        structure suitable for burning into nand via u-boot.
+
 config PKG_ZAPTEL
     bool "zaptel"
     select PKG_KERNEL_LEAVESRC
 

I've used it successfully to create a YAFFS2 image that I can boot my OMAP35x boards as the root filesystem(once burned via u-boot).  Hopefully people find this useful...

--
Peter Barada <address@hidden>
Logic Product Development, Inc.

 


CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please immediately notify the sender by e-mail at the address shown. This e-mail transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity to whom it is intended even if addressed incorrectly. Please delete it from your files if you are not the intended recipient. Thank you for your compliance.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]