From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: Problems with DOC 2000 on 2.4.21
Date: Mon, 04 Aug 2003 18:08:09 +0800 [thread overview]
Message-ID: <3F2E3089.40904@hectrix.com> (raw)
Dear all,
I wish to use kernel 2.4.21 with DOC 2000. In menuconfig, I selected the
followings in the MTD submenu (other options not mentioned here were all
left blank):
* Memory Technology Device (MTD) support
* Debugging
0 Debugging verbosity
M Direct char device access to MTD devices
M Caching block device access to MTD devices
M FTL (Flash Translation Layer) support
M NFTL (NAND Flash Translation Layer) support
* Write support for NFTL (BETA)
In "Self-contained MTD device drivers", I chose:
M M-Systems Disk-On-Chip 2000 and Millennium
And in "NAND Flash Device Drivers", I chose:
M NAND Device Support
* Verify NAND page writes
I successfully compiled the bzImage and modules, installed them and
rebooted. Then I run:
modprobe -a doc2000 nftl mtdchar mtdblock
But there was no message shown about anything loading. Anyway, I tried
"modprobe -a docprobe" also, but I got no message at all and modprobe
only return to the shell prompt after a long time. I wonder why I got no
message about detecting my DOC 2000.
I also tried compiling all the above features as built-in (all *) in the
kernel. Then I noticed that the kernel was probably detecting for DOC on
my computer during the reboot, with something like:
DiskOnChip 2000 found at address 0xD4000
Flash chip found: Manufacturer ID: 98, Chip ID: 73 (Toshiba:NAND 16MB
3,3V)
1 flash chips found. Total DiskOnChip size: 16 MiB
mtd: Giving out device 0 to DiskOnChip 2000
The address D4000 is exactly the address of my DOC 2000. But after the
reboot, I don't know how to access the device given out. I cat /proc/mtd
and got:
dev: size erasesize name
mtd0: 01000000 00004000 "DiskOnChip 2000"
But in /dev I can't find mtd or mtd0.
Do anyone know how to resolve these problems? Thanks in advance!!
Yours,
Selwyn Tang
next reply other threads:[~2003-08-04 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 10:08 Selwyn Tang [this message]
2003-08-04 10:23 ` Problems with DOC 2000 on 2.4.21 Roger
[not found] ` <3F2E38FE.8030800@hectrix.com>
2003-08-05 14:32 ` Roger
2003-08-06 1:24 ` Selwyn Tang
2003-08-06 7:55 ` Roger
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=3F2E3089.40904@hectrix.com \
--to=selwyn@hectrix.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