From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago][master/kirkstone][PATCH v3] branding-ltsprep: LTS migration brand
Date: Fri, 31 Mar 2023 16:25:56 -0400 [thread overview]
Message-ID: <20230331202556.GH18050@denix.org> (raw)
In-Reply-To: <20230331191713.13675-1-reatmon@ti.com>
On Fri, Mar 31, 2023 at 02:17:13PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> Add a new brand to control picking the next LTS version of kernel and
> u-boot while they are under development.
>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> v3: Change u-boot version to 2023.04
> v2: Make the versions wildcarded so that they actually match...
>
> .../conf/distro/include/branding-ltsprep.inc | 11 +++++++++++
> 1 file changed, 11 insertions(+)
> create mode 100644 meta-arago-distro/conf/distro/include/branding-ltsprep.inc
>
> diff --git a/meta-arago-distro/conf/distro/include/branding-ltsprep.inc b/meta-arago-distro/conf/distro/include/branding-ltsprep.inc
> new file mode 100644
> index 00000000..a944bcdf
> --- /dev/null
> +++ b/meta-arago-distro/conf/distro/include/branding-ltsprep.inc
> @@ -0,0 +1,11 @@
> +
> +PREFERRED_VERSION_linux-ti-staging = "6.1%"
> +PREFERRED_VERSION_linux-ti-staging-rt = "6.1%"
> +PREFERRED_VERSION_linux-ti-staging-systest = "6.1%"
> +PREFERRED_VERSION_u-boot-ti-staging = "2023.04%"
> +
> +# GPU support requires out-of-tree SGX and RGX drivers not available in until
> +# LTS prep is complete. fall back to software rendering
> +MACHINE_FEATURES:remove = "gpu"
> +PREFERRED_PROVIDER_virtual/gpudriver = ""
> +
> --
> 2.17.1
prev parent reply other threads:[~2023-03-31 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 19:17 [meta-arago][master/kirkstone][PATCH v3] branding-ltsprep: LTS migration brand Ryan Eatmon
2023-03-31 20:25 ` Denys Dmytriyenko [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=20230331202556.GH18050@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
/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.