OneNAND: Check first or second pages for bad block information

[Kyungmin Park]

Hi, 


> I'm not sure we have to check 2nd page. Yes, Spec. says we will check 1st and 2nd ones.
> 
> It increase the boot time even though it's smaller one than others.

> My experience is that the OneNAND bad block scanning time is very small (i.e. insignicant) compared with overall boot time.
> For example:
>	2048 blocks x 2 pages x 30 microseconds per page = 0.12 seconds

I think it's big :). But if you don't mind.


> The specification says:
> 
> 	Check "FFFFh" at the 1st word of sector 0
> 	of spare area in 1st and 2nd page

> Based on the specification, I would presume that if a bad block goes un-noticed, it could be erased and written without error and only produc> e errors when the data is read back, by which time it is too late.

O.K., We follow the Spec.

I will commit your patch.

Thank you,
Kyungmin Park