From: Shang Ye <yesh25@mail2.sysu.edu.cn>
To: WangYuli <wangyuli@uniontech.com>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH] Input: PS/2 - add support for Lenovo Xiaoxin keyboard
Date: Thu, 18 Apr 2024 16:58:56 +0800 [thread overview]
Message-ID: <BFAD3AED2C23AA7B+1b1a47f6-af12-41a5-ac64-1d82238c8288@mail2.sysu.edu.cn> (raw)
In-Reply-To: <AA3FCBB9232F6C97+0e28ccd7-11cc-4047-866c-92069ddbb550@uniontech.com>
Hi,
On 2024/04/18 4:16 pm, WangYuli wrote:
> Hi,
>
> On 2024/3/29 04:34, Dmitry Torokhov wrote:
>> Could you please tell me more about the keyboard?
>
> Link:
> https://lore.kernel.org/lkml/20230514083336.3811-1-yesh25@mail2.sysu.edu.cn/T/
>
> Link: https://gist.github.com/yescallop/5a97d010f226172fafab0933ce8ea8af
>
> Those links above mentioned the same situation.
>
> Lenovo has a batch of laptops shipped in 2021 with the same problem. And
>
> the combined sales of these products are considerable.
>
>> What ID does it use?
> 0x83.
>> Majority of keyboards are using 0xab83, does your device forget to send
>> 0xab by chance?
> Unfortunalety, I'm afraid not.
>>
>> Thanks.
>>
> Thanks.
>
I'm pretty sure that the problem I encountered was already fixed by a
previous patch:
https://lore.kernel.org/r/20231115174625.7462-1-hdegoede@redhat.com
Could you please check if it is the case?
Regards,
Shang
prev parent reply other threads:[~2024-04-18 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 13:17 [PATCH] Input: PS/2 - add support for Lenovo Xiaoxin keyboard WangYuli
2024-03-28 20:34 ` Dmitry Torokhov
2024-04-18 8:16 ` WangYuli
2024-04-18 8:58 ` Shang Ye [this message]
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=BFAD3AED2C23AA7B+1b1a47f6-af12-41a5-ac64-1d82238c8288@mail2.sysu.edu.cn \
--to=yesh25@mail2.sysu.edu.cn \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=wangyuli@uniontech.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).