From: Richard Weinberger <richard@nod.at>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Alexander Kaplan <alex@nextthing.co>,
Brian Norris <computersforpeace@gmail.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [RFC] Raising the UBI version
Date: Wed, 22 Jun 2016 16:05:17 +0200 [thread overview]
Message-ID: <576A9B1D.3010201@nod.at> (raw)
In-Reply-To: <20160622160118.28a4339a@bbrezillon>
Am 22.06.2016 um 16:01 schrieb Boris Brezillon:
> On Wed, 22 Jun 2016 15:54:34 +0200
> Richard Weinberger <richard@nod.at> wrote:
>
>> Am 22.06.2016 um 14:43 schrieb Boris Brezillon:
>>> Why do we need to hardcode /sys/class/ubi/version to 1? We just need to
>>> update the mtd-utils to support version 2. Am I missing something?
>>
>> We don't want to break existing userspace.
>> Why should ubimkvol or ubiattach fail on a system with SLC NAND and
>> CONFIG_MTD_UBI_CONSOLIDATE=y?
>
> But version won't be set to 2 in this case. If it's an SLC NAND we
> don't need to use UBI version 2, do we.
/sys/class/ubi/version is the version of the UBI implementation,
not the version of the attached UBI image.
It will the here as soon you load the UBI module.
Thanks,
//richard
next prev parent reply other threads:[~2016-06-22 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 19:19 [RFC] Raising the UBI version Richard Weinberger
2016-06-22 12:43 ` Boris Brezillon
2016-06-22 13:09 ` Michal Suchanek
2016-06-22 13:17 ` Boris Brezillon
2016-06-22 13:24 ` Boris Brezillon
2016-06-22 13:54 ` Richard Weinberger
2016-06-22 14:01 ` Boris Brezillon
2016-06-22 14:05 ` Richard Weinberger [this message]
2016-06-22 14:13 ` Boris Brezillon
2016-06-22 14:21 ` Richard Weinberger
2016-06-22 14:39 ` Boris Brezillon
2016-06-22 14:43 ` Richard Weinberger
2016-06-22 14:52 ` Boris Brezillon
2016-06-22 14:59 ` Richard Weinberger
2016-06-22 15:06 ` Boris Brezillon
2016-06-22 19:59 ` Richard Weinberger
2016-06-22 20:12 ` Boris Brezillon
2016-06-22 20:24 ` 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=576A9B1D.3010201@nod.at \
--to=richard@nod.at \
--cc=alex@nextthing.co \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).