From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: 2Marco Gerards (new)
Date: Thu, 22 Sep 2005 20:16:24 +0200 [thread overview]
Message-ID: <874q8d2cjr.fsf@student.han.nl> (raw)
In-Reply-To: <20050921231005.4190.qmail@web35308.mail.mud.yahoo.com> (Ruslan Nikolaev's message of "Wed, 21 Sep 2005 16:10:05 -0700 (PDT)")
Ruslan Nikolaev <nruslan_devel@yahoo.com> writes:
Hi Ruslan,
> Because it requires to build 32-bit file. As I said before this patch
> will work even the OS can't load 32-bit executables at all. I'm not
> sure about compiling it as a 64-bit file because it generates another
> code; moreover x86_64 accepts regparam=6. Perhaps it would detect
> bug... but who knows?
Well, right. If we can't test it, we should just assume the worst
case scenario. That means we should assume the bug is there if we can
not test for it.
I can make this change and will commit my patch tomorrow. Any further
improvements from that point on are more than welcome. For me it is
just important that CVS works because I have some GRUB 2 trees here
that I want to test and all don't compile so it is making progress
from my side slow...
>> ... But I am not sure if we want a 64 bits multiboot and what is
>> involved with changing multiboot that way. I leave that to Okuji.
>
> I can't understand what you mean. If it is support for ELF64 multiboot
> then it already presents in GRUB (see multiboot.c file). If it is
> ELF64 multiboot & switching to 64-bit mode then it is MISTAKE because
> it requires enabling paging and it's not clear at all. If it is
> 64-bit version of GRUB utilities then my patch already provides it
What I mean is that multiboot is a standard. I think we can not
modify GRUB without modifying the standard. But perhaps I am just
mistaken because I do not know enough about the subject.
--
Marco
next prev parent reply other threads:[~2005-09-22 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 23:10 [PATCH] new patch for amd64 Ruslan Nikolaev
2005-09-21 11:38 ` Yoshinori K. Okuji
2005-09-21 23:03 ` 2Yoshinori K. Okuji Ruslan Nikolaev
2005-09-21 13:07 ` [PATCH] new patch for amd64 Marco Gerards
2005-09-21 22:47 ` 2Marco Gerards Ruslan Nikolaev
2005-09-21 23:10 ` 2Marco Gerards (new) Ruslan Nikolaev
2005-09-22 18:16 ` Marco Gerards [this message]
2005-09-22 22:43 ` 2Marco Gerards (important info) Ruslan Nikolaev
2005-09-23 13:46 ` Marco Gerards
2005-09-24 22:17 ` 2Marco Gerards (answer) Ruslan Nikolaev
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=874q8d2cjr.fsf@student.han.nl \
--to=metgerards@student.han.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.