qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Laszlo Ersek <lersek@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: edk2-devel@lists.sourceforge.net,
	qemu devel list <qemu-devel@nongnu.org>,
	BALATON Zoltan <balaton@eik.bme.hu>
Subject: Re: [Qemu-devel] [edk2] syslinux vs. OVMF
Date: Wed, 27 May 2015 00:31:34 +0300	[thread overview]
Message-ID: <5564E636.8080701@msgid.tls.msk.ru> (raw)
In-Reply-To: <5564A7B8.4050001@msgid.tls.msk.ru>

26.05.2015 20:04, Michael Tokarev wrpte:
> 26.05.2015 19:49, Laszlo Ersek wrote:
[]
>> the right (updated) iPXE binaries. (I think Gerd's patches implementing
>> the update have not been merged into upstream qemu yet? The most recent
>> patch from Gerd, under pc-bios/, is
>> c246cee4eedb17ae3932d699e009a8b63240235f. Unrelated, and too old.)
> 
> Oh sh*t.  You're right.  Indeed, that's the last patch, and indeed
> it is too old.  I guess we need http://lists.ipxe.org/pipermail/ipxe-devel/2015-March/004007.html
> or some other bits from https://www.kraxel.org/cgit/qemu/log/?h=rebase/roms-next.
> 
> Somehow, since the talk was about updating binaries before the next
> (2.3 at that time) release, I thought current qemu have all necessary
> bits.

After applying 2 patches from Gerd:

 efi_snp-improve-compliance-with-the-EFI_SIMPLE_NETWORK_PROTOCOL_spec.patch
 efi-make-load-file-protocol-optional.patch

syslinux works fine with the resulting efirom for qemu too,
it successfully loads kernel+initrd and boots the system.

So we're waiting for the missing ipxe bits... ;)

Thanks,

/mjt

      parent reply	other threads:[~2015-05-26 21:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.GSO.2.01.1504062122470.1832@mono>
     [not found] ` <5523E12E.8010103@redhat.com>
     [not found]   ` <1428653687.11559.5.camel@nilsson.home.kraxel.org>
2015-04-10 10:06     ` [Qemu-devel] [edk2] syslinux vs. OVMF Laszlo Ersek
2015-04-10 11:04       ` [Qemu-devel] virtio-net regression [was: syslinux vs. OVMF] Laszlo Ersek
2015-04-10 14:36         ` Laszlo Ersek
2015-04-10 19:56           ` Laszlo Ersek
2015-05-26 14:36       ` [Qemu-devel] [edk2] syslinux vs. OVMF Michael Tokarev
2015-05-26 16:49         ` Laszlo Ersek
2015-05-26 17:04           ` Michael Tokarev
2015-05-26 18:38             ` Laszlo Ersek
2015-05-26 20:17               ` BALATON Zoltan
2015-05-26 20:27                 ` Michael Tokarev
2015-05-26 20:42                   ` BALATON Zoltan
2015-05-26 21:31             ` Michael Tokarev [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=5564E636.8080701@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=balaton@eik.bme.hu \
    --cc=edk2-devel@lists.sourceforge.net \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).