From: David Woodhouse <dwmw2@infradead.org>
To: Boris Bulkin <boris@emcraft.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOC2000 support for a custom PPC750 board
Date: Mon, 05 Nov 2001 09:36:49 +0000 [thread overview]
Message-ID: <29072.1004953009@redhat.com> (raw)
In-Reply-To: <3BE65965.F5C16E70@emcraft.ru>
boris@emcraft.ru said:
> I'm new to the MTD project, so any information will be very
> appreciated. What is the current state of MTD support for DOC?
It works, for the DiskOnChip 2000 and DiskOnChip Millennium. Not the
Millennium Plus. It doesn't do sane wear-levelling though. That's left as an
exercise for the reader. Pointers and CVS access will happily be given to
anyone who looks serious about doing it.
> Do MTD DOC drivers require any firmware from M-Sys, or does MTD provide
> its own DOC firmware?
The DiskOnChip requires no firmware. It is not an intelligent device.
What's normally referred to as the DiskOnChip 'firmware' is the BIOS
extension which installs a driver which hooks the PC INT 13h disk service
interrupt and hence makes DOS and LILO work. I assume you don't want that :)
> Then, I know that M-Systems suggests running its
> DOS-based tools for partitioning and formatting a DOC device. Are
> there any open-source replacements for them?
There is nftl_format.c which performs the basic function of creating an
NFTL on the raw flash. NFTL is the translation layer used on the DiskOnChip
devices to emulate a normal block device. It is preferred to use the DOS
utilities because their response to finding bad blocks has been far better
tested. But nftl_format should be OK.
--
dwmw2
next prev parent reply other threads:[~2001-11-05 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 9:18 DOC2000 support for a custom PPC750 board Boris Bulkin
2001-11-05 9:36 ` David Woodhouse [this message]
2001-11-05 10:53 ` Boris Bulkin
2001-11-05 11:20 ` David Woodhouse
2001-11-05 19:01 ` Bao C. Ha
2001-11-05 22:54 ` 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=29072.1004953009@redhat.com \
--to=dwmw2@infradead.org \
--cc=boris@emcraft.ru \
--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.