DOC + MTD + Advantech Biscuit = nothing?

DOC + MTD + Advantech Biscuit = nothing?

[John Whipple]

Hello,

I'm using a PCM-4823, Linux 2.2.17 with the most recent CVS patch (dated
Oct 25).  I achieve the same result with DOC2000 4MB, DOC2000 8MB, and
Millenium 8MB, whether modular or built-in:

Upon bootup/insertion of modules:

Initializing MTD Layer
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
M-Systems NAND Flash Translation Layer driver. (C) 1999 MVHI
$Id: mtd-patch-2.2.17,v 1.1 2000/10/25 19:04:35 sjhill Exp $

and when I run "fdisk /dev/nftla":

NFTL_open
ENODEV: thisNFTL = 0, minor = 23808, ip = c0a34440, fp = c056a4a0
NFTL_open
ENODEV: thisNFTL = 0, minor = 23808, ip = c0a34440, fp = c056a4a0

Obviously the DOC is not being found, but If I have the address jumpered
to something other than D400, I get:

unable to register NFTL block device

Any helpful hints?  I need them!

-- 
John Whipple / Geek Dept., BroadLink Communications, Inc. / Linux 2.2
Calm down, they're just zeroes and ones.


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: DOC + MTD + Advantech Biscuit = nothing?

[David Woodhouse]

On Fri, 27 Oct 2000, John Whipple wrote:

> Obviously the DOC is not being found,

Looks like it - can you check it's not turning up in /proc/mtd? 
When using modules, make sure doc2000.o and doc2001.o are either loaded
before docprobe.o, or they're somewhere where modprobe can find and
autoload them.


> but If I have the address jumpered to something other than D400, I get:
> unable to register NFTL block device

That really shouldn't depend on where the DiskOnChip is jumpered to or
whether it's found or not. Play with different locations for it until you
get it to turn up in /proc/mtd. Worry about NFTL later. The error message
you quoted looks like you tried to load the NFTL module into a kernel with
NFTL support builtin. Check for nftl in /proc/devices.

-- 
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org