Date: Fri, 27 Mar 2020 11:14:16 -0700 (PDT) From: jason-fbsd-bluetooth@shalott.net To: Adrian Chadd <adrian@freebsd.org> Cc: Chris H <bsd-lists@bsdforge.com>, freebsd-bluetooth@freebsd.org Subject: Re: ath3k USB bluetooth card not detected by ng_ubt, possible regression Message-ID: <alpine.LRH.2.22.394.2003271106260.19809@waffle.shalott.net> In-Reply-To: <CAJ-Vmon1Dkda7BeiieKFXx=r%2B-dBfjyjzB56fE_9n2kwF-Z-Rg@mail.gmail.com> References: <alpine.LRH.2.22.394.2003251812450.19809@waffle.shalott.net> <fd79c3867ad956005ef12847988815ce@udns.ultimatedns.net> <CAJ-Vmon_des%2BSiFKho7L9g%2BWH0JFHguNqye7m%2BsE6s2ocs1Xow@mail.gmail.com> <alpine.LRH.2.22.394.2003270423110.19809@waffle.shalott.net> <CAJ-Vmon1Dkda7BeiieKFXx=r%2B-dBfjyjzB56fE_9n2kwF-Z-Rg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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: <vendor 0x0cf3 product 0x3000> at usbus1 After loading firmware, it becomes: ugen1.4: <vendor 0x0cf3 product 0x3002> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LRH.2.22.394.2003271106260.19809>