From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 208965] not working bluetooth mouse low energy rtl8822ce
Date: Tue, 27 Oct 2020 16:39:29 +0000 [thread overview]
Message-ID: <bug-208965-62941-AF7YQFGteF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208965-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Edward Vear (edwardvear@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edwardvear@gmail.com
--- Comment #25 from Edward Vear (edwardvear@gmail.com) ---
(In reply to david.zakarias from comment #20)
> Is it possible that a newer firmware fixes the problem? I also have version
> 0x09993aa1.
> Julian what version do you have?
Hi David,
I ran into the same Set Resolvable Private Address error with my adapter, an
rtl8761b. I submitted a patch here with my understanding of the issue:
https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you check to
see if that patch helps?
I don't believe it is related to the original issue seen in this thread though.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-10-27 16:42 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
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 [this message]
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-AF7YQFGteF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).