From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=53154 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P8fJ6-0004yp-On
	for qemu-devel@nongnu.org; Wed, 20 Oct 2010 16:30:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <weil@mail.berlios.de>) id 1P8fJ5-0001E3-LF
	for qemu-devel@nongnu.org; Wed, 20 Oct 2010 16:30:44 -0400
Received: from moutng.kundenserver.de ([212.227.126.171]:60421)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <weil@mail.berlios.de>) id 1P8fJ5-0001Dr-9X
	for qemu-devel@nongnu.org; Wed, 20 Oct 2010 16:30:43 -0400
Message-ID: <4CBF5161.7090600@mail.berlios.de>
Date: Wed, 20 Oct 2010 22:30:25 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
References: <4CBC97BE.7070902@codemonkey.ws>
	<1287522501-8091-1-git-send-email-weil@mail.berlios.de>
	<4CBE9808.2040003@redhat.com>
In-Reply-To: <4CBE9808.2040003@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH 1/2] pci: Automatically patch PCI vendor id
 and device id in PCI ROM
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>

Am 20.10.2010 09:19, schrieb Gerd Hoffmann:
>   Hi,
>
>> The i825xx ethernet controller family is a typical example
>> which is implemented in hw/eepro100.c. It uses at least
>> 3 different device ids, so normally 3 boot roms would be needed.
>
> Does this actually work now with the etherboot roms?
>
> cheers,
>   Gerd


Yes. I tested these two cases:

qemu -L pc-bios -boot n -netdev user,id=internet \
     -device i82801,netdev=internet,romfile=gpxe-eepro100-80861209.rom

=> no bootable device

qemu -L pc-bios -boot n -netdev user,id=internet \
     -device i82801,netdev=internet

=> device gets ip address via dhcp

The same works with i82559c or other eepro100 variants, too.

Cheers,
Stefan