Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4668 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752156AbZJWPt6 (ORCPT ); Fri, 23 Oct 2009 11:49:58 -0400 Subject: Re: [PATCH 17/19] [RFC, v2] libertas: Kconfig entry for libertas+cfg80211 From: Dan Williams To: Johannes Berg Cc: Holger Schurig , linux-wireless@vger.kernel.org, John Linville In-Reply-To: <1256307572.12174.33.camel@johannes.local> References: <20091022133043.185554096@mail.mn-solutions.de> <20091022133425.317619132@mail.mn-solutions.de> <1256307572.12174.33.camel@johannes.local> Content-Type: text/plain Date: Fri, 23 Oct 2009 08:49:55 -0700 Message-Id: <1256312995.2164.7.camel@localhost.localdomain> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, 2009-10-23 at 16:19 +0200, Johannes Berg wrote: > On Thu, 2009-10-22 at 15:31 +0200, Holger Schurig wrote: > > > +#ifdef CONFIG_LIBERTAS_WEXT > > dev->ethtool_ops = &lbs_ethtool_ops; > > dev->wireless_handlers = &lbs_handler_def; > > #endif > > So here you make the wireless_handlers optional. > > I still don't understand why you can't just replace only some of the > handlers, i.e. instead of doing this, simply do > > - (iw_handler) lbs_set_freq, /* SIOCSIWFREQ */ > + (iw_handler) cfg80211_wext_siwfreq, > > etc. > > That's why those exist and are exported. And that way you don't need the > Kconfig at all, and can remove most of the wext code. I *think* because Holger is trying to keep WEXT around for a bit, because cfg80211 won't be mature enough yet (IMHO, I could be wrong) by 2.6.33, and because it doesn't support the OLPC-style mesh stuff and the libertas monitor interface code. There's a few loose-ends that need to be tied up before a cfg80211 conversion would completely replace the functionality of the WEXT code. Dan