From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ubifs: Allow ubifsmount volume reference by number
Date: Mon, 05 Nov 2012 23:06:12 +0530 [thread overview]
Message-ID: <5097F90C.8080405@gmail.com> (raw)
In-Reply-To: <CANr=Z=aza5vOfHs5=cXkwMf0cdknVnTiOZW-WtSbKVL9S7E-Cw@mail.gmail.com>
Hi Joe,
On 11/5/2012 10:19 PM, Joe Hershberger wrote:
> Hi Vikram,
>
> On Mon, Nov 5, 2012 at 10:43 AM, Vikram Narayanan<vikram186@gmail.com> wrote:
>>
>> On 11/2/2012 8:24 AM, Joe Hershberger wrote:
>>>
>>> UBI can mount volumes by name or number The current code forces you
>>> to name the volume by prepending every name with "ubi:".
>>>
>>> From fs/ubifs/super.c
>>> * There are several ways to specify UBI volumes when mounting UBIFS:
>>> * o ubiX_Y - UBI device number X, volume Y;
>>> * o ubiY - UBI device number 0, volume Y;
>>> * o ubiX:NAME - mount UBI device X, volume with name NAME;
>>> * o ubi:NAME - mount UBI device 0, volume with name NAME.
>>>
>>> Now any name passed in any of the above forms are allowed.
>>
>>
>> What exactly are we gaining from this naming compared to the default?
>> In what way the old naming affects the end user?
>
> The reason I needed this change is so that I could specify the volume
> by number in a script instead of being forced to know the name. In
> Linux you can use the volume number using the format above (it's the
> same code).
If that is the case, then the one can create the partition using the
below command,
> ubi createvol <vol name>
<vol name> can be any of the 4 methods listed above.
and the prefix "ubi:" will be appended in the environment which is
expected by kernel for mounting. Right?
~Vikram
next prev parent reply other threads:[~2012-11-05 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 2:54 [U-Boot] [PATCH] ubifs: Allow ubifsmount volume reference by number Joe Hershberger
2012-11-05 16:43 ` Vikram Narayanan
2012-11-05 16:49 ` Joe Hershberger
2012-11-05 17:36 ` Vikram Narayanan [this message]
2012-11-05 18:18 ` Joe Hershberger
2012-11-05 18:41 ` Vikram Narayanan
2012-11-05 18:49 ` Joe Hershberger
2013-03-04 21:27 ` [U-Boot] " Tom Rini
2013-03-04 21:27 ` Tom Rini
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=5097F90C.8080405@gmail.com \
--to=vikram186@gmail.com \
--cc=u-boot@lists.denx.de \
/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.