From: "Blue Swirl" <blauwirbel@gmail.com>
To: "takasi-y@ops.dti.ne.jp" <takasi-y@ops.dti.ne.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/3] take3 sh4: Add IRL(4bit encoded interrupt input) support.
Date: Wed, 29 Oct 2008 20:09:15 +0200 [thread overview]
Message-ID: <f43fc5580810291109i225bb246mc90f0356533a95c5@mail.gmail.com> (raw)
In-Reply-To: <200810282058.m9SKwVfH004300@smtp12.dti.ne.jp>
On 10/28/08, takasi-y@ops.dti.ne.jp <takasi-y@ops.dti.ne.jp> wrote:
> > Isn't it possible to use existing qemu_irq for the signals instead? On
> > Sparc32, I have used qemu_irq for interrupt lines, reset signals and a
> > terminal count pulse, one version used it for DMA request.
>
> I have re-written them using qemu_irq.
> This use qemu_irq as multi-level signal. I mean LEVEL as in
> qemu_set_irq(irq, LEVEL) is {0...15} but {0,1}.
If an irq is active at some level, and another irq at some other level
arrives, doesn't the first one get lost? Maybe SH has edge-triggered
irqs and this is OK, I don't know.
Sparc32 has similar 15 level interrupt system with priorities. I've
used a separate qemu_irq for each of these, but perhaps your way could
work if I used a bitmap.
next prev parent reply other threads:[~2008-10-29 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 16:31 [Qemu-devel] [PATCH] sh4: mmio based CF support on r2d board yoshii.takashi
2008-09-22 19:00 ` takasi-y
2008-09-23 8:55 ` Paul Mundt
2008-10-08 15:20 ` pmac kernel & disk image wanted (was Re: [Qemu-devel] [PATCH] sh4: mmio based CF support on r2d board.) Shin-ichiro KAWASAKI
2008-10-26 15:35 ` Andreas Färber
2008-10-26 15:17 ` [Qemu-devel] [PATCH 1/3] sh4: mmio based CF support on r2d board takasi-y
2008-10-26 15:54 ` Blue Swirl
2008-10-27 1:29 ` andrzej zaborowski
2008-10-27 17:10 ` Blue Swirl
2008-10-29 14:22 ` andrzej zaborowski
2008-10-29 18:37 ` Blue Swirl
2008-10-27 18:57 ` takasi-y
2008-10-27 19:12 ` Blue Swirl
2008-10-28 20:58 ` [Qemu-devel] [PATCH 1/3] take3 " takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 0/3] take 2. " takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 2/3] sh4: Add IRL(4bit encoded interrupt input) support takasi-y
2008-10-26 16:09 ` Blue Swirl
2008-10-28 20:58 ` [Qemu-devel] [PATCH 2/3] take3 " takasi-y
2008-10-29 18:09 ` Blue Swirl [this message]
2008-10-30 17:28 ` [Qemu-devel] " takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 3/3] sh4: Add r2d onboard FPGA IRQ controller takasi-y
2008-10-28 20:58 ` [Qemu-devel] [PATCH 3/3] take3 " takasi-y
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=f43fc5580810291109i225bb246mc90f0356533a95c5@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=takasi-y@ops.dti.ne.jp \
/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).