From: David Vrabel <dvrabel@arcom.com>
To: linux-mtd list <linux-mtd@lists.infradead.org>
Subject: Re: Unable to access JFFS2 filesystem
Date: Wed, 24 Dec 2003 09:39:24 +0000 [thread overview]
Message-ID: <3FE95ECC.8010502@arcom.com> (raw)
In-Reply-To: <357032fbc0.2fbc035703@shaw.ca>
> - cfi_cmdset_0002: Disabling fast programming due to code
> brokenness. Any patch to cfi_cmdset_0002.c to fix this.
I'm not aware of one. It doesn't look like it would be that much of a
performance increase anyway.
> - When I accessed the mounted JFFS2 file system, I got "Chip not
> ready after erase suspended".
Erase-suspends for AMD chips are broken in current CVS. I posted a patch
to the list earlier this month fixing it partitially and disabling the
remainging broken bit (which decreased performance significantly).
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end. Email to and from Arcom is automatically monitored for operational and lawful business reasons.
This message has been checked for all viruses by MessageLabs Virus Control Centre.
next prev parent reply other threads:[~2003-12-24 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 19:25 Unable to access JFFS2 filesystem thomaspang
2003-12-24 9:39 ` David Vrabel [this message]
2003-12-30 17:32 ` Thayne Harbaugh
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 18:39 thomaspang
2004-01-02 11:12 ` David Vrabel
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=3FE95ECC.8010502@arcom.com \
--to=dvrabel@arcom.com \
--cc=linux-mtd@lists.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