linux/arch/x86/include/asm/boot.h

#ifndef _ASM_X86_BOOT_H
#define _ASM_X86_BOOT_H

/* Don't touch these, unless you really know what you're doing. */
#define DEF_SYSSEG	0x1000
#define DEF_SYSSIZE	0x7F00

/* Internal svga startup constants */
#define NORMAL_VGA	0xffff		/* 80x25 mode */
#define EXTENDED_VGA	0xfffe		/* 80x50 mode */
#define ASK_VGA		0xfffd		/* ask for it at bootup */

/* Physical address where kernel should be loaded. */
#define LOAD_PHYSICAL_ADDR ((CONFIG_PHYSICAL_START \
				+ (CONFIG_PHYSICAL_ALIGN - 1)) \
				& ~(CONFIG_PHYSICAL_ALIGN - 1))

#ifdef CONFIG_X86_64
#define BOOT_HEAP_SIZE	0x7000
#define BOOT_STACK_SIZE	0x4000
#else
#define BOOT_HEAP_SIZE	0x4000
#define BOOT_STACK_SIZE	0x1000
#endif

#endif /* _ASM_X86_BOOT_H */
x86: Fix ASM_X86__ header guards Change header guards named "ASM_X86__" to "_ASM_X86_" since: a. the double underscore is ugly and pointless. b. no leading underscore violates namespace constraints. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 2008-10-22 22:26:29 -07:00			`#ifndef _ASM_X86_BOOT_H`
			`#define _ASM_X86_BOOT_H`
Linux-2.6.12-rc2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 2005-04-16 15:20:36 -07:00
			`/* Don't touch these, unless you really know what you're doing. */`
			`#define DEF_SYSSEG 0x1000`
			`#define DEF_SYSSIZE 0x7F00`

			`/* Internal svga startup constants */`
			`#define NORMAL_VGA 0xffff /* 80x25 mode */`
			`#define EXTENDED_VGA 0xfffe /* 80x50 mode */`
			`#define ASK_VGA 0xfffd /* ask for it at bootup */`

Fix misspellings collected by members of KJ list. Fix the misspellings of "propogate", "writting" and (oh, the shame :-) "kenrel" in the source tree. Signed-off-by: Robert P. J. Day <rpjday@mindspring.com> Signed-off-by: Adrian Bunk <bunk@stusta.de> 2007-05-09 07:14:03 +02:00			`/* Physical address where kernel should be loaded. */`
[PATCH] i386: Restore CONFIG_PHYSICAL_START option o Relocatable bzImage support had got rid of CONFIG_PHYSICAL_START option thinking that now this option is not required as people can build a second kernel as relocatable and load it anywhere. So need of compiling the kernel for a custom address was gone. But Magnus uses vmlinux images for second kernel in Xen environment and he wants to continue to use it. o Restoring the CONFIG_PHYSICAL_START option for the time being. I think down the line we can get rid of it. Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> 2007-01-05 16:36:30 -08:00			`#define LOAD_PHYSICAL_ADDR ((CONFIG_PHYSICAL_START \`
			`+ (CONFIG_PHYSICAL_ALIGN - 1)) \`
[PATCH] i386: Implement CONFIG_PHYSICAL_ALIGN o Now CONFIG_PHYSICAL_START is being replaced with CONFIG_PHYSICAL_ALIGN. Hardcoding the kernel physical start value creates a problem in relocatable kernel context due to boot loader limitations. For ex, if somebody compiles a relocatable kernel to be run from address 4MB, but this kernel will run from location 1MB as grub loads the kernel at physical address 1MB. Kernel thinks that I am a relocatable kernel and I should run from the address I have been loaded at. So somebody wanting to run kernel from 4MB alignment location (for improved performance regions) can't do that. o Hence, Eric proposed that probably CONFIG_PHYSICAL_ALIGN will make more sense in relocatable kernel context. At run time kernel will move itself to a physical addr location which meets user specified alignment restrictions. Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com> Signed-off-by: Andi Kleen <ak@suse.de> 2006-12-07 02:14:04 +01:00			`& ~(CONFIG_PHYSICAL_ALIGN - 1))`

x86: cleanup boot-heap usage The kernel decompressor wrapper uses memory located beyond the end of the image. This might lead to hard to debug problems, but even if it can be proven to be safe, it is at the very least unclean. I don't see any advantages either, unless you count it not being zeroed out as an advantage. This patch moves the boot-heap area to the bss segment. Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> 2008-04-08 12:54:30 +02:00			`#ifdef CONFIG_X86_64`
			`#define BOOT_HEAP_SIZE 0x7000`
			`#define BOOT_STACK_SIZE 0x4000`
			`#else`
			`#define BOOT_HEAP_SIZE 0x4000`
			`#define BOOT_STACK_SIZE 0x1000`
			`#endif`

x86: Fix ASM_X86__ header guards Change header guards named "ASM_X86__" to "_ASM_X86_" since: a. the double underscore is ugly and pointless. b. no leading underscore violates namespace constraints. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 2008-10-22 22:26:29 -07:00			`#endif /* _ASM_X86_BOOT_H */`