blog_os VS bootloader

but it seems to be flawed because even the example: https://github.com/phil-opp/blog_os/tree/post-02

I suggest looking at the 3rd edition of Philipp Oppermann's blog OS that I mentioned. It's still very much a work-in-progress, but the section on UEFI booting is pretty much done. It's not hosted anywhere yet, so you'll have to clone the repo and switch to the edition-3 branch, then install Zola 0.13 (cargo install zola --git https://github.com/getzola/zola.git --tag v0.13.0) and run zola serve in the blog directory.

RedoxOS, an OS written in Rust A tutorial on making an OS in Rust, complwte with bootable source

I'm currently working on a tutorial for (1). It's still in a very early stage, but maybe it helps you to get started: https://github.com/phil-opp/blog_os/blob/edition-3/blog/content/edition-3/posts/02-booting/uefi.md

That's just an unbased claims. People have written bootloader in rust and the linux kernel is also considering adopting Rust. None of this would happen if Rust cannot interface the hardware or is turing complete.

The "official" (with outdated code) bootloader: https://github.com/rust-osdev/bootloader/blob/main/src/bin/uefi.rs

A quick wander through the docs, and then the repo turned up an open feature request for VESA video modes which mentions a merged PR for 320x200 VGA support.

But here I come across an interesting structure https://github.com/rust-osdev/bootloader/tree/main/examples/test_framework

Long story short, it appears there is no way to get started with UEFI (cue more downvotes). I've even spent a week carefully copying code beginning here: https://github.com/rust-osdev/bootloader/blob/main/src/bin/uefi.rs only to discover that nothing displays to the screen. There is an error somewhere in the 500 lines required to print a character to the screen, and it's impossible to tell where it is.

rust-osdev/bootloader

You can also take a look at the upcoming version of the bootloader crate, which has UEFI support: https://github.com/rust-osdev/bootloader/pull/130 . It is not documented very well yet, but maybe it helps already. The UEFI entry point function is here .The #[entry] macro of the uefi crate just makes the function a pub extern "efiapi" fn. The function is named efi_main because that's the default entry point name for Rust's built-in UEFI targets (e.g. x86_64-unknown-uefi). Theimageandst` function arguments are passed directly by the UEFI firmware.