From: Stefan Neuwirth <neuwirt-xen-devel@trillian.hd.shuttle.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: pciback error - what does it mean?
Date: Tue, 29 Aug 2006 20:12:38 +0200 [thread overview]
Message-ID: <ufu03vh0mh.fsf@trillian.hd.shuttle.de> (raw)
In-Reply-To: <C1191877.EF2%Keir.Fraser@cl.cam.ac.uk> (Keir Fraser's message of "Mon, 28 Aug 2006 22:02:31 +0100")
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> On 28/8/06 9:26 pm, "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> 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
next prev parent reply other threads:[~2006-08-29 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 20:26 pciback error - what does it mean? Ian Pratt
2006-08-28 21:02 ` Keir Fraser
2006-08-29 18:12 ` Stefan Neuwirth [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-29 20:16 Ian Pratt
2006-08-29 20:29 ` Stefan Neuwirth
2006-08-28 19:57 Stefan Neuwirth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ufu03vh0mh.fsf@trillian.hd.shuttle.de \
--to=neuwirt-xen-devel@trillian.hd.shuttle.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.