From: Xavier DEBREUIL <xde@inventel.fr>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Abraham vd Merwe <abraham@2d3d.co.za>,
MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: non cfi flash memory
Date: Tue, 19 Jun 2001 19:09:08 +0200 [thread overview]
Message-ID: <3B2F8734.93729473@inventel.fr> (raw)
In-Reply-To: 10928.992958699@redhat.com
David Woodhouse a écrit :
>
> abraham@2d3d.co.za said:
> > I really think those cfi_cmdset_*.c chip driver modules should be
> > renamed to something else. It's really confusing since they're not
> > only for CFI chips.
>
> I agree.
>
I have 320C3 versions which seem to have cfi properties.
This is a debugged output from initialisation :
cfi_qry_mode, cfi->cfi_mode : 0x0
clep7211: Found 2 x16 devices at 0x0 in 32-bit mode
Number of erase regions: 2
Erase Region #0: BlockSize 0x10000 bytes, 63 blocks
Erase Region #1: BlockSize 0x2000 bytes, 8 blocks
Primary Vendor Command Set: 0003 (Intel/Sharp Standard)
Primary Algorithm Table at 0035
Alternative Vendor Command Set: 0000 (None)
No Alternate Algorithm Table
Vcc Minimum: 2.7 V
Vcc Maximum: 3.6 V
Vpp Minimum: b.4 V
Vpp Maximum: c.6 V
Typical byte/word write timeout: 32 µs
Maximum byte/word write timeout: 512 µs
Full buffer write not supported
Typical block erase timeout: 1024 µs
Maximum block erase timeout: 8192 µs
Chip erase not supported
Device size: 0x400000 bytes (4 MiB)
Flash Device Interface description: 0x0001
- x16-only asynchronous interface
Max. bytes in buffer write: 0x1
Number of Erase Block Regions: 2
check_cmd_set, type : 0x3
cfi_qry_mode, cfi->cfi_mode : 0x0
Intel/Sharp Extended Query Table at 0x0035
Feature/Command Support: 0066
- Chip Erase: unsupported
- Suspend Erase: supported
- Suspend Program: supported
- Legacy Lock/Unlock: unsupported
- Queued Erase: unsupported
- Instant block lock: supported
- Protection Bits: supported
- Page-mode read: unsupported
- Synchronous read: unsupported
Supported functions after Suspend: 01
- Program after Erase Suspend: supported
Block Status Register Mask: 0003
- Lock Bit Active: yes
- Valid Bit Active: yes
Vcc Logic Supply Optimum Program/Erase Voltage: 0.7 V
Vpp Programming Supply Optimum Program/Erase Voltage: 0.0 V
JEDEC ID: 89 C4
number of CFI chips: 1
0: offset=0x0,size=0x20000,blocks=63
1: offset=0x7e0000,size=0x4000,blocks=8
Creating 2 MTD partitions on "clep7211":
0x00000000-0x00100000 : "boot partition"
mtd: Giving out device 0 to boot partition
0x00100000-0x00400000 : "cramfs partition"
mtd: Giving out device 1 to cramfs partition
clep7211 flash access initialized
Is the number of CFI chips: 1 correct since I have two x16 flash in
parallel to have a 32 bit bus ?
And when I try to eraseall /dev/mtd0, I have the following problem :
/dev # eraseall /dev/mtd0
MTD_open
MTD_ioctl
Erasing 128 KibMTD_ioctl
yte @ 0 -- 0 % complete.
eraseall: /dev/mMTD_ioctl
td0: MTD Erase failure: Read-only file system
Erasing 128 Kibyte @ 20000 -- 12 % complete.
eraseall: /dev/mMTD_ioctl
td0: MTD Erase failure: Read-only file system
Erasing 128 Kibyte @ 40000 -- 25 %
complete.
...
(777 for /dev/mtd0 access)
Xavier
prev parent reply other threads:[~2001-06-19 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 13:04 non cfi flash memory Xavier DEBREUIL
2001-06-19 13:24 ` David Woodhouse
2001-06-19 13:43 ` Abraham vd Merwe
2001-06-19 13:51 ` David Woodhouse
2001-06-19 17:09 ` Xavier DEBREUIL [this message]
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=3B2F8734.93729473@inventel.fr \
--to=xde@inventel.fr \
--cc=abraham@2d3d.co.za \
--cc=dwmw2@infradead.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 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.