[uClibc] Disk On Chip

[PHILLIPS John M]

OK, so I missed the point where you had to enable the experimental 
drivers.  I was not seeing the NAND_DISKONCHIP option.

-----Original Message-----
From: uclibc-bounces at uclibc.org
To: 'uclibc at uclibc.org'
Sent: 8/19/05 2:08 PM
Subject: [uClibc] Disk On Chip 

I am trying to get a 2.6 kernel to use the M-Systems DiskOnChip 2000.
With
the 2.4 kernel I had used the M-Systems driver, but that appears not to
be
available with the newer kernel.

Attempting to follow the documentation, I configured the kernal with
   CONFIG_MTD = Y
   CONFIG_MTD_CHAR=y
   CONFIG_MTD_BLOCK=y
   CONFIG_FTL=y
   CONFIG_NFTL=y
   CONFIG_NFTL_RW=y
   CONFIG_INFTL=y
and
   CONFIG_MTD_NAND=y
   CONFIG_MTD_NAND_VERIFY_WRITE=y
   CONFIG_MTD_NAND_IDS=y

With this combination, /var/log/messages and /proc/mtd show that the
kernel
did not find the DOC.

If instead if the CONFIG_MTD_NAND*, I set
   CONFIG_MTD_DOC2000=y

then /proc/mtd shows mtd0: 06000000 00004000 "DiskOnChip", and
nftl_format
runs as explained in  Yaghmour, Building Embedded Linux Systems. But
then
neither fdisk or docfdisk will partition the DOC.

Any help will be greatly appreciated

John M Phillips 
 <<ATT464392.txt>>