From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [2001:838:3de:1000::2] (helo=fserver.unsec.nl) by canuck.infradead.org with esmtps (Exim 4.43 #1 (Red Hat Linux)) id 1Cx1sb-00027V-Mw for linux-mtd@lists.infradead.org; Fri, 04 Feb 2005 06:44:06 -0500 Received: from unsec.nl (localhost.localdomain [127.0.0.1]) by fserver.unsec.nl (8.12.11/8.12.11) with ESMTP id j14Bhwrm024607 for ; Fri, 4 Feb 2005 12:43:58 +0100 From: "Rudi Engelbertink" To: linux-mtd@lists.infradead.org Date: Fri, 4 Feb 2005 12:43:58 +0100 Message-Id: <20050204112622.M33820@unsec.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Subject: unable to get NAND oobinfo List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, trying to get my nand driver (for compulab 586core board) on kernel 2.4.27 working, i ran into the following problem: The driver is recognised and appears to work. That means I can read the mtdchar device but whin I'm trying to format the device, I recieve the message 'flash_eraseall: /dev/mtd3: unable to get NAND oobinfo' An strace replies with: open("/dev/mtd3", O_RDWR) = 3 ioctl(3, 0x80204d01, 0xbffffdf0) = 0 ioctl(3, 0x80c84d0a, 0xbffffd20) = -1 ENOTTY (Inappropriate ioctl for device) At that moment it does an ioctl(fd, MEMGETOOBSEL, &oobinfo) but it looks like the device is not registered properly. NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MB 3,3V) On the mailing list I found an email with the same question about this but no answer. Could you give me a hint about what is going wrong or a posible solution. RGDS Rudi. -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. Benjamin Franklin (1706-1790), Letter to Josiah Quincy, Sept. 11, 1773. GnuPG Key fingerprint = 706C E2AC 7AE2 BCEE 04EB A962 0A75 7F9B 07A1 83E8