00:00 <marex> I tried unset BB_RENAMED_VARIABLES[SDK_LOCAL_CONF_WHITELIST] , I tried python anonymous () {} in layer.conf , I just dont see a way

00:09 <marex> well, unset in local.conf is an option, but that's a workaround

00:32 <khem> RP: I need to take a look at working build for gpgme on x32 is there some AB node I can peek into ?

04:02 <khem> abelloni: RP I have posted another version of autoconf patchset which addresses Ross's comments as well as issue with gpgme on x32

04:03 <khem> the patches are on ml as well as on a contrib branch https://git.yoctoproject.org/poky-contrib/log/?h=kraj/autoconf-2.72

04:03 <khem> give it another shot

10:05 <Guest62> Good morning from the UK

10:06 <Guest62> problem: my yocto build is apparently missing libopencv-core when local.conf contains the following line: IMAGE_INSTALL:append = " opencv opencv-dev opencv-staticdev libopencv-core libopencv-imgproc" and builds without error or warnings

10:07 <Guest62> is anyone familiar enough with opencv to give me a hint?

10:19 <RP> Guest62: Questions I would be asking are whether any of those pieces make it into the image or is it just libopencv-core? are the files you expect in the libopencv-core package?

10:21 <Guest62> it is for a cross compilation on board the  jetson, I think I fathomed the problem, traced it down to a CMakeList.txt file which uses a find_package and fails to initiallise a variable

10:48 <ray-san> hi there, i'm building a yocto image (kirkstone) and try to set the timezone via the TIMEZONE variable in the local.conf but my timezone gets always set to Universal. The needed tzdata files are there, but the symlink from /etc/localtime always points to /usr/share/zoneinfo/Universal. I have also tried to write a recipe which overwirtes the symlink in the do_install function. Do you guys have any idea?

10:57 <flo_32> Hi Everyone.

11:03 <flo_32> Is anyone familiar with pin-muxing stuff for the imx6ul / ull series of processors? I cannot get my output to work as i want. I want to control the state of Pad J16 on a MCIMX6Y2xxxx processor. It is mentioned in the device tree, to belong to the pincontrol gorup for the spi3, and is configured to: MX6UL_PAD_UART2_RX_DATA__ECSPI3_SCLK

11:03 <flo_32> 0x100b1. Therefore I modified the device-tree and set the state of SPI3 to status = "disabled" and rebuild everything.

11:05 <flo_32> gpioinfo lists gpio21 as unused but when i change it to output and activate it nothing changes. Therefore I think gpio21 might be mapped to a different pad. What i dont know: Do i have to map gpio21 in the device-tree myself?

11:11 <flo_32> remark: I know that this is not really a yocto issue. I was just hoping to find someone who has a bit of insight into the imx6.

11:14 <yocton> flo_32: MX6UL_PAD_UART2_RX_DATA__ECSPI3_SCLK mean that you mapped pad "UART2_RX_DATA" to the function "ECSPI3_SCLK" so the fact taht the GPIO does not work as intended is not surprising

11:15 <yocton> You want to use the MX6UL_PAD_UART2_RX_DATA__GPIO... definition

11:16 <flo_32> Okay, so in the imx6ul-pinfunc.h i can find the definition: MX6UL_PAD_UART2_RX_DATA__GPIO1_IO21. What I dont get is: Do I have to create my own pinctrl group in the device-tree? Which driver am i supposed to use?

11:17 <RP> JPEW: I've sent a patch for more of the ssh poll fixing since that was stopping the timeout errors from being raised

11:21 <yocton> flo_32: create a new pinctrl-group (Not the cleanest but I usually finish with a group containing all the random GPIOs I need to use). You don't need a new driver : all the gpios will be supported by the current GPIO driver

11:25 <flo_32> @yocton: so in my dtree patch i add: pinctrl_gpiodev_board: gpiosomegroupnotmentionedanywhereelse { \n fsl,pins = < \n MX6UL_PAD_UART2_RX_DATA__GPIO1_IO21   0x10b0 (0x10b0 from the imx config tool) >; }; ?

11:26 <flo_32> My device-tree patch is applied after the initial spi pincontrol so I believe it should overwrite the old initialization

12:00 <Guest99> hello everyone, i have a question for those who use meta-tegra(nvidia jetson modules).

12:00 <Guest99> a custom carrier board (DSBOARD-ORNX) is used with the Jetson Orin NX 16GB module.

12:00 <Guest99> is it possible to extract images comfortably using meta-tegra? if not, are specific configurations required as it is a custom board?

12:12 <mckoan> Guest99: define "extract images"

12:14 <Guest99> i wanted to say about creating an image that works with custom board(DSBOARD-ORNX)

12:51 <AndreRicardo> I guess I have to modify somehow `meta-swupdate/recipes-support/swupdate/defconfig` to enable the copy? But I did run `bitbake -c menuconfig swupdate` and cannot find anything related to the copy handler

13:04 <adrianf> AndreRicardo: I guess you need to enable the CONFIG_COPY feature in the defconfig file: https://github.com/sbabic/swupdate/blob/master/handlers/Makefile#L14 . But the real exparts are available on the swupdate mailing list https://groups.google.com/g/swupdate

13:06 <adrianf> You might try to search for copy in the menuconfig. Searching works with / (like vim)

13:07 <AndreRicardo> Thank you adrianf I'm going to search in menuconfig

13:13 <AndreRicardo>  .config - SWUpdate Configuration

13:13 <AndreRicardo>  → Search (copy) ──────────────────────────────────────────────────────────────────────────────────────────────────────────────

13:13 <AndreRicardo> ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

13:13 <AndreRicardo> ──────────────────────────────────────

13:13 <AndreRicardo>   ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────

13:13 <AndreRicardo> ─────────────── Search Results ────────────────────────────────────────────────────────────────────────────────────────────────

13:13 <AndreRicardo> ──────────────────────────────────┐

13:13 <AndreRicardo>   │ No matches found.

13:13 <AndreRicardo> │

13:33 <JPEW> RP: k, I'll look at it

13:36 <RP> JPEW: I'm sure there is cleanup to be made but I just want things to work atm!