LiamPowell

26 ms·

331.
by LiamPowell 3y ago
This is correct, people generally don't get to own a device provided by their employer. Not allowing the bootloader to be unlocked on company-owned devices seems like a very desirable feature.
332.
by LiamPowell 3y ago
struct tm in time.h has been around since C89, there may be others but that's all that immediately comes to mind.
333.
by LiamPowell 4y ago
I've never actually used gcc to target UEFI, but under Clang and other LLVM based compilers it really is just a few flags and header files. If I recall correctly my little demo linked above predates any sort of UEFI support in zig and
334.
by LiamPowell 4y ago
You don't need any sort of large toolchain. In short, a UEFI application works like this (from memory so some details may be wrong): The system calls your main function with a parameter for the address of a struct. That struct contains
335.
by LiamPowell 4y ago
Disabling that watchdog timer only requires a single function call and does not require exiting boot services. UEFI is big, but it's also incredibly well documented, there's also no reason that you have to use all of it or even kn
336.
by LiamPowell 4y ago
This has been built right in to YouTube for a while now, click the 3 dots and click show transcript.
337.
by LiamPowell 4y ago
Rather than hosting the build artifacts, MagiskOnWSA asked users to fork the repo and run a GitHub action to build a 2GB file. Given that they had over 100,000 forks (or at least 200TB of identical artifacts), it's pretty clear why Git