From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=43072 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P5hbo-0001Zm-HU for qemu-devel@nongnu.org; Tue, 12 Oct 2010 12:21:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P5hYc-0006fW-00 for qemu-devel@nongnu.org; Tue, 12 Oct 2010 12:18:37 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:60670) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P5hYb-0006f9-Ku for qemu-devel@nongnu.org; Tue, 12 Oct 2010 12:18:29 -0400 Message-ID: <4CB48A51.8040508@mail.berlios.de> Date: Tue, 12 Oct 2010 18:18:25 +0200 From: Stefan Weil MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------070104080209090703060900" Subject: [Qemu-devel] Re: Where's gpxe-eepro100-80862449.rom ? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------070104080209090703060900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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). * 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. 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? --------------070104080209090703060900 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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).

* 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.

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?

 --------------070104080209090703060900--