From: Sascha Hauer <sha@pengutronix.de>
To: Trent Piepho <trent.piepho@igorinstitute.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] state: support backend-diskuuid / backend-offset
Date: Fri, 28 Jan 2022 08:48:12 +0100 [thread overview]
Message-ID: <20220128074812.GS23490@pengutronix.de> (raw)
In-Reply-To: <CAMHeXxMCGpq4+jkhU0hOHy6x6sn9a2=gUW_rfhfF9UtSZZNpDQ@mail.gmail.com>
On Thu, Jan 27, 2022 at 10:53:33AM -0800, Trent Piepho wrote:
> Could a linux dtb fixup be done in barebox? This way userspace will
> only have existing properties: storage devices with partitions
> node(s), and barebox-state backend that points to a partition. In
> this case, the partition node was added by Barebox.
>
> In fact, Barebox already does partition fixups exactly like this. So
> I think this would probably already happen. It won't work if Linux
> dtb does not have the storage device at all, as the partition fixup
> considers that an error. But maybe the Linux dtb will have the
> storage device node? Or if it doesn't have it because the storage is
> "too dynamic" to put into the dts, then another fixup can make the
> node.
Michael wants to use this for EFI, so there is no full device tree under
Linux, there will only be the device tree snippet containing the state
node and now some dummy device describing the disk UUID.
While it sounds like an interesting idea it won't help us here.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://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:[~2022-01-28 7:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:04 [PATCH 0/3] state: find backend with UUID but without a partition Michael Olbrich
2022-01-24 10:04 ` [PATCH 1/3] cdev: rename partuuid to uuid Michael Olbrich
2022-01-24 10:04 ` [PATCH 2/3] cdev: add diskuuid support Michael Olbrich
2022-01-24 10:04 ` [PATCH 3/3] state: support backend-diskuuid / backend-offset Michael Olbrich
2022-01-26 7:57 ` Sascha Hauer
2022-01-26 9:35 ` Michael Olbrich
2022-01-26 10:15 ` Sascha Hauer
2022-01-26 11:16 ` Michael Olbrich
2022-01-27 0:18 ` Trent Piepho
2022-01-27 12:39 ` Sascha Hauer
2022-01-27 18:53 ` Trent Piepho
2022-01-28 7:48 ` Sascha Hauer [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=20220128074812.GS23490@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=trent.piepho@igorinstitute.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