On 06-09-13 17:23 +0400, Vitaly Wool wrote:
> On 9/13/06, Jonathan McDowell <noodles@earth.li> wrote:

[balloon people - this is from thread starting here:
http://aleph1.co.uk/lurker/thread/20060913.132332.e9966350.en.html]

> >Enabling the CONFIG_YAFFS_DOES_ECC option should still work though,
> >shouldn't it? While I agree that using the MTD ECC is probably saner I'm
> >guessing that if yaffs does things slightly differently that method
> >still needs support - eg for other OSes that might use yaffs partitions
> >that need mounted under Linux or bootloaders.

Yes. Yaffs needs to be able to do it's own ECC for YAFFS/direct or
indeed any other situation where there isn't something else like MTD
to do the work for it.
 
> The problem is that yaffs tries to introduce its own OOB layout in
> this case what is fundamentally wrong. The current version of MTD does
> *not* allow OOB layout info substitution (which is absolutely right)
> so there's no way to support CONFIG_YAFFS_DOES_ECC in recent kernels
> other than by introducing evil and ugly hacks.

OK, yes it does sound like this option should simply be disallowed for
2.6.17+, or at least documented as 'do not use - it won't work without
horrible hackery'.

That means balloon project will have to change bootloader and mkyaffsimage to
match for 2.6 use. This is a pain, but now is the time to do it,
before we have serious backwards compatibility issues (few people are
using 2.6 on balloon in the wild so far).

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/                 play: http://wookware.org/