From: Ian Campbell <icampbell@arcomcontrols.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] JFFS on an MTDRAM device
Date: 30 Oct 2002 12:33:57 +0000 [thread overview]
Message-ID: <1035981237.32294.72.camel@LinuxDev> (raw)
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Hi,
I needed the attached patch to allow a JFFS2 filesystem to be mounted
using an MTDRAM driver (actually an SRAM chip).
Without it I get lots of warnings in jffs2_erase_callback: "Erase at
0x%08x finished, but state != MTD_ERASE_DONE. State is 0x%x instead."
Cheers,
Ian.
--
Ian Campbell
Design Engineer
Arcom Control Systems Ltd,
Clifton Road,
Cambridge CB1 7EA
United Kingdom
Tel: +44 (0)1223 403465
E-Mail: icampbell@arcomcontrols.com
Web: http://www.arcomcontrols.com
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
[-- Attachment #2: mtd.ram.erase.patch --]
[-- Type: text/plain, Size: 588 bytes --]
? mtd.ram.erase.patch
? drivers/mtd/chips/.map_ram.c.swp
Index: drivers/mtd/chips/map_ram.c
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/chips/map_ram.c,v
retrieving revision 1.14
diff -u -r1.14 map_ram.c
--- drivers/mtd/chips/map_ram.c 2 Oct 2001 15:05:12 -0000 1.14
+++ drivers/mtd/chips/map_ram.c 30 Oct 2002 12:20:06 -0000
@@ -107,6 +107,8 @@
for (i=0; i<instr->len; i++)
map->write8(map, 0xFF, instr->addr + i);
+ instr->state = MTD_ERASE_DONE;
+
if (instr->callback)
instr->callback(instr);
reply other threads:[~2002-10-30 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1035981237.32294.72.camel@LinuxDev \
--to=icampbell@arcomcontrols.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.