From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] part:efi: add GUID for linux file system data
Date: Mon, 12 Oct 2015 11:14:06 -0400 [thread overview]
Message-ID: <20151012151406.GC23893@bill-the-cat> (raw)
In-Reply-To: <CAKOfRZyxFfx75V92xrG_g-1DOishgRPcdhfDJ75-O1OuzvStmw@mail.gmail.com>
On Mon, Oct 12, 2015 at 05:03:15PM +0200, Patrick Delaunay wrote:
> Signed-off-by: Patrick Delaunay <patrick.delaunay73@gmail.com>
> ---
>
> see https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs
>
> nota 9 :
> Previously, Linux used the same GUID for the data partitions as Windows
> (Basic data partition: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7).
> Linux never had a separate unique partition type GUID defined for its
> data partitions.
> This created problems when dual-booting Linux and Windows in UEFI-GPT
> setup.
> The new GUID (Linux filesystem data: 0FC63DAF-8483-4772-8E79-3D69D8477DE4)
> was defined jointly by GPT fdisk and GNU Parted developers.
> It is identified as type code 0x8300 in GPT fdisk.
> (See definitions in gdisk's parttypes.cc)
Some of this should be in the main commit message, not the discarded
part.
> include/part_efi.h | 3 +++
> 1 file changed, 3 insertions(+)
And without some changes to disk/part_efi.c I believe, this isn't used
anywhere so not actually changing behavior yet :)
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151012/80e15c74/attachment.sig>
next prev parent reply other threads:[~2015-10-12 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 15:03 [U-Boot] [PATCH] part:efi: add GUID for linux file system data Patrick Delaunay
2015-10-12 15:14 ` Tom Rini [this message]
2015-10-12 17:48 ` Patrick Delaunay
2015-10-12 18:09 ` Tom Rini
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=20151012151406.GC23893@bill-the-cat \
--to=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox