From: Ciro Cattuto <ciro@prosa.it>
To: mtd@infradead.org
Subject: DOC2000 & NFTL problems
Date: Wed, 2 Aug 2000 13:48:51 +0200 [thread overview]
Message-ID: <20000802134851.A2924@localhost> (raw)
Hello,
I decided to give a try to the DOC2000/NFTL driver included in mtd.
I have an Eurotech PC104 SBC with a DOC socket. I'm using a 2 Mb DOC2000,
enabled in the SBC BIOS and mapped at 0xd8000.
Under DOS everything works fine: the systems detects, identifies and
formats the DOC. Everything is also fine with the binary-only Linux driver
provided by M-Systems, under Linux 2.0.38.
Next, I try Linux 2.2.16 with the mtd driver and patch.
---------------------------------------------------------------------
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip 2000 found at address 0xD8000
1 flash chips found. Total DiskOnChip size: 2 Mb
Ignoring DiskOnChip 2000 at 0xDA000 - already configured
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.37 2000/07/26 10:02:27 dwmw2 Exp $
---------------------------------------------------------------------
...then I get the following message, repeated for all EUNs (0-511)...
---------------------------------------------------------------------
EUN 506: EraseMark not 0x3c69 (0xffff 0xffff instead)
---------------------------------------------------------------------
...and when it comes to detecting the partition, I get:
---------------------------------------------------------------------
nftla: unknown partition table
---------------------------------------------------------------------
NOTE: there _is_ a valid NFTL partition on the DOC, while the above happens.
Okay, now I try to format the DOC using nftl_format: no errors.
When I try to fdisk /dev/nftla, though, I get an invalid partition table.
Any attempt to write a new partition table results in the following:
---------------------------------------------------------------------
NFTL_writeblock(): Cannot find block to write to
end_request: I/O error, dev 5d:00 (unknown), sector 2
No Virtual Unit Chains available for folding. Failing request
Cannot make free space.
---------------------------------------------------------------------
...I'm probably missing something obvious, but I would still appreciate
some feedback on this problem. Thank you.
Cheers,
Ciro
--
Ciro Cattuto, Open Source Developer, Linuxcare Italia SpA
Tel. +39.338.3002140 Fax +39.049.8036484
ciro@linuxcare.com http://www.linuxcare.com/
ciro@prosa.it http://www.prosa.it/
Linuxcare. Support for the revolution.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-08-02 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 11:48 Ciro Cattuto [this message]
[not found] ` <3988F8D2.FD1AB1E2@sis.com.tw>
2000-08-03 10:58 ` DOC2000 & NFTL problems Ciro Cattuto
2000-08-04 1:54 ` Ollie Lho
2000-08-04 2:17 ` Ciro Cattuto
2000-08-04 7:45 ` 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=20000802134851.A2924@localhost \
--to=ciro@prosa.it \
--cc=mtd@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