From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bob Copeland <me@bobcopeland.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org, Amod Bodas <Amod.Bodas@atheros.com>,
Senthilkumar Balasubramanian
<Senthilkumar.Balasubramanian@atheros.com>,
Sree Durbha <Sree.Durbha@atheros.com>,
Deepak Dhamdhere <Deepak.Dhamdhere@atheros.com>,
Xin Jin <Xin.Jin@atheros.com>
Subject: Re: Support for Android for mac80211 / cfg80211 802.11 drivers
Date: Wed, 2 Feb 2011 13:30:52 +0200 [thread overview]
Message-ID: <20110202113052.GA14126@jm.kir.nu> (raw)
In-Reply-To: <1296633772.3624.2.camel@jlt3.sipsolutions.net>
On Wed, Feb 02, 2011 at 09:02:52AM +0100, Johannes Berg wrote:
> On Tue, 2011-02-01 at 21:41 -0500, Bob Copeland wrote:
> > From the wiki:
> >
> > "The proper approach would be to provide a custom driver_nl80211_android.c
> > wrapper for the modified wpa_supplicant in Android."
> >
> > I just don't think it's strictly necessary to ship a modified wpa_s.
> > Why is Android special when bog standard Linux gets by ok with
> > driver_nl80211?
>
> Agree, that is a dumb idea. What's that driver going to do? Use custom
> nl80211 extensions?! That way lies insanity.
The only reason for that is to be able to support the wpa_supplicant
modifications used in Android that are not acceptable for upstream
hostap.git (mainly, driver_cmd). This would not add any custom nl80211
extensions; the needed functionality should be added properly to
upstream nl80211.
If it is fine to remove the custom wpa_supplicant modifications from
Android, this is obviously a moot point, but until that happens, the
easiest approach seems to be to provide a custom driver_*.c based on
nl80211 to isolate the custom changes to user space and to small part of
it at that. I don't really want to see new drivers trying to provide
WEXT support with private ioctls to address need for making it work with
Android..
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2011-02-02 11:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 23:29 Support for Android for mac80211 / cfg80211 802.11 drivers Luis R. Rodriguez
2011-02-02 0:45 ` Bob Copeland
2011-02-02 0:50 ` Luis R. Rodriguez
2011-02-02 2:41 ` Bob Copeland
2011-02-02 8:02 ` Johannes Berg
2011-02-02 11:30 ` Jouni Malinen [this message]
2011-02-02 11:33 ` Johannes Berg
2011-02-02 13:38 ` Jouni Malinen
2011-02-02 16:37 ` Luis R. Rodriguez
2011-06-10 19:28 ` hedwin
2011-06-10 19:37 ` Luis R. Rodriguez
2011-06-10 20:07 ` hedwin
2011-06-10 20:09 ` John W. Linville
2011-06-10 20:25 ` hedwin
2011-06-12 17:18 ` Jouni Malinen
2011-06-10 20:15 ` hedwin
2011-02-02 11:57 ` Bob Copeland
2011-02-02 12:03 ` Johannes Berg
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=20110202113052.GA14126@jm.kir.nu \
--to=j@w1.fi \
--cc=Amod.Bodas@atheros.com \
--cc=Deepak.Dhamdhere@atheros.com \
--cc=Senthilkumar.Balasubramanian@atheros.com \
--cc=Sree.Durbha@atheros.com \
--cc=Xin.Jin@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.