diff options
| author | Cliff Brake <cbrake@bec-systems.com> | 2007-10-08 21:21:06 +0000 |
|---|---|---|
| committer | Cliff Brake <cbrake@bec-systems.com> | 2007-10-08 21:21:06 +0000 |
| commit | 05946bd1562d45fffb44db20e16609805398ef90 (patch) | |
| tree | 94116186e922ee017005b9a0ffa177396352bee7 | |
| parent | 8fc86a2a51d4d283d89c57482ec24bb1f7658f03 (diff) | |
cm-x270.conf: add variable for NAND flash eraseblock size
| -rw-r--r-- | conf/machine/cm-x270.conf | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/conf/machine/cm-x270.conf b/conf/machine/cm-x270.conf index a77a85186f..db3fb9ba51 100644 --- a/conf/machine/cm-x270.conf +++ b/conf/machine/cm-x270.conf @@ -17,6 +17,13 @@ require conf/machine/include/tune-xscale.inc # the following line to your local.conf: # CMX270_CONSOLE_SERIAL_PORT = "ttyS0" +# NAND flash eraseblock size +# most of the older cm-x270 modules are populated with NAND flash +# that have 128KiB eraseblocks. Recently, a user encounted +# a device that has 16KiB eraseblocks. The following define +# can be overridden in local.conf if you have one of these devices. +CMX270_NAND_ERASEBLOCK_SIZE ?= "0x20000" + # the following is for the cm-x270 L module CMX270_CONSOLE_SERIAL_PORT ?= "ttyS1" @@ -32,10 +39,10 @@ SERIAL_CONSOLE ?= "38400 ${CMX270_CONSOLE_SERIAL_PORT}" ROOT_FLASH_SIZE ?= "32" # for NAND flash. -EXTRA_IMAGECMD_jffs2 = "--little-endian --eraseblock=0x20000 --pad --no-cleanmarkers;\ +EXTRA_IMAGECMD_jffs2 = "--little-endian --eraseblock=${CMX270_NAND_ERASEBLOCK_SIZE} --pad --no-cleanmarkers;\ sumtool -i ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.jffs2 \ -o ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs-summary.jffs2 \ - -e 0x20000 -p; \ + -e ${CMX270_NAND_ERASEBLOCK_SIZE} -p; \ cd ${DEPLOY_DIR_IMAGE}; \ rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.rootfs-summary.jffs2; \ ln -s ${IMAGE_NAME}.rootfs-summary.jffs2 ${IMAGE_LINK_NAME}.rootfs-summary.jffs2 \ |