[dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration

[dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration

[Dan Murphy]

Add a core-next brand branding type to be able to re-direct the recipe
preferred providers or versions to highest PV'd recipe. The
branding-core should indicate the current version to build if not the
highest version.

For the purpose of an example the Arago distribution will be migrating
from the 5.4 kernel to the 5.10 during the 2021 time frame.  In order to
assist with a smoother migration the distribution needs to be able to
build the 5.4 kernel for the core brand and build the 5.10 kernel for
the core-next.

Once the transition from 5.4->5.10 kernel is done then the
PREFERRED_VERSION in the branding-core.inc can be removed.

From: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
 .../conf/distro/include/branding-core-next.inc              | 6 ++++++
 meta-arago-distro/conf/distro/include/branding-core.inc     | 3 +++
 2 files changed, 9 insertions(+)
 create mode 100644 meta-arago-distro/conf/distro/include/branding-core-next.inc

diff --git a/meta-arago-distro/conf/distro/include/branding-core-next.inc b/meta-arago-distro/conf/distro/include/branding-core-next.inc
new file mode 100644
index 000000000000..d65c5db2f379
--- /dev/null
+++ b/meta-arago-distro/conf/distro/include/branding-core-next.inc
@@ -0,0 +1,6 @@
+# Special "migration" branding for testing components that are to be updated in LTS migration
+
+require branding-core.inc
+
+PREFERRED_VERSION_linux-ti-staging = ""
+PREFERRED_VERSION_u-boot-ti-staging = ""
diff --git a/meta-arago-distro/conf/distro/include/branding-core.inc b/meta-arago-distro/conf/distro/include/branding-core.inc
index cab9831be9f9..a0abc6230780 100644
--- a/meta-arago-distro/conf/distro/include/branding-core.inc
+++ b/meta-arago-distro/conf/distro/include/branding-core.inc
@@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
 
 # Raise priority for sample IPC FW images
 ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15"
+
+PREFERRED_VERSION_linux-ti-staging = "5.4%"
+PREFERRED_VERSION_u-boot-ti-staging = "2020.01%"
-- 
2.29.2

Re: [dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration

[Denys Dmytriyenko]

On Thu, Jan 14, 2021 at 10:47:43AM -0600, Dan Murphy wrote:
> Add a core-next brand branding type to be able to re-direct the recipe
> preferred providers or versions to highest PV'd recipe. The
> branding-core should indicate the current version to build if not the
> highest version.
> 
> For the purpose of an example the Arago distribution will be migrating
> from the 5.4 kernel to the 5.10 during the 2021 time frame.  In order to
> assist with a smoother migration the distribution needs to be able to
> build the 5.4 kernel for the core brand and build the 5.10 kernel for
> the core-next.
> 
> Once the transition from 5.4->5.10 kernel is done then the
> PREFERRED_VERSION in the branding-core.inc can be removed.
> 
> From: Dan Murphy <dmurphy@ti.com>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>  .../conf/distro/include/branding-core-next.inc              | 6 ++++++
>  meta-arago-distro/conf/distro/include/branding-core.inc     | 3 +++
>  2 files changed, 9 insertions(+)
>  create mode 100644 meta-arago-distro/conf/distro/include/branding-core-next.inc
> 
> diff --git a/meta-arago-distro/conf/distro/include/branding-core-next.inc b/meta-arago-distro/conf/distro/include/branding-core-next.inc
> new file mode 100644
> index 000000000000..d65c5db2f379
> --- /dev/null
> +++ b/meta-arago-distro/conf/distro/include/branding-core-next.inc
> @@ -0,0 +1,6 @@
> +# Special "migration" branding for testing components that are to be updated in LTS migration
> +
> +require branding-core.inc
> +
> +PREFERRED_VERSION_linux-ti-staging = ""
> +PREFERRED_VERSION_u-boot-ti-staging = ""
> diff --git a/meta-arago-distro/conf/distro/include/branding-core.inc b/meta-arago-distro/conf/distro/include/branding-core.inc
> index cab9831be9f9..a0abc6230780 100644
> --- a/meta-arago-distro/conf/distro/include/branding-core.inc
> +++ b/meta-arago-distro/conf/distro/include/branding-core.inc
> @@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
>  
>  # Raise priority for sample IPC FW images
>  ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15"
> +
> +PREFERRED_VERSION_linux-ti-staging = "5.4%"

Should also include linux-ti-staging-rt and linux-ti-staging-systest


> +PREFERRED_VERSION_u-boot-ti-staging = "2020.01%"
> -- 
> 2.29.2
> 

Re: [dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration

[Dan Murphy]

Denys

On 1/14/21 12:24 PM, Denys Dmytriyenko wrote:
> On Thu, Jan 14, 2021 at 10:47:43AM -0600, Dan Murphy wrote:
>> Add a core-next brand branding type to be able to re-direct the recipe
>> preferred providers or versions to highest PV'd recipe. The
>> branding-core should indicate the current version to build if not the
>> highest version.
>>
>> For the purpose of an example the Arago distribution will be migrating
>> from the 5.4 kernel to the 5.10 during the 2021 time frame.  In order to
>> assist with a smoother migration the distribution needs to be able to
>> build the 5.4 kernel for the core brand and build the 5.10 kernel for
>> the core-next.
>>
>> Once the transition from 5.4->5.10 kernel is done then the
>> PREFERRED_VERSION in the branding-core.inc can be removed.
>>
>> From: Dan Murphy <dmurphy@ti.com>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>>   .../conf/distro/include/branding-core-next.inc              | 6 ++++++
>>   meta-arago-distro/conf/distro/include/branding-core.inc     | 3 +++
>>   2 files changed, 9 insertions(+)
>>   create mode 100644 meta-arago-distro/conf/distro/include/branding-core-next.inc
>>
>> diff --git a/meta-arago-distro/conf/distro/include/branding-core-next.inc b/meta-arago-distro/conf/distro/include/branding-core-next.inc
>> new file mode 100644
>> index 000000000000..d65c5db2f379
>> --- /dev/null
>> +++ b/meta-arago-distro/conf/distro/include/branding-core-next.inc
>> @@ -0,0 +1,6 @@
>> +# Special "migration" branding for testing components that are to be updated in LTS migration
>> +
>> +require branding-core.inc
>> +
>> +PREFERRED_VERSION_linux-ti-staging = ""
>> +PREFERRED_VERSION_u-boot-ti-staging = ""
>> diff --git a/meta-arago-distro/conf/distro/include/branding-core.inc b/meta-arago-distro/conf/distro/include/branding-core.inc
>> index cab9831be9f9..a0abc6230780 100644
>> --- a/meta-arago-distro/conf/distro/include/branding-core.inc
>> +++ b/meta-arago-distro/conf/distro/include/branding-core.inc
>> @@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
>>   
>>   # Raise priority for sample IPC FW images
>>   ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15"
>> +
>> +PREFERRED_VERSION_linux-ti-staging = "5.4%"
> Should also include linux-ti-staging-rt and linux-ti-staging-systest
>
Thanks I will add them in v2

Do you see anything wrong with this approach?

Dan

Re: [dunfell/master] [RFC PATCH] branding: Add branding-core-next to aid in migration

[Denys Dmytriyenko]

On Thu, Jan 14, 2021 at 12:46:01PM -0600, Dan Murphy wrote:
> Denys
> 
> On 1/14/21 12:24 PM, Denys Dmytriyenko wrote:
> >On Thu, Jan 14, 2021 at 10:47:43AM -0600, Dan Murphy wrote:
> >>Add a core-next brand branding type to be able to re-direct the recipe
> >>preferred providers or versions to highest PV'd recipe. The
> >>branding-core should indicate the current version to build if not the
> >>highest version.
> >>
> >>For the purpose of an example the Arago distribution will be migrating
> >>from the 5.4 kernel to the 5.10 during the 2021 time frame.  In order to
> >>assist with a smoother migration the distribution needs to be able to
> >>build the 5.4 kernel for the core brand and build the 5.10 kernel for
> >>the core-next.
> >>
> >>Once the transition from 5.4->5.10 kernel is done then the
> >>PREFERRED_VERSION in the branding-core.inc can be removed.
> >>
> >>From: Dan Murphy <dmurphy@ti.com>
> >>Signed-off-by: Dan Murphy <dmurphy@ti.com>
> >>---
> >>  .../conf/distro/include/branding-core-next.inc              | 6 ++++++
> >>  meta-arago-distro/conf/distro/include/branding-core.inc     | 3 +++
> >>  2 files changed, 9 insertions(+)
> >>  create mode 100644 meta-arago-distro/conf/distro/include/branding-core-next.inc
> >>
> >>diff --git a/meta-arago-distro/conf/distro/include/branding-core-next.inc b/meta-arago-distro/conf/distro/include/branding-core-next.inc
> >>new file mode 100644
> >>index 000000000000..d65c5db2f379
> >>--- /dev/null
> >>+++ b/meta-arago-distro/conf/distro/include/branding-core-next.inc
> >>@@ -0,0 +1,6 @@
> >>+# Special "migration" branding for testing components that are to be updated in LTS migration
> >>+
> >>+require branding-core.inc
> >>+
> >>+PREFERRED_VERSION_linux-ti-staging = ""
> >>+PREFERRED_VERSION_u-boot-ti-staging = ""
> >>diff --git a/meta-arago-distro/conf/distro/include/branding-core.inc b/meta-arago-distro/conf/distro/include/branding-core.inc
> >>index cab9831be9f9..a0abc6230780 100644
> >>--- a/meta-arago-distro/conf/distro/include/branding-core.inc
> >>+++ b/meta-arago-distro/conf/distro/include/branding-core.inc
> >>@@ -11,3 +11,6 @@ ALTERNATIVE_PRIORITY_pn-opencl-monitor-ipu = "1"
> >>  # Raise priority for sample IPC FW images
> >>  ALTERNATIVE_PRIORITY_pn-ti-ipc-rtos = "15"
> >>+
> >>+PREFERRED_VERSION_linux-ti-staging = "5.4%"
> >Should also include linux-ti-staging-rt and linux-ti-staging-systest
> >
> Thanks I will add them in v2
> 
> Do you see anything wrong with this approach?

In general, looks good to me.

-- 
Denys