From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] enable multiboot2 loader on i386-ieee1275
Date: Wed, 23 Jan 2008 12:19:36 +0100 [thread overview]
Message-ID: <87odbcrdpz.fsf@xs4all.nl> (raw)
In-Reply-To: <20080123110531.GB25594@thorin> (Robert Millan's message of "Wed, 23 Jan 2008 12:05:31 +0100")
Robert Millan <rmh@aybabtu.com> writes:
> On Wed, Jan 23, 2008 at 11:38:48AM +0100, Marco Gerards wrote:
>> >> > Though I don't see why not do it. The boot abi is already compatible on
>> >> > PowerPC:
>> >> >
>> >> > http://grub.enbug.org/MultibootDraft#head-198f9346038a3782a8263de281dd9cf2eb2759a8
>> >>
>> >> Do you suggest to change the interface for x86?
>> >
>> > Yes. Multiboot2 is still a draft and not widely used (not even in comparison to
>> > Multiboot1). I don't think it's a big problem to change this.
>>
>> We could use ebx or so. Or will this cause new problems?
>
> Well, EBX itself is being used for the MBI, so not a good choice ;-)
>
> About using a free register (I think ECX and EDX aren't used), this might
> cause the inconvenience that you might need to reestructure startup code, in
> case it is laid out in a way that already makes use of that register.
You can move it to EAX in case you do not care about OFW. In that
case you get the old situation back. In case of OFW the old situation
never worked :-)
> I don't think this is the case for the average OFW application that is written
> in C and just has a few lines of asm in _start.
Right. And like I said, other kernels can just move ECX to EAX and
the old code can be used.
--
Marco
prev parent reply other threads:[~2008-01-23 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 1:38 [PATCH] enable multiboot2 loader on i386-ieee1275 Robert Millan
[not found] ` <200801210813.41382.duwe@lst.de>
2008-01-21 11:20 ` Robert Millan
2008-01-23 9:08 ` Marco Gerards
2008-01-23 9:57 ` Robert Millan
2008-01-23 10:13 ` Marco Gerards
2008-01-23 10:25 ` Robert Millan
2008-01-23 10:38 ` Marco Gerards
2008-01-23 11:05 ` Robert Millan
2008-01-23 11:19 ` Marco Gerards [this message]
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=87odbcrdpz.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.