All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Woody Wu <narkewoody@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: How do I know my UBI/UBIFS code version?
Date: Fri, 10 Oct 2014 20:41:52 +0200	[thread overview]
Message-ID: <54382870.1020607@nod.at> (raw)
In-Reply-To: <1197b309-a9e9-4976-8845-165a4e634bd0@email.android.com>

Am 10.10.2014 um 20:38 schrieb Woody Wu:
> 
> 
> On October 10, 2014 11:28:26 PM GMT+08:00, Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> On Fri, Oct 10, 2014 at 4:57 PM, Woody Wu <narkewoody@gmail.com> wrote:
>>> I am running ubi/ubifs on a ported ARM linux 3.1.x.  How do I get
>> know my ubi/ubifs version? In additional, if I found the version are
>> too old, could I simply copy a newer version source files to my 3.1 ARM
>> linux tree?
>>
>> Ported in terms of utterly broken by a SoC vendor? ;-)
>> If your kernel version is v3.1 then also UBI and UBIFS is v3.1 unless
>> someone messed with it.
>> To find out you need to consult the changelog.
>>
>> And no, you cannot simply copy&paste the sources files between kernel
>> releases as the internal kernel API is
>> a moving target.
> 
> 'ubinfo -a' returns to me "UBI version: 1" in its first line output.  Does it looks strange to you?  Thanks.

This version is always 1.
If we consider UBI Fastmap at some point rock stable _and_ make it default we'll change this version maybe to 2.

Thanks,
//richard

  reply	other threads:[~2014-10-10 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 14:57 How do I know my UBI/UBIFS code version? Woody Wu
2014-10-10 15:24 ` Steve B
2014-10-10 15:28 ` Richard Weinberger
2014-10-10 18:38   ` Woody Wu
2014-10-10 18:41     ` Richard Weinberger [this message]
2014-10-11  4:39       ` Woody Wu
2014-10-11  9:02         ` Richard Weinberger

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=54382870.1020607@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=narkewoody@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.