From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Tue, 19 May 2009 19:29:53 -0400 Subject: [U-Boot] Writing a YAFFS image to NAND In-Reply-To: <49D65B4E.6080003@freescale.com> References: <1238784243.8002.260.camel@blackhole> <49D65B4E.6080003@freescale.com> Message-ID: <200905191929.54942.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Friday 03 April 2009 14:54:06 Scott Wood wrote: > Peter Barada wrote: > > Is there support in the 2009.03 version of U-boot to allow writing a > > YAFFS image created by mkyaffs2image to NAND, including the meta-data in > > the OOB? > > Not that I know of (unless something in cmd_yaffs2.c can do it). > > > Looking over the nand write/read commands, they look to ignore the OOB > > data interleaved in the image (i.e. 2048+16 bytes per page for > > large-block NAND). I did see a patch from fmandarino on the list, but > > that doesn't look to be in the 2009.03 codebase. > > That was several years ago; if someone wants to submit a proper patch > against current u-boot (without the pre-2.6.18 support, or at least with > the newer format being the default), I'll apply it. Better yet would be > a more general mechanism whereby the user specifies how many OOB bytes > are interleaved in the supplied image, without any specific knowledege > of yaffs. here's an updated patch for 2009.03, but i dont think it'll work with latest master due to all the oob stuff being dropped ? http://git.denx.de/?p=u-boot/u-boot-blackfin.git;a=commitdiff;h=44f07de8cc94836cd3b0fd2fb0cf8b8651461087 -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090519/f87d684a/attachment.pgp