Re: do_ioctl of net_devce and .private entry point of iw_handler_def

<[email protected]> Fri, 5 Jan 2007 11:19:46 +0530
Newsgroups gmane.linux.linux-wlan.user
Message-ID <[email protected]>
This is a multi-part message in MIME format.

--===============0057687567==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7308D.4DFF7718"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7308D.4DFF7718
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Thanks Peachy.
we have a range 8BE0-8BEF for the private IOCTLs as mnetioned in wireless.h=
 file.
Is this range for .private entry point or .do_ioctl entry point ?? The only=
 problem is If I implement 32 IOCTLs in .do_ioctl entry point of net_device=
 structure, then will I be able to implement any IOCTLs in .private entry=
 point ??
This is confusing as iwpriv wireless extension application uses the IOCTLs=
 defined in .private entry point.
Please reply.
=20
Thanks,
Rasmit=20
=20
From: Solomon Peachy [mailto:[email protected]]
Sent: Thu 1/4/2007 7:39 PM
To: Rasmit Ranjan (WT01 - Semiconductors & Consumer Electronics)
Cc: [email protected]
Subject: Re: [lwlan-user] do_ioctl of net_devce and .private entry point of=
 iw_handler_def


On Tue, Dec 26, 2006 at 05:02:47PM +0530, [email protected] wrote:
>  I have a doubt regarding the do_ioctl entry point of net_device
>  structure and .private entry point of iw_handler_def structure. I
>  went through the wireless drivers in Linux. Some of them have
>  implemented do_ioctl entry point of net_device structure to define
>  their private IOCTLS ( from SIOCIWFIRSTPRIV to SIOCIWFIRSTPRIV+31)
>  where some drivers have used .private entry point of iw_handler_def
>  structure for the same. So are these two interfaces for private
>  IOCTLs same ?

No, they are not the same.  the '.private' entry point for IW_HANDLER is
for so-called "private wireless extensions".  linux-wlan-ng does not
implemnet anything this way; instead it uses the standard linux
ioctl handler to handle its own private ioctls, via the p80211msg
framework.

 - Solomon
--
Solomon Peachy                        [email protected]
AbsoluteValue Systems                 http://www.linux-wlan.com
721-D North Drive                     +1 (321) 259-0737  (office)
Melbourne, FL 32934                   +1 (321) 259-0286  (fax)




The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and=
 may contain proprietary, confidential or privileged information. If you=
 are not the intended recipient, you should not disseminate, distribute or=
 copy this e-mail. Please notify the sender immediately and destroy all=
 copies of this message and any attachments.=20

WARNING: Computer viruses can be transmitted via email. The recipient=
 should check this email and any attachments for the presence of viruses.=
 The company accepts no liability for any damage caused by any virus=
 transmitted by this email.
=20
www.wipro.com
------_=_NextPart_001_01C7308D.4DFF7718
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=
=3Diso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>

<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7638.1">
<TITLE>Re: [lwlan-user] do_ioctl of net_devce and .private entry point of=
 iw_handler_def</TITLE>
</HEAD>
<BODY>
<DIV id=3DidOWAReplyText19010 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>Thanks Peachy.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>we have a range 8BE0-8BEF for=
 the private=20
IOCTLs as mnetioned in wireless.h file.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>Is&nbsp;this range for .private=
 entry=20
point or .do_ioctl entry point ?? The only problem is If I implement 32=
 IOCTLs=20
in .do_ioctl entry point of net_device structure, then will I be able to=20
implement any IOCTLs in .private entry point ??</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>This is confusing as iwpriv=
 wireless=20
extension application uses the IOCTLs defined in .private entry=20
point.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>Please reply.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>Thanks,</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2>Rasmit</FONT>&nbsp;</DIV>
<DIV dir=3Dltr>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Solomon Peachy=20
[mailto:[email protected]]<BR><B>Sent:</B> Thu 1/4/2007 7:39=20
PM<BR><B>To:</B> Rasmit Ranjan (WT01 - Semiconductors &amp; Consumer=20
Electronics)<BR><B>Cc:</B>=20
[email protected]<BR><B>Subject:</B> Re: [lwlan-user]=20
do_ioctl of net_devce and .private entry point of=20
iw_handler_def<BR></FONT><BR></DIV></DIV>
<DIV id=3DidSignature43610 dir=3Dltr><FONT size=3D2>On Tue, Dec 26, 2006 at=
 05:02:47PM=20
+0530, [email protected] wrote:<BR>&gt;&nbsp; I have a doubt=
 regarding the=20
do_ioctl entry point of net_device<BR>&gt;&nbsp; structure and .private=
 entry=20
point of iw_handler_def structure. I<BR>&gt;&nbsp; went through the=
 wireless=20
drivers in Linux. Some of them have<BR>&gt;&nbsp; implemented do_ioctl=
 entry=20
point of net_device structure to define<BR>&gt;&nbsp; their private IOCTLS=
 (=20
from SIOCIWFIRSTPRIV to SIOCIWFIRSTPRIV+31)<BR>&gt;&nbsp; where some=
 drivers=20
have used .private entry point of iw_handler_def<BR>&gt;&nbsp; structure=
 for the=20
same. So are these two interfaces for private<BR>&gt;&nbsp; IOCTLs same=20
?<BR><BR>No, they are not the same.&nbsp; the '.private' entry point for=20
IW_HANDLER is<BR>for so-called "private wireless extensions".&nbsp;=20
linux-wlan-ng does not<BR>implemnet anything this way; instead it uses the=
=20
standard linux<BR>ioctl handler to handle its own private ioctls, via the=20
p80211msg<BR>framework.<BR><BR>&nbsp;- Solomon<BR>--<BR>Solomon=20
Peachy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
[email protected]<BR>AbsoluteValue=20
Systems&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<A href=
=3D"http://www.linux-wlan.com">http://www.linux-wlan.com</A><BR>721-D North=
=20
Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+1 (321) 259-0737&nbsp; (office)<BR>Melbourne, FL=20
32934&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+1 (321) 259-0286&nbsp; (fax)<BR></FONT></DIV>

</BODY>
</HTML>
<table><tr><td bgcolor=3D#ffffff><font color=3D#000000><br>
The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and=
 may contain proprietary, confidential or privileged information. If you=
 are not the intended recipient, you should not disseminate, distribute or=
 copy this e-mail. Please notify the sender immediately and destroy all=
 copies of this message and any attachments. <br>
<br>
WARNING: Computer viruses can be transmitted via email. The recipient=
 should check this email and any attachments for the presence of viruses.=
 The company accepts no liability for any damage caused by any virus=
 transmitted by this email.<br>
 <br>
www.wipro.com<br>
</font></td></tr></table>
------_=_NextPart_001_01C7308D.4DFF7718--

--===============0057687567==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Linux-wlan-user mailing list
[email protected]
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
--===============0057687567==--