From 524fa5330f72c6a1c2edf60c6e629f3f430b0d38 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Thu, 21 May 2020 09:39:14 +0200 Subject: [PATCH] Point bootloader docs.rs link to latest version --- .../second-edition/posts/09-paging-implementation/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/second-edition/posts/09-paging-implementation/index.md b/blog/content/second-edition/posts/09-paging-implementation/index.md index 00c5e997..f667702d 100644 --- a/blog/content/second-edition/posts/09-paging-implementation/index.md +++ b/blog/content/second-edition/posts/09-paging-implementation/index.md @@ -286,7 +286,7 @@ With this feature enabled, the bootloader maps the complete physical memory to s The `bootloader` crate defines a [`BootInfo`] struct that contains all the information it passes to our kernel. The struct is still in an early stage, so expect some breakage when updating to future [semver-incompatible] bootloader versions. With the `map_physical_memory` feature enabled, it currently has the two fields `memory_map` and `physical_memory_offset`: -[`BootInfo`]: https://docs.rs/bootloader/0.8.9/bootloader/bootinfo/struct.BootInfo.html +[`BootInfo`]: https://docs.rs/bootloader/0.9.3/bootloader/bootinfo/struct.BootInfo.html [semver-incompatible]: https://doc.rust-lang.org/stable/cargo/reference/specifying-dependencies.html#caret-requirements - The `memory_map` field contains an overview of the available physical memory. This tells our kernel how much physical memory is available in the system and which memory regions are reserved for devices such as the VGA hardware. The memory map can be queried from the BIOS or UEFI firmware, but only very early in the boot process. For this reason, it must be provided by the bootloader because there is no way for the kernel to retrieve it later. We will need the memory map later in this post.