From: Tanya Brokhman <tlinder@codeaurora.org>
To: Richard Weinberger <richard@nod.at>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Subject: Re: [PATCH 2/2] ubiformat: Leave space for fastmap anchor
Date: Wed, 22 Oct 2014 13:48:10 +0300 [thread overview]
Message-ID: <54478B6A.4020106@codeaurora.org> (raw)
In-Reply-To: <54476C0F.4050603@nod.at>
On 10/22/2014 11:34 AM, Richard Weinberger wrote:
> Am 22.10.2014 um 10:19 schrieb Tanya Brokhman:
>> I care :) Its in my TODO to update ubinize to leave space for fastmap anchor (and perhaps generate a fastmap data as well but this is just a thought).
>
> While talking about fastmap TODOs, here you can find my fastmap patch queue:
> https://git.kernel.org/cgit/linux/kernel/git/rw/misc.git/log/?h=ubi-current
>
> These patches are *not* ready for mainline, some of them need a rewrite
> to meet all design goals of UBI. But maybe the one or other fixes an issue
> which is on your TODO list. :-)
>
> Thanks,
> //richard
>
thanks! it's very helpful! and just to combine the reply in one email:
"Please generate the fastmap data such that upon the very first attach
fastmap can be used."
This is what I was thinking. Its doable, right? since in ubinize we have
all data required for constructing fastmap.
From all your discussions with Artem I figure we can expect quite a few
changes to the fastmap implementation. Is the layout also going to
change? I remember you mentioning such idea in one of the emails.
Thanks,
Tanya Brokhman
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-22 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 7:48 [PATCH] mtd-utils: ubiformat: Add fastmap support Sascha Hauer
2014-10-22 7:48 ` [PATCH 1/2] ubiformat: Factor out a write_eraseblock function Sascha Hauer
2014-10-22 7:48 ` [PATCH 2/2] ubiformat: Leave space for fastmap anchor Sascha Hauer
2014-10-22 8:15 ` Richard Weinberger
2014-10-22 8:19 ` Tanya Brokhman
2014-10-22 8:27 ` Richard Weinberger
2014-10-22 8:34 ` Richard Weinberger
2014-10-22 10:48 ` Tanya Brokhman [this message]
2014-10-22 10:51 ` Richard Weinberger
2014-10-22 9:01 ` Sascha Hauer
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=54478B6A.4020106@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=artem.bityutskiy@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox