From: Isaac Dupree <id@isaac.cedarswampstudios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] New x86_64 EFI patch
Date: Tue, 24 Jun 2008 08:52:47 -0400 [thread overview]
Message-ID: <4860EE1F.7000207@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <ca0f59980806211004wc7ebb31j405201e26833a657@mail.gmail.com>
Bean wrote:
> On Sat, Jun 21, 2008 at 1:04 AM, Bean <bean123ch@gmail.com> wrote:
>> Hi,
>>
>> This new patch add the following function to the original x86_64 EFI patch:
>>
>> 1, Fix menu drawing problem
>> It maps the unicode char to EFI char so that the rectangle box is
>> showed properly
>>
>> 2, Handle command line option for chainloader command
>>
>> 3, Add new command appleloader
>> The command is used to enable bios boot in apple's bootcamp, for example
>>
>> boot from legacy mbr:
>> appleloader HD
>> boot
>>
>> boot from legacy cd:
>> appleloader CD
>> boot
>>
>> boot from usb:
>> appleloader USB
>> boot
>>
>> The usb booting may not work in some machine.
>
> Hi,
>
> I also fix a few problem in the linux loader, now it can load both 686
> and x86_64 kernel from 64-bit EFI firmware.
>
> Would someone test it in 32-bit EFI ?
with just that patch against CVS, for me
- linux then initrd doesn't run out of memory (that fix is still there).
On the other hand, 'linux' with wrong parameters so I repeated the
command, did give me such an error. In any case, trying again perfectly
and booting, gave me the same (as my last test with your EFI patches)
hanging on the GRUB terminal, not booting successfully.
- appleloader always tells me "Model : Core Duo/Solo" and nothing else
(no matter whether I give it a parameter or not). If I say "boot"
nothing happens, it just stays in GRUB prompt and I can enter more
commands. (admittedly, I think I didn't *have* anything to boot in my
CD drive, USB or MBR)
-Isaac
next prev parent reply other threads:[~2008-06-24 12:53 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 17:04 [PATCH] New x86_64 EFI patch Bean
2008-06-21 17:04 ` Bean
2008-06-23 11:58 ` Isaac Dupree
2008-06-23 12:53 ` Bean
2008-06-24 12:52 ` Isaac Dupree [this message]
2008-06-24 13:12 ` Bean
2008-06-24 16:57 ` Isaac Dupree
2008-06-24 17:11 ` Bean
2008-06-24 21:59 ` Isaac Dupree
2008-06-25 6:49 ` Bean
2008-06-25 12:50 ` Isaac Dupree
2008-06-25 13:54 ` Bean
2008-06-28 10:51 ` Isaac Dupree
2008-06-28 11:55 ` Bean
2008-06-29 23:55 ` Isaac Dupree
2008-06-30 5:05 ` Bean
2008-07-02 13:43 ` Bean
2008-07-05 23:02 ` Isaac Dupree
2008-07-06 4:31 ` Bean
2008-07-08 16:16 ` Isaac Dupree
2008-07-08 16:31 ` Bean
2008-07-12 14:41 ` Robert Millan
2008-07-12 15:16 ` Bean
2008-07-12 15:26 ` Bean
2008-07-12 17:10 ` Robert Millan
2008-07-12 18:05 ` Bean
2008-07-17 9:50 ` Bean
2008-07-17 15:02 ` Javier Martín
2008-07-17 15:18 ` Bean
2008-07-17 15:28 ` Pavel Roskin
2008-07-17 15:22 ` Pavel Roskin
2008-07-17 15:26 ` Bean
2008-07-17 15:45 ` Javier Martín
2008-07-17 15:50 ` Bean
2008-07-17 16:01 ` Javier Martín
2008-07-17 16:17 ` Pavel Roskin
2008-07-17 16:06 ` Pavel Roskin
2008-07-17 16:17 ` Javier Martín
2008-07-19 15:01 ` generic BIOS-less boot (Re: [PATCH] New x86_64 EFI patch) Robert Millan
2008-07-12 15:26 ` [PATCH] New x86_64 EFI patch Robert Millan
2008-07-12 15:37 ` Bean
2008-07-12 15:48 ` Bean
2008-06-25 12:59 ` Isaac Dupree
2008-07-03 18:11 ` Marco Gerards
2008-07-03 19:51 ` Bean
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=4860EE1F.7000207@isaac.cedarswampstudios.org \
--to=id@isaac.cedarswampstudios.org \
--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.