From: "Sampath Kumar" <sampath@spartanlabs.com>
To: "Juergen Oberhofer" <e9826367@student.tuwien.ac.at>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc / linux kernel - user space
Date: Fri, 28 Nov 2003 11:04:09 +0530 [thread overview]
Message-ID: <006801c3b571$408bc6e0$c314a8c0@cm> (raw)
In-Reply-To: Pine.GHP.4.58.0311271703390.25225@stud3.tuwien.ac.at
Hi,
Write an ioctl method in your module. And provide provision in ioctl to take
a function pointer & store it.
Whenever there is an timer interrupt, check for this pointer, if not NULL ,
then you can call the function. When your application comes up, makesure u
pass the command to ioctl of your module with the function pointer as arg.
Hope this help !
Regards
Sampath
----- Original Message -----
From: Juergen Oberhofer <e9826367@student.tuwien.ac.at>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, November 27, 2003 9:37 PM
Subject: mpc / linux kernel - user space
>
> Hi,
>
> I have a module and an application program in user space:
>
> The Module performs the following task: at init it initializes the cpm
> timer register of the mpc823,
> such that an interrupt is generated every x microseconds. Thus, I
> installed an interrupt handling function f that handles the timer
> interrupts.
>
> My problem is that the module / the interrupt handling function should
> execute a procedure defined in the application program. How can I pass a
> pointer (which points to that function) from the appl.program to the
> module, such that the handler can execute this function every x
> milliseconds? I thought to create a procedure in the module that accepts
> a function pointer as argument. But how can I achieve, that this module
> procedure is visible to the application program? Does somebody have a
> suggestion or know another way to do it?
>
> Regards,
> Juergen
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-28 5:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 16:07 mpc / linux kernel - user space Juergen Oberhofer
2003-11-27 17:38 ` Jaap-Jan Boor
2003-11-27 18:08 ` Juergen Oberhofer
2003-11-27 19:28 ` Dan Kegel
2003-11-28 4:30 ` How to change /proc to the writable directory John Zhou
2003-11-28 8:12 ` Wolfgang Denk
2003-11-28 9:16 ` mpc / linux kernel - user space Jaap-Jan Boor
2003-11-28 15:42 ` Dan Malek
2003-12-01 8:18 ` Jaap-Jan Boor
2003-12-01 12:51 ` Peripherals Memory Mapping Kevin A. Sapp
2003-12-14 15:28 ` Paul Miller
2003-12-01 13:47 ` mpc / linux kernel - user space Juergen Oberhofer
2003-11-28 5:34 ` Sampath Kumar [this message]
2003-11-28 8:14 ` 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='006801c3b571$408bc6e0$c314a8c0@cm' \
--to=sampath@spartanlabs.com \
--cc=e9826367@student.tuwien.ac.at \
--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).