From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: oss-tools@pengutronix.de
Subject: [OSS-Tools] [PATCH platsch 4/5] README.rst: fix typos
Date: Wed, 21 Jun 2023 16:17:53 +0200 [thread overview]
Message-ID: <20230621141754.3143325-4-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20230621141754.3143325-1-u.oelmann@pengutronix.de>
Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
README.rst | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/README.rst b/README.rst
index 96337bfd49f2..c1e914990ea8 100644
--- a/README.rst
+++ b/README.rst
@@ -1,7 +1,7 @@
platsch - Splash Screen Application
===================================
-platsch is a simple splash screen application meant to be run as pid 1
+platsch is a simple splash screen application meant to be run as PID 1
(``init=/usr/sbin/platsch``).
The image to be displayed for each DRM connector is expected here::
@@ -11,15 +11,15 @@ The image to be displayed for each DRM connector is expected here::
By default platsch uses the first mode on each DRM connector. ``<format>``
defaults to ``RGB565``. See below how to change that behavior.
-Splash screen image must have the specified resolution and format. See
+Splash screen images must have the specified resolution and format. See
below how to generate them.
After displaying the splash screen(s), platsch forks, sending its child to
sleep to keep the DRM device open and the splash image(s) on the display(s).
-Finally platsch gives pid 1 to ``/sbin/init``. Later another application can
+Finally platsch gives PID 1 to ``/sbin/init``. Later another application can
simply take over.
-Seamless transitions are possible (e.g. to *weston* having the same image
+Seamless transitions are possible (e.g. to *Weston* having the same image
configured as background). Depending on the SoC used, the same format might be
required to achieve that.
@@ -100,11 +100,11 @@ Or a resolution of 1920x1080 and ``XRGB8888`` format on ``LVDS-2``::
platsch_lvds2_mode=1920x1080@XRGB8888
The kernel passes unrecognized key-value parameters not containing dots into
-init’s environment, see
+init's environment, see
`Kernel Parameter Documentation <https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html>`_.
-Therefore the above setting can be supplied via the kernel cmdline. This also
-allows dynamic use cases where the bootloader decides which resolution/mode to
-use on which connector.
+Therefore the above settings can be supplied via the kernel commandline. This
+also allows dynamic use cases where the bootloader decides which resolution/mode
+to use on which connector.
Debugging
---------
--
2.39.2
next prev parent reply other threads:[~2023-06-21 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 14:17 [OSS-Tools] [PATCH platsch 1/5] avoid unnecessary indirections Ulrich Ölmann
2023-06-21 14:17 ` [OSS-Tools] [PATCH platsch 2/5] use pointers to immutable strings for cmdline options Ulrich Ölmann
2023-06-21 14:17 ` [OSS-Tools] [PATCH platsch 3/5] allow directory/basename selection via environment Ulrich Ölmann
2023-06-21 14:17 ` Ulrich Ölmann [this message]
2023-06-21 14:17 ` [OSS-Tools] [PATCH platsch 5/5] README.rst: fix documented purpose of commandline arguments Ulrich Ölmann
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=20230621141754.3143325-4-u.oelmann@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=oss-tools@pengutronix.de \
/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