From: Eugene Surovegin <ebs@ebshome.net>
To: Marco Schramel <Schramel.Linux@go.bartec.de>
Cc: PPC_LINUX <linuxppc-embedded@ozlabs.org>
Subject: Re: mtd mount problem
Date: Thu, 21 Apr 2005 08:47:34 -0700 [thread overview]
Message-ID: <20050421154733.GC8189@gate.ebshome.net> (raw)
In-Reply-To: <200504211144.28584.Schramel.Linux@go.bartec.de>
On Thu, Apr 21, 2005 at 11:44:28AM +0200, Marco Schramel wrote:
> Hi Eugene,
>
> thanks for your answer
>
> > Check that you have CONFIG_MTD_BLOCK enabled in your .config.
> #
> # Memory Technology Devices (MTD)
> #
> CONFIG_MTD=y
> CONFIG_MTD_DEBUG=y
> CONFIG_MTD_DEBUG_VERBOSE=0
> CONFIG_MTD_PARTITIONS=y
> # CONFIG_MTD_CONCAT is not set
> # CONFIG_MTD_REDBOOT_PARTS is not set
> # CONFIG_MTD_CMDLINE_PARTS is not set
> CONFIG_MTD_CHAR=y
> CONFIG_MTD_BLOCK=y
> # CONFIG_FTL is not set
> # CONFIG_NFTL is not set
> # CONFIG_INFTL is not set
>
> >
> > Also, check that you have /dev/mtdblock1 node in /dev directory on the
> > target.
> >
>
> This is what i meant before with ramdisk.
>
> /dev # ls -al mtdblock1
> brw-rw-r-- 1 root root 31, 1 Mar 17 2005 mtdblock1
>
> It should be ok. Isn't it ??
Hmm, yes, provided you have also jffs2 enabled, but I'd expect
different error message if not.
Could you show us dmesg output, and also `cat /proc/devices`?
--
Eugene
next prev parent reply other threads:[~2005-04-21 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 9:17 mtd mount problem Marco Schramel
2005-04-21 8:50 ` Eugene Surovegin
2005-04-21 9:44 ` Marco Schramel
2005-04-21 15:47 ` Eugene Surovegin [this message]
2005-04-21 9:54 ` Daniel Ann
2005-04-21 10:32 ` Wolfgang Denk
2005-04-21 13:02 ` Marco Schramel
2005-04-22 1:31 ` Jörn Engel
2005-04-22 1:53 ` Eugene Surovegin
2005-04-22 1:55 ` Eugene Surovegin
2005-04-22 2:11 ` Jörn Engel
2005-04-21 14:44 ` Kylo Ginsberg
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=20050421154733.GC8189@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Schramel.Linux@go.bartec.de \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).