public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Bob Beers" <bob.beers@gmail.com>
To: "Andy Kennedy" <akennedy@techmoninc.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DiskOnChip 2000 (DOC 2000) woes.
Date: Thu, 9 Aug 2007 13:52:18 -0400	[thread overview]
Message-ID: <4f6ba3b0708091052n132bebb8rcbc0597cb35c75db@mail.gmail.com> (raw)
In-Reply-To: <46BB498D.9040707@techmoninc.com>

On 8/9/07, Andy Kennedy <akennedy@techmoninc.com> wrote:

> root@winsys:~# modprobe nftl
> root@winsys:~# fdisk /dev/nftla

Have you tried compiling the MTD, MTD_NAND, MTD_NAND_DISKONCHIP
 parts into the kernel rather than as modules?

If you do that, what kind of dmesg output do you get related to MTD?

>   I created the block devices nftla{,1,2} using:
> mknod /dev/nftla b 93 0
> and I end up with a device:
> brw-rw---- 1 root disk 93, 0 2007-08-09 10:52 /dev/nftla

my device nodes look like this:
bash-3.00# ls /dev/nftla* -al
brw-r--r--  1 root root 93, 0 Mar  4  2005 /dev/nftla
brw-r--r--  1 root root 93, 1 Mar  4  2005 /dev/nftla1
brw-r--r--  1 root root 93, 2 Mar  4  2005 /dev/nftla2
brw-r--r--  1 root root 93, 3 Mar  4  2005 /dev/nftla3

I never had any success with 32M, but 8M, 16M, 64M worked for me.
(48M worked, but had incredibly slow boot time.)

Does your process work with other sizes of DiskOnChip 2000?

-Bob

  reply	other threads:[~2007-08-09 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 18:57 DiskOnChip 2000 (DOC 2000) woes Andy Kennedy
2007-08-06 22:03 ` Andy Kennedy
2007-08-08 16:26 ` Andy Kennedy
2007-08-08 17:03   ` Bob Beers
     [not found]     ` <46BA05D6.4080605@techmoninc.com>
2007-08-08 19:30       ` Bob Beers
2007-08-09 14:17   ` Andy Kennedy
2007-08-09 17:06     ` Andy Kennedy
2007-08-09 17:52       ` Bob Beers [this message]
2007-08-09 18:00         ` Andy Kennedy

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=4f6ba3b0708091052n132bebb8rcbc0597cb35c75db@mail.gmail.com \
    --to=bob.beers@gmail.com \
    --cc=akennedy@techmoninc.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