From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 29 04:40:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F27F59C3; Mon, 29 Jul 2013 04:40:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3CEE62A86; Mon, 29 Jul 2013 04:40:25 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id f14so600988wiw.3 for ; Sun, 28 Jul 2013 21:40:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=2vvqr2NiFTiqVt1JWq1ncIE+Ne73IcMyTc8GfYbPfCU=; b=s31UZgekWg24oe2aeZgis66RiNL8viJ2N0Vxm5kSiZrdEuoVXsv6tQWNagRFkvLhWW GAwVheChB7Z8GJhiaflscqv3sZuTIJVsG6ftfPZcMrXP45Pk1WRuvuolVi+6U9IOGXOj VRg5NjBpppJCY3508w/TGIhAY6N+Z1OVLVmClwezVfS43hCYA5+4K3TnblAYs/UaTNot J4QGMDXl20cglW6z18EjqZNv0KqR8pWPGJTXcn5gqfjX8fqd799j7qPjLfDbpTa+aT0t cP2/4+BpttpXqRN7w4xZe/iutN14qVput4Xc6w81qlHIChAADnH2F5sQwWAJbH/lTvvz xUBQ== MIME-Version: 1.0 X-Received: by 10.194.11.72 with SMTP id o8mr42571859wjb.0.1375072823509; Sun, 28 Jul 2013 21:40:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Sun, 28 Jul 2013 21:40:23 -0700 (PDT) Date: Sun, 28 Jul 2013 21:40:23 -0700 X-Google-Sender-Auth: GXrvc5pnyluPxdyVBexn0hD1whE Message-ID: Subject: [rfc] I'm going to nuke wi(4) (lucent/orinoco wireless PCMCIA devices) in a week's time unless someone steps up to look after it From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Net , freebsd-current X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2013 04:40:26 -0000 Hi all, I have some reasonably drastic net80211 stack changes planned over the next few months which require some driver work to make happen. The specific big change is to call net80211 for each mbuf transmit completion so it can kick-start the next transmit from a software staging queue. Since this has to happen outside of any driver lock context, it can get a bit hairy. I'm going to do it for the following NICs as I have enough hardware to cover them: * ath (obviously) * iwn * wpi * ipw, if I can find the 2200 series NIC * iwi - same deal, if I can find the hardware * mwl If I can find a bwi and bwn NIC that works enough for basic traffic testing, I'll also do those NICs. There's a reasonably active group of people who (especially using USB wifi NICs) that I plan on enlisting to help me test those drivers. However, I can't test wi - the lucent/orinoco driver. Some changes were made a few years ago that changed the encapsulation frame format from 802.3 to 802.11 and this only seems to work on a very narrow, specific set of NICs and firmware. I have a _big_ collection of wi hardware and _I_ can't get it to work. I started hacking on it in 2011 and quickly realised that although I could likely back out the 802.3 -> 802.11 encapsulation changes so things work with a wider variety of NICs, I don't really want to. So, I'm going to disconnect wi(4) from the build in a week's time and shortly after I'm going to nuke it from the repository. As far as I'm aware no-one has actively used it in a number of years. Now - if someone wants to step up and claim ownership of the driver - then fix it to go _back_ to the 802.3 frame format and then make it work again, I'll be very happy. Sorry. I'd love to claim we still support wi(4) but the truth is that it's been broken since before I became wireless maintainer and it doesn't look like it's ever going to get better. Thanks, -adrian