From: Richard Weinberger <richard@nod.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] Porting UBI fixes (specially fastmap's) to U-Boot
Date: Sat, 3 Oct 2015 11:03:53 +0200 [thread overview]
Message-ID: <560F99F9.5090403@nod.at> (raw)
In-Reply-To: <560F5942.7000500@denx.de>
Hi!
Am 03.10.2015 um 06:27 schrieb Heiko Schocher:
>>> According to Richard Weinberger, UBI fastmap is broken in U-Boot.
>>> There are plenty
>>> of fixes in Linux that we should pull in U-Boot to fix it.
>
> Thanks for pointing!
>
>> BTW: it is not broken in terms of you broke it.
>
> Puuh ;-)
>
> In what way is it broken? If we update to 4.1, will ubi work (mount
> an existing UBI partition with fastmap) on existing boards?
The on-flash layout did not change, so it should work.
The "old" fastmap code had a number of issues, mostly related to powercuts
and some logical issues.
In 4.1 it saw a huge amount of rework and fixes, including UBI core code.
>> It is just the old fastmap version. In v4.1 fastmap saw
>> a massive update. Sadly this changes are a way to big for the stable tree.
>
> What do you mean with "for the stable tree" ?
I was under the assumption that you are porting all UBI fixes to u-boot which are marked for stable.
As the fastmap rework turned out to be much more than a few single fixes they are not
in the Linux stable tree.
>>> Maybe you are already aware of this and you have some work-in-progress
>>> patches to share?
>>> Otherwise, I might be able to spend some time working on this in the next weeks.
>>
>> I'll happily help you!
>
> I am next week in Dublin on the ELCE so I have no time to look into
> this issue ... maybe the week after ...
I'm also at ELCE, maybe we can discuss this also in person.
Thanks,
//richard
next prev parent reply other threads:[~2015-10-03 9:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 16:27 [U-Boot] Porting UBI fixes (specially fastmap's) to U-Boot Ezequiel Garcia
2015-10-02 18:46 ` Richard Weinberger
2015-10-03 4:27 ` Heiko Schocher
2015-10-03 9:03 ` Richard Weinberger [this message]
2015-10-08 12:51 ` Heiko Schocher
2015-10-08 13:03 ` Richard Weinberger
2015-10-08 14:54 ` Heiko Schocher
2015-10-08 14:58 ` Hans de Goede
2015-10-08 16:04 ` Richard Weinberger
2015-10-09 3:34 ` Heiko Schocher
2015-10-08 15:54 ` Ezequiel Garcia
2015-10-09 4:01 ` Heiko Schocher
2015-10-09 12:30 ` Heiko Schocher
2015-10-16 7:56 ` Heiko Schocher
2015-10-16 11:58 ` Ezequiel Garcia
2015-10-17 18:07 ` Ezequiel Garcia
2015-10-17 18:28 ` Richard Weinberger
2015-10-19 5:17 ` Heiko Schocher
2015-10-19 13:47 ` Ezequiel Garcia
2015-10-19 14:53 ` Heiko Schocher
2015-10-19 20:22 ` Richard Weinberger
2015-10-19 21:40 ` Ezequiel Garcia
2015-10-19 21:48 ` Richard Weinberger
2015-10-20 4:00 ` Heiko Schocher
2015-10-20 7:16 ` 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=560F99F9.5090403@nod.at \
--to=richard@nod.at \
--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.