Eraseall crash on uclinux 2.4.19

[David Woodhouse]

daniel.haensse at alumni.ethz.ch said:
> on line 142 a eraseall /dev/mtd0 stops with a failed 11 (EAGAIN)

>  Any idea what might be wrong?

Er, no -- I can't see how the erase function can return EAGAIN. Where's it 
coming from?


> Another question: Can we ignore the AMD_BOOTLOC_BUG and switch this
> off? Is this also Fujitsu  related? 

I think you can ignore it. It's only valid for AMD parts, I believe. Other 
people managed to get a simple table correct. Someone was going to clean 
that up.

--
dwmw2