From: "Filipe Laíns" <lains@archlinux.org>
To: Hamza Attak <hamza@attak.fr>
Cc: nlopezcasad@logitech.com, benjamin.tissoires@gmail.com,
linux-input@vger.kernel.org
Subject: Re: hid-logitech-hidpp / hid-logitech-dj driver hiding inputs and breaking Logitech G700s buttons
Date: Mon, 16 Dec 2019 01:48:08 +0000 [thread overview]
Message-ID: <92d802d928be1ce6c4c64394ee5775f56806d064.camel@archlinux.org> (raw)
In-Reply-To: <1576458752.26677.0@auth.smtp.1and1.fr>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Mon, 2019-12-16 at 01:12 +0000, Hamza Attak wrote:
> Hi Filipe,
>
> I'm on the latest 5.4.3 from kernel from kernel.org git repository. Only
> a few security options are tweaked in the kconfig.
> For your information, I am also facing the same issue on untouched
> Ubuntu
> built kernels,
>
> I never followed linux-input before and don't know how active was the
> code
> taking care of the G700s, but do you think there might have been a
> regression
> since you say that it was a fixed issue?
>
> Unfortunately, I didn't keep track on when it happened, ie after a
> kernel
> upgrade or if it was always there and I only noticed after trying the
> mouse
> wirelessly.
>
> Thanks,
> Hamza ATTAK.
>
Okay. Do the logs show anything interesting?
I don't have the mouse but I think Benjamin does. Let's see if he knows
what's going on.
Filipe Laíns
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-16 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 19:34 hid-logitech-hidpp / hid-logitech-dj driver hiding inputs and breaking Logitech G700s buttons Hamza Attak
2019-12-16 0:49 ` Filipe Laíns
2019-12-16 1:12 ` Hamza Attak
2019-12-16 1:48 ` Filipe Laíns [this message]
2019-12-16 15:41 ` Benjamin Tissoires
2019-12-16 17:33 ` Hamza Attak
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=92d802d928be1ce6c4c64394ee5775f56806d064.camel@archlinux.org \
--to=lains@archlinux.org \
--cc=benjamin.tissoires@gmail.com \
--cc=hamza@attak.fr \
--cc=linux-input@vger.kernel.org \
--cc=nlopezcasad@logitech.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;
as well as URLs for NNTP newsgroup(s).