- 1. ioctl call for network device (score: 1)
- Author: sébastien person <sebastien.person@xxxxxxxxxxx
- Date: Wed, 2 May 2001 10:12:05 +0200
- 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 becau
- /archives/netdev/2001-05/msg00020.html (7,588 bytes)
- 2. Re: ioctl call for network device (score: 1)
- Author: sébastien person <sebastien.person@xxxxxxxxxxx
- Date: Wed, 2 May 2001 13:19:20 +0200
- Le Wed, 2 May 2001 13:55:34 +0200 Ofer Fryman <ofer@xxxxxxxxxxxx> à écrit : yes but I use an network device specific ioctl call wich perform interface-specific ioctl commands. the prototype of the io
- /archives/netdev/2001-05/msg00023.html (10,229 bytes)
- 3. Re: ioctl call for network device (score: 1)
- Author: "Richard B. Johnson" <root@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 May 2001 08:24:37 -0400 (EDT)
- 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 a
- /archives/netdev/2001-05/msg00028.html (10,166 bytes)
- 4. RE: ioctl call for network device (score: 1)
- Author: xxxxxx>
- Date: Tue, 8 May 2001 04:52:40 -0700
- How about a linked list ? Will the driver be able to follow the list where each node was dynamically allocated by the application ? Is there a size limit on the buffer ifr_data points to ? (AFAIK, W
- /archives/netdev/2001-05/msg00094.html (7,997 bytes)
- 5. RE: ioctl call for network device (score: 1)
- Author: xxxxxx>
- Date: Tue, 8 May 2001 08:02:51 -0400 (EDT)
- Again; This is a pointer. Your driver can dereference any valid pointer. You can't do this while holding a lock that will prevent page faults. Other than this, there are no problems. Cheers, Dick Joh
- /archives/netdev/2001-05/msg00095.html (9,324 bytes)
- 6. ioctl call for network device (score: 1)
- Author: sébastien person <sebastien.person@xxxxxxxxxxx>
- Date: Wed, 2 May 2001 10:12:05 +0200
- 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 be
- /archives/netdev/2001-05/msg00157.html (7,588 bytes)
- 7. Re: ioctl call for network device (score: 1)
- Author: sébastien person <sebastien.person@xxxxxxxxxxx>
- Date: Wed, 2 May 2001 13:19:20 +0200
- Le Wed, 2 May 2001 13:55:34 +0200 Ofer Fryman <ofer@xxxxxxxxxxxx> à écrit : yes but I use an network device specific ioctl call wich perform interface-specific ioctl commands. the prototype of the io
- /archives/netdev/2001-05/msg00160.html (10,422 bytes)
- 8. Re: ioctl call for network device (score: 1)
- Author: "Richard B. Johnson" <root@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 May 2001 08:24:37 -0400 (EDT)
- 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 a
- /archives/netdev/2001-05/msg00165.html (10,214 bytes)
- 9. RE: ioctl call for network device (score: 1)
- Author: "Hen, Shmulik" <shmulik.hen@xxxxxxxxx>
- Date: Tue, 8 May 2001 04:52:40 -0700
- How about a linked list ? Will the driver be able to follow the list where each node was dynamically allocated by the application ? Is there a size limit on the buffer ifr_data points to ? (AFAIK, W
- /archives/netdev/2001-05/msg00231.html (7,997 bytes)
- 10. RE: ioctl call for network device (score: 1)
- Author: "Richard B. Johnson" <root@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 May 2001 08:02:51 -0400 (EDT)
- Again; This is a pointer. Your driver can dereference any valid pointer. You can't do this while holding a lock that will prevent page faults. Other than this, there are no problems. Cheers, Dick Joh
- /archives/netdev/2001-05/msg00232.html (9,372 bytes)
This search system is powered by
Namazu