From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RFC: 1.97 roadmap
Date: Wed, 12 Aug 2009 02:43:34 +0200 [thread overview]
Message-ID: <20090812004334.GD8561@thorin> (raw)
In-Reply-To: <d7ead6de0908101010s701d4758va3dccca2f7f6bf5f@mail.gmail.com>
On Mon, Aug 10, 2009 at 07:10:12PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Mon, Aug 10, 2009 at 6:10 PM, Robert Millan<rmh@aybabtu.com> wrote:
> >
> > Hi,
> >
> > I think it's time we begin the discussion on GRUB 1.97. What do we want to
> > see in it, and a rough schedule. 1.97 is meant to be a point release, without
> > any major changes (I mean, except for those we already have ;-)), and it should
> > happen soon (like this month or so).
> I think it would be good if we release before ubuntu's beta freeze.
Agreed.
> > - Low memory heap (useful to move code off kern/i386/pc/startup.S).
> Originally I thought of a path relocator32->relocator users->mm
> relocator32 is ready for next round of review but is untested. Now I
> think about it mm patch isn't actually dependent on relocator32, just
> you won't get some features (as loading big initrds and removal of
> os_area_size/os_area_addr fields) before relocator32 is used by all
> loaders. I will adjust mm patch to this and add
> .(text|data|bss)-lowmem section support.
I don't understand, what is the relation between relocator in loaders and
low memory heap?
I'll need to catch up with the lowmem heap discussion. What's the approach?
> What about savedefault? Which savedefault way you prefer?
I think it would be good to have. But I haven't followed on the savedefault
discussion, I just know it would build upon the existing envfile support.
> > Bigger overhauls like the fancy menu
> I started splitting Collin's patches and actually only quite few need
> to go to the parts already present in grub2. Perhaps 1.97 can be
> brought to a state when gfxmenu can be compiled externally?
Depends on how intrusive are those changes :-)
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-12 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 16:10 RFC: 1.97 roadmap Robert Millan
2009-08-10 17:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 0:43 ` Robert Millan [this message]
2009-08-12 8:41 ` Colin Watson
2009-08-12 8:47 ` Colin Watson
2009-08-12 12:26 ` Yves Blusseau
2009-08-13 20:21 ` Robert Millan
2009-08-10 18:20 ` Michal Suchanek
2009-08-10 19:51 ` Vladimir 'phcoder' Serbinenko
2009-08-12 11:56 ` Michal Suchanek
2009-08-12 8:35 ` Colin Watson
2009-08-13 20:31 ` Robert Millan
2009-08-13 20:45 ` grub configuration file format change? Seth Goldberg
2009-08-13 21:03 ` Robert Millan
2009-08-13 21:12 ` Seth Goldberg
2009-08-17 12:55 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090812004334.GD8561@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.