From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com
Subject: Re: [docs] [PATCH v2 3/3] dev-manual/bmaptool.rst: simplify and fix instructions
Date: Wed, 18 Dec 2024 14:49:04 +0000 (UTC) [thread overview]
Message-ID: <f34239d6-de6e-485d-8d30-9c09d8d22e97@rootcommit.com> (raw)
In-Reply-To: <D6EQ3517THNQ.30JL51D1JWVN8@bootlin.com>
Hi Antonin,
On 12/18/24 10:35, Antonin Godard wrote:
> Hi Michael,
>
> On Wed Dec 4, 2024 at 2:03 PM CET, Michael Opdenacker wrote:
>> Hi Antonin
>>
>> On 12/4/24 13:19, Antonin Godard wrote:
>>> On Wed Dec 4, 2024 at 11:44 AM CET, Michael Opdenacker via 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 37083c9c64..93c8d3a45e 100644
>>>> --- a/documentation/dev-manual/bmaptool.rst
>>>> +++ b/documentation/dev-manual/bmaptool.rst
>>>> @@ -43,14 +43,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
>>>> + $ sudo chmod 666 /dev/sdX
>>> I think you forgot to change to "a+w"
>>> Also, it wasn't moved after the sudo command?
>>>
>>> Looks like the wrong patch may have slipped in? :)
>>
>> Right, I messed things up by modifying the second commit.
>> A V3 is coming, thanks!
> I did not receive it the v3, not sure you sent it? Just want to check whether
> I missed it or not.
Oops, thanks for the reminder. I believe I had sent it, but indeed, no!
Done now.
Thanks
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com/
prev parent reply other threads:[~2024-12-18 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 10:44 [PATCH v2 0/3] Improvements to "bmaptool" usage documentation michael.opdenacker
2024-12-04 10:44 ` [PATCH v2 1/3] dev-manual: fix styling of references to bmaptool michael.opdenacker
2024-12-04 10:44 ` [PATCH v2 2/3] dev-manual/bmaptool.rst: correct command for bmaptool-native michael.opdenacker
2024-12-04 10:44 ` [PATCH v2 3/3] dev-manual/bmaptool.rst: simplify and fix instructions michael.opdenacker
2024-12-04 12:19 ` [docs] " Antonin Godard
2024-12-04 13:03 ` Michael Opdenacker
2024-12-18 9:35 ` Antonin Godard
2024-12-18 14:49 ` Michael Opdenacker [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=f34239d6-de6e-485d-8d30-9c09d8d22e97@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.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 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.