netdev
[Top] [All Lists]

Re: linux-wireless mailing list

To: Jeff Garzik <jgarzik@xxxxxxxxx>
Subject: Re: linux-wireless mailing list
From: Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>
Date: Wed, 10 Mar 2004 15:53:41 -0800
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
Cc: Pavel Roskin <proski@xxxxxxx>, Netdev <netdev@xxxxxxxxxxx>
E-mail: jt@xxxxxxxxxx
In-reply-to: <404F5DAC.4020807@xxxxxxxxx>
Organisation: HP Labs Palo Alto
References: <Pine.LNX.4.58.0403031656090.22365@xxxxxxxxxxxxxxxxxxxxxxxx> <40469DA1.9090502@xxxxxxxxx> <20040305040352.GA16669@xxxxxxxxxxxxxxxxxx> <404F5461.80000@xxxxxxxxx> <20040310180602.GB9531@xxxxxxxxxxxxxxxxxx> <404F5DAC.4020807@xxxxxxxxx>
Reply-to: jt@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Wed, Mar 10, 2004 at 01:25:48PM -0500, Jeff Garzik wrote:
> 
> A type-specific wireless_ops is something that I definitely want to see.
> 
> It reduces code in the drivers, by increasing the amount of code that 
> can be made generic.  It's much better to, for example, have all the 
> user data (length, etc.) validate checks, and capable(CAP_xxx) security 
> checks all in one place.  And perhaps more importantly, a type-specific 
> wireless_ops makes it harder for driver writers to screw up ;-)  That's 
> an important attribute in a driver API, I've come to learn...

        You could define a set of wrapper that would convert from
iw_handler to a type specific call. This is already what is done in
the case of iwspy support ; the driver just adds in the iw_handler
table the generic spy handlers provided in wireless.c. You can check
in airo.c around line 6823.
        But honestly, I believe that there are other more urgent
things to do (such as WPA support for example).

>       Jeff

        Jean

<Prev in Thread] Current Thread [Next in Thread>