All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
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, 02 Feb 2011 12:33:54 +0100	[thread overview]
Message-ID: <1296646434.5671.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20110202113052.GA14126@jm.kir.nu>

On Wed, 2011-02-02 at 13:30 +0200, Jouni Malinen wrote:

> > 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.

What's the driver_cmd things they use? If we they add support for
whatever it is to nl80211, why can those not be normal supplicant
interfaces?

> 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..

Indeed -- no way. Seems Android needs to learn upstream.

johannes


  reply	other threads:[~2011-02-02 11:33 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
2011-02-02 11:33           ` Johannes Berg [this message]
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=1296646434.5671.1.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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=j@w1.fi \
    --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.