From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [Patch] Move multiboot helpers out of the kernel
Date: Sun, 15 Mar 2009 16:34:55 +0100 [thread overview]
Message-ID: <20090315153455.GA24554@thorin> (raw)
In-Reply-To: <49BBEEF7.9000107@gmail.com>
On Sat, Mar 14, 2009 at 06:52:55PM +0100, phcoder wrote:
> Robert Millan wrote:
>> On Sat, Mar 14, 2009 at 12:35:09AM +0100, phcoder wrote:
>>> Index: conf/i386-ieee1275.rmk
>>> ===================================================================
>>> --- conf/i386-ieee1275.rmk (revision 2030)
>>> +++ conf/i386-ieee1275.rmk (working copy)
>>> @@ -126,10 +126,12 @@
>>> # For _multiboot.mod.
>>> _multiboot_mod_SOURCES = loader/ieee1275/multiboot2.c \
>>> + loader/i386/multiboot_helper.S \
>>
>> multiboot_helper.S is not being used on i386-ieee1275 AFAICT
>
> How can it be if multiboot.c is the same for pc and ieee1275?
$ grep multiboot.c conf/*.rmk
conf/i386-coreboot.rmk:_multiboot_mod_SOURCES = loader/i386/multiboot.c \
conf/i386-pc.rmk:_multiboot_mod_SOURCES = loader/i386/multiboot.c \
>> grub_dl_unload_all() just disappeared. Is this intentional? I
>> tend to agree that grub_dl_unload_all() is a waste of time, but
>> this should be discussed separately.
>
> It is intentional because multiboot_real_boot is now in a module so we
> can't unload it
Ok then, I'm fine with disabling the unload. What does everybody else
think?
--
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-03-15 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 10:42 [Patch] Move multiboot helpers out of the kernel phcoder
2009-03-13 23:35 ` phcoder
2009-03-14 14:48 ` Robert Millan
2009-03-14 17:52 ` phcoder
2009-03-15 15:34 ` Robert Millan [this message]
2009-03-21 22:51 ` phcoder
2009-03-21 23:08 ` Robert Millan
2009-03-22 0:15 ` phcoder
2009-03-22 12:29 ` 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=20090315153455.GA24554@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.