From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 82DCF1A704 for ; Wed, 11 Oct 2023 09:01:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arndb.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=arndb.de header.i=@arndb.de header.b="cGAQWZnu"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="mkiW3Emb" Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 74E315C0286; Wed, 11 Oct 2023 05:01:47 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute5.internal (MEProxy); Wed, 11 Oct 2023 05:01:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1697014907; x=1697101307; bh=DE xhJxe6pAvV5eiD/1fwWplvOVteEj7vs73QB2WI/+8=; b=cGAQWZnu0g1DKpMsdQ nwOEGFS/BLPM92HbcGgu7MQ9JHtP6bD0YjbJ+0sKHLKR5nnPPTQMEZFeaJtqSfTT CT6t5BfH67Mk5GjgXaSeJfZUbcqy93H/bgS6uuEiOYd2b1oAKhwI+iRmHvhS0CDa Bpdho81qZDtTuMK8n639b6GK8U1OujeOqf/wLkxj7I9SfWI4D7TgmzzYdil0fxX/ je/43bHzgJROy6ZELUx8czqbM0fhpcqhRK2L7n9WXsd5qHs7/K/havp3dfvryYT2 fAKctxjk6Fkp6FSLGceZ7mYO94VKDqRGAqlPqcWZ+D4FIxQclNkNNRjbIZ5pYY5j s6jw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1697014907; x=1697101307; bh=DExhJxe6pAvV5 eiD/1fwWplvOVteEj7vs73QB2WI/+8=; b=mkiW3Emb3vdKnJhx8bwy1ZihSQQq5 weJSue0zdVPKOYp+zbo07jpwpfsgdMXsXTL1G5GiO8FdIYYycdkfVJl6823/uvJL DmGZSrI9W4BxVKbwuWKHcmu6jfbY7VIqvGOOyya5XmkRLL+A3Z+KYer5/4p05hga dTqUXWAfICNO4a2UBjF/UKeGiXOSQMG13/lFoCbjlCdRF6mkpBVe64CIsMAUwJre /NvHX6+RvX5k08u6UD9HuXfqNs2dYU0lpKyI5me4gldF7a9EdjHyLw8nj8shaPkN l4005mZh+rO6o9hr24wTV2rC4VpCLZFZBWwQd8VZ49kKhppmoXKFVmTGQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrheekgddtkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdetrhhn ugcuuegvrhhgmhgrnhhnfdcuoegrrhhnugesrghrnhgusgdruggvqeenucggtffrrghtth gvrhhnpeejvddvvdduleduheejiedtheehiedvjefgleelffeigfevhffhueduhfegfeef heenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomheprghrnhgusegrrhhnuggsrdguvg X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1EC58B60089; Wed, 11 Oct 2023 05:01:46 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1019-ged83ad8595-fm-20231002.001-ged83ad85 Precedence: bulk X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-Id: In-Reply-To: <87r0m14khb.fsf@kernel.org> References: <20231010155444.858483-1-arnd@kernel.org> <2023101051-unmasked-cleaver-79b3@gregkh> <87y1g94szz.fsf@kernel.org> <87r0m14khb.fsf@kernel.org> Date: Wed, 11 Oct 2023 11:01:25 +0200 From: "Arnd Bergmann" To: "Kalle Valo" Cc: "Greg Kroah-Hartman" , "Arnd Bergmann" , "Alexandre Belloni" , linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev, linux-wireless@vger.kernel.org, "Claudiu Beznea" , "Pavel Machek" , "Jakub Kicinski" , "David S . Miller" , linux-arm-kernel@lists.infradead.org, "Larry Finger" Subject: Re: [PATCH] [RFC] wireless: move obsolete drivers to staging Content-Type: text/plain On Wed, Oct 11, 2023, at 10:44, Kalle Valo wrote: > "Arnd Bergmann" writes: >> On Wed, Oct 11, 2023, at 07:40, Kalle Valo wrote: >>> Greg Kroah-Hartman writes: >>> >>> We (the wireless folks) have been talking about dropping legacy drivers >>> on and off for several years now. The problem is that we don't know >>> which of them work and which not, for example IIRC someone reported >>> recently that wl3501 still works. >>> >>> Personally I would be extremly happy to remove all the ancient drivers >>> as that reduces the amount of code for us to maintain but is that the >>> right thing to do for the users? I don't have an answer to that, >>> comments very welcome. >> >> I had a look at what openwrt enables, to see if any of the drivers >> in my RFC patch are actually enabled, if anything supports legacy >> embedded devices with these it would be openwrt. The good news here >> is that openwrt intentionally leaves WEXT disabled, and none of them >> are still in use. > > I don't think openwrt is a good metric in this case. These drivers are > for 20+ years old hardware, most likely running on really old x86 > laptops. So the chances of them running openwrt on those laptops is low > and I would expect them to run more traditional distros like debian or > ubuntu. But of course this is just guessing. OpenWRT is clearly not a good metric for laptops, but it's a good indicator for embedded systems, in particular those with wireless access points, and it does enable a lot of them (atheros, broadcom, intel, marvell, ralink, realtek, mt76, wlcore, rsi ...) depending on the platform. I can also see that it used to enable airo, p54, hermes, adm8211, zd1211, ipw2x00 and libertas but stopped this a year ago, see https://github.com/openwrt/openwrt/commit/a06e023b4e12 Arnd