From 49d66d6d55a9912e6f6ac9b6885ff4bad5b0c4bf Mon Sep 17 00:00:00 2001 From: 0xAX Date: Sun, 22 Mar 2015 19:53:20 +0600 Subject: [PATCH] Update linux-initialization-3.md --- Initialization/linux-initialization-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Initialization/linux-initialization-3.md b/Initialization/linux-initialization-3.md index 3e95f35..0ae8452 100644 --- a/Initialization/linux-initialization-3.md +++ b/Initialization/linux-initialization-3.md @@ -6,7 +6,7 @@ Last preparations before the kernel entry point This is third part of the Linux kernel initialization process series. In the previous [part](https://github.com/0xAX/linux-insides/blob/master/Initialization/linux-initialization-2.md) we saw early interupt and exception handling and will continue to dive into the linux kernel initialization process in the current part. Our next point is 'kernel entry point' - `start_kernel` function from the [init/main.c](https://github.com/torvalds/linux/blob/master/init/main.c) source code file. Yes, technically it is not kernel's entry point but the start of the generic kernel code which does not depend on certain architecture. But before we will see call of the `start_kernel` function, we must do some preparations. So let's continue. -Store real mode data in the +Again boot_params -------------------------------------------------------------------------------- In the previous part we stopped at the setting Interrupt Descriptor Table and loading it in the `IDTR` register. In the next step after we this we can see call of the `copy_bootdata` function: