inconsistent behaviour with onenand with 2.6.24 kernel

[Abhijit Singh]

Hi Adrian,

On Fri, Apr 18, 2008 at 12:49 PM, Adrian Hunter
<ext-adrian.hunter at nokia.com> wrote:
> Abhijit Singh wrote:
> > I am facing some problem with onenand with the kernel 2.6.24.
> >
>
> Yes it is broken.
>
> Here is a list on OneNAND patches in 2.6.25
>
> 69d79186dc48ca22a0ce69511bef8ef6c2465ada [MTD] [OneNAND] Use pre-alloced oob
> buffer instead of local buffer
> 978cb38a296fceac82a8a757f6387d7ef2a21ac6 [MTD] [OneNAND] Use the u_char
> instead of char in oobbuf
> b2581be291aa8595eadf3d6933d04d0f1d01b46d [MTD] [OneNAND] Check the initial
> bad block using ONENAND_CTRL_ERROR
> e71f04fc9234b14636887ceb5862755f1690642c [MTD] [OneNAND] Get correct density
> from device ID
> b21b72cf33bb212414c1d967850e261b795befa4 [MTD] [OneNAND] Consolidate OneNAND
> operation order
> 9d2f0b7a3de28d06ba4011b835b9a7e772553f0d [MTD] [OneNAND] fix call to
> onenand_verify when writing subpages
> d0b36d8cc8f345ec5faadd15daaecfb409b94523 [MTD] [OneNAND] Do not release chip
> twice
>
> The last one "[MTD] [OneNAND] Do not release chip twice" is absolutely
> essential, so here it is:

I have tried all the above mentioned patches. But the status is same.
behaviour is inconsistent.
It still leads to system hangs while writing big files. Any other pointers ?
But it is working fine on 2.6.20 kernel.


Abhijit