mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>,
	Robin van der Gracht <robin@protonic.nl>
Subject: Re: [PATCH] scripts: rk-usb-loader: push header first
Date: Thu, 12 Mar 2026 15:02:55 +0100	[thread overview]
Message-ID: <abLHj5secNSDzje1@pengutronix.de> (raw)
In-Reply-To: <abFAW56rE6Pr6xIz@pengutronix.de>

On Wed, Mar 11, 2026 at 11:13:47AM +0100, Michael Tretter wrote:
> On Wed, 11 Mar 2026 11:03:47 +0100, Sascha Hauer wrote:
> > From: Michael Tretter <m.tretter@pengutronix.de>
> > 
> > Board that have secure boot enabled need the image header to be able
> > to verify the signature. Boards with secure boot disabled still work
> > with this patch as tested on a RK3588 board.
> 
> I'm not against adding this to the rk-usb-loader, but maybe add some
> comment that this change is based on a wild guess and works by chance. I
> still don't know, how the ROM code or the USB protocol works and if it
> is really correct or necessary to send the entire header.

I can add a comment. FWIW I found another project [1] for a rk-usb-loader
which does exactly the same.

[1] https://github.com/DualTachyon/rk3588-tools/blob/main/rk-usb.c#L117

Sascha

-- 
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 |



  parent reply	other threads:[~2026-03-12 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 10:03 Sascha Hauer
2026-03-11 10:13 ` Michael Tretter
2026-03-12  8:29   ` Robin van der Gracht
2026-03-12 14:02   ` Sascha Hauer [this message]
2026-03-13 14:20 ` Sascha Hauer

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=abLHj5secNSDzje1@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.tretter@pengutronix.de \
    --cc=robin@protonic.nl \
    /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