From owner-freebsd-bluetooth@freebsd.org Thu Mar 26 06:08:25 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 4E629275741 for ; Thu, 26 Mar 2020 06:08:25 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48nvg83vC6z3HQ8; Thu, 26 Mar 2020 06:08:19 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 02Q5GSgl015585 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 25 Mar 2020 22:16:34 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: , In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression Date: Wed, 25 Mar 2020 22:16:34 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48nvg83vC6z3HQ8 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.16 / 15.00]; NEURAL_HAM_MEDIUM(-0.53)[-0.529,0]; NEURAL_HAM_LONG(-0.63)[-0.627,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] 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: Thu, 26 Mar 2020 06:08:25 -0000 On Wed, 25 Mar 2020 19:05:40 -0700 (PDT) jason-fbsd-bluetooth@shalott=2Enet s= aid > >> Hello=2E I am trying to get an ath3k-based USB bluetooth adapter=20 > >> working=2E I previously had this adapter working under FreeBSD, several= =20 > >> years ago[=2E] After loading the firmware, it is not detected by ng_ubt= =2E >=20 > > I tracked this down: > > > > https://svnweb=2Efreebsd=2Eorg/base?view=3Drevision&revision=3D249178 > >=20 > > Can someone explain why these devices were blacklisted from the ng_ubt= =20 > > driver? It seems like the devices will fail to work if the firmware is= =20 > > not loaded to the device before ng_ubt is loaded into the kernel; but i= t=20 > > seems like the failure mode is just that those devices don't work in=20 > > that case=2E So blacklisting them from the driver seems a lot worse=2E=2E=2E >=20 > Pinging again on this=2E >=20 > Any chance we can revert the above commit? >=20 > After reverting the above commit on my box, I am able to fully use my=20 > bluetooth adapter (pair HID devices, play audio through my headset with= =20 > virtual_oss, etc)=2E I don't want to have to maintain a custom kernel in= =20 > perpetuity to maintain that capability=2E >=20 > Am I missing something about the current situation? As far as I can tell= ,=20 > with all of those devices blacklisted in the ng_ubt driver, there is no= =20 > way to use those devices on FreeBSD=2E But if those devices are re-instate= d=20 > in ng_ubt, the only downside is that they _might_ not work, because it's= =20 > left as an exercise to the user to make sure that the device firmware is= =20 > pushed to the device before ng_ubt is loaded into the kernel=2E So my=20 > understanding is: current situation, those devices are impossible to use;= =20 > reverting the above commit, those devices might be usable if the user=20 > knows what they're doing=2E Is that the wrong understanding? And if it's= =20 > correct, is there any reason to not re-instate them? >=20 >=20 > If some other change is needed or wanted instead of just reverting the=20 > above commit -- extra checks, warning log messages, etc -- I would be=20 > happy to take a run at it if someone could describe what's needed=2E I=20 > don't know anything about Bluetooth and don't have any kernel-hacking=20 > experience, but I am an experienced C programmer=2E It might be worth opening a pr (https://bugs=2Efreebsd=2Eorg) for this=2E Doing so might give it higher visibility, and I *think* that's also the preferred direction=2E After all=2E As far as your concerned, this seems like a bug=2E No? :) --Chris >=20 > Thanks=2E >=20 >=20 > -Jason >=20 > _______________________________________________ > freebsd-bluetooth@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd=2Eo= rg"