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" > >