From owner-freebsd-current@freebsd.org  Mon Feb 11 17:50:56 2019
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 2D2A314DEEB9;
 Mon, 11 Feb 2019 17:50:56 +0000 (UTC)
 (envelope-from bwidawsk@freebsd.org)
Received: from smtp.freebsd.org (smtp.freebsd.org
 [IPv6:2610:1c1:1:606c::24b:4])
 (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 "smtp.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 94A8181FCB;
 Mon, 11 Feb 2019 17:50:55 +0000 (UTC)
 (envelope-from bwidawsk@freebsd.org)
Received: from smtp.freebsd.org (c-73-25-164-31.hsd1.or.comcast.net
 [73.25.164.31])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 (Authenticated sender: bwidawsk)
 by smtp.freebsd.org (Postfix) with ESMTPSA id EBB4498E5;
 Mon, 11 Feb 2019 17:50:54 +0000 (UTC)
 (envelope-from bwidawsk@freebsd.org)
Date: Mon, 11 Feb 2019 09:50:53 -0800
From: Ben Widawsky <bwidawsk@freebsd.org>
To: Anthony Jenkins <Scoobi_doo@yahoo.com>, adrian@FreeBSD.org
Cc: freebsd-wireless@FreeBSD.org, FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject: Re: ath10k driver status?
Message-ID: <20190211175052.ojnig6cq35n7vp5r@smtp.freebsd.org>
Mail-Followup-To: Anthony Jenkins <Scoobi_doo@yahoo.com>,
 adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org,
 FreeBSD CURRENT <freebsd-current@freebsd.org>
References: <b5164aa3-45a7-2637-1dc8-328696f49117@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b5164aa3-45a7-2637-1dc8-328696f49117@yahoo.com>
User-Agent: NeoMutt/20180716
X-Rspamd-Queue-Id: 94A8181FCB
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.92 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-1.00)[-0.995,0];
 NEURAL_HAM_SHORT(-0.93)[-0.928,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0];
 ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2019 17:50:56 -0000

On 19-02-04 00:29:29, Anthony Jenkins wrote:

[snip]

Hi Adrian. I too am wondering what the plan is for this chipset. I am currently
using an awful USB wifi dongle. I can help with testing if needed - but I just
really want to know if we should expect upstream support which is relatively
stable in the next month or two. If not, I'll look for alternative solutions.

Thanks.