<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META content="MSHTML 5.50.4930.1700" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=944564916-28012004><FONT face=Tahoma size=2>Hi
all,</FONT></SPAN></DIV>
<DIV><SPAN class=944564916-28012004><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=944564916-28012004><FONT face=Tahoma size=2>It is a little
vague to me why some of the iwpriv commands are handled via do_ioctl() and
others are handled in the by separate iwpriv set/get routines in the
driver. For example, iwpriv commands such as monitor, wd_add and kickmac
are all handled by the do_ioctl() handler in the driver, but other iwpriv
commands such as get/set beacon interval are registered and handled in via their
own routines (e.g. prism2_ioctl_priv_get_prism2_param() and
prism2_ioctl_priv_prism2_param()). What is the reason for this
partitioning? It looks to me as though the private commands handled by the
do_ioctl() handler (e.g. hostap_ioctl()) are specific commands to perform an
action (such as kicking a mac or adding one to the acl list), where the ones
handled by the set/get routines specifically operate on variables. If
somebody can confirm my assumption, or correct it, that would be
great.</FONT></SPAN></DIV>
<DIV><SPAN class=944564916-28012004><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=944564916-28012004><FONT face=Tahoma
size=2>Thanks!<BR>Adam</FONT></SPAN></DIV></BODY></HTML>