From: Jeff Garzik <jgarzik@pobox.com>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>,
Netdev <netdev@oss.sgi.com>,
hostap@shmoo.com, prism54-devel@prism54.org,
Jean Tourrilhes <jt@bougret.hpl.hp.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Prism54 WPA Support - wpa_supplicant - Linux general wpa support
Date: Thu, 03 Jun 2004 00:06:35 -0400 [thread overview]
Message-ID: <40BEA3CB.60908@pobox.com> (raw)
In-Reply-To: <20040602132313.GB7341@jm.kir.nu>
Jouni Malinen wrote:
> The first thing I would like to see is an addition to Linux wireless
> extensions for WPA/WPA2 so that we can get rid of the private ioctls in
> the drivers. Even though these can often be similar, it would be nice to
> just write one driver interface code in wpa_supplicant and have it
> working with all Linu drivers.. I hope to find some time to write a
> proposal for this.
One of the things that is nice about wireless-2.6 is that is affords the
opportunity to totally rethink the wireless extensions.
Although a lot of people would howl, since HostAP is essentially new
code from the mainline kernel perspective, a new userland API (and new
or updated tools) could come along with it.
I have mentioned in the past (no offense Jean!) that I do not like the
overly-generic wireless handler structure. It is less type-safe than is
generally preferred in Linux, IMO.
A low-level wireless driver should not implement ioctls, it should
implement callbacks in some sort of 'struct wireless_operations' as is
done in other kernel subsystems.
ioctl details should be hidden from low-level drivers as much as
possible, through type-safe interfaces. Strive to make both the
wireless driver API and the wireless userland API easy to change and
evolve over time.
Jeff
next prev parent reply other threads:[~2004-06-03 4:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 7:14 Prism54 WPA Support - wpa_supplicant - Linux general wpa support Luis R. Rodriguez
2004-06-02 13:23 ` Jouni Malinen
2004-06-02 15:55 ` Luis R. Rodriguez
2004-06-03 1:40 ` Jouni Malinen
2004-06-03 2:38 ` Pedro Ramalhais
2004-06-03 3:44 ` Jouni Malinen
2004-06-03 11:05 ` Bradley Chapman
2004-06-03 16:52 ` Jean Tourrilhes
2004-06-04 2:33 ` Jouni Malinen
2004-06-04 18:01 ` Jean Tourrilhes
2004-06-03 4:06 ` Jeff Garzik [this message]
2004-06-03 17:07 ` Jean Tourrilhes
2004-06-02 16:28 ` Sam Leffler
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=40BEA3CB.60908@pobox.com \
--to=jgarzik@pobox.com \
--cc=hostap@shmoo.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@bougret.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@studorgs.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).