From: Bin Meng <bmeng.cn@gmail.com>
To: Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: [PATCH 3/3] doc: usage: Convert README.plan9 to reST
Date: Mon, 28 Mar 2022 10:43:51 +0800 [thread overview]
Message-ID: <20220328024351.629189-3-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20220328024351.629189-1-bmeng.cn@gmail.com>
This converts the existing README.plan9 to reST, and puts it under
the doc/usage/os directory.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
---
doc/usage/index.rst | 1 +
doc/{README.plan9 => usage/os/plan9.rst} | 12 ++++++++----
2 files changed, 9 insertions(+), 4 deletions(-)
rename doc/{README.plan9 => usage/os/plan9.rst} (89%)
diff --git a/doc/usage/index.rst b/doc/usage/index.rst
index b8916971bc..ecb4908fd1 100644
--- a/doc/usage/index.rst
+++ b/doc/usage/index.rst
@@ -59,4 +59,5 @@ Booting OS
.. toctree::
:maxdepth: 1
+ os/plan9
os/vxworks
diff --git a/doc/README.plan9 b/doc/usage/os/plan9.rst
similarity index 89%
rename from doc/README.plan9
rename to doc/usage/os/plan9.rst
index 2d3d0e0cf6..f91712c009 100644
--- a/doc/README.plan9
+++ b/doc/usage/os/plan9.rst
@@ -1,3 +1,10 @@
+.. SPDX-License-Identifier: GPL-2.0+
+.. Steven Stallion
+.. June 2013
+
+Plan 9
+======
+
Plan 9 from Bell Labs kernel images require additional setup to pass
configuration information to the kernel. An environment variable named
confaddr must be defined with the same value as CONFADDR (see mem.h).
@@ -10,9 +17,6 @@ bootargs environment variable will be copied.
If no command line arguments or bootargs are defined, CONFADDR is left
uninitialized to permit manual configuration. For example, PC-style
-configuration could be simulated by issuing a fatload in bootcmd:
+configuration could be simulated by issuing a fatload in bootcmd::
# setenv bootcmd fatload mmc 0 $confaddr plan9.ini; ...; bootm
-
-Steven Stallion
-June 2013
--
2.25.1
next prev parent reply other threads:[~2022-03-28 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 2:43 [PATCH 1/3] doc: usage: Convert README.vxworks to reST Bin Meng
2022-03-28 2:43 ` [PATCH 2/3] doc: usage: Update vxworks doc to mention RISC-V support Bin Meng
2022-03-29 17:00 ` Heinrich Schuchardt
2022-03-28 2:43 ` Bin Meng [this message]
2022-03-29 17:11 ` [PATCH 3/3] doc: usage: Convert README.plan9 to reST Heinrich Schuchardt
2022-03-30 19:58 ` Heinrich Schuchardt
2022-03-29 16:56 ` [PATCH 1/3] doc: usage: Convert README.vxworks " Heinrich Schuchardt
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=20220328024351.629189-3-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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