From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Move loader.c out of the kernel
Date: Sun, 22 Mar 2009 14:06:36 +0100 [thread overview]
Message-ID: <49C637DC.4050002@gmail.com> (raw)
In-Reply-To: <200903222157.33568.okuji@enbug.org>
Yoshinori K. Okuji wrote:
> On Sunday 22 March 2009 21:48:21 phcoder wrote:
>> Hello. Now when boot command isn't in kernel anymore I don't see why
>> loader.c stays in kernel. Here is the patch to move it to boot.mod
>
> This is not useful in reality, because the loader interface needs to be
> pre-loaded into core.img anyway.
Why? I successfully tested core.img with just pc fat and biosdisk
modules integrated. It loads boot.mod just fine and boots linux and
multiboot with no problem
> Note that the more you split code into
> modules, the more the size of core.img is, as long as they are all
> pre-loaded.
>
> Regards,
> Okuji
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-03-22 13:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 12:48 Move loader.c out of the kernel phcoder
2009-03-22 12:57 ` Yoshinori K. Okuji
2009-03-22 13:06 ` phcoder [this message]
2009-03-22 13:12 ` Yoshinori K. Okuji
2009-03-22 13:30 ` phcoder
2009-03-22 14:01 ` Yoshinori K. Okuji
2009-03-22 14:19 ` phcoder
2009-03-22 14:59 ` Yoshinori K. Okuji
2009-03-22 14:54 ` Robert Millan
2009-03-31 8:56 ` phcoder
2009-04-01 13:52 ` Yoshinori K. Okuji
2009-04-01 14:19 ` Robert Millan
2009-04-01 14:42 ` Yoshinori K. Okuji
2009-04-01 15:12 ` phcoder
2009-04-01 15:21 ` Vesa Jääskeläinen
2009-04-01 15:46 ` phcoder
2009-04-05 15:19 ` phcoder
2009-04-15 12:46 ` 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=49C637DC.4050002@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.