From: Markus Klotzbuecher <mk@mkio.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] miscellaneous ubispl and ubi improvements
Date: Wed, 17 Apr 2019 08:34:53 +0200 [thread overview]
Message-ID: <20190417063453.GA26887@e460.mkio.de> (raw)
In-Reply-To: <0fdca5b6-5f34-90fa-73b3-da3147f65592@denx.de>
Hello Heiko
On Tue, Apr 16, 2019 at 05:52:15AM +0200, Heiko Schocher wrote:
>
>Am 15.04.2019 um 17:32 schrieb Markus Klotzbuecher:
>> From: Markus Klotzbuecher <markus.klotzbuecher@kistler.com>
>>
>> Hello Heiko and Kyungmin
>>
>> This series contains a couple of UBI and UBI SPL improvements, notably
>> a ubispl extension to allow loading volumes by name. The motivation is
>> to use the UBI atomic volume rename functionality to allow double copy
>> software updates of U-Boot on UBI. To do that we configured the SPL to
>> always load the same volume name (e.g. "u-boot"), and the software
>> updater always installs into the secondary volume "u-boot_r". After a
>> successful upgrade, these two volume names are switched.
>
>Ok ... Hmm... if you use the bootcounter in SPL, you may have a chance
>to unbreak he board, if "u-boot" does not boot?
>
>How do you detect a successfull upgrade ?
At this point, if writing to the to-be-updated volume succeeds, we
consider it a successful upgrade. If not, the rename is not carried
out and the old volume will remain the active one.
To further improve reliability, this could be combined with an SPL
bootcounter, however to really be an improvement, that should probably
use an environment on UBI too (or anything more reliable than raw
NAND).
>> This extension is protected by #ifdefs as it will somewhat slow down
>> loading of volumes by id. This is because the code needs to disable
>> the optimization of ignoring all volume ids which are not
>> to-be-loaded, since these can only be resolved after attaching.
>>
>> We have tested both with and without fastmap enabled and both paths
>> seems to work reliably.
>
>Fine, thanks!
>
>> I also moved the ubispl config to Kconfig. There seem to be two boards
>
>Thanks!
>
>> that use this (Maintainers cc'ed on patch). I have not updated their
>> defconfigs (not being sure if I should) but would be pleased to do so.
>
>I prefer that you do so, but we will see, if the board maintainers
>give some feedback.
>
>Give me some time to look through your patches.
Sure, thank you!
Best regards
Markus
--
Markus Klotzbuecher
Freelancer Embedded, Distributed & Real-time
Am See 28, 78465 Konstanz, Germany
prev parent reply other threads:[~2019-04-17 6:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:32 [U-Boot] [PATCH 0/6] miscellaneous ubispl and ubi improvements Markus Klotzbuecher
2019-04-15 15:32 ` [U-Boot] [PATCH 1/6] env: ubi: KConfig: add CONFIG_ENV_UBI_VOLUME_REDUND Markus Klotzbuecher
2019-04-30 4:54 ` Heiko Schocher
2019-05-02 7:15 ` Markus Klotzbuecher
2019-05-09 8:59 ` Markus Klotzbuecher
2019-05-09 11:17 ` Heiko Schocher
2019-05-09 15:49 ` Markus Klotzbuecher
2019-05-09 18:42 ` mk at mkio.de
2019-04-15 15:32 ` [U-Boot] [PATCH 2/6] env: ubi: support configurable VID offset Markus Klotzbuecher
2019-04-30 4:57 ` Heiko Schocher
2019-04-15 15:32 ` [U-Boot] [PATCH 3/6] ubi: fix UBI_SILENCE_MSG Markus Klotzbuecher
2019-04-30 4:59 ` Heiko Schocher
2019-04-15 15:32 ` [U-Boot] [PATCH 4/6] ubispl: migrate configuration to Kconfig Markus Klotzbuecher
2019-04-30 4:59 ` Heiko Schocher
2019-04-15 15:32 ` [U-Boot] [PATCH 5/6] ubispl: add support for loading volumes by name Markus Klotzbuecher
2019-04-30 5:15 ` Heiko Schocher
2019-04-15 15:32 ` [U-Boot] [PATCH 6/6] ubispl: introduce separate CONFIG_UBI_SPL_SILENCE_MSG Markus Klotzbuecher
2019-04-30 5:16 ` Heiko Schocher
2019-04-16 3:52 ` [U-Boot] [PATCH 0/6] miscellaneous ubispl and ubi improvements Heiko Schocher
2019-04-16 4:03 ` Heiko Schocher
2019-04-16 5:14 ` Markus Klotzbuecher
2019-04-17 6:34 ` Markus Klotzbuecher [this message]
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=20190417063453.GA26887@e460.mkio.de \
--to=mk@mkio.de \
--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.