From owner-freebsd-bluetooth@freebsd.org Thu Mar 26 02:06:17 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 CD45426D10F for ; Thu, 26 Mar 2020 02:06:17 +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 48npHV3nR8z4FP9 for ; Thu, 26 Mar 2020 02:05:57 +0000 (UTC) (envelope-from jason-fbsd-bluetooth@shalott.net) Received: (qmail 19052 invoked by uid 2034); 26 Mar 2020 02:05:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 Mar 2020 02:05:42 -0000 Date: Wed, 25 Mar 2020 19:05:40 -0700 (PDT) From: jason-fbsd-bluetooth@shalott.net X-X-Sender: jason@waffle.shalott.net To: freebsd-bluetooth@freebsd.org cc: adrian@freebsd.org, maksim.yevmenkin@gmail.com 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: 48npHV3nR8z4FP9 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.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx:shalott.net]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; 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: Thu, 26 Mar 2020 02:06:18 -0000 >> Hello. I am trying to get an ath3k-based USB bluetooth adapter >> working. I previously had this adapter working under FreeBSD, several >> years ago[.] After loading the firmware, it is not detected by ng_ubt. > I tracked this down: > > https://svnweb.freebsd.org/base?view=revision&revision=249178 > > Can someone explain why these devices were blacklisted from the ng_ubt > driver? It seems like the devices will fail to work if the firmware is > not loaded to the device before ng_ubt is loaded into the kernel; but it > seems like the failure mode is just that those devices don't work in > that case. So blacklisting them from the driver seems a lot worse... Pinging again on this. Any chance we can revert the above commit? After reverting the above commit on my box, I am able to fully use my bluetooth adapter (pair HID devices, play audio through my headset with virtual_oss, etc). I don't want to have to maintain a custom kernel in perpetuity to maintain that capability. Am I missing something about the current situation? As far as I can tell, with all of those devices blacklisted in the ng_ubt driver, there is no way to use those devices on FreeBSD. But if those devices are re-instated in ng_ubt, the only downside is that they _might_ not work, because it's left as an exercise to the user to make sure that the device firmware is pushed to the device before ng_ubt is loaded into the kernel. So my understanding is: current situation, those devices are impossible to use; reverting the above commit, those devices might be usable if the user knows what they're doing. Is that the wrong understanding? And if it's correct, is there any reason to not re-instate them? If some other change is needed or wanted instead of just reverting the above commit -- extra checks, warning log messages, etc -- I would be happy to take a run at it if someone could describe what's needed. I don't know anything about Bluetooth and don't have any kernel-hacking experience, but I am an experienced C programmer. Thanks. -Jason 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" From owner-freebsd-bluetooth@freebsd.org Thu Mar 26 15:05:06 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 BD4EA2A24AA for ; Thu, 26 Mar 2020 15:05:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qk1-f194.google.com (mail-qk1-f194.google.com [209.85.222.194]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48p7ZC33QZz4D2h for ; Thu, 26 Mar 2020 15:04:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-qk1-f194.google.com with SMTP id x3so6754759qki.4 for ; Thu, 26 Mar 2020 08:04:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B21J0NxGeptZN1KgONekBiCovLXxWIFo3B12xk2LsVQ=; b=Ym7//YquCcOiGInTEwFD3bEAs/C02xoLJXCnpPPJFro8vH/K2hcc+uBBCajgRqgWDm tnMOUt4wj038ktgAykKbbM3ZYaGjxCrPCleIsR8gu1ok9n2Bnv+vd78Mfz6L8oOgAEmn oEtMBNkZR99JdOJwislrjV2i8FTNGztKdsBSZfkmqmr/GlL43qSfYwWZlZp575Aezzkl h+XT8i9jFKQ0JgWUWa3Zy8Dqis0hlyNBPEv93LWu3lCkoUZ8D1DY4BEghelBLWF/k5WX TOuLM/P9xRzCdBoIcAuwHHJsQOLoRgELxHhWLvr8ZuP30s94IO9O9iKvQqH4MNp2PhL+ KZiQ== X-Gm-Message-State: ANhLgQ0dOKYMI6y/WpEeiyB0NK45zwxwiCo/PtpzoQLPLiL37IBOOGxL yAgMD/wl8CI1BR782z+IkDmA6NtsI5wFKdpQA26NCw== X-Google-Smtp-Source: ADFU+vtmEuKLYsdLO+rwD0wAx/kUsBBdjiekchc3MKrlLjklto4ZzkzsrDkGwD6kB8Q4pkAWs6eImbs8SFk+norBmlI= X-Received: by 2002:a37:4a85:: with SMTP id x127mr8642319qka.152.1585235085929; Thu, 26 Mar 2020 08:04:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Thu, 26 Mar 2020 08:04:33 -0700 Message-ID: Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression To: Chris H Cc: jason-fbsd-bluetooth@shalott.net, freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 48p7ZC33QZz4D2h X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of adrianchadd@gmail.com designates 209.85.222.194 as permitted sender) smtp.mailfrom=adrianchadd@gmail.com X-Spamd-Result: default: False [-2.39 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[194.222.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.39)[ip: (-0.06), ipnet: 209.85.128.0/17(-1.37), asn: 15169(-0.48), country: US(-0.05)]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[194.222.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] 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 15:05:06 -0000 hi! 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. -adrian On Wed, 25 Mar 2020 at 23:09, Chris wrote: > > On Wed, 25 Mar 2020 19:05:40 -0700 (PDT) jason-fbsd-bluetooth@shalott.net said > > > >> Hello. I am trying to get an ath3k-based USB bluetooth adapter > > >> working. I previously had this adapter working under FreeBSD, several > > >> years ago[.] After loading the firmware, it is not detected by ng_ubt. > > > > > I tracked this down: > > > > > > https://svnweb.freebsd.org/base?view=revision&revision=249178 > > > > > > Can someone explain why these devices were blacklisted from the ng_ubt > > > driver? It seems like the devices will fail to work if the firmware is > > > not loaded to the device before ng_ubt is loaded into the kernel; but it > > > seems like the failure mode is just that those devices don't work in > > > that case. So blacklisting them from the driver seems a lot worse... > > > > Pinging again on this. > > > > Any chance we can revert the above commit? > > > > After reverting the above commit on my box, I am able to fully use my > > bluetooth adapter (pair HID devices, play audio through my headset with > > virtual_oss, etc). I don't want to have to maintain a custom kernel in > > perpetuity to maintain that capability. > > > > Am I missing something about the current situation? As far as I can tell, > > with all of those devices blacklisted in the ng_ubt driver, there is no > > way to use those devices on FreeBSD. But if those devices are re-instated > > in ng_ubt, the only downside is that they _might_ not work, because it's > > left as an exercise to the user to make sure that the device firmware is > > pushed to the device before ng_ubt is loaded into the kernel. So my > > understanding is: current situation, those devices are impossible to use; > > reverting the above commit, those devices might be usable if the user > > knows what they're doing. Is that the wrong understanding? And if it's > > correct, is there any reason to not re-instate them? > > > > > > If some other change is needed or wanted instead of just reverting the > > above commit -- extra checks, warning log messages, etc -- I would be > > happy to take a run at it if someone could describe what's needed. I > > don't know anything about Bluetooth and don't have any kernel-hacking > > experience, but I am an experienced C programmer. > It might be worth opening a pr (https://bugs.freebsd.org) for this. Doing > so might give it higher visibility, and I *think* that's also the > preferred direction. After all. As far as your concerned, this seems like > a bug. No? :) > > --Chris > > > > Thanks. > > > > > > -Jason > > > > _______________________________________________ > > freebsd-bluetooth@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" > > 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 From owner-freebsd-bluetooth@freebsd.org Fri Mar 27 15:47:04 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 94299279463 for ; Fri, 27 Mar 2020 15:47:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qk1-f193.google.com (mail-qk1-f193.google.com [209.85.222.193]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48pmSJ0D6bz4RWv for ; Fri, 27 Mar 2020 15:46:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-qk1-f193.google.com with SMTP id q188so11245800qke.8 for ; Fri, 27 Mar 2020 08:46:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CV3C4/zC5HlTstfoBJVJ2Opwb1YLJEkzbgemPS+RwbE=; b=AmFok85VZNMohF6KF/Qxk7DOWmAXaimwwwLbqiwfo/yn4YPPIhXdYDz23y2Qp6LftW ZIwBBFXG1JJkxnYVudY+lRVzRZXcck4HYnfuqsCIMzzlY2AAHJTXwP6p0U2Vw41YT1V8 C1QuQbnj4lQLs326cl0rY8cvydxWfmFE+SD/3qRSNRPRqW6oDvVWjNpFoy8hdGwbCRs8 tgump3ItJhZtfqrqPyOGp8Mklrr9RYa9iBetz5DQPZTFvfcyLNUK8YdTltTnykWHVBNJ kt/SYGktU+w/jjHLsI78BoROu3achfDtcB+fMLtPHNzMBuFPE4nQn3n9+HKk3RIoFmga MklA== X-Gm-Message-State: ANhLgQ163HQZt9tug+obGYIqRDEIANWxMvjsEX0eGFf+sym8C20oXPmy TdEWhMA+daCuoCQGvO+ODmBecvPTtqF5tiCSud7J6Q== X-Google-Smtp-Source: ADFU+vvAdfrWrJfqwyibJ2PwfnUjoZarcJCjLjQU7H3rO1XsvOfLcyyR6lABiEiO3bFHzUSMfJAsxNmlxtGHriZ43Gw= X-Received: by 2002:a37:6852:: with SMTP id d79mr13294718qkc.304.1585324013811; Fri, 27 Mar 2020 08:46:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Fri, 27 Mar 2020 08:46:41 -0700 Message-ID: Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression To: jason-fbsd-bluetooth@shalott.net Cc: Chris H , freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 48pmSJ0D6bz4RWv X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of adrianchadd@gmail.com designates 209.85.222.193 as permitted sender) smtp.mailfrom=adrianchadd@gmail.com X-Spamd-Result: default: False [-2.35 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[193.222.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-0.35)[ip: (-0.09), ipnet: 209.85.128.0/17(-1.12), asn: 15169(-0.47), country: US(-0.05)]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[193.222.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; TAGGED_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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 15:47:04 -0000 Hi! Ok so the device ID via USB changes when you've loaded firmware, and ng_ubt should attach to it. -adrian From owner-freebsd-bluetooth@freebsd.org Fri Mar 27 18:14:47 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 7E8F227CCEE for ; Fri, 27 Mar 2020 18:14:47 +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 48pqkW6f7qz4Pl8 for ; Fri, 27 Mar 2020 18:14:27 +0000 (UTC) (envelope-from jason-fbsd-bluetooth@shalott.net) Received: (qmail 11679 invoked by uid 2034); 27 Mar 2020 18:14:18 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Mar 2020 18:14:18 -0000 Date: Fri, 27 Mar 2020 11:14:16 -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: 48pqkW6f7qz4Pl8 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.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,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.999,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 18:14:48 -0000 > Ok so the device ID via USB changes when you've loaded firmware, and > ng_ubt should attach to it. Yes, the device ID does change; no, ng_ubt does not attach to the changed, correct device ID. When the device is plugged, it gets: ugen1.4: at usbus1 After loading firmware, it becomes: ugen1.4: at usbus1 Your change, below, instructed ng_ubt to not attach to this device: https://svnweb.freebsd.org/base?view=revision&revision=249178 static const STRUCT_USB_HOST_ID ubt_ignore_devs[] = { /* ... */ { USB_VPI(0x0cf3, 0x3002, 0) }, Please see my full original email: https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002129.html And the followup: https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002133.html Thanks. -Jason From owner-freebsd-bluetooth@freebsd.org Fri Mar 27 18:27:02 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 D1BC627D2B0 for ; Fri, 27 Mar 2020 18:27:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48pr0l4dxhz4TZ0 for ; Fri, 27 Mar 2020 18:26:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-qt1-f177.google.com with SMTP id z12so9413219qtq.5 for ; Fri, 27 Mar 2020 11:26:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B5L2vNEpc99AYqfRhhhARn4X9cFNz2jtQ9mkLzPSy8A=; b=XRu7+lOqsdEVwR6QjZu+jeknJCOcTWV9suLKQaOwT3MvPyGQ271pba1XHi46ifCI60 t4wZulRmCoKpTgTm20ug/ercPsKxeS5WTenBkiEnbME3XdsbBFq+e8rBmmfaipRMNJPf azCK5gojmaNkVWWtp8HAjmKPel20V2XIuKVRcWiRTcLeWSVGL3Y0r0yl4vDTX4W5UbOd IVZwcJ6JmAsgCShFbLbQsdqpp0LIa2dgs+AP8kP6g+W1N7SY/IevOL5KbFPHSOi9Lf0u fI2Igpi3tb7r1wB2RdC5w77jGlnYt4X4IgNrCqw/J3NTxtI9kNns6m2Jqks/MwckqFGw 1eQw== X-Gm-Message-State: ANhLgQ0C8uQAh26RLzP+TGtu8VxQ8NdDF4ycbkHBSGb3KSfNgSCckKJ1 7ohDjrARfQ5UJ0o4nZuDP856pT3RYBehbrYElU0V4Q== X-Google-Smtp-Source: ADFU+vsnMyrL2YXyzsFvx0tf53Rpk7anpSNp+9LQKAh+IKrK7+sDvXZGPE9Wa0efHleXJuoMGIWLtiXGAheEgjgkVTo= X-Received: by 2002:ac8:3630:: with SMTP id m45mr544869qtb.330.1585333599156; Fri, 27 Mar 2020 11:26:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Fri, 27 Mar 2020 11:26:26 -0700 Message-ID: Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression To: jason-fbsd-bluetooth@shalott.net Cc: Chris H , freebsd-bluetooth@freebsd.org X-Rspamd-Queue-Id: 48pr0l4dxhz4TZ0 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of adrianchadd@gmail.com designates 209.85.160.177 as permitted sender) smtp.mailfrom=adrianchadd@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-bluetooth@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; TO_DN_SOME(0.00)[]; URI_COUNT_ODD(1.00)[9]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[177.160.85.209.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_GOOD(0.00)[177.160.85.209.rep.mailspike.net : 127.0.0.18]; IP_SCORE(-1.00)[ip: (-3.38), ipnet: 209.85.128.0/17(-1.10), asn: 15169(-0.47), country: US(-0.05)]; FORGED_SENDER(0.30)[adrian@freebsd.org,adrianchadd@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[adrian@freebsd.org,adrianchadd@gmail.com]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 18:27:02 -0000 Ooooooooh wait this is something recentish? Which wifi chipset is this attached to? I vaguely remember upstream Linux ath3k having a similar issue super recently..... A On Fri, Mar 27, 2020, 11:14 AM wrote: > > > Ok so the device ID via USB changes when you've loaded firmware, and > > ng_ubt should attach to it. > > Yes, the device ID does change; no, ng_ubt does not attach to the changed, > correct device ID. > > When the device is plugged, it gets: > ugen1.4: at usbus1 > > After loading firmware, it becomes: > ugen1.4: at usbus1 > > Your change, below, instructed ng_ubt to not attach to this device: > > https://svnweb.freebsd.org/base?view=revision&revision=249178 > > static const STRUCT_USB_HOST_ID ubt_ignore_devs[] = { > /* ... */ > { USB_VPI(0x0cf3, 0x3002, 0) }, > > > Please see my full original email: > > https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002129.html > > And the followup: > > https://lists.freebsd.org/pipermail/freebsd-bluetooth/2020-March/002133.html > > Thanks. > > > -Jason > >