public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: dr john halewood <john@frumious.unidec.co.uk>
To: David Hamm <dhamm@itrepro.com>, mtd@infradead.org
Subject: Re: DiskOnChip200 howto
Date: Thu, 11 Jan 2001 09:58:06 +0000	[thread overview]
Message-ID: <0101110958060C.27002@frumious.unidec.co.uk> (raw)
In-Reply-To: <01010910331803.23650@workbox.atlanta.itserve.com>

On Tuesday 09 January 2001 15:28, David Hamm wrote:
> I've been fighting with a DiskOnChip2000 box for a while now and its about
> to win.   I've searched the net for specific info on how to use the MTD
> drivers in the kernel rather than M-Sys driver.  Is there a howto or an old
> email that describes how to use the NFTL drivers?  Getting them in the
> kernel is easy but I don't know which device file to use to format the
> device.

As a quick guide:

Build the mtd support into the kernel.

If using modules, I'd suggest ordering them something like (depending on what 
support you've chosen of course)

mtdcore.o
nftl.o
mtdchar.o
mtdblock.o
doc2000.o
modprobe.o

Run the MAKEDEV script from the utils directory of the cvs tree to create the 
necessary files in /dev

Reboot. You should see a "Disk on Chip found at xxxxx" message followed by a 
"Giving out device <x> to DiskOnChip...". Generally I'd expect the DoC to be 
nftla


fdisk /dev/nftla and set up whatever partitions you want, then run mkfs to 
create the partitions. Mount and enjoy.

Alternatively you can create your own filesystems and dd them in directly.

cheers
john


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

      reply	other threads:[~2001-01-11  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 15:28 DiskOnChip200 David Hamm
2001-01-11  9:58 ` dr john halewood [this message]

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=0101110958060C.27002@frumious.unidec.co.uk \
    --to=john@frumious.unidec.co.uk \
    --cc=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