From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: state: eMMC boot0-partitions backend for Linux
Date: Mon, 11 Nov 2019 16:54:50 +0100 [thread overview]
Message-ID: <288f22e2-d468-0262-6780-adc690ec6f3d@pengutronix.de> (raw)
In-Reply-To: <1572795919.10526.27.camel@googlemail.com>
Hello Christoph,
On 11/3/19 4:45 PM, Christoph Fritz wrote:
> Hi,
>
> I would like to use emmc-hardware-partition boot1 as a state backend,
> this has the charm of keeping the big hw-partition clean while using SLC
> for e.g. serial numbers.
> Within barebox using an emmc-hardware-partition boot1 as a state backend
> just works!
>
> But trying to hand over this backend to Linux fails right before
> starting the kernel:
>
> WARNING: Failed to fixup node in of_state_fixup+0x1/0x288: No such device
I ran into this before, but with the barebox environment.
I 'solved' it by moving the environment out of the boot partition..
See d5285342d87 ("mci: skip of_partitions_register_fixup for boot partitions").
> I guess dt-utils also has no support for using /dev/mmcblk1boot0 as a
> backend (by default Linux doesn't allow to write to boot0/1) ?
Yes.
> What would be the best way to add this feature?
>
> Any ideas?
How about:
- formalize the eMMC boot partitions binding with
a compatible = "barebox,emmc-bootpart" and change barebox to fix it up
into the kernel's device tree.
- have barebox_state handle this properly. You can check out how RAUC
(LGPL-2.1) does it.
Cheers
Ahmad
>
> -- Christoph
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-11-11 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 15:45 Christoph Fritz
2019-11-11 15:54 ` Ahmad Fatoum [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=288f22e2-d468-0262-6780-adc690ec6f3d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@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