From: Sumera Priyadarsini <sylphrenadin@gmail.com>
To: melissa.srw@gmail.com
Cc: rodrigosiqueiramelo@gmail.com, hamohammed.sa@gmail.com,
daniel@ffwll.ch, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH V5 3/3] drm/vkms: Add information about module options
Date: Tue, 12 Jan 2021 00:38:22 +0530 [thread overview]
Message-ID: <4fbc6459377c1dcbe8e6648718453d5693f6451c.1610391685.git.sylphrenadin@gmail.com> (raw)
In-Reply-To: <cover.1610391685.git.sylphrenadin@gmail.com>
Update vkms documentation to contain usage of `modinfo`
command and steps to load vkms with module options enabled.
Signed-off-by: Sumera Priyadarsini <sylphrenadin@gmail.com>
---
Documentation/gpu/vkms.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/gpu/vkms.rst b/Documentation/gpu/vkms.rst
index 9e030c74a82e..2c9b376da5ca 100644
--- a/Documentation/gpu/vkms.rst
+++ b/Documentation/gpu/vkms.rst
@@ -35,6 +35,18 @@ Now, to load the driver, use::
On running the lsmod command now, the VKMS driver will appear listed.
You can also observe the driver being loaded in the dmesg logs.
+The VKMS driver has optional features to simulate different kinds of hardware,
+which are exposed as module options. You can use the `modinfo` command
+to see the module options for vkms::
+
+ modinfo vkms
+
+Module options are helpful when testing, and enabling modules
+can be done while loading vkms. For example, to load vkms with cursor enabled,
+use::
+
+ sudo modprobe vkms enable_cursor=1
+
To disable the driver, use ::
sudo modprobe -r vkms
--
2.25.1
next prev parent reply other threads:[~2021-01-11 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 19:05 [PATCH V5 0/3] Decouple config data for configfs Sumera Priyadarsini
2021-01-11 19:06 ` [PATCH V5 1/3] drm/vkms: Add vkms_config type Sumera Priyadarsini
2021-01-12 10:08 ` Melissa Wen
2021-01-11 19:07 ` [PATCH V5 2/3] drm/vkms: Add support for writeback module Sumera Priyadarsini
2021-01-12 10:10 ` Melissa Wen
2021-01-11 19:08 ` Sumera Priyadarsini [this message]
2021-01-12 10:14 ` [PATCH V5 3/3] drm/vkms: Add information about module options Melissa Wen
2021-01-12 21:04 ` [PATCH V5 0/3] Decouple config data for configfs Melissa Wen
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=4fbc6459377c1dcbe8e6648718453d5693f6451c.1610391685.git.sylphrenadin@gmail.com \
--to=sylphrenadin@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=melissa.srw@gmail.com \
--cc=rodrigosiqueiramelo@gmail.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).