From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Andrei Lalaev <andrey.lalaev@gmail.com>, s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] common: fastboot: send FAIL if variable does not exist
Date: Tue, 22 Jul 2025 17:55:44 +0200 [thread overview]
Message-ID: <bca1e5e8-c70e-4b2b-8383-85bcea2f71bb@pengutronix.de> (raw)
In-Reply-To: <8258cc5e-4223-4777-9c45-3feb6acba793@gmail.com>
Hello Andrei,
On 7/22/25 17:53, Andrei Lalaev wrote:
> On 22.07.2025 16:07, Ahmad Fatoum wrote:
>> Hello Andrei,
>>
>> On 6/11/25 19:56, Andrei Lalaev wrote:
>>> According to doc [1], new implementations should send FAIL if the
>>> variable specified in the getvar command does not exist.
>>>
>>> [1]: https://android.googlesource.com/platform/system/core/+show/refs/heads/main/fastboot/README.md#121
>>>
>>> Signed-off-by: Andrei Lalaev <andrey.lalaev@gmail.com>
>>
>> Did you run into any particular issues that motivated your change?
>
> Hi Ahmad,
>
> Sorry, I should have written a more descriptive commit message
> or at least mentioned the root cause in the footer.
>
> I was using uuu v1.5.201 with barebox 2025.01 (or 2025.02) to flash
> a raw image to eMMC using the raw2flash flag. Unfortunately,
> due to a bug in uuu, it ended up flashing garbage :/
> I’ve fixed the issue in uuu [1], but during the investigation
> I found out that newer implementation of Fastboot should send FAIL
> if variable is missing, so I also decided to send a patch to barebox.
Ah, I only used SDP/SDPS uuu so far and the dedicated fastboot utility
for fastboot instead.
Good to know that it works with barebox (now). Thanks.
Cheers,
Ahmad
>
> 1 - https://github.com/nxp-imx/mfgtools/commit/f7351c1cf626764d902576362421f33b79b3a9e9
>
>>
>> Thanks,
>> Ahmad
>>
>
--
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 |
prev parent reply other threads:[~2025-07-22 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 17:56 Andrei Lalaev
2025-06-12 8:08 ` Sascha Hauer
2025-06-12 14:19 ` Andrei Lalaev
2025-06-23 14:04 ` Sascha Hauer
2025-06-17 6:54 ` Sascha Hauer
2025-07-22 14:07 ` Ahmad Fatoum
2025-07-22 15:53 ` Andrei Lalaev
2025-07-22 15:55 ` Ahmad Fatoum [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=bca1e5e8-c70e-4b2b-8383-85bcea2f71bb@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=andrey.lalaev@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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