Return-path: Received: from charlotte.tuxdriver.com ([70.61.120.58]:52744 "EHLO smtp.tuxdriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932187Ab1FJUQ1 (ORCPT ); Fri, 10 Jun 2011 16:16:27 -0400 Date: Fri, 10 Jun 2011 16:09:01 -0400 From: "John W. Linville" To: hedwin Cc: "Luis R. Rodriguez" , linux-wireless Subject: Re: Support for Android for mac80211 / cfg80211 802.11 drivers Message-ID: <20110610200900.GE2665@tuxdriver.com> (sfid-20110610_221630_688617_B7D095D2) References: <1296633772.3624.2.camel@jlt3.sipsolutions.net> <20110202113052.GA14126@jm.kir.nu> <1296646434.5671.1.camel@jlt3.sipsolutions.net> <20110202133839.GA14904@jm.kir.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Jun 10, 2011 at 10:07:09PM +0200, hedwin wrote: > If it needs to be part of AOSP then it will be a problem. > If not it entirely depends on those maintaining the specific android "distro". > Some follow the google policy others don't. nl80211 doesn't require libnl -- Google will simply have to implement their own replacement. Their apparentl (L)GPL allergy has already led them to do so for the other system components, so why should they stop now? In any case, it is Google's problem to solve. John -- John W. Linville Someday the world will need a hero, and you linville@tuxdriver.com might be all we have. Be ready.