Hi Denys, Indeed using "machine-specific package" when I meant moving the kernel artifacts into packagegroup-core-boot was confusing. Thanks for rewording! Vivien

The AM335x SoC has a built-in 16bit/24bit RGB LCD controller, and the BeagleBone Black uses an external chip to convert this to HDMI. But the SoC does not have a video output port per-se, thus the "sc

Require kernel image and device tree as machine-specific packages with MACHINE_ESSENTIAL_EXTRA_RDEPENDS instead of appending IMAGE_INSTALL. This binds the packages to the packagegroup-core-boot packag

The AM335x SoC has a built-in 16bit/24bit RGB LCD controller, and the BeagleBone Black uses an external chip to convert this to HDMI. But the SoC does not have a video output port per-se, thus the "sc

Hi Denys, Sorry I simply missed part of your previous inline reply... I am indeed in the scenario matching your approach 1), checking available features allows to maintain a generic image while skippi

Hi Denys, Are you suggesting that one must write MACHINE_FEATURES:remove = "screen" if their machine is headless (which is the case for a stock BeagleBone)? Thanks, Vivien

Hi Denys, I understand what you're saying. The confusion comes from the fact that some people think about the 'screen' feature as 'the machine has an LCD _controller_ and/or graphic output port(s)', w

Some distros or image recipes may rely on the presence of the "screen" machine feature to install graphical front-end applications. The ti33x SoC has an integrated GPU but does not have a screen per-s

Hi Richard, Maybe I don't quite get it yet, but since cross-canadian handles ABIEXTENSION and creates symlinks, can't the build (or at least some recipes) be passed an "hf" suffixed link to satisfy re

Hi, For what it's worth: Reported-by: Vivien Didelot <vdidelot@...> Tested-by: Vivien Didelot <vdidelot@...> It would be really appreciated to mention the reporter or at least a Cc ;) Thanks

Hi Denys, True, the package "used to work" for me but I wasn't using the distro feature back then. I'll give the patch a test if that can help. Thanks, Vivien

Hi Denys, Now I'm seeing some level of negativity :-) That's the whole purpose of this thread, this is why I am pointing this sgx patch as an example for the consequences for zeroing the ABI extension

Hi, With latest master(s), ti-sgx-ddk-km fails with: ERROR: ti-sgx-ddk-km-1.17.4948957-r22x do_package: QA Issue: ti-sgx-ddk-km: Files/directories were installed but not shipped in any package: /lib /

Hi Denys, The comment in cross-canadian.bbclass literally states "This is a bit ugly." I'm only talking about code here and did not mean any attack. My point exactly, we shouldn't be adding non-hf too

Hi all, I've, like many, run into the issue of toolchain detection for the ti-sgx-ddk-km driver. I've noticed the ugly patch [1] getting edited to add new toolchains like arm-oe-linux-gnueabi and arm-

Hi Denys, I subscribed, but I did not receive any confirmation email (yet?). Can you forward the patch to the meta-arago mailing list in the meantime? Thanks, Vivien

Instead of maintaining an inappropriate hack on qtwebengine to disable seccomp filter sandbox, export the corresponding chromium flag in the QTWEBENGINE_CHROMIUM_FLAGS environment variable. Signed-off

Require kernel image and device tree as machine-specific packages with MACHINE_ESSENTIAL_EXTRA_RDEPENDS instead of appending IMAGE_INSTALL. This binds the packages to the packagegroup-core-boot packag

Hi Denys, Oops I messed up, can you please add your address as Suggested-by:, and set the author address to my Signed-off-by: address? Otherwise I can resend if that is simpler. Thank you, Vivien

Boards like the beaglebone currently hardcode "u-boot" as a dependency for the image and the wic format, and this prevents one from choosing a different bootloader via: PREFERRED_PROVIDER_virtual/boot