From: Micheal Kelly <michealk@thegravitywell.dhs.org>
To: "mtd@infradead.org" <mtd@infradead.org>
Subject: MTD & JFFS on Arcom SBC
Date: Thu, 7 Dec 2000 12:34:30 -0500 [thread overview]
Message-ID: <0012071234300I.24907@morpheus.espial.com> (raw)
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@infradead.org
next reply other threads:[~2000-12-07 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 17:34 Micheal Kelly [this message]
2000-12-07 18:08 ` MTD & JFFS on Arcom SBC Michiel Ronsse
2000-12-07 18:55 ` Micheal Kelly
2000-12-12 9:24 ` Michiel Ronsse
2000-12-12 10:35 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2000-12-07 17:57 mark.langsdorf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0012071234300I.24907@morpheus.espial.com \
--to=michealk@thegravitywell.dhs.org \
--cc=mtd@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox