From 6b2f1281ae824ac6f61daf3953b0ba65c9d7ac7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Anton=20Str=C3=B6mkvist?= Date: Thu, 28 Jul 2016 18:01:42 +0200 Subject: [PATCH] Fix hex constant (#193) I assume these were in the wrong order since all the others looked this way :) --- blog/post/2015-08-18-multiboot-kernel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/post/2015-08-18-multiboot-kernel.md b/blog/post/2015-08-18-multiboot-kernel.md index dd157007..be1fbf87 100644 --- a/blog/post/2015-08-18-multiboot-kernel.md +++ b/blog/post/2015-08-18-multiboot-kernel.md @@ -110,7 +110,7 @@ There are some new commands: - `global` exports a label (makes it public). As `start` will be the entry point of our kernel, it needs to be public. - the `.text` section is the default section for executable code - `bits 32` specifies that the following lines are 32-bit instructions. It's needed because the CPU is still in [Protected mode] when GRUB starts our kernel. When we switch to [Long mode] in the [next post] we can use `bits 64` (64-bit instructions). -- the `mov dword` instruction moves the 32bit constant `0x2f4f2f4b` to the memory at address `b8000` (it prints `OK` to the screen, an explanation follows in the next posts) +- the `mov dword` instruction moves the 32bit constant `0x2f4b2f4f` to the memory at address `b8000` (it prints `OK` to the screen, an explanation follows in the next posts) - `hlt` is the halt instruction and causes the CPU to stop Through assembling, viewing and disassembling we can see the CPU [Opcodes] in action: