From: Trevor Woerner <twoerner@gmail.com>
To: yocto-patches@lists.yoctoproject.org
Subject: Re: [meta-rockchip][PATCH v2 4/4] rk3308: add provider for trusted firmware-a
Date: Sun, 15 Dec 2024 22:47:04 -0500 [thread overview]
Message-ID: <20241216034704.GA466@localhost> (raw)
In-Reply-To: <20241213154843.27592-4-twoerner@gmail.com>
On Fri 2024-12-13 @ 10:48:43 AM, Trevor Woerner wrote:
> A PREFERRED_PROVIDER entry was missed for rk3308 builds:
>
> NOTE: Multiple providers are available for trusted-firmware-a (rk3308-rkbin, rockchip-rkbin-tf-a)
> Consider defining a PREFERRED_PROVIDER entry to match trusted-firmware-a
>
> This allows the RKBIN_RK3308_LATEST knob to work in all cases again.
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> changes from v1
> - added
> ---
> conf/machine/include/rk3308.inc | 1 +
> 1 file changed, 1 insertion(+)
Added to meta-rockchip, branches master and styhead.
next prev parent reply other threads:[~2024-12-16 3:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 15:48 [meta-rockchip][PATCH v2 1/4] u-boot: switch to upstream SRCREV for rk-u-boot-env Trevor Woerner
2024-12-13 15:48 ` [meta-rockchip][PATCH v2 2/4] u-boot: use upstream for radxa-zero-3{e|w} Trevor Woerner
2024-12-15 17:28 ` [yocto-patches] " Oleksii Kurochko
2024-12-15 21:23 ` Trevor Woerner
2024-12-13 15:48 ` [meta-rockchip][PATCH v2 3/4] radxa-zero-3: switch to yocto-dev kernel Trevor Woerner
2024-12-15 17:29 ` [yocto-patches] " Oleksii Kurochko
2024-12-13 15:48 ` [meta-rockchip][PATCH v2 4/4] rk3308: add provider for trusted firmware-a Trevor Woerner
2024-12-13 16:28 ` [yocto-patches] " Quentin Schulz
2024-12-13 17:11 ` Trevor Woerner
2024-12-13 17:29 ` Quentin Schulz
2024-12-16 3:47 ` Trevor Woerner [this message]
2024-12-13 16:19 ` [yocto-patches] [meta-rockchip][PATCH v2 1/4] u-boot: switch to upstream SRCREV for rk-u-boot-env Quentin Schulz
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=20241216034704.GA466@localhost \
--to=twoerner@gmail.com \
--cc=yocto-patches@lists.yoctoproject.org \
/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.