uefi
Here are 538 public repositories matching this topic...
-
Updated
Mar 23, 2022 - C
-
Updated
May 27, 2022 - Python
-
Updated
May 29, 2022 - Shell
-
Updated
Jul 24, 2020
-
Updated
May 28, 2022 - PowerShell
-
Updated
May 27, 2022 - HTML
-
Updated
May 29, 2022 - C
-
Updated
Mar 22, 2022
-
Updated
Feb 19, 2020 - C
-
Updated
May 23, 2022 - Roff
-
Updated
May 8, 2022
-
Updated
May 6, 2022 - C++
Make issue template
Issues should demand people attach the following outputs:
sudo sbctl statussudo hexdump -C /sys/firmware/efi/efivars/PK-8be4df61-93ca-11d2-aa0d-00e098032b8c
And we should preferably implement sudo sbctl debug as a hidden command so we can have some better structured data we can use for debugging.
Create ports tree
Umm, I dont think its exactly wise to put things like doom in the sysroot, you should create a ports tree where you can access these packages using the internet to download the source, then compiling it(and create eth drivers). Just a thought.
(I also dont want to cherry pick what commits I want to add to uwux, im building other projects rn)
Improve this page
Add a description, image, and links to the uefi topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the uefi topic, visit your repo's landing page and select "manage topics."
Affected: Firmware targeting EFI < 1.10 and UEFI drivers that do not use
BootServices.open_protocolandBootServices.close_protocol.Prior to EFI 1.10, the
EFI_BOOT_SERVICES.UninstallProtocolInterfacefunction lacks the safety checks that were added in 1.10. It simply removes a protocol from a handle, and if the last protocol is removed from a handle, that handle is freed by firmware and