I'd like to tie the user and kernel parts together more tightly than using ioctls if possible. If I have to use ioctl, though, I will. How do I get a file descriptor to my device? It's a network driver, not a char driver, so there's no /dev/foo entry. -Steve -----Original Message----- From: Felipe W Damasio [mailto:felipewd@terra.com.br] Sent: Friday, August 23, 2002 9:43 AM To: LUSTBADER,STEVE (Non-A-hsgAndover,ex1) Cc: kernelnewbies@nl.linux.org Subject: Re: Kernel module <-> user communication On Fri, 23 Aug 2002 10:21:15 -0600 "LUSTBADER,STEVE (Non-A-hsgAndover,ex1)" <steve_lustbader@hsgmed.com> wrote: L> I'm trying to write a kernel network driver but I don't know how to L> access it from a kernel space program. I'd like to "export" a function L> from the driver that a user space program could call, but I'm not sure L> if that's possible. For example, I'd like to be able to call L> "do_something(args)" from a user space program that would make the L> driver perform an action (writing to a device register, etc). This is L> a very specialized device, so the user space program could/will be tied L> very tightly to the driver. Check Dave Miller's ethtool program. You can do the same thing: Adding a bunch of ioctls to communicate between user-space and you driver functions. Felipe -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
