arch/x86: Link gdt_init.S into bootblock
Followup work forces gdtptr and gdt towards the top of bootblock. They need to be realmode-addressable, i.e. within top 64 KiB or same segment with .reset. Change-Id: Ib6f23b2808d0a7e0d277d00a9b0f30c49fdefdd5 Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/47965 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
This commit is contained in:
committed by
Hung-Te Lin
parent
54b5e20cf8
commit
97b76f7191
@@ -142,10 +142,10 @@ gdtaddr:
|
||||
|
||||
/* This is the gdt for GCC part of coreboot.
|
||||
* It is different from the gdt in ASM part of coreboot
|
||||
* which is defined in entry32.inc
|
||||
* which is defined in gdt_init.S
|
||||
*
|
||||
* When the machine is initially started, we use a very simple
|
||||
* gdt from ROM (that in entry32.inc) which only contains those
|
||||
* gdt from ROM (that in gdt_init.S) which only contains those
|
||||
* entries we need for protected mode.
|
||||
*
|
||||
* When we're executing code from RAM, we want to do more complex
|
||||
|
Reference in New Issue
Block a user