[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] memdisk plus lnxboot extension

From: Yoshinori K. Okuji
Subject: Re: [PATCH] memdisk plus lnxboot extension
Date: Thu, 24 Jan 2008 22:23:12 +0100
User-agent: KMail/1.9.4

On Thursday 24 January 2008 12:49, Bean wrote:
> On Jan 24, 2008 7:32 PM, Robert Millan <address@hidden> wrote:
> > Sorry, my question was confusing;  what I meant is, where is it located
> > when core.img is started.  But Just checked in our Linux loader, and it
> > seems to be at a very high address.
> >
> > However, a very high address doesn't garantee that it won't be
> > overwritten by lzo decompression, just makes it less likely.
> >
> > Overall, this is why I don't like having to stick to a particular boot
> > mechanism.  If our goal is overcome the size limit in memdisk, why not
> > design the boot mechanism ourselves?
> I'm not familiar with multiboot spec, does it support arbitrary kernel size
> ?

Why not? ;)

The theoretical limit is that defined by an architecture, such as 4GB in 
32-bit addressing. If you find a stronger limit, it must be an implementation 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]