From owner-freebsd-wireless@freebsd.org Thu Apr 18 15:03:15 2019 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1104C1573EB4 for ; Thu, 18 Apr 2019 15:03:15 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB4F66B154; Thu, 18 Apr 2019 15:03:14 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 9ABFD7C80; Thu, 18 Apr 2019 15:03:14 +0000 (UTC) Date: Thu, 18 Apr 2019 15:03:14 +0000 From: Alexey Dokuchaev To: Adrian Chadd Cc: Matthias Apitz , "freebsd-wireless@freebsd.org" Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD Message-ID: <20190418150314.GA588@FreeBSD.org> References: <20190415044836.GA2635@c720-r342378> <20190415122652.GA22516@FreeBSD.org> <20190415125217.GA3992@c720-r342378> <20190415173503.GA93707@FreeBSD.org> <20190416103412.GA4582@c720-r342378> <20190417143551.GA78014@FreeBSD.org> <20190417165753.GA12433@sh4-5.1blu.de> <20190418145002.GA7750@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: AB4F66B154 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.93 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; TAGGED_RCPT(0.00)[]; NEURAL_HAM_SHORT(-0.94)[-0.938,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 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, 18 Apr 2019 15:03:15 -0000 On Thu, Apr 18, 2019 at 07:58:34AM -0700, Adrian Chadd wrote: > Ok, so it found and loaded in the bluetooth firmware into the > bluetooth NIC RAM. Why do you think so? > On Thu, 18 Apr 2019 at 07:50, Matthias Apitz wrote: > > > > I have booted the other C720 from USB and here are the results: > > > > # ./ath3kfw -D -d ugen0.4 -I > > ath3kfw: opening dev 0.4 > > ath3k_is_3012: found AR3012 > > main: AR3012; bcdDevice=2, exiting /* See if its an AR3012 */ if (ath3k_is_3012(&d)) { is_3012 = 1; /* If it's bcdDevice > 1, don't attach */ if (d.bcdDevice > 0x0001) { ath3k_debug("%s: AR3012; bcdDevice=%d, exiting\n", __func__, d.bcdDevice); exit(0); } } It looks to me it never reached the stage of loading the firmware because of bcdDevice=2. ./danfe