All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angus Ainslie <angus@akkea.ca>
To: sean.anderson@seco.com, Oleh Kravchenko <oleg@kaa.org.ua>,
	u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
	Patrick Delaunay <patrick.delaunay@foss.st.com>,
	Roman Stratiienko <r.stratiienko@gmail.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	kernel@puri.sm, Angus Ainslie <angus@akkea.ca>
Subject: [PATCH v2 0/1] Add more support for NXP's mfgtool
Date: Sun, 19 Dec 2021 08:15:15 -0800	[thread overview]
Message-ID: <20211219161516.118636-1-angus@akkea.ca> (raw)

NXP's mfgtool needs to query the block size for sparse image upload

Changes since v1:

* Dropped the "all" parition type patch
* Added more detail to the patch commit message
* Only define getvar_logical_blocksize when FASTBOOT_FLASH_MMC is defined
* Combined fb_get_block_size into getvar_logical_blocksize
* Fixed fastboot returned error message

Angus Ainslie (1):
  fastboot: fb_getvar: Add getvar_logical_blocksize for NXP mfgtool

 drivers/fastboot/fb_getvar.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

-- 
2.25.1


             reply	other threads:[~2021-12-19 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 16:15 Angus Ainslie [this message]
2021-12-19 16:15 ` [PATCH v2 1/1] fastboot: fb_getvar: Add getvar_logical_blocksize for NXP mfgtool Angus Ainslie
2021-12-28 16:59   ` Sean Anderson
2021-12-29 13:35     ` Angus Ainslie
2021-12-29 15:07       ` Oleh Kravchenko
2021-12-29 15:15         ` Angus Ainslie
2021-12-30 16:21       ` Sean Anderson
2022-01-03 13:27         ` Angus Ainslie
2022-01-04 16:22           ` Sean Anderson

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=20211219161516.118636-1-angus@akkea.ca \
    --to=angus@akkea.ca \
    --cc=kernel@puri.sm \
    --cc=m.szyprowski@samsung.com \
    --cc=oleg@kaa.org.ua \
    --cc=patrick.delaunay@foss.st.com \
    --cc=r.stratiienko@gmail.com \
    --cc=sean.anderson@seco.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 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.