From: Andrey Butirsky <butirsky@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Lenovo Legion M600 wireless bluetooth mouse connected and paired yet not working
Date: Thu, 17 Feb 2022 16:06:52 +0300 [thread overview]
Message-ID: <58080949-4139-3dda-cb2a-d89f20713ffb@gmail.com> (raw)
In-Reply-To: <CABBYNZKjUYAqctfpap2f36TcBuJFk0wX5P8jkUjpw1qqupeb0A@mail.gmail.com>
On 17.02.2022 02:10, Luiz Augusto von Dentz wrote:
> Hi Andrey,
>
> On Wed, Feb 16, 2022 at 2:36 PM Andrey Butirsky <butirsky@gmail.com> wrote:
>> Tried BlueZ 5.63 on my Fedora installation, no luck. Will try to build
>> head if no better idea..
> If that doesn't work I'm afraid you will need a dedicated kernel
> driver in order to deal with its HID reports since BlueZ just forwards
> the reports to the kernel.
Could you clarify do you mean usual BlueZ dedicated driver just built
from bluetooth-next for my kernel or some non-existent driver one yet
had to write?
In the latter case, do you have some sample drivers maybe one could easy
to adopt?
next prev parent reply other threads:[~2022-02-17 13:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 19:49 Lenovo Legion M600 wireless bluetooth mouse connected and paired yet not working Andrey Butirsky
2022-02-15 23:22 ` Luiz Augusto von Dentz
2022-02-16 16:03 ` Andrey Butirsky
2022-02-16 20:26 ` Luiz Augusto von Dentz
2022-02-16 20:32 ` Andrey Butirsky
2022-02-16 21:08 ` Luiz Augusto von Dentz
2022-02-16 22:35 ` Andrey Butirsky
2022-02-16 23:10 ` Luiz Augusto von Dentz
2022-02-16 23:55 ` Andrey Butirsky
2022-02-17 13:06 ` Andrey Butirsky [this message]
2022-02-18 11:54 ` Andrey Butirsky
2022-02-18 21:15 ` Luiz Augusto von Dentz
2022-02-18 21:26 ` Andrey Butirsky
2022-02-18 21:38 ` Luiz Augusto von Dentz
2022-02-18 22:31 ` Andrey Butirsky
2022-02-19 23:18 ` Andrey Butirsky
2022-02-20 0:06 ` Andrey Butirsky
2022-03-08 10:30 ` Bastien Nocera
2022-03-09 10:21 ` Andrey Butirsky
2022-03-22 5:48 ` Luiz Augusto von Dentz
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=58080949-4139-3dda-cb2a-d89f20713ffb@gmail.com \
--to=butirsky@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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