From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: "Michael Opdenacker via lists.yoctoproject.org"
<michael.opdenacker=rootcommit.com@lists.yoctoproject.org>
Cc: docs@lists.yoctoproject.org, michael.opdenacker@rootcommit.com
Subject: Re: [docs] [PATCH 3/3] dev-manual/bmaptool.rst: simplify and fix instructions
Date: Sun, 01 Dec 2024 20:26:58 +0100 [thread overview]
Message-ID: <6rwmgj6w71.fsf@pengutronix.de> (raw)
In-Reply-To: <20241201173801.3290796-3-michael.opdenacker@rootcommit.com> (Michael Opdenacker via lists yoctoproject org's message of "Sun, 01 Dec 2024 17:38:10 +0000 (UTC)")
Hey Michael,
On Sun, Dec 01 2024 at 17:38 +0000, "Michael Opdenacker via lists.yoctoproject.org" <michael.opdenacker=rootcommit.com@lists.yoctoproject.org> wrote:
> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>
> - Remove duplicate instructions
>
> - Detail how to run bmaptool directly if you installed it on your host
> instead of building it through the ``bmaptool-native`` recipe,
> as running "oe-run-native bmaptool-native bmaptool ..." won't work
> in this case.
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
> ---
> documentation/dev-manual/bmaptool.rst | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/documentation/dev-manual/bmaptool.rst b/documentation/dev-manual/bmaptool.rst
> index 5fc46c7792..e17074b65b 100644
> --- a/documentation/dev-manual/bmaptool.rst
> +++ b/documentation/dev-manual/bmaptool.rst
> @@ -44,14 +44,16 @@ any type of image. Use these steps to flash an image using `bmaptool`:
> depending on your particular setup. The following commands assume the
> image resides in the :term:`Build Directory`'s ``deploy/images/`` area:
>
> - - If you have write access to the media, use this command form::
> + - If needed, set permissions to get write access to the media::
>
> - $ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
> + $ such chmod 666 /dev/sdX
a small typo slipped in here: s/such/sudo/
Best regards
Ulrich
> +
> + - If you installed the package for `bmaptool`, you can directly run::
> +
> + $ sudo bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
>
> - - If you do not have write access to the media, set your permissions
> - first and then use the same command form::
> + - Otherwise, if you built `bmaptool` with BitBake, run::
>
> - $ sudo chmod 666 /dev/sdX
> $ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX
>
> For help on the ``bmaptool`` command, use the following command::
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#5860): https://lists.yoctoproject.org/g/docs/message/5860
> Mute This Topic: https://lists.yoctoproject.org/mt/109865516/3618626
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [u.oelmann@pengutronix.de]
> -=-=-=-=-=-=-=-=-=-=-=-
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-12-01 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 17:38 [PATCH 1/3] dev-manual: fix styling of references to bmaptool michael.opdenacker
2024-12-01 17:38 ` [PATCH 2/3] dev-manual/bmaptool.rst: add missing command for bmaptool-native michael.opdenacker
2024-12-02 9:02 ` [docs] " Antonin Godard
2024-12-04 10:31 ` Michael Opdenacker
2024-12-01 17:38 ` [PATCH 3/3] dev-manual/bmaptool.rst: simplify and fix instructions michael.opdenacker
2024-12-01 19:26 ` Ulrich Ölmann [this message]
2024-12-04 9:19 ` [docs] " Michael Opdenacker
2024-12-02 9:02 ` Antonin Godard
2024-12-04 9:26 ` Michael Opdenacker
2024-12-04 9:33 ` Michael Opdenacker
2024-12-04 10:17 ` Antonin Godard
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=6rwmgj6w71.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker=rootcommit.com@lists.yoctoproject.org \
--cc=michael.opdenacker@rootcommit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.