RE: ioctl call for network device

2001-05-08 Thread Richard B. Johnson
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

RE: ioctl call for network device

2001-05-08 Thread Hen, Shmulik
> 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

Re: ioctl call for network device

2001-05-02 Thread Richard B. Johnson
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

Re: ioctl call for network device

2001-05-02 Thread Alan Cox
> 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[]

Re: ioctl call for network device

2001-05-02 Thread sébastien person
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 other > Linux version. yes but I use an network device specific ioc