From: Armin Wolf <W_Armin@gmx.de>
To: Hridesh MG <hridesh699@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: platform-driver-x86@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: platform/x86: wmi: mention tool for invoking WMI methods
Date: Wed, 1 Jan 2025 19:52:14 +0100 [thread overview]
Message-ID: <df7d0307-0b21-4a58-a599-538a4ffdfd94@gmx.de> (raw)
In-Reply-To: <20250101092730.87160-1-hridesh699@gmail.com>
Am 01.01.25 um 10:27 schrieb Hridesh MG:
> Add a reference to WMIExplorer, a tool useful for inspecting and
> invoking WMI methods on Windows. This can assist developers in testing
> and understanding WMI device functionality when porting drivers to
> Linux.
Nice find!
Reviewed-by: Armin Wolf <W_Armin@gmx.de>
>
> Signed-off-by: Hridesh MG <hridesh699@gmail.com>
> ---
> Documentation/wmi/driver-development-guide.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/wmi/driver-development-guide.rst b/Documentation/wmi/driver-development-guide.rst
> index 676873c98680..f7e1089a0559 100644
> --- a/Documentation/wmi/driver-development-guide.rst
> +++ b/Documentation/wmi/driver-development-guide.rst
> @@ -41,6 +41,10 @@ helps in understanding how the WMI device is supposed to work. The path of the A
> method associated with a given WMI device can be retrieved using the ``lswmi`` utility
> as mentioned above.
>
> +If you are attempting to port a driver to Linux and are working on a Windows
> +system, `WMIExplorer <https://github.com/vinaypamnani/wmie2>`_ can be useful
> +for inspecting available WMI methods and invoking them directly.
> +
> Basic WMI driver structure
> --------------------------
>
next prev parent reply other threads:[~2025-01-01 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 9:27 [PATCH] docs: platform/x86: wmi: mention tool for invoking WMI methods Hridesh MG
2025-01-01 18:52 ` Armin Wolf [this message]
2025-01-07 18:36 ` 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=df7d0307-0b21-4a58-a599-538a4ffdfd94@gmx.de \
--to=w_armin@gmx.de \
--cc=corbet@lwn.net \
--cc=hridesh699@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=skhan@linuxfoundation.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