diskonchip2000 support in 2.4.22

diskonchip2000 support in 2.4.22

[Andre Sodermans]

hello all,
I can't access my diskonchip2000 partitions from
linux. I have linuxmz 2.4.18 installed on it and it
boots fine from diskonchip. 

The kernel I built for LFS5.0 is based on 2.4.22. 
I compiled the kernel with:
CONFIG_MTD = m
CONFIG_MTD_CHAR = m
CONFIG_NFTL = m

Running modprobe docprobe, I get:

DiskOnChip Millennium found at address: 0xD000
no flash chips recognized

It is actually a diskonchip2000.
There is no entry in /proc/mtd.

After I installed the kernel I noticed that I was
missing the /dev/msys/fla* so I created those. Also
the /dev/nftl* were missing, so I downloaded the
latest mtd snapshot and ran the MAKEDEV script.

I tried to mount -t ext2 /dev/msys/fla1 /mnt/doc -
result:
mount: /dev/msys/fla1 is not a valid block device

I tried to mount -t ext2 /dev/nftla
mount: /dev/nftla1: unknown device


Did I miss something?


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

Re: diskonchip2000 support in 2.4.22

[Jonathan M. Schlueter]

On Sun, 9 May 2004, Andre Sodermans wrote:

> hello all,
> I can't access my diskonchip2000 partitions from
> linux. I have linuxmz 2.4.18 installed on it and it
> boots fine from diskonchip.
>
> The kernel I built for LFS5.0 is based on 2.4.22.
> I compiled the kernel with:
> CONFIG_MTD = m
> CONFIG_MTD_CHAR = m
> CONFIG_NFTL = m
>
> Running modprobe docprobe, I get:
>
> DiskOnChip Millennium found at address: 0xD000
> no flash chips recognized
>
> It is actually a diskonchip2000.
> There is no entry in /proc/mtd.

Which driver are you using?

> After I installed the kernel I noticed that I was
> missing the /dev/msys/fla* so I created those. Also
> the /dev/nftl* were missing, so I downloaded the
> latest mtd snapshot and ran the MAKEDEV script.

/dev/msys/fla* are the dev files from M-Sys's custom driver

/dev/nftla  are the dev files for the mtd subsystem (this list)

They are two seperate and different methods of accessing the DiskonChip


> I tried to mount -t ext2 /dev/msys/fla1 /mnt/doc -
> result:
> mount: /dev/msys/fla1 is not a valid block device
>
> I tried to mount -t ext2 /dev/nftla
> mount: /dev/nftla1: unknown device
>
>
> Did I miss something?
>



Jon Schlueter

Re: diskonchip2000 support in 2.4.22

[Andre Sodermans]

> > hello all,
> > I can't access my diskonchip2000 partitions from
> > linux. I have linuxmz 2.4.18 installed on it and
> it
> > boots fine from diskonchip.
> >
> > The kernel I built for LFS5.0 is based on 2.4.22.
> > I compiled the kernel with:
> > CONFIG_MTD = m
> > CONFIG_MTD_CHAR = m
> > CONFIG_NFTL = m
> >
> > Running modprobe docprobe, I get:
> >
> > DiskOnChip Millennium found at address: 0xD000
> > no flash chips recognized
> >
> > It is actually a diskonchip2000.
> > There is no entry in /proc/mtd.
> 
> Which driver are you using?

the one from the unpatched 2.4.22 kernel. I actually
forgot to mention the following config flags that I
used on my most recent kernel:
CONFIG_MTD_DOC2000=m
CONFIG_MTD_DOCPROBE=m
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_NAND_IDS=m

I then ran:
modprobe -a doc2000 nftl mtdchar
modprobe -a docprobe

I'm actually now building another kernel with the
latest mtd patch, just to be sure.

> 
> > After I installed the kernel I noticed that I was
> > missing the /dev/msys/fla* so I created those.
> Also
> > the /dev/nftl* were missing, so I downloaded the
> > latest mtd snapshot and ran the MAKEDEV script.
> 
> /dev/msys/fla* are the dev files from M-Sys's custom
> driver
> 
> /dev/nftla  are the dev files for the mtd subsystem
> (this list)
> 
> They are two seperate and different methods of
> accessing the DiskonChip
> 

Ok, I was being desperate, I meant to just use the one
from the kernel since the one from mtd is a lot
better.


> 
> > I tried to mount -t ext2 /dev/msys/fla1 /mnt/doc -
> > result:
> > mount: /dev/msys/fla1 is not a valid block device
> >
> > I tried to mount -t ext2 /dev/nftla
> > mount: /dev/nftla1: unknown device
> >
> >
> > Did I miss something?
> >
> 
> 
> 
> Jon Schlueter



	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

Re: diskonchip2000 support in 2.4.22

[Andre Sodermans]

I rebuilt my kernel 2.4.22 after patching it with
mtd-snapshot-20040508.
I used the following config flags:

# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set
# CONFIG_MTD_CONCAT is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
CONFIG_MTD_CHAR=m
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
# CONFIG_INFTL is not set

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
# CONFIG_MTD_GEN_PROBE is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not set
# CONFIG_MTD_CFI_UTIL is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
# CONFIG_MTD_SC520CDP is not set
# CONFIG_MTD_NETSC520 is not set
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_ELAN_104NC is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_OCTAGON is not set
# CONFIG_MTD_VMAX is not set
# CONFIG_MTD_SCx200_DOCFLASH is not set
# CONFIG_MTD_L440GX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_SCB2_FLASH is not set
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_PCMCIA is not set

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
CONFIG_MTD_DOC2000=m
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_DOCPROBE=m
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
# CONFIG_MTD_DOCPROBE_HIGH is not set
# CONFIG_MTD_DOCPROBE_55AA is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set
CONFIG_MTD_NAND_IDS=m


Then after bootup, I run:
modprobe -a doc2000 nftl mtdchar mtdblock
modprobe -a docprobe

Here is the output from dmesg:


NFTL driver: nftlcore.c $Revision: 1.94 $, nftlmount.c
$Revision: 1.34 $
Refusing to drive DiskOnChip 2000 TSOP until Bad Block
Table is correctly supported by INFTL
No recognised DiskOnChip devices found

What am I missing?



	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

Re: diskonchip2000 support in 2.4.22

[David Woodhouse]

On Sun, 2004-05-09 at 18:47 -0700, Andre Sodermans wrote:
> Refusing to drive DiskOnChip 2000 TSOP until Bad Block
> Table is correctly supported by INFTL

> What am I missing?

-- 
dwmw2

Re: diskonchip2000 support in 2.4.22

[Andre Sodermans]

hmmmm

So, I do need 'CONFIG_INFTL'? I wasn't sure when I
built my most recent kernel.

Andre

--- David Woodhouse <dwmw2@infradead.org> wrote:
> On Sun, 2004-05-09 at 18:47 -0700, Andre Sodermans
> wrote:
> > Refusing to drive DiskOnChip 2000 TSOP until Bad
> Block
> > Table is correctly supported by INFTL
> 
> > What am I missing?
> 
> -- 
> dwmw2
> 
> 



	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 

Re: diskonchip2000 support in 2.4.22

[David Woodhouse]

On Tue, 2004-05-11 at 08:53 -0700, Andre Sodermans wrote:
> hmmmm
> 
> So, I do need 'CONFIG_INFTL'? I wasn't sure when I
> built my most recent kernel.

Yes, and then you need to write support for the Bad Block Table.
It's not hard -- I can help you. But I haven't got round to doing it
myself yet, and while it's not yet done the hardware driver deliberately
disables itself.

-- 
dwmw2