Hi,
after some thinking about device trees and secure boot today, I
pondered if we should just allow wrapping a filesystem image in a
signed PE binary into a "grubext" section perhaps. Use cases can be:
- signed fonts packages
- signed themes packages
- signed device trees
This probably needs
Signed-off-by: Glenn Washburn
---
docs/grub.texi | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/docs/grub.texi b/docs/grub.texi
index dae10621b99f..5f6f0895ef4f 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -4361,6 +4361,7 @@ you forget a command, you
Add documentation on hexdump.
Glenn
Glenn Washburn (2):
docs: Document hexdump command
docs: A note to cat that hexdump should be used for binary data
docs/grub.texi | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
--
2.34.1
Signed-off-by: Glenn Washburn
---
docs/grub.texi | 42 +-
1 file changed, 25 insertions(+), 17 deletions(-)
diff --git a/docs/grub.texi b/docs/grub.texi
index fe94ef9e94fc..dae10621b99f 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -104,15 +104,7 @@
The cat command should not be used to print binary data because it can
show bytes not in the binary data and not show bytes that are in the data,
which can lead to confusion. This happens because cat does some processing
of the data stream, namely trying to decode substrings as UTF-8.
On Wed, Jul 26, 2023 at 13:50:10 -0500, Glenn Washburn wrote:
> Add documentation on hexdump.
>
> Glenn
>
> Glenn Washburn (2):
> docs: Document hexdump command
> docs: A note to cat that hexdump should be used for binary data
>
> docs/grub.texi | 22 +-
> 1 file
This patch series (for me) was motivated by the "gdb: Add more support for
debugging on EFI platforms" patch series, which allowed printing in early
EFI init of the GDB command for properly loading symbols. That approach of
having the functionality be included at compile time was ultimately
Signed-off-by: Glenn Washburn
---
Makefile.util.def| 6 +
tests/efienv_test.in | 57
2 files changed, 63 insertions(+)
create mode 100644 tests/efienv_test.in
diff --git a/Makefile.util.def b/Makefile.util.def
index
From: Peter Jones
This allows setting GRUB variables before any user interaction or GRUB
script can run. It is primarily intended to be used to turn on early
debugging.
Signed-off-by: Peter Jones
Replace grub_efi_guid_t -> grub_guid_t
Signed-off-by: Glenn Washburn
---
If the variable "enable_earlyinit_gdbinfo" exists, print the GDB command
needed to properly load symbols in an attached GDB session. This variable
must come from the environment block stored in the GRUB_ENV EFI variable,
which allows this to get printed as early as possible.
Signed-off-by: Glenn
According to commit 0231d00082 ("ACPI: SPCR: Make SPCR available to x86")
to the Linux kernel, "On x86, many systems have a valid SPCR table but the
table version is not 2 so the table version check must be a warning."
Signed-off-by: Glenn Washburn
---
grub-core/term/ns8250-spcr.c | 4 +++-
1
From: Peter Jones
This adds "efi-export-env VARIABLES" and "efi-load-env", which manipulate
the environment block stored in the EFI variable
GRUB_ENV-91376aff-cba6-42be-949d-06fde81128e8.
Signed-off-by: Peter Jones
Fix rebase, cherry-pick issues, grub_efi_guid_t -> grub_guid_t,
module name
Have you considered that some firmwares brick if EFI storage is over 50%
full? Why not having a file on ESP instead?
Le jeu. 27 juil. 2023, 00:09, Glenn Washburn
a écrit :
> This patch series (for me) was motivated by the "gdb: Add more support for
> debugging on EFI platforms" patch series,
On Wed, 2023-07-26 at 16:02 -0500, Glenn Washburn wrote:
> According to commit 0231d00082 ("ACPI: SPCR: Make SPCR available to
> x86")
> to the Linux kernel, "On x86, many systems have a valid SPCR table
> but the
> table version is not 2 so the table version check must be a warning."
>
>
14 matches
Mail list logo