From: Marco Scardovi <scardracs@disroot.org>
To: ilpo.jarvinen@linux.intel.com, Denis Benato <denis.benato@linux.dev>
Cc: corentin.chary@gmail.com, hansg@kernel.org,
linux-kernel@vger.kernel.org, luke@ljones.dev,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: asus-armoury: add support for G614PR
Date: Mon, 15 Jun 2026 17:07:30 +0200 [thread overview]
Message-ID: <wwPQu_JvTXK897kIBeAj8A@disroot.org> (raw)
In-Reply-To: <524bc16a-6a66-4b2f-8aa6-6a4b0bc31f09@linux.dev>
>
> In general all these data have been posted in the ppt data collection thread
> in form of screenshots (and I'd like to have yours too for future
> reference).
>
> Your model isn't posted there, so I assumed these values were what is
> available to you on the official windows app, if so the previous one has to
> be kept unless you find an explanation of why what is see is different from
> what you expect to see.
>
Hi Denis,
as I wrote you in private it was my bad in the end: I made gemini extrapolate
them from the ThrottleGear_G614PR.xml, which was encrypted, and didn't
triple check them.
As I told you I wrote down a python script [1], completely free from the ASUS
code, that can handle these xml files, decrypt them and even create the quirks
necessary to post in asus-armoury.h. I tried it with my G614PR.xml: it works
without problems and the values are correct.
[1] https://gitlab.com/scardracs/throttlegear
next prev parent reply other threads:[~2026-06-15 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:21 [PATCH] platform/x86: asus-armoury: add support for G614PR Marco Scardovi
2026-06-10 17:54 ` Denis Benato
2026-06-11 15:02 ` Ilpo Järvinen
2026-06-11 15:53 ` Marco Scardovi
2026-06-14 8:44 ` [PATCH v2 0/1] " Marco Scardovi
2026-06-14 8:44 ` [PATCH v2] " Marco Scardovi
2026-06-14 12:33 ` Denis Benato
2026-06-15 15:07 ` Marco Scardovi [this message]
2026-06-27 6:18 ` Marco Scardovi
2026-06-29 11:04 ` Ilpo Järvinen
2026-06-29 11:27 ` Marco Scardovi
2026-06-30 14:18 ` Ilpo Järvinen
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=wwPQu_JvTXK897kIBeAj8A@disroot.org \
--to=scardracs@disroot.org \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.