From: "Frank Ch. Eigler" <fche@redhat.com>
To: Partha Palit <chessrook2001@yahoo.com>
Cc: sid@sources.redhat.com
Subject: Re: how to generate external interrupts
Date: Tue, 24 Jun 2003 16:18:00 -0000 [thread overview]
Message-ID: <20030624154839.GB1520@redhat.com> (raw)
In-Reply-To: <20030623211200.20420.qmail@web12903.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Hi -
> [...] I have a very basic question regarding interrupts.I
> was wondering how to simulate an external interrupt in
> SID? Can we use some script/program to continuously
> generate interrupts ? Or do I have to use the system
> monitor GUI.
All of these are possible. Scripts, GUIs, glue components
intercepting memory accesses are all ways of triggering sid pin
signals for a simulated interrupt controller. How would you
prefer to cause interrupts?
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-24 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 21:17 error building SID Partha Palit
2003-06-20 21:31 ` Frank Ch. Eigler
[not found] ` <20030623211200.20420.qmail@web12903.mail.yahoo.com>
2003-06-24 16:18 ` Frank Ch. Eigler [this message]
2003-06-24 19:01 ` how to generate external interrupts Partha Palit
2003-06-24 20:26 ` Frank Ch. Eigler
2003-06-26 22:47 ` Partha Palit
2003-06-27 2:33 ` Frank Ch. Eigler
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=20030624154839.GB1520@redhat.com \
--to=fche@redhat.com \
--cc=chessrook2001@yahoo.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).