Re: [PATCH 0/4] EFI envblk

2023-09-14 Thread Glenn Washburn
Adding a few others in case interested... On Thu, 14 Sep 2023 18:47:13 +0200 Daniel Kiper wrote: > On Wed, Jul 26, 2023 at 03:59:58PM -0500, Glenn Washburn wrote: > > This patch series (for me) was motivated by the "gdb: Add more support for > > debugging on EFI platforms" patch series, which al

Re: [PATCH 0/4] EFI envblk

2023-09-14 Thread Daniel Kiper
On Wed, Jul 26, 2023 at 03:59:58PM -0500, Glenn Washburn wrote: > 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 > hav

Re: [PATCH 0/4] EFI envblk

2023-07-28 Thread Dimitri John Ledkov
On Wed, 26 Jul 2023, 23:03 Vladimir 'phcoder' Serbinenko, wrote: > Have you considered that some firmwares brick if EFI storage is over 50% > full? Why not having a file on ESP instead? > Yes bricking did happen before. It was triggered by excessive runtime updates of bootloader settings. It did

Re: [PATCH 0/4] EFI envblk

2023-07-28 Thread Glenn Washburn
On Thu, 27 Jul 2023 00:49:06 +0300 "Vladimir 'phcoder' Serbinenko" wrote: > Have you considered that some firmwares brick if EFI storage is over 50% > full? Why not having a file on ESP instead? What if the ESP is readonly? What if there is no ESP? I take your point about crappy firmwares. As me

Re: [PATCH 0/4] EFI envblk

2023-07-26 Thread Vladimir 'phcoder' Serbinenko
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, whi

[PATCH 0/4] EFI envblk

2023-07-26 Thread Glenn Washburn
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 rejecte