qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Where's gpxe-eepro100-80862449.rom ?
Date: Fri, 15 Oct 2010 23:03:18 +0200	[thread overview]
Message-ID: <4CB8C196.8030403@mail.berlios.de> (raw)
In-Reply-To: <m3bp6y5zvu.fsf@blackfin.pond.sub.org>

Am 13.10.2010 09:13, schrieb Markus Armbruster:
> Stefan Weil<weil@mail.berlios.de>  writes:
>
>    
>> Am 12.10.2010 14:41, schrieb Markus Armbruster:
>>      
>>> Commit db667a12 added a reference to ROM file
>>> gpxe-eepro100-80862449.rom, but no such file. Intentional?
>>>        
>> Yes. See
>> http://lists.nongnu.org/archive/html/qemu-devel/2010-05/msg00418.html
>>
>> Citation from my former mail:
>>
>>     Yes, it is missing. I did not add it for several reasons:
>>
>>     * The new variant i82801 (which needs the missing ROM) is currently
>>     not available
>>     via model=i82801 (it can be selected by experts using other methods).
>>      
> It's available via -device i82801.  -net nic,model= is obsolescent.
>
>    
>>     * Experts can get the missing ROM from ROM-o-matic.
>>
>>     * All three ROMs differ only in one or two bytes (device id). That's
>>     a waste
>>     of binary space (56832 bytes!). Therefore I plan to remove all but
>>     the first
>>     ROM file. The missing ones can be created by make or patched on the
>>     fly by
>>     QEMU during load. Maybe it is also possible to create ROM files
>>     which support
>>     more than one vendor/device entry - that would be the best solution.
>>      
> No objections to creating by make or on load, but I'd be just fine with
> the duplicated ROMs.  Disk space waste in the order of 100KiB is lost in
> the noise nowadays.  My qemu/.git is>100MiB, and my build tree for all
> targets ~1.5GiB.
>
>    
>> There is still nothing new regarding these last points
>> because I did not spend any time on them.
>>
>> Do you think there is urgent need for a gpxe-eepro100-80862449.rom binary?
>>      
> Well, "-device i82801" complains because it misses this binary.  Do we
> want to ship that way?
>    

I just sent two patches which create the rom data on load.
So -device i82801 no longer complains but gets the boot
information from dhcp (tested with i386-softmmu).

Your build tree will be made smaller by at least 50 KB :-)

Do you think these patches should be added to stable-0.13, too?

Regards,
Stefan

  parent reply	other threads:[~2010-10-15 21:03 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 12:41 [Qemu-devel] Where's gpxe-eepro100-80862449.rom ? Markus Armbruster
2010-10-12 16:18 ` [Qemu-devel] " Stefan Weil
2010-10-13  7:13   ` Markus Armbruster
2010-10-15 20:51     ` [Qemu-devel] [PATCH 1/2] pci: Automatically patch PCI device id in PCI ROM Stefan Weil
2010-10-15 21:05       ` Anthony Liguori
2010-10-18 10:09         ` Gerd Hoffmann
2010-10-18 18:39           ` Anthony Liguori
2010-10-21 10:09             ` [SeaBIOS] " Avi Kivity
2010-10-21 13:14               ` Anthony Liguori
2010-10-21 15:34                 ` Avi Kivity
2010-10-18 10:04       ` Gerd Hoffmann
2010-10-18 11:16         ` Stefan Weil
2010-10-18 11:54           ` Gerd Hoffmann
2010-10-18 13:16             ` Stefan Weil
2010-10-18 13:30               ` Gerd Hoffmann
2010-10-18 15:50                 ` Gerd Hoffmann
2010-10-18 17:54                   ` Stefan Weil
2010-10-18 17:55                   ` [Qemu-devel] [PATCH 1/2] pci: Automatically patch PCI vendor id and " Stefan Weil
2010-10-18 17:58                     ` [Qemu-devel] " Michael S. Tsirkin
2010-10-18 18:42                       ` Anthony Liguori
2010-10-18 19:03                         ` Michael S. Tsirkin
2010-10-18 19:36                           ` Stefan Weil
2010-10-18 19:59                             ` Anthony Liguori
2010-10-19  6:40                             ` Gerd Hoffmann
2010-10-18 19:56                           ` Anthony Liguori
2010-10-18 18:44                     ` [Qemu-devel] " Anthony Liguori
2010-10-18 18:53                       ` Anthony Liguori
2010-10-18 19:11                         ` Stefan Weil
2010-10-19  8:37                           ` Michael S. Tsirkin
2010-10-19 21:15                             ` Stefan Weil
2010-10-19 21:22                               ` Anthony Liguori
2010-10-19 21:25                                 ` Michael S. Tsirkin
2010-10-19 21:08                         ` Stefan Weil
2010-10-20  7:19                           ` [Qemu-devel] " Gerd Hoffmann
2010-10-20 20:30                             ` Stefan Weil
2010-11-22  6:29                           ` Michael S. Tsirkin
2010-10-15 20:51     ` [Qemu-devel] [PATCH 2/2] eepro100: Use a single rom file for all i825xx devices Stefan Weil
2010-11-22  6:29       ` [Qemu-devel] " Michael S. Tsirkin
2010-10-15 21:03     ` Stefan Weil [this message]
2010-10-25 12:11       ` [Qemu-devel] Re: Where's gpxe-eepro100-80862449.rom ? Markus Armbruster
2010-10-25 16:23         ` Stefan Weil
2010-10-25 16:54           ` Michael S. Tsirkin
2010-11-15 17:06             ` Stefan Weil

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=4CB8C196.8030403@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=armbru@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).