No oob scheme defined for oobsize 218

[Joo Aun Saw]

I'm running UBI(FS) on top of it, so I don't need the OOB area. In
this case, what's the best way to work around this problem? Should I
use a smaller ECC layout or disable ECC?

How is the ECC layout defined, as in what decides how big the
eccbytes, eccpos, oobfree should be?




On Tue, Jan 10, 2012 at 4:36 AM, Brian Norris
<computersforpeace at gmail.com> wrote:
> On Sun, Jan 8, 2012 at 10:34 PM, Joo Aun Saw <jasaw at dius.com.au> wrote:
>> I'm getting this error and hope someone can help me.
>>
>> ONFI flash detected
>> ONFI param page 0 valid
>> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron MT29F8G08AAA)
>> No oob scheme defined for oobsize 218
>>
>> Do I need to define struct nand_ecclayout nand_oob_218? or can I use
>> the nand_oob_128 ecc layout?
>> I'm running Linux version 3.0.4.
>
> This may depend on what hardware/driver, what type of ECC you're
> using, and what filesystem you're using on top of your MTD. It's
> possible you can get by with just using a "smaller" ECC layout,
> especially if you're not using the OOB area for filesystem data (e.g.,
> UBI(FS), which doesn't use OOB). You just won't have as much "free"
> OOB area (again, doesn't matter much for UBI(FS)) and your ECC layout
> might not reflect the actual positioning of your ECC data.
>
> Brian