From: Oleh Kravchenko <oleg@kaa.org.ua>
To: Angus Ainslie <angus@akkea.ca>
Cc: u-boot@lists.denx.de, Sean Anderson <seanga2@gmail.com>,
Simon Glass <sjg@chromium.org>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Roman Stratiienko <r.stratiienko@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH 0/2] Add more support for NXP's mfgtool
Date: Sat, 18 Dec 2021 23:52:43 +0200 [thread overview]
Message-ID: <9e66f1cb-edb4-61ec-0cda-e48d2bff4c5a@kaa.org.ua> (raw)
In-Reply-To: <531dc80bb5b4812a1ecc45d0fe7848bd@akkea.ca>
18.12.21 16:34, Angus Ainslie пише:
> Hi Oleh
>
> On 2021-12-18 00:44, Oleh Kravchenko wrote:
>> Hello Angus!
>> What is the use-case for these patches?
>>
>> Would you mind defining why the current implementation is not enough?
>> Used like that:
>>> FB: flash -raw2sparse mmc0 emmc.wic
>>
>>
>
> Thanks, it looks like the way I'm using fastboot is causing the issue.
>
> FB: ucmd setenv fastboot_dev mmc
> FB: ucmd setenv mmcdev 0
> FB: flash -raw2sparse all <image>
>
> using your syntax I likely won't need these patches.
Just make sure you have these configs enabled:
> CONFIG_FASTBOOT_MMC_USER_SUPPORT=y
> CONFIG_FASTBOOT_MMC_BOOT_SUPPORT=y # enable this if you planning flash boot area too
> FB: flash -raw2sparse mmc0 <image>
>
> Cheers
> Angus
--
Best regards,
Oleh Kravchenko
prev parent reply other threads:[~2021-12-18 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:41 [PATCH 0/2] Add more support for NXP's mfgtool Angus Ainslie
2021-12-17 15:41 ` [PATCH 1/2] fastboot: fb_getvar: Add getvar_logical_blocksize for MXP mfgtool Angus Ainslie
2021-12-17 23:10 ` Sean Anderson
2021-12-19 15:25 ` Angus Ainslie
2021-12-17 15:42 ` [PATCH 2/2] fastboot: fb_mmc: Add mfgtool all partition size Angus Ainslie
2021-12-17 23:02 ` Sean Anderson
2021-12-18 8:44 ` [PATCH 0/2] Add more support for NXP's mfgtool Oleh Kravchenko
2021-12-18 14:34 ` Angus Ainslie
2021-12-18 21:52 ` Oleh Kravchenko [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=9e66f1cb-edb4-61ec-0cda-e48d2bff4c5a@kaa.org.ua \
--to=oleg@kaa.org.ua \
--cc=angus@akkea.ca \
--cc=m.szyprowski@samsung.com \
--cc=patrick.delaunay@foss.st.com \
--cc=r.stratiienko@gmail.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).