From: Artem Bityutskiy <dedekind@infradead.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org, vicky <vicky.irobot@gmail.com>
Subject: Re: question about node creation /dev/mtd*
Date: Fri, 18 Jan 2008 14:56:42 +0200 [thread overview]
Message-ID: <1200661002.6934.23.camel@sauron> (raw)
In-Reply-To: <20080118064432.19233a37@zod.rchland.ibm.com>
On Fri, 2008-01-18 at 06:44 -0600, Josh Boyer wrote:
> On Fri, 18 Jan 2008 17:42:39 +0530
> vicky <vicky.irobot@gmail.com> wrote:
>
> > Hi,
> >
> > I have enabled mtd in my config. When I boot from the updated kernel I
> > find that /dev/mtdblock is not created?
> >
> > How does the /dev/mtdblock get created? I didn't find this in the
> > init/rcs script. I am under an impression that once the mtd is enabled
> > in the linux
> > config file the creation of the corresponding node is taken care in some
> > script.
>
> You need to either have udev running, or create it manually yourself
> with mknod (which can be done via a script you write). This is, of
> course, assuming you have the mtdblock module loaded or compiled into
> your kernel.
udev will not help because MTD is not Linux Device Model-enabled, so
only ancient manual device node creation method may be used. There is a
MAKEDEV script in mtd-utils.git which may help.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-01-18 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 12:12 question about node creation /dev/mtd* vicky
2008-01-18 12:27 ` vicky
2008-01-18 12:44 ` Josh Boyer
2008-01-18 12:56 ` Artem Bityutskiy [this message]
2008-01-18 13:14 ` Josh Boyer
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=1200661002.6934.23.camel@sauron \
--to=dedekind@infradead.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vicky.irobot@gmail.com \
/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.