Tim Crawford

This is probably firmware-manager then. That is responsible for the notifications. - https://github.com/pop-os/firmware-manager/blob/c9367bbdacef57e4909f7263ea09cc67c5f6e6e3/notify/src/main.rs#L59-L64 - https://github.com/pop-os/firmware-manager/blob/c9367bbdacef57e4909f7263ea09cc67c5f6e6e3/src/system76.rs#L34-L36

This probably requires making `ReadOnly` (and other structs in `Io`) `repr(transparent)`, to ensure all types are the same size (and thus always aligned to `T`, assuming the struct itself is...

**Consideration**: Power switch is "a key on the keyboard". **Example**: HP Dev One HP Dev One is an example of a model with the power switch being "a key on...

Since the goal is to work on AArch64, might be better to gate implementation per arch? - x86_64: Continue using port IO - aarch64: Parse devicetree to determine address I've...

Error comes from the OS application. Need to determine if this affects the UEFI app, OS libs/app, or both. Should be able to test if system76-firmware-update is affected by building...

Barlow Ridge BIOS Implementation Guide r1.1 (2024-07-16) now states that FW CM is supported. - 5 USB4 Software Connection Manager > The CM in the USB4 host system can be...

Reverting to SDCC's `makebin` might work. If so, would also remove the need for installing the host GCC toolchain (gcc-avr would still be needed for the Arduino tools). Well, not...

I don't consider any Rust UEFI project anywhere close to "1.0", because so many interfaces and types from the specifications are missing. But version numbers are cheap.

I haven't used the crate much because I'm waiting for the license change, so my feedback is limited. I expect that most of my use will be with uefi-raw anyway...

It is simply not feasible to consider the >200 protocols of "the UEFI specification"--plus PI, Shell, TCG, ACPI, and "unofficial" edk2 protocols (like `BootLogo2` and `GopPolicy` which I will need)--as...