From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64"
Date: Mon, 5 Nov 2018 08:30:03 -0200 (BRST) [thread overview]
Message-ID: <1795749492.59166.1541413803133.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20181102110420.0f4f44f1@windsurf>
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Erico Nunes" <nunes.erico@gmail.com>
> Cc: "sumit garg" <sumit.garg@linaro.org>, "buildroot" <buildroot@buildroot.org>
> Sent: Sexta-feira, 2 de novembro de 2018 7:04:20
> Subject: Re: [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64"
> Hello,
>
> On Tue, 30 Oct 2018 20:23:27 +0100, Erico Nunes wrote:
>
>> Using PARTUUID seems to be an interesting change. I'd like to hear the
>> opinion of the other Buildroot developers before making this change in
>> this patchset though, since most other platforms in Buildroot are not
>> doing this.
>
> It is certainly a good idea to use PARTUUID when possible.
>
>> If there is interest in it, maybe we can do this change for other
>> platforms too and in a separate patchset?
>
> In general yes. However, my understanding was that it works only with a
> GPT partition table, because only the GPT partition table can embed a
> unique identifier per partition, not the old MBR partition table. But
> apparently this disk-signature thing allows to embed a disk-wide
> identifier, not a per-partition one, so it works only when there's a
> single partition ?
PARTUUID works with MBR partition tables too, even tough the ID is
not a true UUID. It's build from the 32-bit long disk ID plus the
partition number, e.g. "f000-baad-01", "f000-baad-02".
One can force the disk ID of a disk image to a known value with
something like this (requires host-util-linux):
img_name="disk.img"
disk_id="$("${HOST_DIR}/bin/uuidgen" -r | cut -d - -f 1)"
printf 'x\ni\n0x%s\nr\nw\n' "${disk_id}" \
| "${HOST_DIR}/sbin/fdisk" "${BINARIES_DIR}/${img_name}" \
> /dev/null
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
prev parent reply other threads:[~2018-11-05 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 5:58 [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64" Sumit Garg
2018-10-30 9:05 ` Sumit Garg
2018-10-30 19:23 ` Erico Nunes
2018-11-01 2:02 ` Carlos Santos
2018-11-02 10:04 ` Thomas Petazzoni
2018-11-02 10:53 ` Sumit Garg
2018-11-02 11:00 ` Thomas Petazzoni
2018-11-02 13:10 ` Erico Nunes
2018-11-05 10:30 ` Carlos Santos [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=1795749492.59166.1541413803133.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=buildroot@busybox.net \
/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