From: "José Expósito" <jose.exposito89@gmail.com>
To: inochiama@outlook.com
Cc: benjamin.tissoires@redhat.com, jikos@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] HID: uclogic: Add support for recent Huion tablets
Date: Mon, 19 Dec 2022 10:56:22 +0100 [thread overview]
Message-ID: <20221219095622.255134-1-jose.exposito89@gmail.com> (raw)
In-Reply-To: <PH7PR20MB49624FFCDF1F9382886933D3BB1E9@PH7PR20MB4962.namprd20.prod.outlook.com>
Hi Inochi and thanks for the patch!
> Since Huion uses a new device id for recent tablets, add a new
> device id 0x0064 to support recent Huion tablets.
>
> At least these tablets are using device id 0x0064:
>
> Gaomon 1060 Pro (0x256c:0x0064)
> Gaomon M6 (0x256c:0x0064)
> Huion KD200 (0x256c:0x0064)
> Huion KD100 (0x256c:0x0064)
>
> This patch was tested on Gaomon 1060 Pro and Huion KD200. This patch
> may affect other models with the same id, however, it's seems that the
> other models of Huion do not have incompatible hardware changes, so
> this patch should still work.
While this patch is correct, HUION always reuse the same vendor/product
IDs, meaning that it'll affect a fairly big number of devices.
Checking some comments in DIGImend's issue tracker [1], users report
that their tablet works applying a similar patch. However, I think that
it could be a good idea if you could build a version of the driver
including your patch and request them to test it.
I'm pretty sure it'll work, but it might be a good idea to test it on
more devices before merging it.
Best wishes,
Jose
[1] https://github.com/DIGImend/digimend-kernel-drivers/issues?q=0064
next prev parent reply other threads:[~2022-12-19 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 8:37 Inochi Amaoto
2022-12-19 9:56 ` José Expósito [this message]
2022-12-20 23:47 ` Inochi Amaoto
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=20221219095622.255134-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=inochiama@outlook.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®