From: Claudio Fontana <claudio.fontana@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] QEMU pci mach-virt: setting PCI_INTERRUPT_LINE?
Date: Tue, 24 Feb 2015 15:34:11 +0100 [thread overview]
Message-ID: <54EC8BE3.703@huawei.com> (raw)
Hello,
I am trying to set the pci interrupt line field in the configuration space
(offset 0x3c), since it is initialized as zero.
I would like to set it to the right value as read from the device tree,
in order for other existing software which relies on it to be able to work unmodified..
but it does not seem to work (I seem to read back zero even after setting the PCI_INTERRUPT_LINE field).
I am also reading the interrupt pin, but that one instead seems to work out of the box..
Thank you for any suggestion,
Claudio
next reply other threads:[~2015-02-24 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 14:34 Claudio Fontana [this message]
2015-02-25 12:07 ` [Qemu-devel] QEMU pci mach-virt: setting PCI_INTERRUPT_LINE? Claudio Fontana
2015-02-25 12:08 ` Alexander Graf
2015-02-25 12:16 ` Claudio Fontana
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=54EC8BE3.703@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=agraf@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).