qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xie Xianshan <xiexs@cn.fujitsu.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-ppc <qemu-ppc@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Disabling IRQ error
Date: Thu, 12 Sep 2013 18:51:32 +0800	[thread overview]
Message-ID: <52319CB4.3010701@cn.fujitsu.com> (raw)
In-Reply-To: <CAMo8BfK=HZGp=kUGvzsMemVLi=P4tcB=TOB2Rj9d_Y4SA+aD6w@mail.gmail.com>

Dear Max,
    > Does it mean an IRQ to be edge-triggered?
    No, it is a level-sensitive and active-high interrupt.
This is why i tried to use qemu_irq_raise() to trigger IRQ.


Thanks,
Simen


>> Hi Max,
>>      Thanks for your patience and help.
>>      I`ve tried to do what you said, but the problem doesn`t go away.
>> And actually i cannot add a new register to the fpga device, because the
>> fpga device i`m emulating already exists in the real world.
>> So i cannot change anything about hardware properties and linux driver for
>> this device.
>
> Then I don't get its IRQ logic. Does it mean an IRQ to be edge-triggered?
> Its model should use qemu_irq_pulse then instead of qemu_irq_raise and
> its IRQ line should be connected to edge-sensing input of interrupt controller.
> Input that you have used is also used to sense PCI IRQ and is level-sensing.
>
>>      By the way, how did you finally fix your problem?
>
> I didn't have any. (:
>

  reply	other threads:[~2013-09-12 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10  7:25 [Qemu-devel] Disabling IRQ error Xie Xianshan
2013-09-10  8:23 ` Max Filippov
2013-09-11  8:12   ` Xie Xianshan
2013-09-11  9:29     ` Max Filippov
2013-09-12  7:49       ` Xie Xianshan
2013-09-12  7:59         ` Max Filippov
2013-09-12 10:51           ` Xie Xianshan [this message]
2013-09-12 11:10             ` Max Filippov
2013-10-23  2:38       ` Xie Xianshan

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=52319CB4.3010701@cn.fujitsu.com \
    --to=xiexs@cn.fujitsu.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).