From: "Raj Kumar Yadav" <ryadav@neomagic.com>
To: <linux-mtd@lists.infradead.org>
Subject: RE: nandwrite problem
Date: Mon, 17 Jul 2006 22:31:49 +0530 [thread overview]
Message-ID: <004e01c6a9c2$b330d7b0$491fa8c0@pcryadav> (raw)
In-Reply-To: <625fc13d0607170804i745f2566k8173ba5d85cad662@mail.gmail.com>
Also for mtdblock/5 the character node will be mtd10 "mknod /dev/mtd10 c 90
10".
With mtd character interface every partition is accessed through pair of two
char device node.
First with read-write permission. Second with read-only permission.
It is like
/dev/mtdblock/0 b 31 0
/dev/mtd0 c 90 0 (Read-write)
/dev/mtd1 c 90 1 (read only)
/dev/mtdblock/1 b 31 1
/dev/mtd2 c 90 2 (Read-write)
/dev/mtd3 c 90 3 (read only)
...
/dev/mtdblock/5 b 31 5
/dev/mtd10 c 90 10 (Read-write)
/dev/mtd11 c 90 11 (read only)
Raj Kumar Yadav
-----Original Message-----
From: linux-mtd-bounces@lists.infradead.org
[mailto:linux-mtd-bounces@lists.infradead.org] On Behalf Of Josh Boyer
Sent: Monday, July 17, 2006 8:35 PM
To: Davide CASCONE
Cc: linux-mtd@lists.infradead.org
Subject: Re: nandwrite problem
On 7/17/06, Davide CASCONE <davide.cascone@st.com> wrote:
>
> I have a NAND device related to MTD block 5. The NAND device is correctly
probing during the kernel boot phase.
> If I run the following commands
>
> #mkdir /dev/mtdblock/5 b 31 5
> #mount -t jffs2 /dev/mtdblock/5 /nand/
>
> the JFFS2 file system is correctly mounting on the /nand/ directory.
> But, if I run the following command
>
> #./nandwrite -j /dev/mtdblock/5 filesys.jffs2_nand
nandwrite needs a character device, not a block device. Use /dev/mtd5
instead.
josh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2006-07-17 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 14:59 nandwrite problem Davide CASCONE
2006-07-17 15:04 ` Josh Boyer
2006-07-17 17:01 ` Raj Kumar Yadav [this message]
2006-07-17 17:43 ` Josh Boyer
2006-07-17 18:10 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 5:24 Sridhar C.R
2009-04-09 7:29 Donal Morrissey
[not found] ` <BAY131-W55A4C892E0412CE9650E0EE2830@phx.gbl>
2009-04-09 20:27 ` Donal Morrissey
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='004e01c6a9c2$b330d7b0$491fa8c0@pcryadav' \
--to=ryadav@neomagic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox