UnitSizeFactor in nftlmount.c

Ilguiz Latypov ilatypov at superbt.com
Wed May 29 12:19:08 EDT 2002


On Wed, 29 May 2002, Frederic Marmond wrote:

> i made a "nftl_format /dev/mtd0 2097152", from the lastest CVS from 

I believe the second parameter is a start offset for the NFTL layer.  It 
can be supplied to provide a space for the bootloader.

The error might persist because part of the older NFTL layer still remains 
in the beginning of the chip.

On Wed, 29 May 2002, Frederic Marmond wrote:

> but impossible to boot (even with the "lilo-mtd -r /diskonchip").

As far as I know the lilo patched by M-Sys operates with the boot media
through BIOS calls.  The M-Sys firmware stored in the beginning of the
flash memory hooks up to the BIOS disk interrupt and will emulate a hard

I haven't tried combining the M-Sys firmware with MTD drivers as they
perform the same task.  The choice of Linux driver for DOC 2000 (M-Sys or
MTD) will affect the choice of the bootloader.  With the M-Sys driver, the 
lilo loader provided by M-Sys will operate with the chip via BIOS.  It 
will make sense to stay with the same firmware when running Linux then.

One of the bootloader DOC2000 BIOS disk interface for the bootloader Using
MTD drivers instead of M-Sys allows to replace the M-Sys firmware because 
the latter is no longer critical for Linux kernel operation.

A patch exists to make another bootloader (GRUB) aware of DOC 2000 and its 
NFTL layer.  Essentially the patch provide a block read interface to the 
NFTL "payload".

The GRUB bootloader can be found at


and the patch is the


file from MTD tree.  The patch contains a short instruction on building 
and installing the firmware in README_DiskOnChip.  See also



More information about the linux-mtd mailing list