From owner-freebsd-current@FreeBSD.ORG Mon Sep 22 20:45:02 2014 Return-Path: Delivered-To: freebsd-current@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 ESMTPS id 4876C59F; Mon, 22 Sep 2014 20:45:02 +0000 (UTC) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BCA268B; Mon, 22 Sep 2014 20:45:01 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id k48so3557548wev.28 for ; Mon, 22 Sep 2014 13:44:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=Nu1i67SOK4vjT1Tms/utpVh7gmtgbID+qzvao17JtQc=; b=Kl4c4aZMk7bkU+JY+wGfQ/YUisc+5jwiZOsr0asMuyyTZNJmNJzh6nlYnMRs6ePQg5 nekhbZviXEWEuQ28mE7htnAsclEcllK5ra5EHtiqSJ/hVG/Q75/UOnTmp2J2XSSoVcP2 7/ifO6gwjybjv0qomoyLXRJGomH+6JvUkw4FfvBhm2N0YMJTY5EK5gyZEk6o5HjoYWEj hUikhMlE20Q3f6INL8+IetHwuZKv1LddGIpYHsfj8DoN7WVP1GhTp5uOxKaaq5Dxfpbq jp2grtBWNk3mTewy2vtn1XG+p6dmHLUhOz/U/TC7xI00dwkwPoRMDCq00WrAqxH5YeLp rHJg== MIME-Version: 1.0 X-Received: by 10.180.9.144 with SMTP id z16mr17325561wia.26.1411418699734; Mon, 22 Sep 2014 13:44:59 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.199 with HTTP; Mon, 22 Sep 2014 13:44:59 -0700 (PDT) In-Reply-To: <9238703.p5asNz0dlH@ralph.baldwin.cx> References: <1815820.OytfPhNq3X@ralph.baldwin.cx> <2930763.7FbKMgYveJ@ralph.baldwin.cx> <9238703.p5asNz0dlH@ralph.baldwin.cx> Date: Mon, 22 Sep 2014 13:44:59 -0700 X-Google-Sender-Auth: vz2inGSI66oXlMecvpvpmJvRNZI Message-ID: Subject: Re: [PATCH] Various fixes to wl(4) From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current , Warner Losh , Warner Losh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2014 20:45:02 -0000 Oh yeah, I am. but wl likely hasn't been tested in a long time.. I think my last pair of wl(4) NICs disappeared in 2001. -a On 22 September 2014 13:35, John Baldwin wrote: > On Monday, September 22, 2014 12:42:34 PM Adrian Chadd wrote: >> On 22 September 2014 12:20, John Baldwin wrote: >> > On Friday, September 19, 2014 03:47:16 PM Warner Losh wrote: >> >> I got rid of my pre-802.11 WaveLAN cards about 8 years go after not >> >> having >> >> them in a system at all for 8 years. And they were about 4 years obso= lete >> >> when I took them out of service=E2=80=A6 I=E2=80=99m not even sure I = have a machine with >> >> an >> >> ISA slot to test the card, even if I still had it. >> >> >> >> Sorry I can=E2=80=99t help more :) >> > >> > If no one tests them then I will happily toss the driver into the dust= bin, >> > just giving folks a chance to test patches before I do so. (I'm secre= tly >> > hoping I can purge several old drivers during the current round of >> > timeout() purging.) >> >> The wavelan/prism driver no longer works out of the box and hasn't >> since I took over the net80211 stack. >> >> TL;DR - some changes from sam and others a few years ago to do raw >> 802.11 frame transmit just doesn't work on all the wavelan cards that >> are in use. I've asked for someone interested to go through the >> changelog and back out those changes, making the driver again a >> straight 802.3 transmit driver - but noone has. :( >> >> So yes, you have a +1 to disconnect the wavelan driver from the build. > > I think you are referring to wi(4)? > > -- > John Baldwin