From: "Roger Lathrop" <ratchetr@sprynet.com>
To: qemu-devel@nongnu.org
Subject: Re:[Qemu-devel] Interrupt request info
Date: Wed, 1 Nov 2006 18:25:42 -0500 [thread overview]
Message-ID: <002e01c6fe0d$0d434460$7e00a8c0@DELL3G> (raw)
In-Reply-To: 200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net
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
next parent reply other threads:[~2006-11-01 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611011205.1gFjwA1qs3Nl3pX2@cave.mail.atl.earthlink.net>
2006-11-01 23:25 ` Roger Lathrop [this message]
2006-11-01 23:31 ` [Qemu-devel] Interrupt request info Paul Brook
2006-11-04 16:08 ` Alessandro Corradi
2006-11-06 14:39 ` Fwd: " Alessandro Corradi
2006-11-11 11:32 ` Alessandro Corradi
2006-11-12 15:46 ` Alessandro Corradi
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='002e01c6fe0d$0d434460$7e00a8c0@DELL3G' \
--to=ratchetr@sprynet.com \
--cc=qemu-devel@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).