From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 18 15:41:19 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 ESMTPS id 671F43D2 for ; Wed, 18 Dec 2013 15:41:19 +0000 (UTC) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 25076189F for ; Wed, 18 Dec 2013 15:41:19 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id e16so6290541qcx.3 for ; Wed, 18 Dec 2013 07:41:18 -0800 (PST) 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; bh=jbY7x4dwXu5fYN92TiQ6XS+dZY92kmJySCQGhoVmLIc=; b=Hm176hiDO3nc4IAdFoz/TH+wuZanOI94Cy64bTt4pjHe/kurv/biX7tk68I60IkgiB xMvvwlrDgv7C33rTPU173KxcY/nOGCmeBDRCrvZAlA1RFHgYBslbkVSAUOFF6oSmPj7R T5qKzeqP1TYgmIcqylyVi21EN41vR2OywwxkxvFwc00JIJZFIsw8SIPftNVEo+PvztFw ZfsS7jKAeTGaUkdIKtlmpNS/65W+iUCBauqk80ZfQ3/l5TpCD4RR713ebRZ7DDfW6K/h YVK0k0g9hXOcPjH41vZ7dGIpg1DbK7HdWSelkw736NxowAd19lg+KRUp4rAWUk42guy0 cfhA== MIME-Version: 1.0 X-Received: by 10.224.5.69 with SMTP id 5mr54837330qau.95.1387381278224; Wed, 18 Dec 2013 07:41:18 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Wed, 18 Dec 2013 07:41:17 -0800 (PST) In-Reply-To: <610753.22725.bm@smtp119.sbc.mail.ne1.yahoo.com> References: <597989.6329.bm@smtp118.sbc.mail.bf1.yahoo.com> <610753.22725.bm@smtp119.sbc.mail.ne1.yahoo.com> Date: Wed, 18 Dec 2013 07:41:17 -0800 X-Google-Sender-Auth: M8lih4aFQnvYbJR9cnOiZwFJ4Sc Message-ID: Subject: Re: Atheros 9271 From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 18 Dec 2013 15:41:19 -0000 I just don't want to be on the hook for supporting the USB side of things. I've been slowly writing an AR9170 USB driver. I am still having issues getting all of the USB stuff stable and bulletproof. The existing USB drivers for wifi aren't really paragons of virtue from a driver perspective. -a On 18 December 2013 01:26, Thomas Mueller wrote: > from Adrian Chadd: > >> THe bit(s) i don't want to really make work mostly involve the USB >> stuff. So, if you grab the USB drivers in sys/dev/usb/wlan/ and look >> at the netbsd/openbsd athn usb code, that right there is what would be >> good to start with. > >> So, if you or someone could port the initial USB glue - attach, >> detach, upload firmware, send commands, receive commands - that'll be >> a big help. > > Now you make me curious why you don't want to work on the USB stuff: > you may have a good reason, but I'm still curious. > > I can look through the source code even when not running NetBSD. > > NetBSD is much less stable than FreeBSD on my hardware. OpenBSD may > possibly be stabler than NetBSD but is more crippled for lack of support > for GPT and USB 3.0, meaning my running of OpenBSD is limited to live USB > from liveusb-openbsd.sourceforge.net : plenty of space on sparsely > occupied 16 GB USB 2.0 stick, but X and GNOME 3.8.3 don't start. This is > the latest version, with OpenBSD 5.4. > > Earlier I had a kernel crash on FreeBSD 10-stable amd64, from just before RC1 > release, preceded by trouble messages from dhclient in connection with rsu. > "make buildworld" with TARGET=i386 went through successfully about 25 minutes > before the crash, and subsequently I completed the build and installation of > FreeBSD 10-stable i386 on 32 GB USB 3.0 stick. I posted a message about that > kernel crash on freebsd-stable list, suspect instability in rsu driver, but > evidence is not conclusive. I could try to improve by > set hint.re.0.disabled="1" > at loader prompt to keep the failing re0 out of the way. I once did that, and > re0 was conspicuous by its absence from /var/run/dmesg.boot and from the output > of running "ifconfig" without parameters. > > Tom >