All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Efiemu
Date: Sun, 01 Mar 2009 22:13:59 +0100	[thread overview]
Message-ID: <49AAFA97.7010504@gmail.com> (raw)
In-Reply-To: <ca0f59980903011200t55589582iae817fc5e9c8f301@mail.gmail.com>

Bean wrote:
> 
> First, I notice some novel use of macro. For example, use GRUB_EFI to
> wrap around efi calls, which expands to different prefix in different
> environment. I'm not a big fan of macro, and this seems a little
> weird.
It can't be done without at least some macros because it's able to load 
64-bit efiemu from 32-bit mode and vice-versa. But GRUB_EFI can be 
replaced to a set of grub_autoefi_* aliases

> 
> Also, perhaps you should just avoid linux_efiemu altogether. The efi
> linux loader contains some tricks that mostly make sense in apple efi
> firmware, and it might cause hazard in bios environment. Besides, if
> it's just for testing purpose, linux is not a very good efi citizen,
> it doesn't even have a efi loader of its own.
> 
I agree that for now this part of patch should probably be left out. At 
least until we merge all i386/*/linux.c to i386/linux.c by using Vesa's 
memory manager and video functions. However efiemu can help linux to get 
decent efi support in future.

-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-01 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 16:17 Efiemu phcoder
2009-03-01 10:49 ` Efiemu phcoder
2009-03-01 20:00   ` Efiemu Bean
2009-03-01 21:13     ` phcoder [this message]
2009-03-20 19:32       ` Efiemu 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=49AAFA97.7010504@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.