From: bandwidthcrunch <bandwidthcrunch@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Obtaining NAND oobinfo
Date: Thu, 28 Oct 2004 11:03:57 +0530 [thread overview]
Message-ID: <b4618e0f04102722337611da67@mail.gmail.com> (raw)
Hi All,
Any clues why
./flash_eraseall -j /dev/mtd3
./flash_eraseall: /dev/mtd3: unable to get NAND oobinfo
should happen ?
cat /proc/mtd shows
dev: size erasesize name
mtd0: 00040000 00040000 "Bootloader"
mtd1: 00100000 00040000 "Kernel"
mtd2: 01ec0000 00040000 "Filesystem"
mtd3: 02000000 00004000 "Filesystem on nand"
and dmesg shows
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Creating 1 MTD partitions on "Samsung K9D1208V0M":
0x00000000-0x02000000 : "Filesystem on nand"
Any suggestions would be great
regards,
band
reply other threads:[~2004-10-28 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b4618e0f04102722337611da67@mail.gmail.com \
--to=bandwidthcrunch@gmail.com \
--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.