On Tue, Nov 05, 2024 at 02:24:40PM -0600, Ryan Eatmon wrote:
>
>
> On 11/5/2024 1:10 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko
> >
> >The new meta-beagle will host all supported Beagle platforms that
> >use TI SoCs and hence need to depend on me
From: Denys Dmytriyenko
Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and
move them to own beagleplay machine config in meta-beagle.
The differences between 2 configs are minimal, hence beagleplay in meta-beagle
inherits beagleplay-ti from meta-ti-bsp as
From: Denys Dmytriyenko
Include beagle-bsp.inc to define "bb_org" BSP settings and select that
as a default.
Signed-off-by: Denys Dmytriyenko
---
{meta-ti-bsp => meta-beagle}/conf/machine/beagle-x15.conf | 3 +--
.../conf/machine/beaglebone-ai64-k3r5.conf
From: Denys Dmytriyenko
The new meta-beagle will host all supported Beagle platforms that
use TI SoCs and hence need to depend on meta-ti-bsp. The default
BSP for the platforms in this layer will use BeagleBoard.org
official trees for the Linux kernel and U-boot.
Signed-off-by: Denys
From: Denys Dmytriyenko
Move "bb_org" kernel and U-boot providers that use corresponding official
BeagleBoard.org trees into own meta-beagle layer.
Signed-off-by: Denys Dmytriyenko
---
.../recipes-bsp/u-boot/u-boot-bb.org_git.bb | 2 +-
.../0001-blk-iocost-av
From: Denys Dmytriyenko
Define "bb_org" default BSP settings in meta-beagle layer that all Beagle
platforms will use.
Signed-off-by: Denys Dmytriyenko
---
.../conf/machine/include/beagle-bsp.inc | 24 +++
meta-ti-bsp/conf/machine/include/ti-bsp.
From: Denys Dmytriyenko
BeaglePlay is officially supported by TI "ti-6_6" BSP and is part
of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org"
settings for the same machine is possible within the same layer.
But having different machine configs for the same mach
On Thu, Oct 31, 2024 at 03:49:55PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> PREFERRED_VERSION matches against the PV in the recipe, not against the
> file name. With the upcoming 6.12, the 6.1 kernel version string was a
> little too loose. The "6.1%" could glob onto the 6.12 recipe
On Thu, Oct 31, 2024 at 06:47:43PM -0500, r...@ti.com wrote:
> From: Randolph Sapp
>
> Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
> 6.6 and the same version of mesa rogue is using right now (23.2.1).
> These commits are currently compatible with both kernel 6.1 and 6.6
I don't think you need bsp-overrides anymore...
On Thu, Oct 17, 2024 at 02:08:25PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> It was suggested to move the reproducibility patches out of
> ti-kernel.inc and into the respective recipes. Take this time to also
> rename the variable bei
On Wed, Oct 16, 2024 at 04:35:17PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
>
> On 10/16/2024 2:51 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 10/14/2024 3:27 PM, Sergio Prado wrote:
> >>Use weak assignment to make it possible to override the default
> >>value v
From: Denys Dmytriyenko
The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files
From: Denys Dmytriyenko
The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files
On Wed, Oct 09, 2024 at 08:51:30AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
> I thought of this in the middle of the night and realized it was a
> simpler fix. Rather than create the extra variable and have to set
> it in all of the BSPs, just add two new PREFERRED_VERSION settings
Same comment with --find-copies-harder, although the recipe itself is quite
smalle, so the diff could even be larger...
On Fri, Oct 04, 2024 at 10:18:55AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Adding needed recipe for initial testing and development of the 2024.10
> version of
This might have been easier to review with --find-copies-harder flag...
And I was wondering if setting KERNEL_PATCHES would be cleaner in the
corresponding recipes, instead of globally in ti-kernel.inc?
On Fri, Oct 04, 2024 at 10:18:54AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> A
On Fri, Oct 04, 2024 at 10:18:56AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Add new BSP for the 6.12 kernel and u-boot 2024.10 versions.
>
> Signed-off-by: Ryan Eatmon
> ---
> meta-ti-bsp/conf/machine/include/ti-bsp.inc | 15 ++-
> 1 file changed, 14 insertions(+), 1 d
I was wondering if OPTEE and TFA should also be made BSP-aware. Maybe even
SYSFW and/or other FWs.
How much backward compatibility is ensured and tested here? Will 4.3.0 version
here work with BSP 6.1?
On Fri, Oct 04, 2024 at 02:08:25PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> U
NAK
This does not make any sense. The subject says DEPLOYDIR, then you add
INSTALL_DM_FW_DIR (that is ${nonarch_base_libdir}/firmware/${DM_FW_DIR})
to FILES, which has nothing to do with do_deploy, only do_install.
Moreover, ti-dm-fw.bb includes ti-linux-fw.inc, which already sets FILES
to inc
On Tue, Aug 27, 2024 at 05:14:07PM -0500, Ryan Eatmon wrote:
>
>
> On 8/27/2024 5:08 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 8/27/2024 2:38 PM, Denys Dmytriyenko wrote:
> >>On Fri, Aug 16, 2024 at 01:53:07PM -0500, Ryan Eatmon
On Fri, Aug 16, 2024 at 01:53:07PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> From: Kamlesh Gurudasani
>
> Update to latest release tag, i.e. v2.11.
>
> Also update the LIC_FILES_CHKSUM since the license file changed since
> the last SRCREV change.
Changed in what way? It is recomm
or-for-llvm.patch
> | ...
>
> Signed-off-by: Max Krummenacher
Tested-by: Denys Dmytriyenko
> ---
> CC: Randolph Sapp
> meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 1 +
> meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_23.2.1.bb | 1 +
> 2 files changed, 2 insertions(
From: Denys Dmytriyenko
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko
---
.../recipes-ti/openmp-rtos/openmp-rtos_git.bb | 62 ---
1 file changed, 62
On Thu, Aug 08, 2024 at 12:17:45PM -0500, Andrew Davis wrote:
> On 8/4/24 11:36 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko
> >
> >Remove openmp-rtos component as deprecated and not maintained.
> >
> >This used to provide OpenMP DSP runtime components
From: Denys Dmytriyenko
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko
---
.../recipes-ti/openmp-rtos/openmp-rtos_git.bb | 62 ---
1 file changed, 62
On Sun, Aug 04, 2024 at 05:15:09PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Update the entry for KERNEL_DEVICETREE to match what is in the 6.10
> kernel.
Will this change work with 6.6 (or even 6.1)?
> Signed-off-by: Ryan Eatmon
> ---
> meta-ti-bsp/conf/machine/omapl138-lcdk.con
On Fri, Jul 19, 2024 at 10:10:18AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Applying the patches to all kernels is not going to work. Each kernel
> might need different patches to address reproducibility issues.
Can you also backport this to scarthgap, as these patches fon't apply
On Sat, Jul 20, 2024 at 02:02:01PM -0400, Denys Dmytriyenko wrote:
> On Fri, Jul 19, 2024 at 03:36:03PM -0500, Ryan Eatmon via
> lists.yoctoproject.org wrote:
> > The TI cl6x compiler does not have a mechanism for replacing paths in
> > the obj files it creates. So replace the
On Fri, Jul 19, 2024 at 03:36:03PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> The TI cl6x compiler does not have a mechanism for replacing paths in
> the obj files it creates. So replace the string we want to remove with
> an equally sized replacement string that does not contain the
On Fri, Jul 19, 2024 at 09:18:14AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
>
> On 7/19/2024 8:29 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> >
> >
> >On 7/18/2024 11:27 PM, Chirag Shilwant wrote:
> >>Hi Ryan,
> >>On 18/07/24 23:54, Ryan Eatmon via lists.yoctoproject.org wr
From: Denys Dmytriyenko
Installer log contains absolute paths and is not really needed.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb
b
From: Denys Dmytriyenko
These patches are not used anywhere now.
Signed-off-by: Denys Dmytriyenko
---
...s-Fix-build-for-upcoming-GCC-release.patch | 46
...ture-changes-causes-compile-failures.patch | 111 --
2 files changed, 157 deletions(-)
delete mode 100644
From: Denys Dmytriyenko
Add reproducibility patches from linux-yocto to resolve "buildpaths"
QA errors.
Signed-off-by: Denys Dmytriyenko
---
..._registry-fix-reproducibility-issues.patch | 46 +++
...-pnmtologo-use-relocatable-file-name.
From: Denys Dmytriyenko
Fix warning that S does not exist, since it defaults to ${WORKDIR}/${BP}
Signed-off-by: Denys Dmytriyenko
---
meta-ti-extras/recipes-ti/devtools/ti-cgt-pru_2.3.3.bb | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta-ti-extras/recipes-ti
On Tue, Jul 09, 2024 at 06:03:59PM +0530, Paresh Bhagat via
lists.yoctoproject.org wrote:
> Update SRCREV for jailhouse which incorporates makefile changes for
> scarthgap.
> Add ${ARAGO_IMAGE_SUFFIX} so that jailhouse can pick correct inmate
NAK - this is meta-ti, no Arago specifics here.
> im
Does this apply to master?
On Thu, Jun 27, 2024 at 02:04:28PM +0530, Vaishnav Achath via
lists.yoctoproject.org wrote:
> CSI2 connectivity of J721E SK, AM68 SK and AM69 SK is similar and
> the camera overlays can be reused, this series adds the necessary
> changes to pick the reused overlays acr
On Thu, Jun 20, 2024 at 03:40:22PM -0500, Sabeeh Khan via
lists.yoctoproject.org wrote:
>
> On 6/20/2024 3:20 PM, Denys Dmytriyenko wrote:
> >On Wed, Jun 19, 2024 at 10:21:59PM -0500, Sabeeh Khan via
> >lists.yoctoproject.org wrote:
> >>cc33conf is a tool provided by
On Mon, Jun 24, 2024 at 01:17:12PM -0500, r...@ti.com wrote:
> From: Randolph Sapp
>
> Resolve some issues afer the new bsp-provider selection logic was added and
> add
> some patches to help with compilation flag checks in the KM.
FWIW, the new bsp-provider selection logic was not causing any
On Thu, Jun 20, 2024 at 03:37:12PM -0500, Khan, Sabeeh wrote:
>
> On 6/20/2024 3:27 PM, Denys Dmytriyenko wrote:
> >On Wed, Jun 19, 2024 at 10:22:02PM -0500, Sabeeh Khan via
> >lists.yoctoproject.org wrote:
> >>[...]
> >>
> >>diff --git
> >&
From: Denys Dmytriyenko
Share the most commonality between the recipes, except:
* SRC_URI torvalds vs. linux-next
* SRCREV and PV
* Device Tree list vs. DT prefix
* SUMMARY
Signed-off-by: Denys Dmytriyenko
---
.../linux/linux-ti-mainline_git.bb| 19
From: Denys Dmytriyenko
The use of external metadata file to control RTOS binary firmware
integration has been deprecated some time ago. Remove it now.
Signed-off-by: Denys Dmytriyenko
---
.../recipes-ti/ti-rtos-bin/files/empty| 1 -
.../ti-rtos-bin/ti-rtos-metadata.bb | 47
On Wed, Jun 19, 2024 at 10:22:02PM -0500, Sabeeh Khan via
lists.yoctoproject.org wrote:
> Add scripts and conf files to be used to control and configure
> the cc33xx WLAN device. Documentation for these scripts can be found here:
> https://www.ti.com/tool/CC33XX-SOFTWARE
>
> Signed-off-by: Sabeeh
On Wed, Jun 19, 2024 at 10:22:00PM -0500, Sabeeh Khan via
lists.yoctoproject.org wrote:
> cc33calibrator is a tool provided by TI to manually control the
> radio frontend of the cc33xx device. This tool can also be used
> for production line testing of the radio.
> Documentation for this tool is p
On Wed, Jun 19, 2024 at 10:21:59PM -0500, Sabeeh Khan via
lists.yoctoproject.org wrote:
> cc33conf is a tool provided by TI to configure
> cc33xx WLAN devices. It can be used to change
> the RF parameters and other features of the target.
> Documentation for this tool is provided within the follow
On Wed, Jun 19, 2024 at 10:22:01PM -0500, Sabeeh Khan via
lists.yoctoproject.org wrote:
> Download and install the cc33xx firmware and binaries
> to be used with the cc33xx drivers.
>
> FW Version: 1.7.0.120
>
> Signed-off-by: Sabeeh Khan
> ---
> .../recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb|
From: Denys Dmytriyenko
Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 3 +++
1 file changed, 3
From: Denys Dmytriyenko
Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations
of SR1.0, SR2.0, HS-FS and HS-SE variants.
Suggested-by: Aniket Limaye
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/include/j7200.inc | 8 ++--
1 file changed, 6
On Mon, Jun 17, 2024 at 07:25:32PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
> Update am62xxsip-evm machine configuration to support
> TI kernel 6.1 & ti-u-boot-2023.04
>
> Signed-off-by: Chirag Shilwant
> ---
> v2: In commit message, s/ti-u-boot-2024.04/ti-u-boot-2023.04
Were am
On Mon, Jun 17, 2024 at 07:31:59PM +0530, Limaye, Aniket wrote:
>
> On 6/14/2024 10:08 PM, Denys Dmytriyenko wrote:
> >On Fri, Jun 14, 2024 at 03:50:14PM +0530, Aniket Limaye via
> >lists.yoctoproject.org wrote:
> >>Hi Denys,
> >>
> >>On 6/13/2024
On Mon, Jun 17, 2024 at 01:56:40PM +0530, Chirag Shilwant wrote:
> Hi Denys,
>
> On 14/06/24 22:11, Denys Dmytriyenko wrote:
> >On Fri, Jun 14, 2024 at 12:31:23PM +0530, Chirag Shilwant via
> >lists.yoctoproject.org wrote:
> >>Modify the U-Boot defconfig na
On Mon, Jun 17, 2024 at 02:03:51PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
> Update am62xxsip-evm machine configuration to support
> TI kernel 6.1 & ti-u-boot-2024.04
Should it be ti-u-boot-2023.04 here?
Otherwise looks good to me.
Do you know if there are any changes needed fo
From: Denys Dmytriyenko
Update all Beagle platform configurations to support multiple BSPs.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/beagle-x15.conf | 18 ++--
.../conf/machine/beaglebone-ai64-k3r5.conf| 8 +-
meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 23
From: Denys Dmytriyenko
Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/include/j721e.inc | 18 ++
1 file changed, 10 insertions(+), 8 deletions
From: Denys Dmytriyenko
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
---
v2 - rename TI_DEFAULT_BSP to
From: Denys Dmytriyenko
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.
And these defaults can still be changed with TI_PREFERRED_BSP setting in a
distro config or by end user in the local.conf
From: Denys Dmytriyenko
MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been
needed for quite some time. Let's finally remove it completely.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/include/k3.inc | 3 ---
meta-ti-bsp/co
On Fri, Jun 14, 2024 at 12:34:23PM -0400, Denys Dmytriyenko wrote:
> 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
> > >
> > >This adds a facil
On Thu, Jun 13, 2024 at 04:09:46PM -0500, Ryan Eatmon wrote:
>
>
> On 6/13/2024 2:47 PM, Denys Dmytriyenko wrote:
> >On Thu, Jun 13, 2024 at 02:29:34PM -0500, Ryan Eatmon wrote:
> >>
> >>
> >>On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
> >&
On Fri, Jun 14, 2024 at 12:31:23PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
> Modify the U-Boot defconfig names for A53 and R5
> machine configurations based on ti-u-boot-2024.04 [1]
>
> [1]:
> https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=df5181f8c6c
On Fri, Jun 14, 2024 at 03:50:14PM +0530, Aniket Limaye via
lists.yoctoproject.org wrote:
> Hi Denys,
>
> On 6/13/2024 10:52 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko Adjust
> >IMAGE_BOOT_FILES list as some BSPs do not support all combinations
> >of SR1.
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
> >
> >This adds a facility to define multiple supported BSPs with their own
> >preferences for individual components
Thanks Alexandre
And sorry this has taken longer than expected to get it fixed.
As I explained last time, we were holding until nanbield got EOL-ed in May,
since the component in question python3-yamllint was added to OE-Core since
scarthgap and meta-ti doesn't have a separate nanbield branch.
From: Denys Dmytriyenko
As nanbield has been EOL-ed recently.
Signed-off-by: Denys Dmytriyenko
---
TODO | 7 ---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
3 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/TODO b
From: Denys Dmytriyenko
This has been accepted to oe-core and is available in scarthgap and newer.
This reverts commit e9a56223ed04f9e0874177c5685db37a5eb6ea82.
Signed-off-by: Denys Dmytriyenko
---
.../python-yamllint/python3-yamllint_1.33.0.bb| 15 ---
1 file changed, 15
On Thu, Jun 13, 2024 at 02:29:34PM -0500, Ryan Eatmon wrote:
>
>
> On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko
> >
> >This adds a facility to define multiple supported BSPs with their own
> >preferences for individual components
From: Denys Dmytriyenko
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
---
meta-ti-bsp/conf/machine/beagleplay
From: Denys Dmytriyenko
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.
And these defaults can still be changed with TI_DEFAULT_BSP setting in a
distro config or by end user in the local.conf
From: Denys Dmytriyenko
Update all Beagle platform configurations to support multiple BSPs.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/beagle-x15.conf | 18 ++--
.../conf/machine/beaglebone-ai64-k3r5.conf| 8 +-
meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 23
From: Denys Dmytriyenko
Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants.
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/include/j721e.inc | 18 ++
1 file changed, 10 insertions(+), 8 deletions
On Thu, Jun 06, 2024 at 11:35:55AM +0530, Chirag Shilwant wrote:
> - From LTS scarthgap, the beagleplay yocto machine will by
> default build with TI baseline (i.e kernel 6.6 & U-Boot 2024.04 as of today).
> Hence, remove all the references of bb.org from machine configuration file.
>
> - Users ca
On Thu, Jun 06, 2024 at 02:37:46PM -0500, Randolph Sapp via
lists.yoctoproject.org wrote:
> On Thu Jun 6, 2024 at 11:02 AM CDT, Amol Practise wrote:
> > Hi Team,
> >
> > Any help would be appreciated on below issue.
> >
> > On Sun, Jun 2, 2024 at 12:40 PM Amol Practise via lists.yoctoproject.org
>
Oops, this is meant for master/scarthgap - forgot the branch tag, but sent the
updated version.
On Thu, Jun 06, 2024 at 03:47:56PM -0400, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko
>
> In order to be able to switch between different kernel providers, as well
> as different
From: Denys Dmytriyenko
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:
* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe fo
From: Denys Dmytriyenko
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:
* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe fo
On Mon, Jun 03, 2024 at 02:55:15PM -0500, r...@ti.com wrote:
> From: Randolph Sapp
>
> Lift the common parts of the top level gitignore from oe-core and
> meta-openembedded. This masks out temporary python files, intermediate
> artifacts, and patches at the root of the project.
FWIW, this is a m
From: Denys Dmytriyenko
* Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms
* Update DTB/DTBO lists to include latest renames and additions
* Re-enable vendored DTB layout by default
Signed-off-by: Denys Dmytriyenko
---
meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 1 +
meta
On Wed, May 22, 2024 at 07:06:25PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
> + Bryan for providing more details on the u-boot defconfig name
> change for am62xx-lp-evm
>
> On 22/05/24 18:46, Ryan Eatmon wrote:
> >
> >This changes make scarthgap and master incompatible with the
>
1. U-boot and SPL seem to be old from Dunfell
2. Check your env:
> append: root=PARTUUID= rootwait rw earlycon console=ttyO0,115200n8,115200
...
> [3.961253] VFS: PARTUUID= is invalid.
> [3.961253] Expected PARTUUID=[/PARTNROFF=%d]
> [3.970800] Disabling rootwait; root= is invalid.
>
On Thu, May 09, 2024 at 08:51:21AM -0500, Ryan Eatmon wrote:
>
>
> On 5/8/2024 3:42 PM, Randolph Sapp wrote:
> >On Thu May 2, 2024 at 2:45 PM CDT, Denys Dmytriyenko wrote:
> >>Can you make it a diff please? As shown previously, that helps with review
> >>an
On Wed, May 08, 2024 at 11:52:22PM +0200, Alexandre Belloni via
lists.yoctoproject.org wrote:
> Hello,
>
> meta-ti is currently failing check-layer-nightly:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/2063/steps/20/logs/stdio
Thanks, Alexandre,
This issue is master-s
Can you make it a diff please? As shown previously, that helps with review and
allows spotting issues much easier.
-M[]
--find-renames[=]
Detect renames. If n is specified, it is a threshold on the similarity index
(i.e. amount of addition/deletions compared to the file’s size). For example,
On Thu, May 02, 2024 at 12:49:13PM -0500, Randolph Sapp wrote:
> On Wed May 1, 2024 at 10:06 PM CDT, Denys Dmytriyenko wrote:
> > On Wed, May 01, 2024 at 08:26:21PM -0400, Denys Dmytriyenko wrote:
> > > From: Randolph Sapp
> > >
> > > Add a recipe for mesa-pvr
On Wed, May 01, 2024 at 08:26:21PM -0400, Denys Dmytriyenko wrote:
> From: Randolph Sapp
>
> Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
> This branch does not currently contain SGX patches so it is also being
> masked by the ltsprep branding to prevent r
Reformatted to be a diff against the previous version to spot the actual
changes and spot any issues. See below.
On Wed, May 01, 2024 at 08:26:19PM -0400, Denys Dmytriyenko wrote:
> From: Randolph Sapp
>
> Add these recipes but lock them behind ltsprep tags because they require
>
SIGGEN_EXCLUDERECIPES_ABISAFE you may run into sstate errors when
switching away from the ltsprep tag. Please issue a clean to mesa and
ti-img-rogue-umlibs if you get warnings from either package's
do_create_runtime_spdx step.
Signed-off-by: Randolph Sapp
Signed-off-by: Denys Dmytri
From: Randolph Sapp
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp
Signed-off-by: Denys Dmytriyenko
---
.../0001-gallium-Fix-build-with-llvm-17.patch | 41
From: Randolph Sapp
Add these recipes but lock them behind ltsprep tags because they require
device tree changes that does not work on the current default kernel for
this layer.
Signed-off-by: Randolph Sapp
Signed-off-by: Denys Dmytriyenko
---
6512818.bb => ti-img-ro
From: Ryan Eatmon
Reusing the j784s4.inc file presents problems as the am69-sk platform
does not support GP. So copy the j784s4.inc to am69.inc and update
accordingly.
Signed-off-by: Ryan Eatmon
Signed-off-by: Denys Dmytriyenko
---
No changes from the original patch, just formatted as copy
On Tue, Apr 30, 2024 at 04:38:21PM -0500, Randolph Sapp via
lists.yoctoproject.org wrote:
> From: Randolph Sapp
>
> Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
> This branch does not currently contain SGX patches so it is also being
> masked by the ltsprep branding to p
On Tue, Apr 30, 2024 at 02:58:11PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Reusing the j784s4.inc file presents problems as the am69-sk platform
> does not support GP. So copy the j784s4.inc to am69.inc and update
> accordingly.
Any chance to get this as a diff against j784s4.inc
Ryan,
Will you be able to pick up v2 of this? Thanks.
On Wed, Apr 24, 2024 at 12:46:48PM -1000, Jon Cormier wrote:
> Reviewed-by: Jonathan Cormier
>
> On Wed, Apr 24, 2024, 12:36 PM Denys Dmytriyenko via lists.yoctoproject.org
> wrote:
>
> > From: Denys Dmytriyenko
On Thu, Apr 25, 2024 at 02:36:10PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
>
> On 4/24/2024 10:59 PM, Limaye, Aniket wrote:
> >On 4/24/2024 6:53 PM, Ryan Eatmon wrote:
> >>
> >>We have consistently named the machines with -evm and not -sk.
> >>Is there a good reason to not name t
From: Denys Dmytriyenko
Separate FAT boot partition holds SPL, SYSFW and U-boot images, while
rootfs places kernel images and DTBs into /boot directory. So it is not
desirable to mount boot FAT partition into /boot directory of the rootfs
and shadow its original content - adjust corresponding
From: Denys Dmytriyenko
Separate FAT boot partition holds SPL, SYSFW and U-boot images, while
rootfs places kernel images and DTBs into /boot directory. So it is not
desirable to mount boot FAT partition into /boot directory of the rootfs
and shadow its original content - adjust corresponding
From: Denys Dmytriyenko
It is useful to have U-boot initial environment deployed for future
reference or to initialize environment files as part of the build.
In multiconfig setup, such as TI K3 platforms, building U-boot
multiple times for Cortex-R5 and Cortex-A53 cores results in file
From: Denys Dmytriyenko
Last time around SRCPV was removed from meta-ti-bsp[1], but meta-ti-extras
got missed. Resolve it now.
[1]
https://git.yoctoproject.org/meta-ti/commit/?id=d7624a767e20c776eb937c2942127299b4dc0093
Signed-off-by: Denys Dmytriyenko
---
meta-ti-extras/recipes-bsp/bt-fw
On Wed, Apr 17, 2024 at 06:39:02AM -0700, Katu Txakur wrote:
> Hi,
>
> I've built a, Yocto scarthgap, core-image-minimal for the
> machine=beaglebone. When I booted what it's defined as gpio0 in the device
> tree, it becomes /dev/gpiochip3. The rest are in order.
> This also happened using the b
On Wed, Apr 17, 2024 at 01:40:31PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
> Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead.
>
> Signed-off-by: Ryan Eatmon
Acked-by: Denys Dmytriyenko
> ---
> v2: Add missing nanbield in meta-ti-extras/
the time when the
> patches can be safely removed.
>
> Signed-off-by: Ryan Eatmon
Acked-by: Denys Dmytriyenko
> ---
> TODO | 9 +
> 1 file changed, 9 insertions(+)
> create mode 100644 TODO
>
> diff --git a/TODO b/TODO
> new file mode 100644
> index
lict.
>
> Signed-off-by: Ryan Eatmon
Acked-by: Denys Dmytriyenko
> ---
> .../python-yamllint/python3-yamllint_1.33.0.bb| 15 +++
> 1 file changed, 15 insertions(+)
> create mode 100644
> meta-ti-extras/recipes-devtools/python-yamllint/python3-yamllint_1.
1 - 100 of 1020 matches
Mail list logo
