From: Frank R Callaghan <f.callaghan@ieee.org>
To: MTD <linux-mtd@lists.infradead.org>
Subject: Help with 2.4.22 MTD driver
Date: Thu, 16 Oct 2003 15:57:19 -0400 [thread overview]
Message-ID: <200310161557.19824.f.callaghan@ieee.org> (raw)
Hi All,
I have been using 2.4.19 + mdt patches for sometime with no problem, now
I must switch to 2.4.22 and I have a problem with MTD
The kernel seem to detect the chip correctly:
physmap flash device: 200000 at 9400000
Amd/Fujitsu Extended Query Table v1.1 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
mtd: Giving out device 0 to Physically mapped flash
Using physmap partition definition
Creating 2 MTD partitions on "Physically mapped flash":
0x00000000-0x001e0000 : "fixed_flash"
mtd: Giving out device 1 to fixed_flash
0x001e0000-0x00200000 : "BIOS-DO_NOT_TOUCH"
mtd: Giving out device 2 to BIOS-DO_NOT_TOUCH
but latter:
.......................
.......................
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001e0024: 0x7265
id
Further such events for this erase block will not be printed
JFFS2: Erase block at 0x001e0000 is not formatted. It will be erased
................... repeated for tree more blocks
cat /proc/mtd gives:
dev: size erasesize name
mtd0: 00200000 00010000 "Physically mapped flash"
mtd1: 001e0000 00010000 "fixed_flash"
mtd2: 00020000 00010000 "BIOS-DO_NOT_TOUCH"
I'm not sure if this correct as before with 2.4.19 it looks like this
# cat /proc/mtd
dev: size erasesize name
mtd0: 001e0000 00010000 "fixed_flash"
mtd1: 00020000 00010000 "BIOS-DO_NOT_TOUCH"
Now the flash file system on the partision is corrupt :(
can someone please give me a little guidance on how to find the problem ?
what other info would help ?
Thanks In Advance,
Frank.
reply other threads:[~2003-10-16 20:00 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=200310161557.19824.f.callaghan@ieee.org \
--to=f.callaghan@ieee.org \
--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