Maybe you could write a user space header that translates a nice system
call into an ioctl...
int your_syscall_wrapper( ... )
{
/* translate parameters to a format used by ioctl */
/* call your ioctl */
/* return the return value of the ioctl */
}
On Tue, 20 Nov 2001, Amit Purohit wrote:
> I am writing a kernel module.
>
> Currently the entry point to my module is a SYSTEM
> CALL.
>
> My problem is I have to compile the whole kernel each
> time I make any changes to my code. So I want to
> convert my code to a lodable module. So that I don't
> need to recompile the kernel each time.
>
> I am not sure how should I provide an entry point to
> the user processes to my module. I don't want to use
> ioctl as an entry point to my module.
>
> For Eg. My module has defined function "foo". How
> should I make this function available to the user
> process ?
>
> Thanks
> --Amit
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
> http://geocities.yahoo.com/ps/info1
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> IRC Channel: irc.openprojects.net / #kernelnewbies
> Web Page: http://www.kernelnewbies.org/
>
--
John Tyner
jtyner@cs.ucr.edu
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
IRC Channel: irc.openprojects.net / #kernelnewbies
Web Page: http://www.kernelnewbies.org/
