Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753605Ab1BBIDD (ORCPT ); Wed, 2 Feb 2011 03:03:03 -0500 Received: from he.sipsolutions.net ([78.46.109.217]:45803 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753551Ab1BBIDA (ORCPT ); Wed, 2 Feb 2011 03:03:00 -0500 Subject: Re: Support for Android for mac80211 / cfg80211 802.11 drivers From: Johannes Berg To: Bob Copeland Cc: "Luis R. Rodriguez" , linux-wireless , linux-kernel@vger.kernel.org, Amod Bodas , Senthilkumar Balasubramanian , Sree Durbha , Deepak Dhamdhere , Xin Jin In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Wed, 02 Feb 2011 09:02:52 +0100 Message-ID: <1296633772.3624.2.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 28 On Tue, 2011-02-01 at 21:41 -0500, Bob Copeland wrote: > On Tue, Feb 1, 2011 at 7:50 PM, Luis R. Rodriguez wrote: > > >> I don't think it's good to advocate a custom driver. They should be able > >> to use stock wpa_supplicant w/ nl80211 and put the extensions in the > >> hardware layer. > > > > Can you elaborate? > > 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. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/