From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1OA5nV-00050w-Lo for qemu-devel@nongnu.org; Thu, 06 May 2010 14:27:45 -0400 Received: from [140.186.70.92] (port=33031 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OA5nQ-0004vx-8B for qemu-devel@nongnu.org; Thu, 06 May 2010 14:27:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OA5nJ-0007Vb-8B for qemu-devel@nongnu.org; Thu, 06 May 2010 14:27:39 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:60651) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OA5nI-0007V1-ST for qemu-devel@nongnu.org; Thu, 06 May 2010 14:27:33 -0400 Message-ID: <4BE30A12.5050807@mail.berlios.de> Date: Thu, 06 May 2010 20:27:30 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] eepro100: missing gpxe-eepro100-80862449.rom? References: <2FA29919D4DA45669D7DEC5918977328@FSCPC> In-Reply-To: <2FA29919D4DA45669D7DEC5918977328@FSCPC> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Herbszt Cc: qemu-devel@nongnu.org Am 05.05.2010 22:03, schrieb Sebastian Herbszt: > eepro100_register_devices() references three option roms: > - gpxe-eepro100-80861209.rom > - gpxe-eepro100-80861229.rom > - gpxe-eepro100-80862449.rom > > The last one seems to be missing because it's not in the pc-bios > directory. > > Sebastian 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. Regards Stefan