From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: Andre Puschmann <andre.puschmann@stud.tu-ilmenau.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting mtd block device raises "Block device required"
Date: Wed, 11 Jun 2008 11:55:46 +0200 [thread overview]
Message-ID: <484FA122.1030208@cetrtapot.si> (raw)
In-Reply-To: <g2o5oo$fqe$1@ger.gmane.org>
Andre Puschmann wrote:
> Hi,
>
> Hinko Kocevar wrote:
>> Char device seems to work..
>
> Yes, sorry for being not precise.
> Coping a jffs2 image (in 2.6.25) at /dev/mtd5 and mouting the same one
> in 2.6.21 (/dev/mtdblock5) works. So accessing the flash as a character
> device works.
>
>> What is the ls -l /dev/mtdblock5 output?
>
> As expected:
> $ ls -l /dev/mtdblock5
> brw-rw---- 1 root root 31, 5 Jan 1 1970 /dev/mtdblock5
>
Good.
>
>> Also could you try:
>> mount -t jffs2 /dev/mtdblock5 /mnt/flash
>
> I also tried that:
>
> # mount -t jffs2 /dev/mtdblock5 /mnt/flash
> mount: mounting /dev/mtdblock5 on /mnt/flash failed: Invalid argument
>
Is this true (kernel config)?:
CONFIG_JFFS2_FS=y
>
> But it seems like it has to do something with the block device driver
> mapping:
>
> $ head -n 2 /dev/mtdblock5 | hexdump -C
> head: /dev/mtdblock5: No such device or address
>
What about kernel configuration around the MTD block devices? I think these should be enabled:
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
--
ČETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar@cetrtapot.si
Http: www.cetrtapot.si
next prev parent reply other threads:[~2008-06-11 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 8:44 Mounting mtd block device raises "Block device required" Andre Puschmann
2008-06-11 8:55 ` Hinko Kocevar
2008-06-11 9:26 ` Andre Puschmann
2008-06-11 9:38 ` Nancy
2008-06-11 9:55 ` Hinko Kocevar [this message]
2008-06-11 10:33 ` Andre Puschmann
2008-06-12 13:08 ` Andre Puschmann
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 18:10 Fabiano Ferronato
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=484FA122.1030208@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--cc=andre.puschmann@stud.tu-ilmenau.de \
--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