http://users.actrix.co.nz/manningc/yaffs/HowYaffsWorks.pdf
YAFFS2 mode is designed to support a wider range of devices and sparearea
layouts. Thus, YAFFS2 does not decide
which bytes to mark but instead calls driver functions to determine whether the
block is bad, or to mark it bad.
Does anyone know which OOB bytes ARE used to mark bad blocks on the stock TS
installation?
It seems that yaffs2 differentiates between factory BB and its own BB
detection.
The first step in understanding this problem is to examine the detail of what
has happened. Rather than just blasting all BB markers , real and false. A
technique which apparently does not always work.
thx
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|