Specify bootloader version as v0.9 (without patch version) in all posts

Cargo automatically chooses the latest patch version, but beginners might not know that. So this hopefully avoids some confusion.
This commit is contained in:
Philipp Oppermann
2024-02-16 13:24:48 +01:00
parent 3556211904
commit 1f6402f746
9 changed files with 9 additions and 9 deletions

View File

@@ -281,7 +281,7 @@ frame.map(|frame| frame.start_address() + u64::from(addr.page_offset()))
```toml
[dependencies]
bootloader = { version = "0.9.23", features = ["map_physical_memory"]}
bootloader = { version = "0.9", features = ["map_physical_memory"]}
```
この機能を有効化すると、ブートローダは物理メモリの全体を、ある未使用の仮想アドレス空間にマッピングします。この仮想アドレスの範囲をカーネルに伝えるために、ブートローダは**boot information**構造体を渡します。

View File

@@ -278,7 +278,7 @@ We choose the first approach for our kernel since it is simple, platform-indepen
```toml
[dependencies]
bootloader = { version = "0.9.23", features = ["map_physical_memory"]}
bootloader = { version = "0.9", features = ["map_physical_memory"]}
```
With this feature enabled, the bootloader maps the complete physical memory to some unused virtual address range. To communicate the virtual address range to our kernel, the bootloader passes a _boot information_ structure.

View File

@@ -288,7 +288,7 @@ frame.map(|frame| frame.start_address() + u64::from(addr.page_offset()))
```toml
[dependencies]
bootloader = { version = "0.9.23", features = ["map_physical_memory"]}
bootloader = { version = "0.9", features = ["map_physical_memory"]}
```
启用这个功能后bootloader 将整个物理内存映射到一些未使用的虚拟地址范围。为了将虚拟地址范围传达给我们的内核bootloader 传递了一个 _启动信息_ 结构。