uefi
Here are 552 public repositories matching this topic...
-
Updated
Aug 3, 2022 - C
-
Updated
Aug 9, 2022 - Python
-
Updated
Aug 9, 2022 - Shell
-
Updated
Jun 12, 2022
-
Updated
May 28, 2022 - PowerShell
-
Updated
Jul 22, 2022 - HTML
-
Updated
Mar 22, 2022
In rust-osdev/uefi-rs#309, the Handle type was changed from containing just a raw pointer to NonNull<c_void>, which has the nice advantage that you can then use Option<Handle> when you want a nullable Handle, and this is FFI-safe.
As was mentioned in rust-osdev/uefi-rs#309 (comment), it would make sense to do this for the `Eve
-
Updated
Feb 19, 2020 - C
-
Updated
Jul 12, 2022 - Roff
-
Updated
Jul 30, 2022 - C++
-
Updated
Jun 20, 2022
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.
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."

As it can be seen from https://app.codecov.io/gh/vvaltchev/tilck/blobs/master/kernel/misc.c,
print_banner_line()andshow_tilck_logo()don't have coverage, despite being always run on boot. That's simply because in coverage builds, the env variableTILCK_NO_LOGOis set. See https://github.com/vvaltchev/tilck/blob/master/other/coverage_build.yml.Because those trivial code lines that don'