From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GfPSl-0007eE-3X
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:25:39 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GfPSh-0007dQ-Nw
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:25:38 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GfPSh-0007dN-Ey
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:25:35 -0500
Received: from [209.86.89.61] (helo=elasmtp-galgo.atl.sa.earthlink.net)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GfPSh-0002kY-ED
	for qemu-devel@nongnu.org; Wed, 01 Nov 2006 18:25:35 -0500
Message-ID: <002e01c6fe0d$0d434460$7e00a8c0@DELL3G>
From: "Roger Lathrop" <ratchetr@sprynet.com>
References: <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
Subject: Re:[Qemu-devel] Interrupt request info
Date: Wed, 1 Nov 2006 18:25:42 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Alessandro,

All you should need to do to raise an IRQ in your code is:
pic_set_irq(s->irq,1);

When the irq is serviced (in one of your ioport traps, I would assume), 
knock the irq down:
pic_set_irq(s->irq,0);

For debugging, you might want to go into i8259.c and uncomment the #define 
DEBUG_IRQ_COUNT line.
You can then use command 'info irq' in the monitor console. This will show 
you a count of interrupts for each IRQ.

Regards,
Roger

> For example, I wrote a module of a simple memory without implementing 
> IRQ...
> I think it is  an error but it works fine... are IRQ raise in any case???
> I look at other code source of implemented hw but for each device there is 
> a
> differeny way to raise an interrupt (i see).
> Is there a standard way to do this?
> The following is an excerpt of my simple memory, please can you describe 
> me
> fastly how can I manage this?
>
> Thank you