From owner-freebsd-wireless@freebsd.org Thu Jun 30 11:02:55 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 689F0B87F31 for ; Thu, 30 Jun 2016 11:02:55 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1AA624DA for ; Thu, 30 Jun 2016 11:02:53 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id u5UB2m4o048614; Thu, 30 Jun 2016 21:02:49 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 30 Jun 2016 21:02:48 +1000 (EST) From: Ian Smith To: freebsd-wireless@freebsd.org Subject: Re: ath (AR9280) with nanoBSD (fwd) Message-ID: <20160630210043.U11465@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 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: Thu, 30 Jun 2016 11:02:55 -0000 Sorry Felix, didn't notice you hadn't cc'd the list .. hoping you don't mind if I do, might save someone else from responding .. cheers, Ian ---------- Forwarded message ---------- Date: Thu, 30 Jun 2016 20:52:43 +1000 (EST) From: Ian Smith To: Felix Friedlander Subject: Re: ath (AR9280) with nanoBSD On Thu, 30 Jun 2016 20:28:54 +1000, Felix Friedlander wrote: > > On 30 Jun 2016, at 19:12, Ian Smith wrote: > > > > On Wed, 29 Jun 2016 11:51:40 -0700, Adrian Chadd wrote: > > > >> Hi, > >> > >> It's there, it just doesn't show up in ifconfig anymore. > >> > >> sysctl net.wlan.devices > >> > >> if you create the interface (ifconfig wlan0 create wlandev ath0) then > >> it'll show up! > > > > Just curious .. why was it considered a good idea not to have ifconfig > > show wireless interfaces? Won't this make for ongoing such confusion? > > As I understand it, it was to avoid duplication. You have to create a > wlanN interface to use a wireless device, so you would end up with > both athN and wlanN. Now ath (and every other wireless driver) don˙˙t > directly appear in ifconfig, you only have one interface. Ah, that sounds fair enough. I expect there'll be something in 11.0 release notes about that. > I believe there is a sysctl to list the hardware devices if you want. I guess that might be net.wlan.devices :) Ok, sorry for the side-track .. cheers, Ian