mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Robin van der Gracht <robin@protonic.nl>
Subject: Re: [PATCH 0/6] ARM: Rockchip: fix OP-TEE as BL32 installation
Date: Fri, 08 Nov 2024 11:20:26 +0100	[thread overview]
Message-ID: <173106122637.2306089.11349967618608085808.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20241106185724.2526-1-a.fatoum@pengutronix.de>


On Wed, 06 Nov 2024 19:57:18 +0100, Ahmad Fatoum wrote:
> This series resulted while getting OP-TEE to work on RK3399.
> There is no upstream OP-TEE support for the RK3568 or RK3588,
> but the expectation that loading the blob is analogous to the
> RK3399, which is fixed by this series.
> 
> Ahmad Fatoum (6):
>   firmware: rockchip: rename from rk3xxx-op-tee.bin to rk3xxx-bl32.bin
>   ARM: lds: move stack top section to front of rodata
>   ARM: Rockchip: fix clang warning about passing 32-bit register operand
>   ARM: Rockchip: save pointer to scratch memory in global variable
>   ARM: Rockchip: implement tee.bin v1 header parsing
>   ARM: Rockchip: use vendor blob OPTEE load addresses
> 
> [...]

Applied, thanks!

[1/6] firmware: rockchip: rename from rk3xxx-op-tee.bin to rk3xxx-bl32.bin
      https://git.pengutronix.de/cgit/barebox/commit/?id=c8d797dad31a (link may not be stable)
[2/6] ARM: lds: move stack top section to front of rodata
      https://git.pengutronix.de/cgit/barebox/commit/?id=3def2f136aea (link may not be stable)
[3/6] ARM: Rockchip: fix clang warning about passing 32-bit register operand
      https://git.pengutronix.de/cgit/barebox/commit/?id=9cd71fc171b6 (link may not be stable)
[4/6] ARM: Rockchip: save pointer to scratch memory in global variable
      https://git.pengutronix.de/cgit/barebox/commit/?id=73a2b3c8d293 (link may not be stable)
[5/6] ARM: Rockchip: implement tee.bin v1 header parsing
      https://git.pengutronix.de/cgit/barebox/commit/?id=e1ecb0bdeeed (link may not be stable)
[6/6] ARM: Rockchip: use vendor blob OPTEE load addresses
      https://git.pengutronix.de/cgit/barebox/commit/?id=d857e9ea91fd (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-11-08 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 18:57 Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 1/6] firmware: rockchip: rename from rk3xxx-op-tee.bin to rk3xxx-bl32.bin Ahmad Fatoum
2024-11-06 22:13   ` [PATCH] fixup! " Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 2/6] ARM: lds: move stack top section to front of rodata Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 3/6] ARM: Rockchip: fix clang warning about passing 32-bit register operand Ahmad Fatoum
2024-11-07  8:42   ` Marco Felsch
2024-11-07  8:48     ` Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 4/6] ARM: Rockchip: save pointer to scratch memory in global variable Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 5/6] ARM: Rockchip: implement tee.bin v1 header parsing Ahmad Fatoum
2024-11-06 18:57 ` [PATCH 6/6] ARM: Rockchip: use vendor blob OPTEE load addresses Ahmad Fatoum
2024-11-08 10:20 ` Sascha Hauer [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=173106122637.2306089.11349967618608085808.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --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