On Thu, Aug 4, 2011 at 9:24 PM, Geoff Levand ge...@infradead.org wrote:
Also, it needs to be considered that a lot of kernels are out
there will be confused if started with high mem already allocated.
True, but is there anything we can do about that?
Isn't is okay to tell users of first stage
On 08/03/2011 06:19 PM, Hector Martin wrote:
On 08/04/2011 12:30 AM, Geoff Levand wrote:
How would a kexec based bootloader work? If it's kernel were to allocate
high mem and the bootloader program uses the high mem, how could it tell
that kernel not to destroy the region on shutdown?
The
On 08/01/2011 01:02 PM, Andre Heider wrote:
This lets the bootloader preallocate the high lv1 region and pass its
location to the kernel through the devtree. Thus, it can be used to hold
the initrd. If the property doesn't exist, the kernel retains the old
behavior and attempts to allocate
On 08/04/2011 12:30 AM, Geoff Levand wrote:
With this mechanism how is the address of the initrd passed to the
new kernel, in the DT?
Using the /chosen linux,initrd-{start,end} properties. The bootloader
knows about the Linux trick of sticking together bootmem and highmem and
precalculates the
From: Hector Martin hec...@marcansoft.com
This lets the bootloader preallocate the high lv1 region and pass its
location to the kernel through the devtree. Thus, it can be used to hold
the initrd. If the property doesn't exist, the kernel retains the old
behavior and attempts to allocate the
