unable to get NAND oobinfo
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 fordevice)
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.
Signature · 4 lines
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
What does cat /proc/mtd say ?
Quoted 15 lines · Rudi Engelbertink
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 fordevice)
At that moment it does anioctl(fd, MEMGETOOBSEL, &oobinfo)but it looks like the device is not registered properly.
Quoted 18 lines
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.
Signature · 9 lines
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 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
cat /proc/mtd
dev: size erasesize name
mtd0: 000e0000 00010000 "cl586nor Dos Low"
mtd1: 00100000 00010000 "cl586nor Dos High"
mtd2: 00020000 00010000 "cl586nor BIOS"
mtd3: 04000000 00004000 "cl586core NAND FS 0"
On Fri, 4 Feb 2005 11:58:33 +0000 (GMT), Artem B. Bityuckiy wrote
Quoted 8 lines
What does cat
/proc/mtdsay ?Quoted 5 lines · Rudi Engelbertink
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
Quoted 29 lines
Quoted 10 lines
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 fordevice)
At that moment it does anioctl(fd, MEMGETOOBSEL, &oobinfo)but it looks like the device is not registered properly.Quoted 18 lines
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.
Signature · 9 lines
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 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
Quoted 4 lines
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
--
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
Quoted 8 lines · Rudi Engelbertink
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:
Quoted 4 lines
open("/dev/mtd3", O_RDWR) = 3 ioctl(3, 0x80204d01, 0xbffffdf0) = 0 ioctl(3, 0x80c84d0a, 0xbffffd20) = -1 ENOTTY (Inappropriate ioctl fordevice)
I guess you are using vanilla 2.4.27 without mtd patches. So the ioctl is not implemented. The NAND stuff in MTD/JFFS2 on vanilla 2.4.xx is not really fully functional.
tglx