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: multiboot on EFI
Date: Mon, 23 Mar 2009 23:33:50 +0100	[thread overview]
Message-ID: <49C80E4E.4050409@gmail.com> (raw)
In-Reply-To: <49C809BB.2000006@gmail.com>

You may also need my elf bugfix patch (was applied as rev 2037)
phcoder wrote:
> Try with 2030. Actually it's diffed against 2030+some of my posted and 
> unposted patches. If it still doesn't apply please report I'll update 
> and rediff it against HEAD.
> I'm interested in behaviour of this code on real EFI however doesn't 
> expect this version to be able to work completely.
> x86_64-efi isn't supported by this patch yet
> Also if xen uses any bios interrupts it will probably triple fault. On 
> IRC we discussed a possibility of loading seabios and it's probably 
> feasible but will take more time
> uzer cheg wrote:
>> Vladimir,
>>
>> First of all I'd like to say thank you for a quick feedback and 
>> development.
>>
>> I  tried to apply your patches and test it on my Apple Xserve Intel 32 
>> bit.
>> I've done following;
>>
>> # svn co svn://svn.sv.gnu.org/grub/trunk/grub2
>> # cd ./grub2
>> # patch -b -p1 < ./uppermem.diff
>> patching file conf/i386.rmk
>> patching file lib/i386/uppermem.c
>>  --- it's Ok
>>  --- Than
>> #  patch -b -p1 < ./efiboot.diff
>> patching file conf/common.rmk
>> Hunk #1 succeeded at 503 (offset -4 lines).
>> patching file conf/i386-coreboot.rmk
>> Hunk #1 succeeded at 99 with fuzz 2 (offset -3 lines).
>> Hunk #2 succeeded at 200 (offset -10 lines).
>> patching file conf/i386-efi.rmk
>> Hunk #1 FAILED at 80.
>> Hunk #2 FAILED at 103.
>> ...
>> etc.
>>
>>
>> I would like to ask you for what revision of grub2 this patches where 
>> done?
>> Do I have to checkout any specific branch of grub2?
>>
>> Thank you in advance.
>>
>> 2009/3/23 phcoder <phcoder@gmail.com>:
>>> Hello. Here is an initial version of patch for booting multiboot 
>>> kernels on
>>> i386-efi. No Changelog yet because it's not for inclusion yet.
>>> -- 
>>>
>>> Regards
>>> Vladimir 'phcoder' Serbinenko
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>>
>>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
> 
> 


-- 

Regards
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2009-03-23 22:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 12:29 multiboot on EFI phcoder
2009-03-23 21:16 ` uzer cheg
2009-03-23 22:14   ` phcoder
2009-03-23 22:33     ` phcoder [this message]
2009-03-24 10:31     ` uzer cheg
2009-03-24 10:54       ` phcoder
2009-03-24 10:58         ` uzer cheg
2009-03-26 19:25           ` Vladimir Serbinenko
2009-03-28 13:13 ` Robert Millan
2009-03-28 14:31   ` Yoshinori K. Okuji
2009-04-01 12:57     ` Robert Millan
2009-04-01 13:58       ` Yoshinori K. Okuji
2009-03-28 22:33   ` phcoder
2009-04-04 16:28     ` phcoder
2009-04-04 16:51       ` 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=49C80E4E.4050409@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.