qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/7] ipxe: update binaries
Date: Wed, 15 Jul 2015 14:01:18 +0200	[thread overview]
Message-ID: <1436961678.8987.3.camel@redhat.com> (raw)
In-Reply-To: <55A63FA6.5090907@redhat.com>

On Mi, 2015-07-15 at 13:10 +0200, Laszlo Ersek wrote:
> On 07/15/15 12:10, Gerd Hoffmann wrote:
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > ---
> >  pc-bios/efi-e1000.rom    | Bin 197120 -> 192512 bytes
> >  pc-bios/efi-eepro100.rom | Bin 197632 -> 192512 bytes
> >  pc-bios/efi-ne2k_pci.rom | Bin 195584 -> 190976 bytes
> >  pc-bios/efi-pcnet.rom    | Bin 195584 -> 190976 bytes
> >  pc-bios/efi-rtl8139.rom  | Bin 200192 -> 194560 bytes
> >  pc-bios/efi-virtio.rom   | Bin 194048 -> 188928 bytes
> >  6 files changed, 0 insertions(+), 0 deletions(-)
> 
> Shouldn't you also rebuild (well, commit) the non-EFI (ie. pxe-*)
> binaries too? The rebase in patch #1, the QEMU branding in patch #5, and
> the now-visible git version from patch #6, all seem to affect the pxe-*
> binaries as well.

We didn't do that in the past, because of size problems and because the
pxe-* versions are only used by old machine types.

Lets have a look:

 pc-bios/pxe-e1000.rom    | Bin 67072 -> 62976 bytes
 pc-bios/pxe-eepro100.rom | Bin 61440 -> 62976 bytes
 pc-bios/pxe-ne2k_pci.rom | Bin 61440 -> 62464 bytes
 pc-bios/pxe-pcnet.rom    | Bin 61440 -> 62464 bytes
 pc-bios/pxe-rtl8139.rom  | Bin 61440 -> 63488 bytes
 pc-bios/pxe-virtio.rom   | Bin 60416 -> 61952 bytes

So, the update doesn't work for e1000, where the size goes from > 64k to
< 64k, which in turn changes the pci rom bar size from 128k to 64k ...

cheers,
  Gerd

  reply	other threads:[~2015-07-15 12:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 10:10 [Qemu-devel] [PATCH 0/7] ipxe update, continued Gerd Hoffmann
2015-07-15 10:10 ` [Qemu-devel] [PATCH 1/7] ipxe: update from 35c53797 to 24112d9 (upstream/master) Gerd Hoffmann
2015-07-15 10:51   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 2/7] ipxe: update to 87981bb (qemu) Gerd Hoffmann
2015-07-15 10:57   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 3/7] ipxe: rm local config in cleanup Gerd Hoffmann
2015-07-15 10:58   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 4/7] ipxe: disable load file protocol Gerd Hoffmann
2015-07-15 11:01   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 5/7] ipxe: add qemu branding Gerd Hoffmann
2015-07-15 11:02   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 6/7] ipxe: don't override GITVERSION Gerd Hoffmann
2015-07-15 11:06   ` Laszlo Ersek
2015-07-15 10:10 ` [Qemu-devel] [PATCH 7/7] ipxe: update binaries Gerd Hoffmann
2015-07-15 11:10   ` Laszlo Ersek
2015-07-15 12:01     ` Gerd Hoffmann [this message]
2015-07-15 12:58       ` Laszlo Ersek
2015-07-15 10:47 ` [Qemu-devel] [PATCH 0/7] ipxe update, continued Laszlo Ersek
2015-07-15 11:13 ` Laszlo Ersek
2015-07-16 15:22 ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2015-04-10 14:17 [Qemu-devel] [PATCH 0/7] ipxe: update pxe boot roms for qemu Gerd Hoffmann
2015-04-10 14:17 ` [Qemu-devel] [PATCH 7/7] ipxe: update binaries Gerd Hoffmann

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=1436961678.8987.3.camel@redhat.com \
    --to=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).