From: Hilton Chain <hako@ultrarare.space>
To: "José Expósito" <jose.exposito89@gmail.com>
Cc: bryancain3@gmail.com, jikos@kernel.org,
benjamin.tissoires@redhat.com, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: apple: Reset quirks when Fn key is not found
Date: Tue, 31 May 2022 22:11:02 +0800 [thread overview]
Message-ID: <20220531221102.7bd7da7d@ultrarare.space> (raw)
In-Reply-To: <20220530061812.GA10391@elementary>
On Mon, 30 May 2022 08:18:12 +0200 José Expósito wrote:
> That could be problematic because Apple keyboards can be renamed after
> connecting them to a Mac.
>
> For example, the name of my keyboard is: "José Expósito’s Keyboard".
Well, editable name. I have a bad feeling about this...
> I think it'd be safer to assume that the device is an Apple keyboard
> and create exceptions for know non-Apple keyboards because the
> majority of the devices handled by this driver are Apple keyboards and
> because there is already a config option available (real_fnmode) to fix
> the problematic devices in the meanwhile.
>
> In my opinion, creating a function like "apple_is_non_apple_keyboard"
> (or similar) containing all the rules to identify devices from
> Keychron, GANSS, etc could do the trick. Something similar to:
>
> if (apple_is_non_apple_keyboard(hdev)) {
> hid_info(hdev, "Non-apple keyboard detected; function keys will default to fnmode=2 behavior\n");
> asc->quirks |= APPLE_IS_NON_APPLE;
> }
Done. However I couldn't figure out corresponding names from other known
bug reports, so that the initial array only contains two devices.
> Unfortunately, I can't think of a generic way to detect those devices
> as they have the same vendor and product as the Apple ones :S
T^T
Stay boiled,
Chain
next prev parent reply other threads:[~2022-05-31 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 10:02 Hilton Chain
2022-05-29 18:20 ` José Expósito
2022-05-30 0:42 ` Hilton Chain
2022-05-30 1:42 ` [PATCH] HID: apple: Properly handle function keys on misset non-apple keyboards Hilton Chain
2022-05-30 6:18 ` [PATCH] HID: apple: Reset quirks when Fn key is not found José Expósito
2022-05-31 14:11 ` Hilton Chain [this message]
2022-05-31 14:33 ` [PATCH v2] HID: apple: Workaround for non-Apple keyboards Hilton Chain
2022-05-31 17:20 ` José Expósito
2022-05-31 19:50 ` Bryan Cain
2022-05-31 23:13 ` hako
2022-05-31 23:26 ` [PATCH v3] HID: apple: Properly handle function keys on non-Apple keyboard Hilton Chain
2022-06-01 4:17 ` [PATCH v4] " Hilton Chain
2022-06-01 17:49 ` José Expósito
2022-06-02 8:12 ` [PATCH v5] " Hilton Chain
2022-06-02 21:00 ` Bryan Cain
2022-06-03 17:53 ` José Expósito
2022-06-08 9:54 ` Jiri Kosina
2022-06-18 13:51 ` [PATCH v6] " Hilton Chain
2022-06-02 0:35 ` [PATCH v3] " Bryan Cain
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=20220531221102.7bd7da7d@ultrarare.space \
--to=hako@ultrarare.space \
--cc=benjamin.tissoires@redhat.com \
--cc=bryancain3@gmail.com \
--cc=jikos@kernel.org \
--cc=jose.exposito89@gmail.com \
--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®