From owner-freebsd-bluetooth@freebsd.org Fri Mar 27 11:38:13 2020 Return-Path: Delivered-To: freebsd-bluetooth@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C76492725DA for ; Fri, 27 Mar 2020 11:38:12 +0000 (UTC) (envelope-from jason-fbsd-bluetooth@shalott.net) Received: from waffle.shalott.net (waffle.shalott.net [209.151.236.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.shalott.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48pfx10rfRz3L2M for ; Fri, 27 Mar 2020 11:37:56 +0000 (UTC) (envelope-from jason-fbsd-bluetooth@shalott.net) Received: (qmail 19996 invoked by uid 2034); 27 Mar 2020 11:37:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Mar 2020 11:37:43 -0000 Date: Fri, 27 Mar 2020 04:37:41 -0700 (PDT) From: jason-fbsd-bluetooth@shalott.net X-X-Sender: jason@waffle.shalott.net To: Adrian Chadd cc: Chris H , freebsd-bluetooth@freebsd.org Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression In-Reply-To: Message-ID: References: User-Agent: Alpine 2.22 (LRH 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 48pfx10rfRz3L2M X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jason-fbsd-bluetooth@shalott.net designates 209.151.236.43 as permitted sender) smtp.mailfrom=jason-fbsd-bluetooth@shalott.net X-Spamd-Result: default: False [-2.29 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978,0]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:shalott.net]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[shalott.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NO_DN(0.00)[]; IP_SCORE(-0.01)[country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11051, ipnet:209.151.224.0/19, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2020 11:38:14 -0000 > Ok, so it's because in theory the firmware could be buggy and need > patching via the ath3kfw tool (which gosh I really should just import > into -head already) before it starts up. > > can you clone https://github.com/erikarn/ath3k and try to load in what > it thinks the right patch set / config file is? See if it comes up ok? > Now that we have the hotplug work from warner and others I bet we could > import ath3k and just have it autorun via devd in a non-terrible > fashion. Thanks, I can try out the newer ath3kfw tool and see if it has any better luck loading my firmware than the one already in the tree. But that doesn't really address my issue, which is that a bunch of devices were removed from ng_ubt. Just to be clear, for my personal device, I can load a working firmware right now; but even if I do, the device is unusable because ng_ubt refuses to attach to it. When I revert the commit that removed support for it, my device works fine. So I'm not sure what useful information it would give to see if the new ath3kfw tool works for me; I still need the fix to ng_ubt in order to actually use my device. Even in the cases where the firmware is buggy and needs patching, the worst that could happen when you try to load it is that the bluetooth card just doesn't work, right? So my question is still why it's better to completely remove support rather than just let the user try to use the device, which might indeed work (as my device does)? If I'm misunderstanding the potential problem in trying to proceed with potentially buggy firmware, please let me know. Thanks. -Jason