From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Gilles <gilles.ganault@free.fr>, linux-mtd@lists.infradead.org
Subject: Re: [Ubi] Wrong major:minor
Date: Wed, 01 Jun 2011 13:14:14 +0300 [thread overview]
Message-ID: <1306923254.4405.92.camel@localhost> (raw)
In-Reply-To: <BANLkTikha6F8GbWDNpwB4Q-v1V36ARcVVA@mail.gmail.com>
On Wed, 2011-06-01 at 06:11 -0400, Mike Frysinger wrote:
> On Wed, Jun 1, 2011 at 04:37, Artem Bityutskiy wrote:
> > On Wed, 2011-06-01 at 11:36 +0300, Artem Bityutskiy wrote:
> >> On Sun, 2011-05-29 at 12:39 +0200, Gilles wrote:
> >> > I used the following data to compile Ubi(fs) into a uClinux kernel:
> >> >
> >> > ========= device_table.txt
> >> > #UBIFS nodes
> >> > /dev/ubi_ctrl c 644 0 0 10 63 0 0 -
> >> > /dev/ubi0 c 644 0 0 253 0 0 0 -
> >> > =========
> >>
> >> But I guess you may add an UBI module parameter which will ask UBI to
> >> use major numbers you want - should be easy to do. E.g., if you add a
> >> 'major_base=200' parameter then UBI will use 200:0 for ubi0, 201:0 for
> >> ubi1, 200:1 for ubi0_0, 200:2 for ubi0_1, etc.
> >
> > Although I'm not sure - dynamic numbers were introduced because fixed
> > numbers are PITA, so adding such a parameter would be a step backward.
> > Not sure...
>
> yeah, i dont think there should be. at least nothing specific to ubi.
> perhaps a general kernel thing where you could match the registered
> name to a static #, but then that wouldnt be ubi's problem. that'd be
> in the core logic and work for all devices.
Yes, I agree. Gilles, please, disregard my suggestion.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-06-01 10:18 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
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 [this message]
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=1306923254.4405.92.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox