From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gir70-0001ke-3o
	for qemu-devel@nongnu.org; Sat, 11 Nov 2006 06:33:26 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gir6y-0001ib-71
	for qemu-devel@nongnu.org; Sat, 11 Nov 2006 06:33:25 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gir6x-0001iE-Nq
	for qemu-devel@nongnu.org; Sat, 11 Nov 2006 06:33:23 -0500
Received: from [64.233.162.204] (helo=nz-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gir6v-0003jg-NQ
	for qemu-devel@nongnu.org; Sat, 11 Nov 2006 06:33:22 -0500
Received: by nz-out-0102.google.com with SMTP id i11so689986nzi
	for <qemu-devel@nongnu.org>; Sat, 11 Nov 2006 03:32:12 -0800 (PST)
Message-ID: <b921df970611110332v68900bbeka5f3f0a8b73b1191@mail.gmail.com>
Date: Sat, 11 Nov 2006 12:32:12 +0100
From: "Alessandro Corradi" <ale.corradi@gmail.com>
Subject: Re: [Qemu-devel] Interrupt request info
In-Reply-To: <200611012331.38312.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_50499_31451022.1163244732166"
References: <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
	<002e01c6fe0d$0d434460$7e00a8c0@DELL3G>
	<200611012331.38312.paul@codesourcery.com>
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

------=_Part_50499_31451022.1163244732166
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thank you very much,
But I don't understand what the first parameter is on pic_set_irq_new...
I tried anyway to implement my hw with pic_set_irq, but in qemu console I
didn't see my irq (13) with info irq.
I tried to raise it: pic_set_irq(s->irq,1);

What I need to do to raise irq correctly with pic_set_irq_new specially the
first parameter)?

Thank you

2006/11/2, Paul Brook <paul@codesourcery.com>:
>
> On Wednesday 01 November 2006 23:25, Roger Lathrop wrote:
> > 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);
>
> No. You should use pic_set_irq_new. Otherwise your code will break on
> machines
> with multiple interrupt controllers.
>
> Paul
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

------=_Part_50499_31451022.1163244732166
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thank you very much,<br>
But I don't understand what the first parameter is on pic_set_irq_new...<br>
I tried anyway to implement my hw with pic_set_irq, but in qemu console I didn't see my irq (13) with info irq.<br>
I tried to raise it: pic_set_irq(s-&gt;irq,1);<br>
<br>
What I need to do to raise irq correctly with pic_set_irq_new specially the first parameter)?<br>
<br>
Thank you<br><br><div><span class="gmail_quote">2006/11/2, Paul Brook &lt;<a href="mailto:paul@codesourcery.com">paul@codesourcery.com</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 01 November 2006 23:25, Roger Lathrop wrote:<br>&gt; Alessandro,<br>&gt;<br>&gt; All you should need to do to raise an IRQ in your code is:<br>&gt; pic_set_irq(s-&gt;irq,1);<br>&gt;<br>&gt; When the irq is serviced (in one of your ioport traps, I would assume),
<br>&gt; knock the irq down:<br>&gt; pic_set_irq(s-&gt;irq,0);<br><br>No. You should use pic_set_irq_new. Otherwise your code will break on machines<br>with multiple interrupt controllers.<br><br>Paul<br><br><br>_______________________________________________
<br>Qemu-devel mailing list<br><a href="mailto:Qemu-devel@nongnu.org">Qemu-devel@nongnu.org</a><br><a href="http://lists.nongnu.org/mailman/listinfo/qemu-devel">http://lists.nongnu.org/mailman/listinfo/qemu-devel</a><br></blockquote>
</div><br>

------=_Part_50499_31451022.1163244732166--