From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Documentation: boards: sandbox: describe --image flags
Date: Wed, 13 Jan 2021 10:05:26 +0100 [thread overview]
Message-ID: <20210113090526.GH19063@pengutronix.de> (raw)
In-Reply-To: <20210111143555.13002-1-a.fatoum@pengutronix.de>
On Mon, Jan 11, 2021 at 03:35:55PM +0100, Ahmad Fatoum wrote:
> barebox partition table parsing can be tested in sandbox using the
> recently added ,blkdev flag. Extend the documentation to cover this.
>
> Cc: Juergen Borleis <jbe@pengutronix.de>
> Reported-by: Lucas Stach <lst@pengutronix.de>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> Documentation/boards/sandbox.rst | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/Documentation/boards/sandbox.rst b/Documentation/boards/sandbox.rst
> index 8b24b6a64584..e9e5183653e6 100644
> --- a/Documentation/boards/sandbox.rst
> +++ b/Documentation/boards/sandbox.rst
> @@ -34,6 +34,20 @@ Available sandbox invocation options include:
> Map a <file> to barebox. This option can be given multiple times. The <file>s
> will show up as ``/dev/fd0`` ... ``/dev/fdX`` in the barebox simulator.
>
> + How the file is mapped in barebox can be controlled by a number of flags:
> +
> + * ``,ro``: The host file is mapped read-only
> +
> + * ``,blkdev``: The host file is to be mapped as block device. This is the
> + default when passing block devices from the host. The file's size must
> + be a multiple of the barebox sector size of 512 bytes.
> +
> + * ``,cdev``: The host file is mapped as character device. This is the default,
> + unless the the host file is a block device.
> +
> + Multiple options can be appended if they don't clash. Literal commas within the
> + file path can be escaped with a backslash. Example: ``-i './0\,0.hdimg,blkdev,ro'``.
> +
> ``-e <file>``
>
> Map <file> to barebox. With this option <file>s are mapped as
> --
> 2.30.0
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-01-13 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:35 Ahmad Fatoum
2021-01-13 9:05 ` Sascha Hauer [this message]
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=20210113090526.GH19063@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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