View Single Post
  #56 (permalink)  
Old 02-21-2011, 03:25 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Threadstarter
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: [NAND ROM] - Rom Dev only

Quote:
Originally Posted by arrrghhh View Post
Sounds tedious... isn't there a way we can identify bad blocks and intentionally avoid them? Because I would assume the bad blocks are going to be in different places for everyone.

Everything I've read says bad blocks aren't a big deal, even the Wikipedia article...
ur absolutely right. we should be able to handle them with no issues.

from what i understand a format should mark the bad blocks so they can be skipped. So if you do a task 28/29 again, does it still say you have bad blocks? i guess it would be nice to know if these blocks can be avoided by the boot-loader since it has the ability to detect em.
__________________
Reply With Quote