From: Gerd Hoffmann <kraxel@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Question] PCI-to-PCI bridge
Date: Wed, 17 Aug 2011 22:48:47 +0200 [thread overview]
Message-ID: <4E4C292F.9060403@redhat.com> (raw)
In-Reply-To: <4E4B2A4B.2040702@cn.fujitsu.com>
On 08/17/11 04:41, Wen Congyang wrote:
> At 08/16/2011 09:40 PM, Gerd Hoffmann Write:
>> There is one in hw/dec_pci.c. This isn't compiled by default, but that
>> is just a configuration issue. I had some IRQ routing issues with that
>> one though.
>
> Yes, I found this device. Do you mean there are some IRQ problems about this
> device?
I think so, I'm not fully sure though. Just did a quick test and
figured devices behind the bridge where not working correctly. I think
some IRQ bug is the most likely cause, but I didn't investigate in detail.
cheers,
Gerd
prev parent reply other threads:[~2011-08-17 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 2:22 [Qemu-devel] [Question] PCI-to-PCI bridge Wen Congyang
2011-08-16 13:40 ` Gerd Hoffmann
2011-08-17 2:41 ` Wen Congyang
2011-08-17 20:48 ` Gerd Hoffmann [this message]
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=4E4C292F.9060403@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).