MTD & JFFS on Arcom SBC

[mark.langsdorf at amd.com]

I'm getting a similar set of error messages with
my AMD flash chips.

I posted a partial message list (for some reason, the
MTD printks weren't being collected properly) under the
title "Odd behavior of JFFS with AMD chips - kernel panic!"
on Monday.

-Mark Langsdorf
AMD, Inc.

> -----Original Message-----
> From: Micheal Kelly [mailto:michealk at thegravitywell.dhs.org]
> Sent: Thursday, December 07, 2000 11:35 AM
> To: mtd at infradead.org
> Subject: MTD & JFFS on Arcom SBC
> 
> 
> Hi all,
> 
> I've got an Arcom MediaGX board here that I'm trying to get 
> working w/Linux 
> 2.4-test12pre7 ...  Has anyone else tried the latest MTD 
> source from CVS with 
> this board?
> 
> It boots, loads the kernel, and it *does* identify the 
> onboard flash - it 
> even seems able to *read* from the flash (a JFFS 
> filesystem)... but when a 
> write occurs, the screen fills with errors - they go 
> scrolling by too quickly 
> to see, but they're something along the lines of:
> 
> Chip not ready for buffer write ...  XStatus = 30  bstatus = 0
> 
> and
> 
> flash_safe_write returned 5
> 
> After a few seconds, the screen fills with:
> 
> jffs_garbage_collect_thread():  free size == 0 This is BAD.
> 
> :)
> 
> Also,
> I inadvertently compiled the latest MTD sources from CVS with 
> the JFFS 
> included in the 2.4 sources and while I still couldn't write 
> to the flash, I 
> wouldn't get clobbered by 1000's of errors - I'd get one 
> "Chip not ready", 
> and then get the # prompt back....
> 
> Anyone have this working with 2.4?
> 
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org
> 



To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org