WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Fix etherboot option ROM loading

To: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix etherboot option ROM loading
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 28 Jun 2010 19:57:34 +0100
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Delivery-date: Mon, 28 Jun 2010 11:58:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1277748430.5325.93.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsW7IaAIF9jjtegTdqiQmCS5krrnQABz4An
Thread-topic: [Xen-devel] [PATCH] Fix etherboot option ROM loading
User-agent: Microsoft-Entourage/12.24.0.100205
On 28/06/2010 19:07, "Gianni Tedesco" <gianni.tedesco@xxxxxxxxxx> wrote:

> I am working on improved fix for this by building a gPXE ROM with
> support for both rtl8139 and e1000

Which is what we do already, right? Or do we actually end up with two
separate ROMs, one for rtl8139 and one for e1000?

Hm, anyway, presumably internally gpxe has a list of vendor_id:device_id
pairs for each NIC type that it supports? Shouldn't we just patch it so that
the entire list gets exposed in the option ROM headers? That seems the
simple straightforward fix, or is it more complex than that?

 -- Keir

> and then ignoring PCI ID's in the
> option ROM header from within hvmloader - effectively providing a single
> Multi-ROM.
>
> This fix is enough to get things working for now though.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel