[PATCH 3/3] doc: usage: Convert README.plan9 to reST

[Heinrich Schuchardt]

On 3/28/22 04:43, Bin Meng wrote:
> This converts the existing README.plan9 to reST, and puts it under
> the doc/usage/os directory.
> 
> Signed-off-by: Bin Meng <bmeng.cn at 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

Does U-Boot support any hardware that Plan 9 supports?

Or can we simply drop this document?

>   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

Is this prompt correct?
I cannot find any defconfig where CONFIG_SYS_PROMPT="# ".

Best regards

Heinrich

> -
> -Steven Stallion
> -June 2013