From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Pavel Roskin <proski@gnu.org>, Netdev <netdev@oss.sgi.com>
Subject: Re: linux-wireless mailing list
Date: Wed, 10 Mar 2004 15:53:41 -0800 [thread overview]
Message-ID: <20040310235341.GA16621@bougret.hpl.hp.com> (raw)
In-Reply-To: <404F5DAC.4020807@pobox.com>
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
next prev parent reply other threads:[~2004-03-10 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0403031656090.22365@marabou.research.att.com>
2004-03-04 3:08 ` linux-wireless mailing list Jeff Garzik
2004-03-04 17:34 ` Jean Tourrilhes
2004-03-05 4:03 ` Jean Tourrilhes
2004-03-10 17:46 ` Jeff Garzik
2004-03-10 18:06 ` Jean Tourrilhes
2004-03-10 18:25 ` Jeff Garzik
2004-03-10 23:53 ` Jean Tourrilhes [this message]
2004-03-12 0:12 ` Jean Tourrilhes
[not found] ` <20040303233343.GA14803@bougret.hpl.hp.com>
2004-03-04 7:08 ` Pavel Roskin
2004-03-05 4:08 ` Jouni Malinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040310235341.GA16621@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
--cc=proski@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).