Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: EFI boot problem with MBP 5,4
Date: Tue, 19 Jan 2010 23:40:52 +0100	[thread overview]
Message-ID: <4B5634F4.3000209@gmail.com> (raw)
In-Reply-To: <20100119223408.GC8599@thorin>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Robert Millan wrote:
> On Tue, Jan 19, 2010 at 12:37:57PM +0000, Daire Byrne wrote:
>   
>> Is this just a kernel bug that I should report or can grub work around
>> this? It seems to be a unique incomparability with the EFI firmware in
>> the latest MBP because grub-efi can boot kernels with this patch on
>> earlier macbooks (e.g. MBP4,1).
>>     
>
> Given this note in commit log:
>
>   
>>     [...]  This is somewhat hacky, but it
>>     appears to be the only way to do this that does not break some some
>>     set of existing bootloaders.
>>     
>
> I think you should report it to them.
>
>   
I would be ok with adjusting bootloader but I want a clean doc on it.
This commit vaguely mentions some fields. But I haven't looked into new
boot protocol docs


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

      reply	other threads:[~2010-01-19 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <131780341001050857t6794b2a5o18be810f5bc30d11@mail.gmail.com>
2010-01-05 17:15 ` EFI boot problem with MBP 5,4 Daire Byrne
2010-01-07 21:21   ` Robert Millan
2010-01-11 17:17   ` Daire Byrne
2010-01-19 12:37     ` Daire Byrne
2010-01-19 22:34       ` Robert Millan
2010-01-19 22:40         ` Vladimir 'φ-coder/phcoder' Serbinenko [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=4B5634F4.3000209@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox