From d9bfb1265074c2b2b3efe7dd139032d8de1987a9 Mon Sep 17 00:00:00 2001 From: Fabio Pozzi Date: Mon, 9 Mar 2015 17:05:55 +0100 Subject: [PATCH] fix typo: 1MB is 0xfffff, not 0xffff which is 65535 --- Booting/linux-bootstrap-1.md | 2 +- contributors.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/Booting/linux-bootstrap-1.md b/Booting/linux-bootstrap-1.md index c5719e4..7bad25c 100644 --- a/Booting/linux-bootstrap-1.md +++ b/Booting/linux-bootstrap-1.md @@ -177,7 +177,7 @@ General real mode's memory map is: 0x000F0000 - 0x000FFFFF - System BIOS ``` -But stop, at the beginning of post I wrote that first instruction executed by the CPU is located at address `0xfffffff0`, which is much bigger than `0xffff` (1MB). How can CPU access it in real mode? As I write about and you can read in [coreboot](http://www.coreboot.org/Developer_Manual/Memory_map) documentation: +But stop, at the beginning of post I wrote that first instruction executed by the CPU is located at address `0xfffffff0`, which is much bigger than `0xfffff` (1MB). How can CPU access it in real mode? As I write about and you can read in [coreboot](http://www.coreboot.org/Developer_Manual/Memory_map) documentation: ``` 0xFFFE_0000 - 0xFFFF_FFFF: 128 kilobyte ROM mapped into address space diff --git a/contributors.md b/contributors.md index 26d5755..ff5a8c0 100644 --- a/contributors.md +++ b/contributors.md @@ -26,3 +26,4 @@ Thank you to all contributors: * [George Horrell](https://github.com/georgehorrell) * [Ciro Santilli](https://github.com/cirosantilli) * [Kevin Soules](https://github.com/eax64) +* [Fabio Pozzi](https://github.com/fabiopozzi)