From: Craig Hollabaugh <craig@hollabaugh.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: RE: How?
Date: 15 May 2003 08:03:48 -0600 [thread overview]
Message-ID: <1053007429.481.6.camel@ch> (raw)
Rakesh,
Your interrupt routine can send a signal to your user space process.
Here's what I've used
void sendSignal(void)
{
struct task_struct *p;
if ( pid ) {
/*
for_each_task(p) {
if (p->pid == pid) {
send_sig(SIGIO,p,1);
break;
}
}
*/
/* or better yet */
if (p = find_task_by_pid(pid)) send_sig(SIGIO,p,1);
/* from page 83 in ulk */
}
}
ulk is Understanding The Linux Kernel.
Craig
--
___________________________________________________________
Dr. Craig Hollabaugh craig@hollabaugh.com
Author of Embedded Linux
P.O. Box 1405
Ouray, CO 81427-1405 See my "kitchen sink" resume at
970 325 4810 home www.hollabaugh.com/resume.html
970 325 0509 office
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-15 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 14:03 Craig Hollabaugh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 5:07 How ? Rakesh Jagota
2003-05-15 13:31 ` Bret Indrelee
2003-05-15 13:35 ` Wolfgang Denk
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=1053007429.481.6.camel@ch \
--to=craig@hollabaugh.com \
--cc=linuxppc-embedded@lists.linuxppc.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).