From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Move BSD and multiboot boot helper out of the kernel to their respective modules
Date: Sun, 08 Feb 2009 00:12:00 +0100 [thread overview]
Message-ID: <498E1540.3090808@gmail.com> (raw)
In-Reply-To: <20090207222052.GN6343@thorin>
I agree. Such workarounds take boot time and create situations when
first action of kernel is to undo last action of booter.
Sometimes it can't be avoided but if we can we should try. Also it adds
some flexibility since last action of booter is
performed in nice unix-like environment and kernel starts in "tabula
rasa". An example is my system with widescreen. To init
widescreen special commands specific to my framebuffer controller are
necessary. So if grub2 sets it kernel can start in
undistorted video mode.
Thanks
Vladimir 'phcoder' Serbinenko
> Or perhaps we could avoid grub_dl_unload_all_modules altogether. For example,
> gfxterm might think that graphical mode needs to be disabled when it's
> unloaded, but the OS loader knows better. You could want to tell your OS
> about the framebuffer state so it can be used by it without glitches.
>
> The same would apply, for example, to stopping the floppy drive. Instead
> of waiting for the drive to tell us it has stopped, we could tell the OS
> it's still spinning if our loader knows how to do that (and the OS knows
> how to receive this information).
>
next prev parent reply other threads:[~2009-02-07 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 15:57 Move BSD and multiboot boot helper out of the kernel to their respective modules phcoder
2009-02-04 12:08 ` phcoder
2009-02-07 22:20 ` Robert Millan
2009-02-07 23:12 ` phcoder [this message]
2009-02-07 22:14 ` Robert Millan
2009-02-07 23:05 ` phcoder
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=498E1540.3090808@gmail.com \
--to=phcoder@gmail.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.