qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com, mcb30@ipxe.org
Subject: Re: [Qemu-devel] [PATCH] pc-bios: Use iPXE ROMs
Date: Tue, 15 Mar 2011 16:38:40 -0600	[thread overview]
Message-ID: <1300228720.3141.82.camel@x201> (raw)
In-Reply-To: <4D7FE71D.9060805@mail.berlios.de>

On Tue, 2011-03-15 at 23:24 +0100, Stefan Weil wrote:
> Am 15.03.2011 18:00, schrieb Alex Williamson:
> > Refresh PXE ROMs from the iPXE project (http://ipxe.org). This
> > includes moving eepro100 to use standard naming and including a
> > script to easily refresh PXE ROMs from either a local git tree
> > or the upstream project. We include the 'git describe' output
> > in the resulting product name, making it easy to identify and
> > reproduce.

Sorry for not cc'ing, I picked the wrong Stefan.

> The name used for eepro100 was the result of this discussion thread:
> http://lists.nongnu.org/archive/html/qemu-devel/2010-01/msg00729.html

Thanks for the pointer, here's the relevant text:

        But a modified name without the gpxe version like
        gpxe-80861209.rom would have some advantages:
        
        * gpxe* is better than pxe* because the files contain
           a gPXE boot ROM - not a proprietary PXE ROM.

A generic pxe- prefix to me doesn't imply a proprietary ROM, simply the
purpose of the ROM.  Naming it gpxe- just means here we'd need to rename
everything to ipxe- and eventually lpxe-, npxe-, etc...

        * The romfiles are ROM files, not undefined binaries,
           so *.rom looks better than *.bin.

I agree with this one, I'm happy to rename them as .rom files.

        * For drivers like eepro100.c which implement several devices,
           a naming rule based on PCI device and vendor id (80861209)
           is better than a rule based on device names:
           devices with same ids can share the same romfile.

eepro100 now only has one ROM for all devices, so I think this is not
currently an issue.  As Kevin pointed out in the original thread,
pxe-eepro100 is more meaningful to a user than pxe-80861209.

        * Transforming an etherboot romfile name to a qemu romfile name
           is simple when all you have to do is to remove the version.
           This would also simplify pc-bios/README.

The README already leaves something to be desired for reproducibility,
I'm hoping the subtree and build script clear that up.

> So you could as well change all other rom names.
> 
> iPXE default names like 80861209.rom are nice, too.

Yes, but confusing when we end up using that same rom for every eepro100
variant.  Thanks,

Alex

  reply	other threads:[~2011-03-15 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 17:00 [Qemu-devel] [PATCH] pc-bios: Use iPXE ROMs Alex Williamson
2011-03-15 17:35 ` [Qemu-devel] " Anthony Liguori
2011-03-15 19:08   ` Alex Williamson
2011-03-15 22:24 ` [Qemu-devel] " Stefan Weil
2011-03-15 22:38   ` Alex Williamson [this message]
2011-03-16 18:48 ` Stefan Hajnoczi
2011-03-16 19:15   ` Alex Williamson

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=1300228720.3141.82.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=mcb30@ipxe.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=weil@mail.berlios.de \
    /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).