mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 0/3] use environment partitions in GPT
Date: Mon, 19 Feb 2024 16:06:45 +0100	[thread overview]
Message-ID: <20240219150645.pumpmaqelykk62nz@pengutronix.de> (raw)
In-Reply-To: <20240219145159.1962618-1-s.hauer@pengutronix.de>

On 24-02-19, Sascha Hauer wrote:
> We have specified a GUID for GPTs to be used as barebox environment
> partition, but so far we haven't made any use of that. This series
> changes that. We now start using environment partitions when we find
> them, provided the board code hasn't specified any other partition.
> 
> This likely doesn't change much for existing boards because most of
> them actually have an environment partition specified. For new boards
> however it becomes feasible to not register a partition explicitly.
> 
> Something that has hold me back from doing this earlier was that barebox
> was not able to create an environment partition itself, so barebox
> couldn't persist the environment on an unpartitioned device. Now with
> parted support this has changed, so I think it's worth it to give it a
> try now.
> 
> Sascha

LGTM, feel free to add my:

Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>

> 
> Sascha Hauer (3):
>   partitions: efi: Allow to create barebox environment partition
>   bootsource: add function to get device_node we booted from
>   environment: use barebox environment from GPT partitions
> 
>  commands/parted.c       |  2 +-
>  common/bootsource.c     | 14 +++++++++
>  common/environment.c    | 65 ++++++++++++++++++++++++++++++++++++++++-
>  common/oftree.c         |  7 +----
>  common/partitions/efi.c |  3 ++
>  include/bootsource.h    |  1 +
>  include/efi/partition.h |  3 ++
>  7 files changed, 87 insertions(+), 8 deletions(-)
> 
> -- 
> 2.39.2
> 
> 
> 



      parent reply	other threads:[~2024-02-19 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 14:51 Sascha Hauer
2024-02-19 14:51 ` [PATCH 1/3] partitions: efi: Allow to create barebox environment partition Sascha Hauer
2024-02-19 15:20   ` Ahmad Fatoum
2024-02-20 10:52     ` Sascha Hauer
2024-02-19 14:51 ` [PATCH 2/3] bootsource: add function to get device_node we booted from Sascha Hauer
2024-02-19 14:59   ` Marco Felsch
2024-02-19 15:21     ` Sascha Hauer
2024-02-20 10:56       ` Sascha Hauer
2024-02-19 14:51 ` [PATCH 3/3] environment: use barebox environment from GPT partitions Sascha Hauer
2024-02-19 15:06 ` Marco Felsch [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=20240219150645.pumpmaqelykk62nz@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --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