Hi!
On Mon, May 14, 2001 at 06:38:07AM +0800, Rogelio Serrano wrote:
>
> > Alternately, I suppose that GRUB could be hacked to map 0xc000-0x
> > to the physical range 0x-0x3000.
>
> I think that this would violate the multiboot standard. There is a
> linker option to c
Hello,
I'm looking at using GRUB to load a Multiboot compliant kernel. I'm using a
reduced Linux kernel as a starting point for playing with this (the goal is
to eventually load the ELF executable 'vmlinux' as produced by 'make
vmlinux').
Anyway, the first problem seems to be that the kernel wou
From: Luca Abeni <[EMAIL PROTECTED]>
Subject: Question about multiboot
Date: Fri, 17 Nov 2000 17:13:17 -0500
> Now, how can the kernel understand which part of the upper memory is
> free (part of that memory contains the kernel itself and the modules)?
> Must the kernel computes
Hi all,
I have a question about the multiboot standard:
according to the standard, when a multiboot compliant kernel is loaded
in memory it can read the amount of upper memory from the multiboot
information structure, and the upper memory is assumed to start at 1
megabyte.
Now, how can the kernel
