Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751476AbaLaPCa (ORCPT ); Wed, 31 Dec 2014 10:02:30 -0500 Received: from mail-gw2-out.broadcom.com ([216.31.210.63]:23343 "EHLO mail-gw2-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750734AbaLaPC2 (ORCPT ); Wed, 31 Dec 2014 10:02:28 -0500 X-IronPort-AV: E=Sophos;i="5.07,673,1413270000"; d="scan'208";a="53970388" Message-ID: <54A41000.3040306@broadcom.com> Date: Wed, 31 Dec 2014 16:02:24 +0100 From: Arend van Spriel User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.24) Gecko/20111103 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: Jiri Kosina CC: "Grumbach, Emmanuel" , Linus Torvalds , Borislav Petkov , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "egrumbach@gmail.com" , "peter@hurleysoftware.com" , "ilw@linux.intel.com" , "Berg, Johannes" , Larry Finger Subject: Re: [PATCH] Revert "cfg80211: make WEXT compatibility unselectable" References: <54A2B807.1020202@hurleysoftware.com> <0BA3FCBA62E2DC44AF3030971E174FB31B5DC915@hasmsx107.ger.corp.intel.com> <1419971304.30412.0.camel@egrumbacBox> <20141230212326.GA29263@pd.tnic> <54A328C2.5080606@lwfinger.net> <54A3D955.6020809@broadcom.com> <0BA3FCBA62E2DC44AF3030971E174FB31B5DD72E@hasmsx107.ger.corp.intel.com> <54A3E1F1.7030807@broadcom.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/31/14 15:07, Jiri Kosina wrote: > On Wed, 31 Dec 2014, Arend van Spriel wrote: > >> The thing with WEXT is that it will stay as is. So if tools like wicd >> want to support new features like P2P it will need to make the switch. I >> checked out wicd repo and found a number of iwconfig calls and they kick >> off wpa_supplicant with wext driver. > > Unfortunately this is by no means just about wicd. I have already received > a few off-list mails from people who were wondering why their home-made > scripts / tools, which are running 'iwconfig' directly suddenly stopped to > work, and that it was indeed fallout of WEXT going away. Given the very > short time this has been in mainline, you can probably imagine the > fireworks once this appears in major release. It is unfortunately indeed. I think iwconfig and friends will never go away although iw is a better alternative, simply because people don't like to change their home-made scripts/tools. WIRELESS_EXT actually is largely, but not entirely, gone in upstream drivers and what we are talking about here is CFG80211_WEXT which allows WEXT userspace to interact with cfg80211-based drivers through a compatibility layer. Regards, Arend -- 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/