* NAND detect
@ 2004-09-22 15:55 lp4u
2004-09-22 20:29 ` Ben Dooks
0 siblings, 1 reply; 9+ messages in thread
From: lp4u @ 2004-09-22 15:55 UTC (permalink / raw)
To: linux-mtd
Hi,
I have a s3c2410 board (BAST architecture).
I have installed on board a kernel2.4.26 patched and with MTD.
But the board, at boot, don't detect the NAND (I've 3 NANDs on board: 2 samsung & 1 STM).
The MTD detect only NOR Flash.
This is my configuration:
#
CONFIG_ARM=y
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_UID16=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_RWSEM_XCHGADD_ALGORITHM is not set
# CONFIG_GENERIC_BUST_SPINLOCK is not set
# CONFIG_GENERIC_ISA_DMA is not set
#
CONFIG_EXPERIMENTAL=y
# CONFIG_OBSOLETE is not set
#
# CONFIG_MODULES is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set
#
# CONFIG_ARCH_ANAKIN is not set
# CONFIG_ARCH_ARCA5K is not set
# CONFIG_ARCH_CLPS7500 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_CO285 is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_CAMELOT is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_OMAHA is not set
# CONFIG_ARCH_L7200 is not set
# CONFIG_ARCH_MX1ADS is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_RISCSTATION is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_SHARK is not set
CONFIG_ARCH_BAST=y
# CONFIG_ARCH_AT91RM9200 is not set
#
# CONFIG_ARCH_ARC is not set
# CONFIG_ARCH_A5K is not set
#
# CONFIG_MACH_VR1000 is not set
#
# CONFIG_ARCH_CATS is not set
# CONFIG_ARCH_PERSONAL_SERVER is not set
# CONFIG_ARCH_EBSA285_ADDIN is not set
# CONFIG_ARCH_EBSA285_HOST is not set
# CONFIG_ARCH_NETWINDER is not set
#
# CONFIG_SA1100_ACCELENT is not set
# CONFIG_SA1100_ASSABET is not set
# CONFIG_ASSABET_NEPONSET is not set
# CONFIG_SA1100_ADSAGC is not set
# CONFIG_SA1100_ADSBITSY is not set
# CONFIG_SA1100_ADSBITSYPLUS is not set
# CONFIG_SA1100_BRUTUS is not set
# CONFIG_SA1100_CEP is not set
# CONFIG_SA1100_CERF is not set
# CONFIG_SA1100_H3100 is not set
# CONFIG_SA1100_H3600 is not set
# CONFIG_SA1100_H3800 is not set
# CONFIG_SA1100_H3XXX is not set
# CONFIG_H3600_SLEEVE is not set
# CONFIG_SA1100_EXTENEX1 is not set
# CONFIG_SA1100_FLEXANET is not set
# CONFIG_SA1100_FREEBIRD is not set
# CONFIG_SA1100_FRODO is not set
# CONFIG_SA1100_GRAPHICSCLIENT is not set
# CONFIG_SA1100_GRAPHICSMASTER is not set
# CONFIG_SA1100_HACKKIT is not set
# CONFIG_SA1100_BADGE4 is not set
# CONFIG_SA1100_JORNADA720 is not set
# CONFIG_SA1100_HUW_WEBPANEL is not set
# CONFIG_SA1100_ITSY is not set
# CONFIG_SA1100_LART is not set
# CONFIG_SA1100_NANOENGINE is not set
# CONFIG_SA1100_OMNIMETER is not set
# CONFIG_SA1100_PANGOLIN is not set
# CONFIG_SA1100_PLEB is not set
# CONFIG_SA1100_PT_SYSTEM3 is not set
# CONFIG_SA1100_SHANNON is not set
# CONFIG_SA1100_SHERMAN is not set
# CONFIG_SA1100_SIMPAD is not set
# CONFIG_SA1100_SIMPUTER is not set
# CONFIG_SA1100_PFS168 is not set
# CONFIG_SA1100_VICTOR is not set
# CONFIG_SA1100_XP860 is not set
# CONFIG_SA1100_YOPY is not set
# CONFIG_SA1100_USB is not set
# CONFIG_SA1100_USB_NETLINK is not set
# CONFIG_SA1100_USB_CHAR is not set
# CONFIG_SA1100_SSP is not set
#
# CONFIG_ARCH_AT91RM9200DK is not set
# CONFIG_MACH_CSB337 is not set
#
# CONFIG_ARCH_AUTCPU12 is not set
# CONFIG_ARCH_CDB89712 is not set
# CONFIG_ARCH_CLEP7312 is not set
# CONFIG_ARCH_EDB7211 is not set
# CONFIG_ARCH_FORTUNET is not set
# CONFIG_ARCH_GUIDEA07 is not set
# CONFIG_ARCH_P720T is not set
# CONFIG_ARCH_EP7211 is not set
# CONFIG_ARCH_EP7212 is not set
# CONFIG_ARCH_ACORN is not set
# CONFIG_PLD is not set
# CONFIG_FOOTBRIDGE is not set
# CONFIG_FOOTBRIDGE_HOST is not set
# CONFIG_FOOTBRIDGE_ADDIN is not set
CONFIG_CPU_32=y
# CONFIG_CPU_26 is not set
# CONFIG_CPU_ARM610 is not set
# CONFIG_CPU_ARM710 is not set
# CONFIG_CPU_ARM720T is not set
# CONFIG_CPU_ARM920T is not set
CONFIG_CPU_ARM920T=y
CONFIG_CPU_S3C2410X=y
# CONFIG_CPU_ARM922T is not set
# CONFIG_CPU_ARM926T is not set
# CONFIG_CPU_ARM1020 is not set
# CONFIG_CPU_ARM1020E is not set
# CONFIG_CPU_ARM1022 is not set
# CONFIG_CPU_ARM1026 is not set
# CONFIG_CPU_SA110 is not set
# CONFIG_CPU_SA1100 is not set
# CONFIG_CPU_32v3 is not set
CONFIG_CPU_32v4=y
# CONFIG_ARM_THUMB is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_WRITETHROUGH is not set
# CONFIG_DISCONTIGMEM is not set
#
# CONFIG_PCI is not set
CONFIG_ISA=y
# CONFIG_ISA_DMA is not set
# CONFIG_ZBOOT_ROM is not set
CONFIG_ZBOOT_ROM_TEXT=0
CONFIG_ZBOOT_ROM_BSS=0
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_FPE_NWFPE=y
# CONFIG_FPE_NWFPE_XP is not set
# CONFIG_FPE_FASTFPE is not set
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_PM is not set
# CONFIG_ARTHUR is not set
CONFIG_CMDLINE="root=/dev/nfs rw nfsroot=143.225.229.44:/board ip=dhcp init/bin/bash
console=ttySAC0"
CONFIG_ALIGNMENT_TRAP=y
CONFIG_S3C2410_DMA_PROC=y
# CONFIG_S3C2410_DMA_DEBUG is not set
#
# CONFIG_PARPORT is not set
#
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=1
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_REDBOOT_PARTS=y
# CONFIG_MTD_CMDLINE_PARTS is not set
CONFIG_MTD_AFS_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
#
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_AMDSTD=y
# CONFIG_MTD_CFI_STAA is not set
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_ABSENT=y
# 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
#
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_NORA is not set
# CONFIG_MTD_ARM_INTEGRATOR is not set
# CONFIG_MTD_CDB89712 is not set
# CONFIG_MTD_SA1100 is not set
# CONFIG_MTD_DC21285 is not set
# CONFIG_MTD_IQ80310 is not set
# CONFIG_MTD_FORTUNET is not set
# CONFIG_MTD_EPXA is not set
CONFIG_MTD_BAST=y
# CONFIG_MTD_VR1000RAM is not set
# CONFIG_MTD_AUTCPU12 is not set
# CONFIG_MTD_EDB7312 is not set
# CONFIG_MTD_IMPA7 is not set
# CONFIG_MTD_CEIVA is not set
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_PCMCIA is not set
#
# 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_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOCPROBE is not set
#
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_VERIFY_WRITE=y
CONFIG_MTD_NAND_S3C2410=y
CONFIG_MTD_NAND_BAST=y
CONFIG_MTD_NAND_IDS=y
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_CISS_MONITOR_THREAD is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLK_STATS=y
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
#
# CONFIG_IP_NF_CONNTRACK is not set
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# CONFIG_NET_SCHED is not set
#
# CONFIG_NET_PKTGEN is not set
#
CONFIG_NETDEVICES=y
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
CONFIG_NET_ETHERNET=y
# CONFIG_ARM_AM79C961A is not set
# CONFIG_ARM_CIRRUS is not set
CONFIG_NE2K_BAST=y
CONFIG_DM9000_BAST=y
# CONFIG_SUNLANCE is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
CONFIG_NE2000=y
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
CONFIG_SLIP=y
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
#
# CONFIG_NET_RADIO is not set
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# CONFIG_WAN is not set
#
# CONFIG_HAMRADIO is not set
#
# CONFIG_IRDA is not set
#
CONFIG_IDE=y
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDE_BAST=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_MEDLEY is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set
#
# CONFIG_SCSI is not set
#
# CONFIG_I2O is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set
#
# CONFIG_ISDN is not set
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_UINPUT is not set
# CONFIG_INPUT_MX1TS is not set
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
# CONFIG_SERIAL is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_DUMMY_KEYB=y
#
# CONFIG_SERIAL_ANAKIN is not set
# CONFIG_SERIAL_ANAKIN_CONSOLE is not set
# CONFIG_SERIAL_AMBA is not set
# CONFIG_SERIAL_AMBA_CONSOLE is not set
# CONFIG_SERIAL_CLPS711X is not set
# CONFIG_SERIAL_CLPS711X_CONSOLE is not set
# CONFIG_SERIAL_21285 is not set
# CONFIG_SERIAL_21285_OLD is not set
# CONFIG_SERIAL_21285_CONSOLE is not set
# CONFIG_SERIAL_UART00 is not set
# CONFIG_SERIAL_UART00_CONSOLE is not set
# CONFIG_SERIAL_SA1100 is not set
# CONFIG_SERIAL_SA1100_CONSOLE is not set
# CONFIG_SERIAL_OMAHA is not set
# CONFIG_SERIAL_OMAHA_CONSOLE is not set
# CONFIG_SERIAL_AT91 is not set
# CONFIG_SERIAL_AT91_CONSOLE is not set
CONFIG_SERIAL_S3C2410X=y
CONFIG_SERIAL_S3C2410X_CONSOLE=y
# CONFIG_SERIAL_8250 is not set
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_EXTENDED is not set
# CONFIG_SERIAL_8250_MANY_PORTS is not set
# CONFIG_SERIAL_8250_SHARE_IRQ is not set
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_HUB6 is not set
# CONFIG_SERIAL_BAST_16550 is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
CONFIG_I2C=y
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_PHILIPSPAR is not set
# CONFIG_I2C_ELV is not set
# CONFIG_I2C_VELLEMAN is not set
# CONFIG_SCx200_I2C is not set
# CONFIG_I2C_GUIDE is not set
CONFIG_I2C_S3C2410BIT=y
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_PROC=y
# CONFIG_I2C_DS1307 is not set
# CONFIG_I2C_M41ST87 is not set
#
# CONFIG_L3 is not set
# CONFIG_L3_ALGOBIT is not set
# CONFIG_L3_BIT_SA1100_GPIO is not set
# CONFIG_L3_SA1111 is not set
# CONFIG_BIT_SA1100_GPIO is not set
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
# CONFIG_MK712_MOUSE is not set
#
# CONFIG_INPUT_GAMEPORT is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_SC520_WDT is not set
# CONFIG_PCWATCHDOG is not set
# CONFIG_21285_WATCHDOG is not set
# CONFIG_977_WATCHDOG is not set
# CONFIG_SA1100_WATCHDOG is not set
# CONFIG_EPXA_WATCHDOG is not set
# CONFIG_OMAHA_WATCHDOG is not set
CONFIG_S3C2410_WATCHDOG=y
# CONFIG_AT91_WATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I810_TCO is not set
# CONFIG_MIXCOMWD is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_SCx200_WDT is not set
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_WDT is not set
# CONFIG_WDTPCI is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_AMD7XX_TCO is not set
# CONFIG_SCx200 is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
CONFIG_BAST_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
#
# CONFIG_DRM is not set
#
# CONFIG_VIDEO_DEV is not set
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
CONFIG_JFFS_FS=y
CONFIG_JFFS_FS_VERBOSE=0
CONFIG_JFFS_PROC_FS=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_CRAMFS=y
# CONFIG_TMPFS is not set
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
CONFIG_ROMFS_FS=y
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set
# CONFIG_XFS_FS is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_RT is not set
# CONFIG_XFS_TRACE is not set
# CONFIG_XFS_DEBUG is not set
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
CONFIG_ZISOFS_FS=y
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# CONFIG_VGA_CONSOLE is not set
#
# CONFIG_FB is not set
#
# CONFIG_SOUND is not set
#
# CONFIG_MCP is not set
# CONFIG_MCP_SA1100 is not set
# CONFIG_MCP_UCB1200 is not set
# CONFIG_MCP_UCB1200_AUDIO is not set
# CONFIG_MCP_UCB1200_TS is not set
#
# CONFIG_USB is not set
#
# CONFIG_USB_GADGET is not set
#
# CONFIG_BLUEZ is not set
#
CONFIG_FRAME_POINTER=y
CONFIG_DEBUG_USER=y
CONFIG_DEBUG_INFO=y
# CONFIG_NO_PGT_CACHE is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SLAB=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_WAITQ=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_ERRORS=y
CONFIG_DEBUG_LL=y
# CONFIG_DEBUG_DC21285_PORT is not set
# CONFIG_DEBUG_CLPS711X_UART2 is not set
CONFIG_DEBUG_S3C2410X_UART0=y
# CONFIG_DEBUG_VR1000_SER3 is not set
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
Thanks.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NAND detect
2004-09-22 15:55 NAND detect lp4u
@ 2004-09-22 20:29 ` Ben Dooks
2004-09-23 7:11 ` Thomas Gleixner
0 siblings, 1 reply; 9+ messages in thread
From: Ben Dooks @ 2004-09-22 20:29 UTC (permalink / raw)
To: lp4u@inwind.it; +Cc: linux-mtd, gavin
On Wed, Sep 22, 2004 at 05:55:20PM +0200, lp4u@inwind.it wrote:
> Hi,
>
> I have a s3c2410 board (BAST architecture).
> I have installed on board a kernel2.4.26 patched and with MTD.
> But the board, at boot, don't detect the NAND (I've 3 NANDs on board: 2 samsung & 1 STM).
Does the bootloader list them, newish versions of the bootloader
should probe all available devices and print the ID information
it finds as it goes.
> The MTD detect only NOR Flash.
I've just had a check through, and it seems the driver was
written pre the nand hooks for >1 chip per controller, and
therefore just selects slot 0 (smartmedia card) at start time.
A quick way to get going would be to change the value passed
to bast_nand_select_slot() in bast_nand_init() in the driver
to at least show that a chip can be detected and used. The
current default in the driver is to select the SmartMedia socket.
The slots are allocated as 0 for the SmartMedia card slot, and
1 through 3 for the chips on the board (U52, U53 and U54)
Looking through the NAND code, it seems that we may have a
few problems with implementing >1 chip, which could bite
in your configuration:
1) The driver needs to work out which slots are used and
create a linear mapping of chips -> slots.
2) The NAND layer itself seems to concatenate the chips
together, not export them as seperate devices, which
makes supporting removable devices in the card slot
and on-board NAND difficult.
I would be interesting in anyone's comments about how difficult
it would be to have an overall controller activity lock and
allow a single controller to register more than one NAND chip
as a seperate device.
It would also be nice to have at least some form of hotplug
mechanism support where a chip can be re-scanned after a
change in it's detect status.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NAND detect
2004-09-22 20:29 ` Ben Dooks
@ 2004-09-23 7:11 ` Thomas Gleixner
2004-09-23 9:48 ` Ben Dooks
[not found] ` <20040923191506.GE25491@home.fluff.org>
0 siblings, 2 replies; 9+ messages in thread
From: Thomas Gleixner @ 2004-09-23 7:11 UTC (permalink / raw)
To: Ben Dooks; +Cc: linux-mtd, gavin
On Wed, 2004-09-22 at 22:29, Ben Dooks wrote:
> I've just had a check through, and it seems the driver was
> written pre the nand hooks for >1 chip per controller, and
> therefore just selects slot 0 (smartmedia card) at start time.
>
> A quick way to get going would be to change the value passed
> to bast_nand_select_slot() in bast_nand_init() in the driver
> to at least show that a chip can be detected and used. The
> current default in the driver is to select the SmartMedia socket.
>
> The slots are allocated as 0 for the SmartMedia card slot, and
> 1 through 3 for the chips on the board (U52, U53 and U54)
>
> Looking through the NAND code, it seems that we may have a
> few problems with implementing >1 chip, which could bite
> in your configuration:
>
> 1) The driver needs to work out which slots are used and
> create a linear mapping of chips -> slots.
>
> 2) The NAND layer itself seems to concatenate the chips
> together, not export them as seperate devices, which
> makes supporting removable devices in the card slot
> and on-board NAND difficult.
You can call nandscan (onboardnand, nrchips) and nandscan(removablenand,
1) and you have two independend mtd devices where the first
(onboardnand) is a concatenation of the available chips.
You can also call nandscan for each chip seperate and you have n
independend devices. They share the hwcontrol function, but the mtd
private structure should tell you which chip you are handling.
For concatenated chips you have to provide the getchip function to
select the appropriate chip.
> I would be interesting in anyone's comments about how difficult
> it would be to have an overall controller activity lock and
> allow a single controller to register more than one NAND chip
> as a seperate device.
Are you talking about a hardware controller, where several chips are
connected to and which can handle only one chip at a time ?
That's not supported at the moment. It is not hard to make this work. It
needs some additional information about which devices share the
controller and some access management which puts you on the right
waitqueue.
struct nand_hw_controller {
spinlock_t lock;
struct mtd_info *active;
};
The driver provides the structure for its hardware controller and adds a
pointer to this structure to the nand structure before calling nandscan.
nand_get_chip and nand_release_chip need some tweaks to check the
availablity of such an structure. If active == NULL then the current mtd
device is stored in active and we can grab the chip. Otherwise we add
the current process to the waitqueue of the nand device, which holds the
controller.
> It would also be nice to have at least some form of hotplug
> mechanism support where a chip can be re-scanned after a
> change in it's detect status.
It should be not too hard to integrate such functionality into the
generic hotplug framework. If the driver is a selfcontained module for
one chip, then it should work right now. If the driver must stay in the
kernel because it controls more than one chip, then interfacing to the
kobject framework should be a valuable solution.
Most stuff must be done in the driver, but we have to figure out if we
need additional functionality for removal in the nand reps. mtd
framework.
dwmw2 ???
tglx
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NAND detect
2004-09-23 7:11 ` Thomas Gleixner
@ 2004-09-23 9:48 ` Ben Dooks
[not found] ` <20040923191506.GE25491@home.fluff.org>
1 sibling, 0 replies; 9+ messages in thread
From: Ben Dooks @ 2004-09-23 9:48 UTC (permalink / raw)
To: Thomas Gleixner; +Cc: linux-mtd, Ben Dooks, gavin
On Thu, Sep 23, 2004 at 09:11:10AM +0200, Thomas Gleixner wrote:
> On Wed, 2004-09-22 at 22:29, Ben Dooks wrote:
> > I've just had a check through, and it seems the driver was
> > written pre the nand hooks for >1 chip per controller, and
> > therefore just selects slot 0 (smartmedia card) at start time.
> >
> > A quick way to get going would be to change the value passed
> > to bast_nand_select_slot() in bast_nand_init() in the driver
> > to at least show that a chip can be detected and used. The
> > current default in the driver is to select the SmartMedia socket.
> >
> > The slots are allocated as 0 for the SmartMedia card slot, and
> > 1 through 3 for the chips on the board (U52, U53 and U54)
> >
> > Looking through the NAND code, it seems that we may have a
> > few problems with implementing >1 chip, which could bite
> > in your configuration:
> >
> > 1) The driver needs to work out which slots are used and
> > create a linear mapping of chips -> slots.
> >
> > 2) The NAND layer itself seems to concatenate the chips
> > together, not export them as seperate devices, which
> > makes supporting removable devices in the card slot
> > and on-board NAND difficult.
>
> You can call nandscan (onboardnand, nrchips) and nandscan(removablenand,
> 1) and you have two independend mtd devices where the first
> (onboardnand) is a concatenation of the available chips.
> You can also call nandscan for each chip seperate and you have n
> independend devices. They share the hwcontrol function, but the mtd
> private structure should tell you which chip you are handling.
> For concatenated chips you have to provide the getchip function to
> select the appropriate chip.
>
> > I would be interesting in anyone's comments about how difficult
> > it would be to have an overall controller activity lock and
> > allow a single controller to register more than one NAND chip
> > as a seperate device.
>
> Are you talking about a hardware controller, where several chips are
> connected to and which can handle only one chip at a time ?
Yes, our hardware designer decided that since we had a card socket
and wanted a device on board, he'd put a mux in all the signals to
steer the cpu's nand controller to either the socket or the chip,
and since he had a 4 way mux, he decided to add two more onboard chips
whilst he was at it.
> That's not supported at the moment. It is not hard to make this work. It
> needs some additional information about which devices share the
> controller and some access management which puts you on the right
> waitqueue.
>
> struct nand_hw_controller {
> spinlock_t lock;
> struct mtd_info *active;
> };
>
> The driver provides the structure for its hardware controller and adds a
> pointer to this structure to the nand structure before calling nandscan.
> nand_get_chip and nand_release_chip need some tweaks to check the
> availablity of such an structure. If active == NULL then the current mtd
> device is stored in active and we can grab the chip. Otherwise we add
> the current process to the waitqueue of the nand device, which holds the
> controller.
Would that be something welcome as a patch for the current mtd code?
I guess it'll require a new registration point, and a new nand_chip
function call to allow the hw driver to be notified about the change in
chip.
> > It would also be nice to have at least some form of hotplug
> > mechanism support where a chip can be re-scanned after a
> > change in it's detect status.
>
> It should be not too hard to integrate such functionality into the
> generic hotplug framework. If the driver is a selfcontained module for
> one chip, then it should work right now. If the driver must stay in the
> kernel because it controls more than one chip, then interfacing to the
> kobject framework should be a valuable solution.
>
> Most stuff must be done in the driver, but we have to figure out if we
> need additional functionality for removal in the nand reps. mtd
> framework.
>
> dwmw2 ???
>
>
> tglx
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] 9+ messages in thread
* NAND detect
@ 2004-09-23 9:54 lp4u
2004-09-23 10:53 ` Ben Dooks
0 siblings, 1 reply; 9+ messages in thread
From: lp4u @ 2004-09-23 9:54 UTC (permalink / raw)
To: MTD mailing list
Hi,
I have a s3c2410 board (BAST architecture).
I have installed on board a kernel2.4.26 patched and with MTD.
But the board, at boot (OF LINUX), don't detect the NAND (I've 3 NANDs on board: 2 samsung
& 1 STM).
The MTD detect only NOR Flash.
This is my configuration:
#
CONFIG_ARM=y
.....
.....
Thanks.
PS: excuse my imprecision.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NAND detect
2004-09-23 9:54 NAND detect lp4u
@ 2004-09-23 10:53 ` Ben Dooks
0 siblings, 0 replies; 9+ messages in thread
From: Ben Dooks @ 2004-09-23 10:53 UTC (permalink / raw)
To: lp4u@inwind.it; +Cc: MTD mailing list
On Thu, Sep 23, 2004 at 11:54:47AM +0200, lp4u@inwind.it wrote:
> Hi,
>
> I have a s3c2410 board (BAST architecture).
> I have installed on board a kernel2.4.26 patched and with MTD.
> But the board, at boot (OF LINUX), don't detect the NAND (I've 3 NANDs on board: 2 samsung
> & 1 STM).
> The MTD detect only NOR Flash.
ok, we are looking into this, see the previous thread for
any more info on what is happening with this.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: NAND detect
[not found] ` <20040923191506.GE25491@home.fluff.org>
@ 2004-09-23 23:05 ` Ben Dooks
0 siblings, 0 replies; 9+ messages in thread
From: Ben Dooks @ 2004-09-23 23:05 UTC (permalink / raw)
To: Ben Dooks; +Cc: linux-mtd, gavin
On Thu, Sep 23, 2004 at 08:15:06PM +0100, Ben Dooks wrote:
> On Thu, Sep 23, 2004 at 09:11:10AM +0200, Thomas Gleixner wrote:
> > On Wed, 2004-09-22 at 22:29, Ben Dooks wrote:
>
> I've posted the patch to a 2.6.9 kernel from my first
> effort here (the kernel has the 19th September snapshot
> applied to it first):
>
> http://www.fluff.org/ben/mtd/nand-multi1.diff
after discussions with tglx, the patch is too invasive into
nand_base.c and has other problems.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] 9+ messages in thread
* Nand detect
@ 2004-09-28 10:17 lp4u
2004-09-28 10:55 ` Ben Dooks
0 siblings, 1 reply; 9+ messages in thread
From: lp4u @ 2004-09-28 10:17 UTC (permalink / raw)
To: Ben Dooks, MTD mailing list
Hi,
I've a s3c24210 board with BAST architecture, with 2 NAND on board.
I've compiling the kernel 2.6.9-rc2 after patched it with:
- patch-2.6.9-rc2-bk11
- dm9k-rc2.patch
- patchin (mtd 2004/09/19)
- nand_multi1.diff
Now, the board start with NFS e detect the NAND Flash; but boot output is unusual, infact is:
FTL driver: nftlcore.c $Revision: 1.96 $, nftlmount.c $Revision: 1.36 $
S3C2410 NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand: mapped registers at c4880000
s3c2410-nand: timing Master 10ns, Tacls 70ns, Twrph0 70ns, Twrph1 70ns
No NAND device found!!!
NAND device: Manufacturer ID: 0x20, Chip ID: 0x76 (ST Micro NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1154 at 0x01208000
Bad eraseblock 4085 at 0x03fd4000
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 17 at 0x00044000
Bad eraseblock 18 at 0x00048000
Bad eraseblock 19 at 0x0004c000
Bad eraseblock 20 at 0x00050000
Bad eraseblock 21 at 0x00054000
Bad eraseblock 22 at 0x00058000
Bad eraseblock 23 at 0x0005c000
Bad eraseblock 24 at 0x00060000
Bad eraseblock 25 at 0x00064000
Bad eraseblock 27 at 0x0006c000
Bad eraseblock 28 at 0x00070000
Bad eraseblock 29 at 0x00074000
Bad eraseblock 30 at 0x00078000
Bad eraseblock 31 at 0x0007c000
Bad eraseblock 32 at 0x00080000
Bad eraseblock 33 at 0x00084000
Bad eraseblock 34 at 0x00088000
Bad eraseblock 35 at 0x0008c000
Bad eraseblock 36 at 0x00090000
Bad eraseblock 37 at 0x00094000
Bad eraseblock 38 at 0x00098000
Bad eraseblock 39 at 0x0009c000
Bad eraseblock 40 at 0x000a0000
Bad eraseblock 41 at 0x000a4000
Bad eraseblock 42 at 0x000a8000
Bad eraseblock 43 at 0x000ac000
Bad eraseblock 44 at 0x000b0000
Bad eraseblock 45 at 0x000b4000
Bad eraseblock 46 at 0x000b8000
Bad eraseblock 47 at 0x000bc000
Bad eraseblock 48 at 0x000c0000
Bad eraseblock 49 at 0x000c4000
Bad eraseblock 50 at 0x000c8000
Bad eraseblock 51 at 0x000cc000
Bad eraseblock 52 at 0x000d0000
Bad eraseblock 53 at 0x000d4000
Bad eraseblock 54 at 0x000d8000
Bad eraseblock 55 at 0x000dc000
Bad eraseblock 56 at 0x000e0000
Bad eraseblock 57 at 0x000e4000
Bad eraseblock 58 at 0x000e8000
Bad eraseblock 59 at 0x000ec000
Bad eraseblock 60 at 0x000f0000
Bad eraseblock 61 at 0x000f4000
Bad eraseblock 62 at 0x000f8000
Bad eraseblock 63 at 0x000fc000
Bad eraseblock 64 at 0x00100000
Bad eraseblock 65 at 0x00104000
Bad eraseblock 66 at 0x00108000
Bad eraseblock 67 at 0x0010c000
Bad eraseblock 68 at 0x00110000
Bad eraseblock 69 at 0x00114000
Bad eraseblock 70 at 0x00118000
Bad eraseblock 71 at 0x0011c000
Bad eraseblock 72 at 0x00120000
Bad eraseblock 73 at 0x00124000
Bad eraseblock 74 at 0x00128000
Bad eraseblock 75 at 0x0012c000
Bad eraseblock 76 at 0x00130000
Bad eraseblock 77 at 0x00134000
Bad eraseblock 78 at 0x00138000
Bad eraseblock 79 at 0x0013c000
Bad eraseblock 80 at 0x00140000
Bad eraseblock 81 at 0x00144000
Bad eraseblock 82 at 0x00148000
Bad eraseblock 83 at 0x0014c000
Bad eraseblock 84 at 0x00150000
Bad eraseblock 85 at 0x00154000
Bad eraseblock 86 at 0x00158000
Bad eraseblock 87 at 0x0015c000
Bad eraseblock 88 at 0x00160000
Bad eraseblock 89 at 0x00164000
Bad eraseblock 1193 at 0x012a4000
Bad eraseblock 1500 at 0x01770000
Bad eraseblock 1844 at 0x01cd0000
Bad eraseblock 2290 at 0x023c8000
Bad eraseblock 3946 at 0x03da8000
No NAND device found!!!
s3c2410-nand: registered device sets:
s3c2410-nand: set 0, SmartMedia:error 1
s3c2410-nand: set 1, chip0:ok:
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00004000 : "Boot Agent"
mtd: Giving out device 0 to Boot Agent
0x00004000-0x00400000 : "/boot"
mtd: Giving out device 1 to /boot
0x00400000-0x04000000 : "user"
mtd: Giving out device 2 to user
s3c2410-nand: set 2, chip1:ok:
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00004000 : "Boot Agent"
mtd: Giving out device 3 to Boot Agent
0x00004000-0x00400000 : "/boot"
mtd: Giving out device 4 to /boot
0x00400000-0x04000000 : "user"
mtd: Giving out device 5 to user
s3c2410-nand: set 3, chip2:error 1
I don't get work with the NAND, why?
MTD detect 5 devices, I've only 2 NAND. Why, occurs that?
The proc/ is empty, there aren't device, why?
Must I work with /dev/mtdN or /dev/mtdblockN?
Thanks,
Lorenzo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Nand detect
2004-09-28 10:17 Nand detect lp4u
@ 2004-09-28 10:55 ` Ben Dooks
0 siblings, 0 replies; 9+ messages in thread
From: Ben Dooks @ 2004-09-28 10:55 UTC (permalink / raw)
To: lp4u@inwind.it; +Cc: MTD mailing list
On Tue, Sep 28, 2004 at 12:17:22PM +0200, lp4u@inwind.it wrote:
> Hi,
>
> I've a s3c24210 board with BAST architecture, with 2 NAND on board.
> I've compiling the kernel 2.6.9-rc2 after patched it with:
> - patch-2.6.9-rc2-bk11
> - dm9k-rc2.patch
> - patchin (mtd 2004/09/19)
> - nand_multi1.diff
the next release should be in mtd, and we will be able to do
away with the nand_multi1.diff
[snip]
> Bad eraseblock 3946 at 0x03da8000
> No NAND device found!!!
> s3c2410-nand: registered device sets:
> s3c2410-nand: set 0, SmartMedia:error 1
> s3c2410-nand: set 1, chip0:ok:
> Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
> 0x00000000-0x00004000 : "Boot Agent"
> mtd: Giving out device 0 to Boot Agent
> 0x00004000-0x00400000 : "/boot"
> mtd: Giving out device 1 to /boot
> 0x00400000-0x04000000 : "user"
> mtd: Giving out device 2 to user
> s3c2410-nand: set 2, chip1:ok:
> Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
> 0x00000000-0x00004000 : "Boot Agent"
> mtd: Giving out device 3 to Boot Agent
> 0x00004000-0x00400000 : "/boot"
> mtd: Giving out device 4 to /boot
> 0x00400000-0x04000000 : "user"
> mtd: Giving out device 5 to user
> s3c2410-nand: set 3, chip2:error 1
>
> I don't get work with the NAND, why?
> MTD detect 5 devices, I've only 2 NAND. Why, occurs that?
each mtd device node is 1 partition, not one chip.
> The proc/ is empty, there aren't device, why?
/proc is for information, not device nodes.
> Must I work with /dev/mtdN or /dev/mtdblockN?
/dev/mtdX and /dev/mtdblockN are the proper devices to
use for accessing the NAND partitions
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2004-09-28 10:55 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-23 9:54 NAND detect lp4u
2004-09-23 10:53 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 10:17 Nand detect lp4u
2004-09-28 10:55 ` Ben Dooks
2004-09-22 15:55 NAND detect lp4u
2004-09-22 20:29 ` Ben Dooks
2004-09-23 7:11 ` Thomas Gleixner
2004-09-23 9:48 ` Ben Dooks
[not found] ` <20040923191506.GE25491@home.fluff.org>
2004-09-23 23:05 ` Ben Dooks
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox