Re: Not detecting DOC2000 at boot up ...

[Holger Friedrich <friedrich@MAZeT.de>]

Hi Patrick,
I got my kernel 2.4.0 to recognize the DOC2000 last week. 
This is the MTD section of my .config :
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
# CONFIG_MTD_DEBUG is not set
# CONFIG_MTD_PARTITIONS is not set
 
#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
 
#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_JEDEC is not set
 
#
# Mapping drivers for chip access
#
# CONFIG_MTD_SUN_UFLASH is not set
# CONFIG_MTD_OCELOT is not set
 
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_LART is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set
 
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC1000 is not set
CONFIG_MTD_DOC2000=y
# CONFIG_MTD_DOC2001 is not set
CONFIG_MTD_DOCPROBE=y
CONFIG_MTD_DOCPROBE_ADVANCED=y
CONFIG_MTD_DOCPROBE_ADDRESS=dc000
# CONFIG_MTD_DOCPROBE_HIGH is not set
# CONFIG_MTD_DOCPROBE_55AA is not set
 
#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set          

Maybe that will help you.

Patrick Allaire wrote:
> 
> Hi all,
> 
> My new kernel(2.2.19) does not detect the DOC at boot up !!! I cannot see
> any messges related to MTD in the boot up log (appended to this email) ?
> Should mtd driver show a message before it tries to find devices ? Is there
> a utility to force the checkup of devices once the kernel is booted ?
> 
> I am also adding my kernel config file. There is so much options in the
> config that I may have choosen wrong.
> 
> thank you all for your time in helping me  (c:
> 
>