From: Denys Dmytriyenko <denis@denix.org>
To: Ryan Eatmon <reatmon@ti.com>
Cc: meta-ti@lists.yoctoproject.org, Denys Dmytriyenko <denys@konsulko.com>
Subject: Re: [meta-ti] [master/scarthgap][PATCH 1/4] conf/machine, ti-bsp: add support for multiple BSP providers
Date: Fri, 14 Jun 2024 12:34:23 -0400 [thread overview]
Message-ID: <20240614163423.GX21287@denix.org> (raw)
In-Reply-To: <f74e3a99-3dbc-4a68-b4b8-a5f77f6e149a@ti.com>
On Thu, Jun 13, 2024 at 04:18:16PM -0500, Ryan Eatmon wrote:
>
>
> On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko <denys@konsulko.com>
> >
> >This adds a facility to define multiple supported BSPs with their own
> >preferences for individual components, as well as lets machine configs
> >specify conditional configurations for different BSPs.
> >
> >Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
>
>
>
> >diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >new file mode 100644
> >index 00000000..3bb94a7f
> >--- /dev/null
> >+++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
> >@@ -0,0 +1,109 @@
> >+# Support multiple BSP providers
> >+# The main input is TI_DEFAULT_BSP, which translates into default
> >+# preferences for kernel, bootloader and graphics components, as
> >+# well as a dedicated machine override.
> >+
> >+# Supported options are: mainline, ti-6_6, ti-6_1, bb_org
> >+TI_DEFAULT_BSP ??= "ti-6_6"
>
> Should this variable be named TI_DEFAULT_BSP? That implies that
> this is the value of the default for this feature. But in reality
> this variable is what chooses the TI BSP version. Should it be
> something like TI_BSP_VERSION instead?
It's not just the version, it's entire BSP stack. E.g. "mainline" vs. "bb_org"
Initially I started with only 2 options - "ti" vs. "bb_org", but eventually
expanded it to support "mainline" and in case of "ti" also different LTS
versions - "ti-6_1" and "ti-6_6"... Hence the original name stayed. And not
sure how long both LTS versions will be supported in meta-ti...
Anyway, I'm fine changing it to something else, but I thing calling it
"version" will be more confusing.
--
Denys
next prev parent reply other threads:[~2024-06-14 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 17:22 [master/scarthgap][PATCH 1/4] conf/machine, ti-bsp: add support for multiple BSP providers Denys Dmytriyenko
2024-06-13 17:22 ` [master/scarthgap][PATCH 2/4] conf/machine/j721e: some BSPs don't support all SR and HS variants Denys Dmytriyenko
2024-06-14 10:20 ` [EXTERNAL] [meta-ti] " Limaye, Aniket
2024-06-14 16:38 ` Denys Dmytriyenko
2024-06-17 14:01 ` Limaye, Aniket
2024-06-17 15:48 ` Denys Dmytriyenko
2024-06-13 17:22 ` [master/scarthgap][PATCH 3/4] conf/machine/beagle*, linux-bb.org: update for multi-BSP support Denys Dmytriyenko
2024-06-13 17:22 ` [master/scarthgap][PATCH 4/4] conf/machine: use the default TI BSP for BeaglePlay Denys Dmytriyenko
2024-06-13 19:29 ` [meta-ti] [master/scarthgap][PATCH 1/4] conf/machine, ti-bsp: add support for multiple BSP providers Ryan Eatmon
2024-06-13 19:47 ` Denys Dmytriyenko
2024-06-13 21:09 ` Ryan Eatmon
2024-06-14 17:20 ` Denys Dmytriyenko
2024-06-13 21:18 ` Ryan Eatmon
2024-06-14 6:27 ` [EXTERNAL] " Chirag Shilwant
2024-06-14 16:34 ` Denys Dmytriyenko [this message]
[not found] ` <17D8EC1D0CB8CAB1.25108@lists.yoctoproject.org>
2024-06-14 18:55 ` Denys Dmytriyenko
2024-06-14 19:29 ` Ryan Eatmon
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=20240614163423.GX21287@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--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.