osdev

The Win32 back end includes support for bundle-private fonts as documented here. This should be ported to the X11 back end as well.

See https://github.com/mszoek/airyx/blob/62919a7f4d5e703bf2e09125796dee8fc4241c58/Frameworks/AppKit/Win32.subproj/Win32Display.m#L100-L142

The virtio_scsi driver enqueues buffers to the eventq but does not actually handle them on completion. The following events could be reported to the driver which require some action to be taken:

• transport reset: This may occur as a result of hotplug events or a device being reset. Sense codes cannot be relied on when new devices or busses appear, so this event needs to be handled.
• asynchro

This is on hold because of the many bugs in the compiler

The build has received support for C++20 modules and it's now time to port the whole codebase to it.

The battle plan is to first port applications and utilities and then works our way down the dependency chain except everything needed by the kernel and the libc: libsystem, libio, libutils, libjson

Applications

• about

Splitting this out from rust-osdev/uefi-rs#285:

@timrobertsdev wrote:

I've been attempting to investigate why, but I've been having a little trouble getting rust-gdb and rust-lldb to recognize the symbols in the uefi-test-runner.efi binary. Oddly enough, objdump -freports that it is flagged as HAS_DEBUG, but objdump -t wasn't able to find any symbols. At

Although a new inline assembly syntax asm! was announced in Rust on 2020/06/08[1], KRaBs still uses llvm_am!.

[1] New inline assembly syntax available in nightly

According to the blog, the asm! macro should be safer and easier to use. This is expected to become the mainstream of inline assembly in the future, so

the binary memory map describes only one space, starting with the physical address 0x00100000
process the rest of the memory map entries and describe them in a binary memory map