michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #108 from jonfk/fixed/alloc-frames

Browse Source 
Fixed typos in post Allocating Frames
This commit is contained in:
Philipp Oppermann
2016-01-09 12:57:58 +01:00
parent 43a86e7b86 376ab13f1a
commit 519bb2b385
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
posts/2015-11-15-allocating-frames.md
View File

@@ -69,7 +69,7 @@ let boot_info = unsafe{ multiboot2::load(multiboot_information_address) };
let memory_map_tag = boot_info.memory_map_tag().expect("Memory map tag required");
println!("memory areas:");
for area in emory_map_tag.memory_areas() {
for area in memory_map_tag.memory_areas() {
println!(" start: 0x{:x}, length: 0x{:x}", area.base_addr, area.length);
}
```
@@ -361,7 +361,7 @@ let mut frame_allocator = memory::AreaFrameAllocator::new(
Now we can test it by adding some frame allocations:
```rust
println!("{:?}", frame_allocator.allocate_frame())
println!("{:?}", frame_allocator.allocate_frame());
```
You will see that the frame number starts at `0` and increases steadily, but the kernel and Multiboot frames are left out (you need to allocate many frames to see this since the kernel starts at frame 256).