* Re: Eraseall crash on uclinux 2.4.19
[not found] <200210082238.02460.haensse@swissembedded.com>
@ 2002-10-08 20:53 ` David Woodhouse
0 siblings, 0 replies; only message in thread
From: David Woodhouse @ 2002-10-08 20:53 UTC (permalink / raw)
To: daniel.haensse; +Cc: JFFS developer mailing list, linux-mtd
daniel.haensse@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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-10-08 20:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200210082238.02460.haensse@swissembedded.com>
2002-10-08 20:53 ` Eraseall crash on uclinux 2.4.19 David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox