From: Artem Bityutskiy <dedekind1@gmail.com>
To: Gilles <gilles.ganault@free.fr>
Cc: linux-mtd@lists.infradead.org, Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [Ubi] Wrong major:minor
Date: Wed, 01 Jun 2011 11:29:23 +0300 [thread overview]
Message-ID: <1306916963.4405.72.camel@localhost> (raw)
In-Reply-To: <BANLkTimab0pKp68f_coPfsjm_6GdKAxSew@mail.gmail.com>
On Sun, 2011-05-29 at 11:54 -0400, Mike Frysinger wrote:
> On Sun, May 29, 2011 at 06:39, Gilles wrote:
> > I'm no Linux expert, and was wondering how to find out what the
> > correct major:minor is for the Ubi device nodes?
>
> they're most likely dynamic and there's no safe way you could create
> the nodes ahead of time with a device table. simply run mdev to take
> care of /dev for you.
>
> you can check /proc/devices to be sure ... anything over 250 is dynamic
> -mike
Right, UBI allocates device numbers dynamically, so pre-creating device
nodes is not a good idea.
Major/minor for every UBI device / UBI volume can be found at:
/sys/class/ubi/ubiX/dev
/sys/class/ubi/ubiX_Y/dev
Or the major number can be indeed found at /proc/devices, and then the
minor numbers follow the following fomula:
UBI Volume major number = UBI device major number.
UBI Volume minor number = UBI volume ID + 1.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-06-01 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 10:39 [Ubi] Wrong major:minor Gilles
2011-05-29 13:22 ` Gilles
2011-05-29 15:54 ` Mike Frysinger
2011-05-30 9:53 ` Gilles
2011-05-30 12:06 ` Gilles
2011-05-30 15:00 ` Gilles
2011-05-30 16:29 ` Mike Frysinger
2011-06-01 11:22 ` Gilles
2011-06-01 8:29 ` Artem Bityutskiy [this message]
2011-06-01 8:36 ` Artem Bityutskiy
2011-06-01 8:37 ` Artem Bityutskiy
2011-06-01 10:11 ` Mike Frysinger
2011-06-01 10:14 ` Artem Bityutskiy
2011-06-24 11:46 ` Peter Korsgaard
2011-06-24 12:05 ` Gilles
2011-06-24 14:33 ` Mike Frysinger
2011-06-01 11:21 ` Gilles
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=1306916963.4405.72.camel@localhost \
--to=dedekind1@gmail.com \
--cc=gilles.ganault@free.fr \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@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.