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] pciback error - what does it mean?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] pciback error - what does it mean?
From: Stefan Neuwirth <neuwirt-xen-devel@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 29 Aug 2006 20:12:38 +0200
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 29 Aug 2006 11:17:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1191877.EF2%Keir.Fraser@xxxxxxxxxxxx> (Keir Fraser's message of "Mon, 28 Aug 2006 22:02:31 +0100")
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C1191877.EF2%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux)
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> writes:

> On 28/8/06 9:26 pm, "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
>
>>> I'm still playing around with xen-3.0.2-3 and the pciback.hide
>>> option. Currently I'm trying to give the guest a pcmcia-to-pci card
>>> with a prism54 wlan card in the slot. When starting the guest the
>>> following message apears in the bootlog:
>>> 
>>> ...
>>> pciback 0000:02:09.0: can't export pci devices that don't have a
>>> normal (0) or bridge (1) header type!
>>> ...
>> 
>> Cardbus bridges have a "2" in this field. No idea what will happen if
>> you disable this test in pciback, but it's worth a go...
>
> It'll almost certainly just work. I'm not sure a test on device type is
> really necessary.

Just disable the test will lead to trouble in function
pciback_config_header_add_fields
(.../xen/pciback/conf_space_header.c). There are two structures called
header_0 and header_1 that are used by pciback_config_add_fields. So
someone decided to not implement header_2 - maybe there was a reason
for the decision...

  Stefan

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