From owner-freebsd-wireless@freebsd.org  Mon Apr 15 12:26:52 2019
Return-Path: <owner-freebsd-wireless@freebsd.org>
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 DC2CE15727DD
 for <freebsd-wireless@mailman.ysv.freebsd.org>;
 Mon, 15 Apr 2019 12:26:52 +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 79E1C7717D;
 Mon, 15 Apr 2019 12:26:52 +0000 (UTC)
 (envelope-from danfe@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1033)
 id 521005DC5; Mon, 15 Apr 2019 12:26:52 +0000 (UTC)
Date: Mon, 15 Apr 2019 12:26:52 +0000
From: Alexey Dokuchaev <danfe@freebsd.org>
To: Matthias Apitz <guru@unixarea.de>
Cc: Adrian Chadd <adrian.chadd@gmail.com>,
 "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject: Re: Atheros AR5B22 WLAN+Bluetooth support on FreeBSD
Message-ID: <20190415122652.GA22516@FreeBSD.org>
References: <20190411142350.GA71446@FreeBSD.org>
 <20190412171218.GA16463@FreeBSD.org>
 <20190413142006.GA59512@FreeBSD.org>
 <20190414154658.GA2589@c720-r342378>
 <CAJ-VmonqqGdCAGOK6tN22fq_3ashHCa+oD0ndfS-ZFj8aVG=cA@mail.gmail.com>
 <20190414160236.GA2980@c720-r342378>
 <CAJ-Vmoku6P1awHFXuV9bkR6ifNocWaSi86Y0a9Z9dS-vKgMsKQ@mail.gmail.com>
 <20190414163841.GA3208@c720-r342378>
 <CAJ-Vmonvko=vpbr3kSGBpS-zpeONdQHBjkqMf4gasq=CzDbRpg@mail.gmail.com>
 <20190415044836.GA2635@c720-r342378>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190415044836.GA2635@c720-r342378>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Rspamd-Queue-Id: 79E1C7717D
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.89 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-0.99)[-0.990,0];
 NEURAL_HAM_LONG(-1.00)[-0.999,0]; TAGGED_RCPT(0.00)[];
 NEURAL_HAM_SHORT(-0.90)[-0.896,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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2019 12:26:53 -0000

On Mon, Apr 15, 2019 at 06:48:36AM +0200, Matthias Apitz wrote:
> I git cloned it and built it, but this does not give any kernel module
> to load: [...]
> 
> $ ./ath3kfw
> Usage: ath3kfw (-D) -d ugenX.Y (-f firmware path) (-I)
>     -D: enable debugging
>     -d: device to operate upon
>     -f: firmware path, if not default
>     -I: enable informational output
> 
> What next? Will it brick my Wifi chip? I need this C720 for work. :-)

No, it should not brick your chip (well, at least it didn't brick mine,
even that it didn't manage to load the firmware correctly and left the
chip in a bogus state, but reboot seems to cure it).

I've posted exact instructions how to use it and debug log earlier in
this thread, you being CC'ed, I don't understand how could you've missed
those emails.

./danfe