On Tue, 8 May 2001, Hen, Shmulik wrote:
> > struct ifreq has a member called ifr_data. It is a pointer. You can
> > put a pointer to any of your data, including the most complex structure
> > you might envision, in that area. This allows you to pass anything
> > to and from your module. This poin
> struct ifreq has a member called ifr_data. It is a pointer. You can
> put a pointer to any of your data, including the most complex structure
> you might envision, in that area. This allows you to pass anything
> to and from your module. This pointer can be properly dereferenced
> in kernel spac
On Wed, 2 May 2001, [ISO-8859-1] sébastien person wrote:
> Le Wed, 2 May 2001 13:55:34 +0200
> Ofer Fryman <[EMAIL PROTECTED]> à écrit :
>
> > The definition of ioctl is "extern int __ioctl __P ((int __fd, unsigned long
> > int __request, ...));" on Linux 2.0.x, and I believe it is also on any
> but I believe that I'm oblige to use the struct ifreq and I can't
> pass any other arguments because an user can't acces kernel space
> so the ioctl call recopy data in the kernel space (this is what I've
> understood, maybe I'm wrong ...).
You can either pass your own data inside of ifr_data[]
rectly from the kernel mode
> with the restriction of interrupt handlers and bottom-halfs.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 10:08 AM
> To: liste noyau linux
> Subject: ioctl call for network devic
Hi,
I've succeed to do an ioctl call and recept it in my module
ioctl(file_descriptor, cmd, struct ifreq)
but I believe that I'm oblige to use the struct ifreq and I can't
pass any other arguments because an user can't acces kernel space
so the ioctl call recopy data in the kernel space (this i
6 matches
Mail list logo
