From: Iwo Mergler <Iwo.Mergler@netcommwireless.com>
To: Richard Weinberger <richard@nod.at>, Josh Cartwright <joshc@ni.com>
Cc: Ben Shelton <ben.shelton@ni.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"punnaiah.choudary.kalluri@xilinx.com"
<punnaiah.choudary.kalluri@xilinx.com>,
"xander.huff@ni.com" <xander.huff@ni.com>
Subject: RE: Adding subpage support to NAND driver -- backwards compatibility concerns
Date: Fri, 24 Apr 2015 09:13:24 +1000 [thread overview]
Message-ID: <EACD232272DA4849B060F0828564D13B95342BDE88@ntcex01.corp.netcomm.com.au> (raw)
In-Reply-To: <5539486F.60407@nod.at>
On Fri, 24 Apr 2015 05:30:55 +1000
Richard Weinberger <richard@nod.at> wrote:
> Am 23.04.2015 um 20:39 schrieb Josh Cartwright:
> > Is there no metadata in the UBI data structures in flash that
> > indicate the min IO boundary? Assuming no, is another option to,
> > at the time of attach, try both the min IO access size, and, if
> > that doesn't work, try the page size?
>
> Correct. UBI has no information about that.
> If you add subpage support to the driver I'd make it opt-in such that
> existing setups won't break.
I'm wondering, given that EC headers contain vid header offset
and data offset fields, shouldn't UBI be able to deduce at attach
time what the relevant parameters are on a partition?
Something along the lines of using the parameters of the first
PEB with valid EC header, then balking if another EC header is
encountered with different info. As long as MTD allows the
so deduced minimum access size, it seems safe.
This could help enormously in situations like this, where
MTD drivers experience sudden bursts of improvement.
Best regards,
Iwo
next prev parent reply other threads:[~2015-04-23 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 17:29 Adding subpage support to NAND driver -- backwards compatibility concerns Ben Shelton
2015-04-23 2:48 ` Iwo Mergler
2015-04-23 18:39 ` Josh Cartwright
2015-04-23 19:30 ` Richard Weinberger
2015-04-23 23:13 ` Iwo Mergler [this message]
2015-04-23 23:32 ` 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=EACD232272DA4849B060F0828564D13B95342BDE88@ntcex01.corp.netcomm.com.au \
--to=iwo.mergler@netcommwireless.com \
--cc=adrian.hunter@intel.com \
--cc=ben.shelton@ni.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joshc@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=punnaiah.choudary.kalluri@xilinx.com \
--cc=richard@nod.at \
--cc=xander.huff@ni.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;
as well as URLs for NNTP newsgroup(s).