I tried with both pic_set_irq and pic_set_irq_new but nothing happen
(the irq number is 13 and I verified with info irq in qemu monitor).
I tried also to hack i8259.c and the function is not called (I think).
What the first parameter of pic_set_irq_new is referred to?
Another question: why a new v
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 pi
-- Forwarded message --From: Alessandro Corradi <[EMAIL PROTECTED]>Date: 4-nov-2006
17.08Subject: Re: [Qemu-devel] Interrupt request infoTo: qemu-devel@nongnu.orgThank you very much for the answer,so the only think to do to raise correctly an interrupt (I think) is only to raise it
Thank you very much for the answer,so the only think to do to raise correctly an interrupt (I think) is only to raise it when a read funciton is completed (in case of my simple memory) because it will alarm the process in waiting status to read the value in the register.
the workaround of a read op
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
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_IR
> I already read this, but give no usefull information... and I searched
> everywhere in the web...
> 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
-- Forwarded message --From: Alessandro Corradi <[EMAIL PROTECTED]>Date: 31-ott-2006
10.25Subject: Re: [Qemu-devel] Interrupt request infoTo: Rob Landley <[EMAIL PROTECTED]>I already read this, but give no usefull information... and I searched everywhere in the web...
For example,
On Saturday 28 October 2006 5:36 am, Alessandro Corradi wrote:
> Hello,
> Can someone give me detailed information (or a link where it is described)
> how qemu manage hw interrupts?
> I can't find any usefull info about it in QEMU doc.
http://www.qemu.org/qemu-tech.html#SEC18
> ps: Obviously, if
Hello,Can someone give me detailed information (or a link where it is described) how qemu manage hw interrupts?I can't find any usefull info about it in QEMU doc.For example, how does work Interrupts for the parallel port? (I see in the code that it is the easier device to understand how qemu works
10 matches
Mail list logo
