public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, mhaeuser@posteo.de,
	 Pedro Falcato <pedro.falcato@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [edk2-devel] efi and ext4 and case sensitive file names
Date: Fri, 29 Sep 2023 10:58:44 +0000	[thread overview]
Message-ID: <0102018ae097455a-2ac36c7a-b10d-4622-be37-d8adf5f4d5b6-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <944EB976-23EA-4921-AAF4-23435772C65A@posteo.de>

On 29/09/2023 10:47, Marvin Häuser wrote:
> Maybe when Linux starts adhering the spec for file names (the spec clearly defines e.g. BOOTx64.EFI, while at least some distros/images use bootx64.efi), this can be discussed. :) Let's not break various GRUB setups...

Seems slightly unfair to blame Linux when EDK2 also apparently gets it 
wrong (in a different way)... :)

//
// EFI File location to boot from on removable media devices
//
...
#define EFI_REMOVABLE_MEDIA_FILE_NAME_X64 L"\\EFI\\BOOT\\BOOTX64.EFI"

Is this something worth fixing in UefiSpec.h?

Thanks,

Michael



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109194): https://edk2.groups.io/g/devel/message/109194
Mute This Topic: https://groups.io/mt/101615699/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2023-09-29 10:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 12:09 [edk2-devel] efi and ext4 and case sensitive file names Gerd Hoffmann
2023-09-28  8:01 ` Laszlo Ersek
2023-09-28 17:57 ` Pedro Falcato
2023-09-29  9:47   ` Marvin Häuser
2023-09-29 10:55     ` Pedro Falcato
2023-09-29 10:58     ` Michael Brown [this message]
2023-09-29 11:01       ` Marvin Häuser

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-list 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=0102018ae097455a-2ac36c7a-b10d-4622-be37-d8adf5f4d5b6-000000@eu-west-1.amazonses.com \
    --to=devel@edk2.groups.io \
    /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