Support far various OOB layouts is lacking.

[GoogleCodeExporter]

When using NAND controllers from various chip vendors (in our case a freescale 
processor) the free OOB bytes may differ from the standard linux ones.

If the layout could be made configurable (optionally with a contrib directory 
carrying various layouts in the sources) this would help in using mkyaffs2 for 
various other platforms.

Original issue reported on code.google.com by HIGH...@gmail.com on 14 Dec 2010 at 12:23

[GoogleCodeExporter]

It's a good suggestion.
But could this problem be solved by simplying modifying the free oob 
information in the source code (such as yaffs2utils.h)?
Adding an option to support this feature is simple, but the format and the 
license will be the important things to be discussed.

Best Regards,
by Luen-Yung Lin

Original comment by penguin.lin on 20 Dec 2010 at 11:25

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

That's the current approach we took: modify the source code and add a new 
layout.
then (ab)use the page size to select another layout.

This involves patching the code for each and every NAND platform that has 
another layout. It boils down to maintainability: do you really want to modify 
the source for each and every platform?

Ultimately a small tool could be made to run on the target:
  readoobinfo /dev/mtd0
which outputs the contents of the configuration file through the use of the 
ECCGETLAYOUT ioctl call. This could then be used by the image creation tool to 
select correct placement of ECC bytes.

Original comment by HIGH...@gmail.com on 21 Dec 2010 at 9:37

[GoogleCodeExporter]

This feature is finished this morning and under debugging now,
but the integration with the "mkyaffs2" and "unyaffs2" is still implementing.

I notice the ioctl "ECCGETLAYOUT" is deprecated,
any other better suggestion.

I will merge this tool into the next version.

Original comment by penguin.lin on 1 Feb 2011 at 3:46

• Changed state: Started

[GoogleCodeExporter]

Original comment by penguin.lin on 3 Mar 2011 at 2:24

[GoogleCodeExporter]

I will start committing the codes into the trunk,
and these enhancement will be set as fixed in the several days.

Original comment by penguin.lin on 4 May 2011 at 6:39

[GoogleCodeExporter]

Original comment by penguin.lin on 7 Jul 2011 at 10:19

• Changed state: Fixed