From: David Hamm <dhamm@itrepro.com>
To: mtd@infradead.org
Subject: DiskOnChip 2000 again
Date: Wed, 17 Jan 2001 16:48:53 -0500 [thread overview]
Message-ID: <01011716530001.08043@workbox.atlanta.itserve.com> (raw)
I've tried a number of things. When I patch the 2.4.0 kernel with the M-Sys
patches in won't compile. So I've compiled using the MTD stuff and plundered
through making the entrys in the /dev directory. Below is my /dev/nftl entry.
brw-rw---- 1 root root 93, 0 Jan 12 22:39 /dev/nftl
But when I try to fdisk /dev/nftl the modules load and print the following on
the console.
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
Using configured probe address 0xd000
Possible DiskOnChip with unknown ChipID 63 found at 0xd000
Any suggestions?
-- ---------------------------------
David Hamm
Systems Analyst
Imaging Technologies Services Inc.
email: dhamm@itrepro.com
voice: 404-870-6663
---------------------------------
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2001-01-17 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 21:48 David Hamm [this message]
2001-01-18 11:28 ` DiskOnChip 2000 again 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=01011716530001.08043@workbox.atlanta.itserve.com \
--to=dhamm@itrepro.com \
--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