From: "Rudi Engelbertink" <rudi@unsec.nl>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: unable to get NAND oobinfo
Date: Fri, 4 Feb 2005 13:00:35 +0100 [thread overview]
Message-ID: <20050204120004.M34991@unsec.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0502041157560.29798@phoenix.infradead.org>
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
> What does cat /proc/mtd say ?
>
> On Fri, 4 Feb 2005, Rudi Engelbertink wrote:
> > 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
> >
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
> >
>
> --
> 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
next prev parent reply other threads:[~2005-02-04 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 11:43 unable to get NAND oobinfo Rudi Engelbertink
2005-02-04 11:58 ` Artem B. Bityuckiy
2005-02-04 12:00 ` Rudi Engelbertink [this message]
2005-02-08 16:51 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050204120004.M34991@unsec.nl \
--to=rudi@unsec.nl \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.