From: Alexandru Harsanyi <a.harsanyi@willhart-tech.com>
To: Linux Mtd <linux-mtd@lists.infradead.org>
Subject: DOC 2000 driver (NFTL) in kernel 2.4.7
Date: Tue, 31 Jul 2001 12:40:42 +0800 [thread overview]
Message-ID: <3B6636CA.374A6E14@willhart-tech.com> (raw)
Hi,
I'm trying to configure the 2.4.7 kernel to access a DOC, and I have the
following problems:
1) Although I have only one DOC 2000, the DOC driver detects many more
(see dmesg below)
2) The DOC driver detects 3 flash chips, I only have one
3) (and this is the show stopper) The NFTL driver is not able to find a
boot record on the DOC. This is strange because I'm actually booting
from the DOC.
The previous configuration used a 2.0.36 kernel with M-System provided
drivers and it worked fine.
Here is the relevant dmesg part from the system:
----- dmesg -----
DiskOnChip 2000 found at address 0xC8000
Flash chip found: Manufacturer ID: 98, Chip ID: 6B (Toshiba TC5832DC)
3 flash chips found. Total DiskOnChip size: 12 MiB
Possible DiskOnChip with unknown ChipID FF found at 0xca000
Possible DiskOnChip with unknown ChipID 00 found at 0xcc000
Possible DiskOnChip with unknown ChipID 00 found at 0xce000
Possible DiskOnChip with unknown ChipID FF found at 0xd0000
Possible DiskOnChip with unknown ChipID FF found at 0xd2000
Possible DiskOnChip with unknown ChipID FF found at 0xd4000
Possible DiskOnChip with unknown ChipID FF found at 0xd6000
Possible DiskOnChip with unknown ChipID FF found at 0xd8000
Possible DiskOnChip with unknown ChipID FF found at 0xda000
Possible DiskOnChip with unknown ChipID FF found at 0xdc000
Possible DiskOnChip with unknown ChipID FF found at 0xde000
Possible DiskOnChip with unknown ChipID 0B found at 0xe0000
Possible DiskOnChip with unknown ChipID 00 found at 0xe2000
Possible DiskOnChip with unknown ChipID 28 found at 0xe4000
Possible DiskOnChip with unknown ChipID 00 found at 0xe6000
Possible DiskOnChip with unknown ChipID 6D found at 0xe8000
Possible DiskOnChip with unknown ChipID 07 found at 0xea000
Possible DiskOnChip with unknown ChipID 00 found at 0xec000
Possible DiskOnChip with unknown ChipID FE found at 0xee000
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftlcore.c,v 1.73 2001/06/09 01:09:43 dwmw2 Exp $
Could not find valid boot record
Could not mount NFTL device
---- end dmesg ----
Does anyone know what's the problem?
Thanx,
Alex.
next reply other threads:[~2001-07-31 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 4:40 Alexandru Harsanyi [this message]
2001-07-31 20:45 ` DOC 2000 driver (NFTL) in kernel 2.4.7 David Woodhouse
[not found] <E15RXGo-00058Q-00@pentafluge.infradead.org>
2001-08-01 3:46 ` Saul Thurrowgood
2001-08-07 9:36 ` David Woodhouse
2001-08-08 4:30 ` Alexandru Harsanyi
2001-08-08 6:42 ` David Woodhouse
2001-08-08 7:42 ` Alexandru Harsanyi
2001-08-08 8:52 ` David Woodhouse
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=3B6636CA.374A6E14@willhart-tech.com \
--to=a.harsanyi@willhart-tech.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