From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 208965] not working bluetooth mouse low energy rtl8822ce
Date: Fri, 23 Oct 2020 22:00:59 +0000 [thread overview]
Message-ID: <bug-208965-62941-WoBp9AaVly@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208965-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #9 from julian@blk9.net ---
I've patched my kernel to add the missing USB identifier and that seem to have
solved the issue. I can now properly pair with a bluetooth mouse.
My dmesg now shows firmware files being loaded for the device:
[ 5.909847] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c
lmp_ver=0
a lmp_subver=8822
[ 5.912751] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 5.912754] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 5.918147] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 5.918282] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
What's the right way to go about this ? Should I submit my patch upstream ?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-10-23 22:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
2020-10-04 13:41 ` [Bug 208965] " bugzilla-daemon
2020-10-11 6:51 ` bugzilla-daemon
2020-10-21 18:14 ` bugzilla-daemon
2020-10-23 9:50 ` bugzilla-daemon
2020-10-23 9:52 ` bugzilla-daemon
2020-10-23 22:00 ` bugzilla-daemon [this message]
2020-10-24 7:49 ` bugzilla-daemon
2020-10-24 9:02 ` bugzilla-daemon
2020-10-24 17:34 ` bugzilla-daemon
2020-10-25 12:47 ` bugzilla-daemon
2020-10-25 14:11 ` bugzilla-daemon
2020-10-25 17:02 ` bugzilla-daemon
2020-10-26 8:37 ` bugzilla-daemon
2020-10-27 8:34 ` bugzilla-daemon
2020-10-27 8:58 ` bugzilla-daemon
2020-10-27 16:39 ` bugzilla-daemon
2020-10-28 12:56 ` bugzilla-daemon
2020-10-28 14:47 ` bugzilla-daemon
2020-10-28 20:37 ` bugzilla-daemon
2020-10-28 21:56 ` bugzilla-daemon
2020-10-29 7:16 ` bugzilla-daemon
2020-11-09 16:55 ` bugzilla-daemon
2020-11-21 15:18 ` bugzilla-daemon
2020-11-26 18:44 ` bugzilla-daemon
2020-11-28 18:59 ` bugzilla-daemon
2020-12-02 14:05 ` bugzilla-daemon
2020-12-11 12:00 ` bugzilla-daemon
2020-12-11 18:44 ` bugzilla-daemon
2020-12-12 1:00 ` bugzilla-daemon
2020-12-12 6:24 ` bugzilla-daemon
2020-12-12 8:10 ` bugzilla-daemon
2020-12-19 19:59 ` bugzilla-daemon
2021-01-11 18:29 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-208965-62941-WoBp9AaVly@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.