All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan J Simon <brendan.simon@ctam.com.au>
To: Linux MTD <linux-mtd@lists.infradead.org>
Subject: doc2000 nftl[abcd] devices
Date: Thu, 20 Jun 2002 14:52:43 +1000	[thread overview]
Message-ID: <3D115F9B.9030203@ctam.com.au> (raw)

I'm using a powerpc linux 2.4.18-pre8 kernel with an 8MB DOC2000.  I've 
managed to create 3 virtual disks using the latest nftl_format from cvs.
$ nftl_format /dev/mtd0 0x00000000 0x02000000
$ nftl_format /dev/mtd0 0x02000000 0x04000000
$ nftl_format /dev/mtd0 0x06000000 0x02000000

I've also compiled the latest cfdisk from util-linux-2.11n.
I loaded the nftl driver (insmod nftl) and did a fdisk (cfdisk 
/dev/nftla).  It complained about having no partition table and aksed if 
I wanted to continue.  I said yes and I created a new partition and it 
recognised the size as being 2MB :)  I wrote this to disk and then 
rebooted my embedded system (power cycled).  It came back up and I could 
mkfs.ext2 it and mount it.  Another power cycle and mount to prove to 
myself everything was written to the DOC correctly.

Now I try the same thing with nftlb and I get errors saying "Cannot open 
disk drive".  It should be the same process shouldn't it ?  Any ideas of 
where to look to fix or debug this ??  I've had a look at nftldump and I 
can see the 3 sets of media headers and they seem like they are in the 
right place.

My devices are:
crw-------    1 0        0         90,   0 Jun 17  2002 /dev/mtd0
brw-------    1 0        0         93,   0 Jun 17  2002 /dev/nftla
brw-------    1 0        0         93,   1 Jun 17  2002 /dev/nftla1
brw-------    1 0        0         93,   2 Jun 17  2002 /dev/nftla2
brw-------    1 0        0         93,   3 Jun 17  2002 /dev/nftla3
brw-------    1 0        0         93,   4 Jun 17  2002 /dev/nftla4
brw-------    1 0        0         93,  16 Jun 17  2002 /dev/nftlb
brw-------    1 0        0         93,  17 Jun 17  2002 /dev/nftlb1
brw-------    1 0        0         93,  32 Jun 17  2002 /dev/nftlc
brw-------    1 0        0         93,  33 Jun 17  2002 /dev/nftlc1
brw-------    1 0        0         93,  48 Jun 17  2002 /dev/nftld
brw-------    1 0        0         93,  49 Jun 17  2002 /dev/nftld1

Do I need to patch the kernel with the latest MTD stuff or should the 
MTD stuff in linuxppc-2.4.18-pre8 be OK ??

Thanks,
Brendan Simon.

             reply	other threads:[~2002-06-20  4:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  4:52 Brendan J Simon [this message]
2002-06-20  9:03 ` doc2000 nftl[abcd] devices David Woodhouse
2002-06-21  0:41   ` Brendan J Simon
2002-06-21  0:53     ` David Woodhouse
2002-06-21  5:34       ` Brendan J Simon
2002-06-21  6:01         ` Brendan J Simon
2002-06-21  7:11           ` 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=3D115F9B.9030203@ctam.com.au \
    --to=brendan.simon@ctam.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.