Re: [PATCH] memdisk plus lnxboot extension

[Robert Millan]

On Thu, Jan 24, 2008 at 03:24:37AM +0800, Bean wrote:
> On Jan 24, 2008 3:14 AM, Robert Millan <address@hidden> wrote:
> > On Thu, Jan 24, 2008 at 03:01:33AM +0800, Bean wrote:
> > > On Jan 24, 2008 12:18 AM, Bean <address@hidden> wrote:
> > > > On Jan 23, 2008 4:54 PM, Marco Gerards <address@hidden> wrote:
> > > > > When is this feature useful?  Can you give an example?  More features
> > > > > can mean more bugs, more maintainance work, etc.  If the feature is
> > > > > not worthwhile for more than one person, I am not sure if it should be
> > > > > included.  Perhaps a better explaination of the problem to solve,
> > > > > instead of what the patch does might help here.
> > > >
> > > > the most important usage of external initrd is to overcome the size
> > > > limit of core.img.
> > >
> > > this is the new patch, now no need to modify grub-mkimage, use cat
> > > just as before.
> >
> > Well..  even though I still don't see the motivation, I'm less concerned 
> > about
> > this if it's just added to lnxboot.img.
> >
> > > +VARIABLE(grub_memdisk_image_addr)
> > > +     .long   0
> >
> > I recall you said use of this variable could be avoided ?
> 
> This variable can't be avoided. it's used by grub_arch_memdisk_addr to
> return the address of initrd. however, i can copy initrd to the
> location to make it look like core.img load it, but that means an
> extra memory copy.

The region where memdisk is normally put has no size limit, only the core
image itself does.  Why not load it at the same address?

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)