Wednesday, 2024-09-25

*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Remote host closed the connection)00:32
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto00:35
*** vthor <vthor!~thor@user/vthor> has quit IRC (Excess Flood)01:39
*** vthor <vthor!~thor@2605:59c8:71e9:3e10:fbc8:4e22:594a:59ab> has joined #yocto01:40
*** jclsn <jclsn!~jclsn@2a04:4540:6531:a800:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 264 seconds)01:55
*** jclsn <jclsn!~jclsn@2a04:4540:653e:f500:2ce:39ff:fecf:efcd> has joined #yocto01:57
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Ping timeout: 260 seconds)02:05
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto02:07
*** starblue1 <starblue1!~juergen@87.122.36.79> has quit IRC (Ping timeout: 260 seconds)02:14
*** starblue1 <starblue1!~juergen@87.122.126.14> has joined #yocto02:15
*** Articulus <Articulus!~Articulus@2601:642:4f7f:1df1:16ac:60ff:fed8:386b> has joined #yocto04:18
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto04:39
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Ping timeout: 265 seconds)04:40
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 248 seconds)05:00
*** amitk <amitk!~amit@58.84.60.140> has joined #yocto05:06
*** goliath <goliath!~goliath@user/goliath> has joined #yocto05:07
*** LocutusOfBorg <LocutusOfBorg!~locutusof@host-95-231-134-228.business.telecomitalia.it> has quit IRC (Remote host closed the connection)05:50
*** rob_w <rob_w!~rob@2001:a61:13e4:b701:3dde:3787:71f0:23bb> has joined #yocto05:53
*** micka_ is now known as micka06:01
*** micka_ <micka_!~micka@reverse-177-98.fdn.fr> has joined #yocto06:03
*** micka <micka!~micka@reverse-177-98.fdn.fr> has quit IRC (Ping timeout: 252 seconds)06:05
*** micka_ is now known as micka06:05
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has joined #yocto06:08
*** rfuentess <rfuentess!~rfuentess@154.45.232.215> has joined #yocto06:18
*** CrazyGecko <CrazyGecko!~gecko@90.251.200.213.static.wline.lns.sme.cust.swisscom.ch> has joined #yocto06:20
*** sng <sng!~quassel@217.140.105.54> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)06:39
*** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto06:39
*** sng <sng!~quassel@217.140.105.54> has joined #yocto06:39
*** ray-san2 <ray-san2!~ray-san@195.50.168.194> has joined #yocto07:09
*** zpfvo <zpfvo!~fvo@i59F5CC85.versanet.de> has joined #yocto07:11
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has joined #yocto07:16
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has quit IRC (Remote host closed the connection)07:18
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has joined #yocto07:20
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has quit IRC (Remote host closed the connection)07:21
*** ThomasRoos <ThomasRoos!~ThomasRoo@ip5b43ff2a.dynamic.kabel-deutschland.de> has joined #yocto07:22
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:23
*** Kubu_work <Kubu_work!~kubu@static-css-ccs-204145.business.bouyguestelecom.com> has joined #yocto07:23
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto07:24
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has joined #yocto07:32
*** rfuentess <rfuentess!~rfuentess@154.45.232.215> has quit IRC (Read error: Connection reset by peer)07:41
*** xmn <xmn!~xmn@2600:4040:9398:a200:dd11:432b:46aa:fb01> has quit IRC (Ping timeout: 246 seconds)07:42
*** rfuentess <rfuentess!~rfuentess@147.161.182.248> has joined #yocto07:42
*** rber|res <rber|res!~rber|res@213-225-13-254.nat.highway.a1.net> has joined #yocto07:46
rber|resHey - I am playing with the yocto-check-layer tool and it looks like if you change a signature in your layer (e.g. bbappend) your layer fails. Why?07:48
*** dmoseley_ <dmoseley_!~dmoseley@129.222.253.147> has joined #yocto07:50
*** dmoseley <dmoseley!~dmoseley@129.222.87.213> has quit IRC (Ping timeout: 246 seconds)07:51
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Quit: Konversation terminated!)07:52
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:eec0:45cd:5c05:b682> has joined #yocto07:52
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has joined #yocto07:52
*** dmoseley <dmoseley!~dmoseley@129.222.255.133> has joined #yocto07:53
*** dmoseley_ <dmoseley_!~dmoseley@129.222.253.147> has quit IRC (Ping timeout: 255 seconds)07:54
*** dmoseley <dmoseley!~dmoseley@129.222.255.133> has quit IRC (Ping timeout: 255 seconds)07:59
*** dmoseley <dmoseley!~dmoseley@129.222.253.147> has joined #yocto08:00
*** olani_ <olani_!~olani@wlan-gw.se.axis.com> has quit IRC (Ping timeout: 264 seconds)08:05
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:10
*** sng <sng!~quassel@217.140.105.54> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)08:27
*** sng <sng!~quassel@217.140.105.54> has joined #yocto08:28
mcfrisk_RP: do the master-next test runs look good? no more failures from systemd uki changes?08:32
rburtonmcfrisk_: RP is away this week, i'll dig out the latest -next build shortly and see what broke08:34
mcfrisk_rburton: ok, thanks08:37
*** ThomasRoos <ThomasRoos!~ThomasRoo@ip5b43ff2a.dynamic.kabel-deutschland.de> has quit IRC (Quit: Client closed)08:37
*** Saur_Home17 <Saur_Home17!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto08:43
* rob_w finally back to setup some fancy fresh new toolchains,,, love that part the most08:44
*** Saur_Home16 <Saur_Home16!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Ping timeout: 256 seconds)08:47
*** belsirk <belsirk!~rfuentess@154.45.232.215> has joined #yocto08:51
*** rfuentess <rfuentess!~rfuentess@147.161.182.248> has quit IRC (Ping timeout: 260 seconds)08:54
LetoThe2ndrob_w: feeling like android much?09:08
rob_wnot in a long time, no09:08
*** Granjow <Granjow!~Granjow@46.140.188.244> has joined #yocto09:08
rob_wwhy ur asking ?09:08
LetoThe2ndrob_w: "fancy toolchains" has basically been the android theme (in our tiny embedded bubble) at OSS+LPC :)09:09
rob_wah sorry09:09
LetoThe2nd:-)09:10
rob_wi actually love yocto in the positiv way of my wording09:10
LetoThe2ndrob_w: all good!09:10
GranjowHello again. I'm trying to generate custom GRUB menu entries with LABELS and APPEND, but I need different kernel parameters for different entries. Looking at grub-efi-cfg.bbclass, it looks like this is not possible, and I wonder if either I don't understand it or if there generally is no point in having multiple labels because they would all do the09:10
Granjowsame anyway?09:10
rob_wdoing the same thing again , sounds generally doubtfull09:11
GranjowFollow-up question is: how do I create a GRUB configuration with different menu entries AND different kernel parameters? Do I have to change grub-efi-cfg.bbclass, or is there a different way?09:12
rob_wGranjow, maybe check how poky/meta/recipes-bsp/grub/grub-bootconf_1.00.bb does it and bbappend to that ?09:16
Granjowrob_w: It does an inherit on grub-efi-cfg.bbclass, and from what I know, I cannot un-inherit and I cannot override the .bbclass unless I patch poky directly, but I need to modify the .bbclass to fix it?09:18
rob_wwhat i ses is that grub-bootconf is to create a grub.cfg , if that isnt what u want09:21
Granjowrob_w: It does, but it does not generate it in a useful way09:32
GranjowIt can generate multiple entries, but they are all the same except for the name, which is useless09:32
qschulztlwoerner: ah, well... starting gst-launch with video decoding on weston in scarthgap crashes with a segfault09:38
mcfrisk_Granjow: I know the pain, had to patch grub-efi quite heavily to do what we wanted.09:50
mcfrisk_Granjow: you can check https://gitlab.com/Linaro/trustedsubstrate/meta-ledge-secure/-/tree/main/meta-ledge-secure/recipes-bsp/grub?ref_type=heads and https://gitlab.com/Linaro/trustedsubstrate/meta-ledge-secure/-/blob/main/meta-ledge-secure/conf/machine/include/image-efi-boot.inc?ref_type=heads for the ugly hacks09:51
mcfrisk_not sure if adding extra boot entries with different kernel command lines is any easier with systemd-boot09:52
*** starblue1 <starblue1!~juergen@87.122.126.14> has quit IRC (Ping timeout: 260 seconds)09:56
*** starblue1 <starblue1!~juergen@87.122.126.14> has joined #yocto10:00
*** Ad0 <Ad0!~Ad0@93.124.245.194> has quit IRC (Ping timeout: 260 seconds)10:15
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)10:27
*** rber|res <rber|res!~rber|res@213-225-13-254.nat.highway.a1.net> has quit IRC (Remote host closed the connection)10:46
*** Piraty_ is now known as Piraty10:57
*** sstiller <sstiller!~sstiller@p200300f07f14ca00652ea6321ae326d8.dip0.t-ipconnect.de> has joined #yocto10:59
*** Ad0 <Ad0!~Ad0@93.124.245.194> has joined #yocto11:04
*** kalj <kalj!~kalj@h-158-174-207-174.NA.cust.bahnhof.se> has joined #yocto11:19
*** belsirk is now known as rfuentess11:27
Granjowmcfrisk_: Thank you! Gives me some inspiration! And maybe I'll send a patch for poky …11:30
*** Granjow <Granjow!~Granjow@46.140.188.244> has quit IRC (Quit: Client closed)11:35
*** Granjow <Granjow!~Granjow@46.140.188.244> has joined #yocto11:36
*** Saur_Home17 <Saur_Home17!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)11:38
*** Saur_Home17 <Saur_Home17!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto11:38
*** sstiller <sstiller!~sstiller@p200300f07f14ca00652ea6321ae326d8.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)12:26
qschulzdoes anyone else have atrocious git clone download speed for linux-yocto?12:33
qschulzi'm at 26kbps12:33
qschulzkBps sorry12:33
Granjowqschulz: I get 11 MB/s when running it now12:40
qschulzGranjow: which timezone/continent are you? I just restarted it and it's still 32KBps from Europe12:41
qschulzare you in :)12:42
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:eec0:45cd:5c05:b682> has quit IRC (Ping timeout: 244 seconds)12:42
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:eec0:45cd:5c05:b682> has joined #yocto12:43
qschulzGranjow: mmmmmm, 30MBps from my office's server12:44
Granjowqschulz: Switzerland12:53
*** kalj <kalj!~kalj@h-158-174-207-174.NA.cust.bahnhof.se> has quit IRC (Ping timeout: 256 seconds)12:53
*** rber|res <rber|res!~rber|res@213-225-13-254.nat.highway.a1.net> has joined #yocto12:53
* qschulz shrugs12:55
GranjowI'm trying to install a yocto from USB stick, but as soon as the live system boots, it finds neither keyboard nor the usb stick it booted from. How can I debug this? The serial console is not of much help without a keyboard13:04
rob_wwhere would i hack to get DL_DIR include the downloads/ dir again when i use file:// SRC_URIs ? scarthgap seems to miss that path on those13:06
*** xmn <xmn!~xmn@2600:4040:9398:a200:659e:a4d7:8dbb:60a3> has joined #yocto13:08
qschulzrob_w: i don't understand what you're trying to do, can you provide the actual thing you want to do?13:08
qschulzGranjow: very likely a kernel issue? maybe you have built the USB drivers as modules and they aren't installed in the initramfs/rootfs?13:09
rob_won kirkstone, i had me recipes use a simple SRC_URI like file://my.tar.bz2 and just have that package in my build/download/ dir13:10
rob_wscarthgap seems to only include meta-layer paths for my tar.bz2 and miss out the download dir13:10
*** Granjow <Granjow!~Granjow@46.140.188.244> has quit IRC (Quit: Client closed)13:11
*** Granjow <Granjow!~Granjow@46.140.188.244> has joined #yocto13:13
qschulzthere usually is a .done file associated with every file in DL_DIR13:13
qschulzit contains some data (463B according to ls)13:13
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto13:16
Granjowqschulz: We actually disabled some USB_XHCI features in the kernel to support the Siemens 227E, just testing if that broke USB on the new hardware. How can I check if the USB drivers are in initramfs, can I just extract the initrd file and see it there?13:16
qschulzGranjow: you can check with lsmod if some modules are loaded13:17
GranjowWhen I look at usr/lib/modules/6.6.30-intel-pk-standard/modules.builtin in the initrd, there are some usb drivers, not sure if that is relevant and if it is, which one is the right one13:17
qschulzGranjow: I don't think the modules are supposed to be in /usr/lib rather in /lib13:18
Granjowqschulz: how can I check that … without keyboard … ok, I'll just put it into the 80-setup-live which runs in the boot phase13:18
qschulzGranjow: ssh? serial?13:18
Granjowqschulz: I dont have a serial interface, and it stops at “waiting for removable media”13:19
Granjowso no IP and ssh yet13:20
Granjowlib/modules/6.6.30-intel-pk-standard/modules.builtin also contains some usb drivers, again no idea what they are good for :)13:20
qschulzGranjow: won't be able to tell myself either :)13:21
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 276 seconds)13:28
*** reatmon_ <reatmon_!~reatmon@192.91.75.12> has quit IRC (Remote host closed the connection)13:29
*** reatmon_ <reatmon_!~reatmon@192.91.75.30> has joined #yocto13:30
rburtonGranjow: definitely you either don't have an initrd, you're kernel isn't using the initrd, or the initrd is missing a load of modules.  if you're really unlucky you've managed to build an initrd that can't load modules, master was like that for a few weeks but is fixed now.13:49
*** goliath <goliath!~goliath@user/goliath> has joined #yocto13:50
Granjowrburton: I'm on poky scarthgap-5.0.3, was it affected as well? I think the kernel is using the initrd, because I can extract it with unmkinitramfs on my host and there is a script in /init.d/ which I modified, and the modified version is also started when booting from USB stick.13:52
rburtonthe easy fix is to just put the needed drivers into the kernel instead of as modules13:52
GranjowI have almost no clue about kernel modules unfortunately, can I check if it fails loading modules and how do I generally know which module I would need?13:52
GranjowOk :) how do I know which drivers I need?13:53
GranjowMy new image is about to complete its build, so I can add an lsmod in the startup file, and if it is not too long, I can still see it on the screen13:53
rburtonan actual serial port is usually easier than usb if your board has one of those13:54
GranjowUsing Siemens BX-21A, 3 Ethernet ports, but no serial port :(13:55
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:eec0:45cd:5c05:b682> has quit IRC (Ping timeout: 248 seconds)13:57
GranjowOh. Cool. It was the drivers we disabled for the old hardware which are now required for this hardware. The image I just built includes these again. It boots so much!13:57
*** Xagen <Xagen!~Xagen@4.14.206.69> has joined #yocto13:58
GranjowThough, it does not detect any of the 3 ethernet adapters, so I anyway have to look into kernel drivers :D14:02
rburtonif your hardware vendor doesn't provide a list of all the hardware and the kernel options they need to work then ask them for that list14:02
rburtoni was so pleased with i found a board that actually had that in the hardware overview14:02
Granjowrburton: That sounds like something that would make my life much easier in that regard. Will do!14:03
*** zpfvo <zpfvo!~fvo@i59F5CC85.versanet.de> has quit IRC (Remote host closed the connection)14:06
qschulzrburton: people complain about Device Tree but at least I have a way of figuring out what kind of drivers I need based on the compatibles :)14:11
qschulzwondering if there's something similar for the ACPI world14:11
rburtonit would be nice14:11
qschulz(especially since there seems to be Aarch64 systems now support ACPI?14:11
qschulzsupporting*14:12
rburtonsome, yeah14:12
rburtonhas anyone written a tool to scan a devicetree and automatically list the modules that match?14:12
qschulzrburton: likely14:12
qschulzI have one of my thousands open tabs which explains how they added runtime checks for driver probing based on device tree14:12
qschulzcollabora or linaro folks are working on this14:13
GranjowJust to still understand the approach. There is a manual which says Marwell 88E1512 is used. According to $searchengine it is spelled Marvell and not Marwell. There is e.g. https://github.com/torvalds/linux/blob/master/drivers/net/phy/marvell.c and I found out that there is a kernel configuration reference which lists marvell drivers:14:13
Granjowhttps://www.kernelconfig.io/search?q=marvell&kernelversion=6.6.52&arch=x86 now I have to find one and add the kernel configuration and it might work? (might, because the marvell.c only contains the 88E1510 explicitly)14:13
rburtonqschulz: i also want to glue the module metadata that lists the firmware it loads into package dependencies, so if you install a kernel module it pulls in the firmware automatically14:15
rburton(does need rewriting linux-firmware first though)14:15
qschulzGranjow: it is possible your PHY simply isn't supported yet14:16
qschulzthough.... if marvell have done their job properly and it is compliant with one of the ieee standards for Ethernet PHYs, the generic driver could handle it14:17
*** guest92 <guest92!~guest92@dslb-092-072-052-087.092.072.pools.vodafone-ip.de> has joined #yocto14:17
qschulzif you want more features that aren't part of the standard, or it simply doesn't work, then you'll need driver support14:17
qschulztry to figure out the ID of the PHY through mii/mdio tools14:18
qschulzor if you have access to some datasheet you can get it from there14:18
*** guest92 <guest92!~guest92@dslb-092-072-052-087.092.072.pools.vodafone-ip.de> has quit IRC (Killed (ozone (No Spam)))14:18
qschulzGranjow: seems like your PHY could be compatible with the 88E151014:20
qschulzhttps://www.marvell.com/content/dam/marvell/en/public-collateral/phys-transceivers/marvell-phys-transceivers-alaska-88e151x-datasheet.pdf14:20
qschulztable 67 and 6814:20
qschulzthey don't seem to say anything about a different identifier for the PHYs in that datasheet14:21
rburtonlove that its 2024 and people are still having to google and read data sheets to figure out if hardware is supported on linux and if so what the modules to use are14:22
qschulzrburton: i'm actually surprised there was a publicly available datasheet for a marvell PHY )14:23
qschulz:)14:23
qschulzrburton: let's take a moment to thank vendors to provide job security to the whole industry14:24
qschulzrburton: https://lore.kernel.org/kernelci/20230828211424.2964562-1-nfraprado@collabora.com/14:27
qschulzstraight from my unopened tab, haven't read it14:27
qschulzhttps://www.youtube.com/watch?v=vKsP6MCFLZk14:28
*** ray-san2 <ray-san2!~ray-san@195.50.168.194> has quit IRC (Ping timeout: 252 seconds)14:36
*** guest92 <guest92!~guest92@5.83.191.81> has joined #yocto14:39
Granjowqschulz: Cool, will try! So if the PHY identifier is identical, that means the driver should be compatible because hardware detection is done based on this identifier?14:46
*** guest92 <guest92!~guest92@5.83.191.81> has quit IRC (Ping timeout: 256 seconds)14:46
qschulzGranjow: correct, it's reading the PHY Identifier as part of the standard, applying a mask (defined in the driver) and if it matches, it uses that driver14:46
rber|resis there any good reason why we pull tarballs via http and not https in some of the recipes?14:48
Granjowqschulz: Ok, interesting! :)14:52
qschulzGranjow: interesting is what happens when you have two drivers matching :D14:53
*** guest92 <guest92!~guest92@dslb-092-072-052-087.092.072.pools.vodafone-ip.de> has joined #yocto14:53
Granjowqschulz: lol – what happens? Random? Alphabetic? Nuclear Fusion?14:54
qschulzGranjow: I actually do not know, I hit this once when migrating support of one PHY to another driver but didn't investigate14:55
Granjowok :)14:55
qschulzconsidering the probe order isn't guaranteed to be deterministic, I would assume that the PHY drivers registering in the subsystem are not necessarily in a guaranteed order and thus, chaos ensues14:56
qschulzone boot one driver, another boot another driver (not necessarily 50/50 :) )14:56
qschulz(i have nothing to back this claim though)14:56
GranjowThough, if both drivers work, would it really be an issue? :)14:58
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:9790:538a:45d9:11f6> has joined #yocto14:59
qschulzGranjow: very unlikely they both work, at least the same way with the same set of features, bugs, etc...15:00
*** guest92 <guest92!~guest92@dslb-092-072-052-087.092.072.pools.vodafone-ip.de> has quit IRC (Ping timeout: 256 seconds)15:02
*** CrazyGecko <CrazyGecko!~gecko@90.251.200.213.static.wline.lns.sme.cust.swisscom.ch> has quit IRC (Ping timeout: 248 seconds)15:04
NishanthMenondumb devtool question, since my search foo is failing me: https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/linux/linux-yocto_6.10.bb#n43 -> there are two uris there - but when I use devtool modify linux-yocto, I just get the  linux-yocto.git and not yocto-kernel-cache. wondering if there is a better way of using devtool ?15:05
NishanthMenon^^ I mean to work on yocto-kernel-cache15:06
Granjowqschulz and rburton, thanks for your help! Will try the new driver on Friday, kernel ignores my configuration today :)15:06
*** Granjow <Granjow!~Granjow@46.140.188.244> has quit IRC (Quit: Granjow)15:07
*** gspbirel1 <gspbirel1!~chrrreeee@user/gspbirel56> has joined #yocto15:15
*** gspbirel1 is now known as gspbirel5615:15
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto15:16
*** Saur_Home21 <Saur_Home21!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto15:23
*** rfuentess <rfuentess!~rfuentess@154.45.232.215> has quit IRC (Remote host closed the connection)15:24
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has joined #yocto15:24
*** Saur_Home17 <Saur_Home17!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Ping timeout: 256 seconds)15:27
*** astlep5504018066 <astlep5504018066!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has joined #yocto15:29
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Remote host closed the connection)15:38
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:40
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 246 seconds)15:51
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 252 seconds)15:51
*** Saur_Home12 <Saur_Home12!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto16:00
*** druppy <druppy!~Thunderbi@user/druppy> has joined #yocto16:01
*** Saur_Home21 <Saur_Home21!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Ping timeout: 256 seconds)16:03
*** CrazyGecko <CrazyGecko!~gecko@90.251.200.213.static.wline.lns.sme.cust.swisscom.ch> has joined #yocto16:08
*** mbulut_ <mbulut_!~mbulut@2a02:8108:1607:2800:9790:538a:45d9:11f6> has quit IRC (Ping timeout: 276 seconds)16:14
*** Kubu_work <Kubu_work!~kubu@static-css-ccs-204145.business.bouyguestelecom.com> has quit IRC (Quit: Leaving.)16:17
*** Articulus <Articulus!~Articulus@2601:642:4f7f:1df1:16ac:60ff:fed8:386b> has quit IRC (Quit: Leaving)16:27
*** jmd <jmd!~user@2001:a61:2b0b:2c01:58dc:32d:3d4c:e7a> has joined #yocto16:40
*** druppy <druppy!~Thunderbi@user/druppy> has quit IRC (Ping timeout: 252 seconds)16:40
qschulzrburton: re: tf-a recipe before v2.12 is released... shouldn't we just add a _git.bb recipe in meta-arm?16:59
rburtonmaaaybe16:59
qschulzif yes, AUTOREV, no AUTOREV?16:59
rburtonnot autorev by default17:00
qschulzI know you mentioned devupstream17:00
qschulzbut I don't see it applying here17:00
khemautorev throws whole build under the bus17:00
qschulzwell... actually, probably for the lts branches it could make sense17:00
qschulzkhem: care to give a few more bits on that?17:01
qschulzfor context, there's RK356x and RK3588 (initial) support in TF-A17:01
qschulzno release yet, and I know migrating meta-rockchip to it will take some time as I need to rework a few recipes with a few assumptions we made to make things easy17:01
qschulzso I want to test before the v2.12 is released17:02
qschulzor at least have the opportunity to do so17:02
qschulzI imagine i'm not the only one who would ever want to build a non-release build of TF-A to prepare for stuff17:02
qschulz(after all, TF-A is releasing like twice a year?)17:02
rburtonyeah, i'd like to be able to throw a 'git head' build in our CI occasionally17:04
qschulzso, instead of keeping this on my disk, I asked rburton if he was open to contributions on meta-arm :)17:04
qschulzrburton: I guess we could have a _git which is stable and a devupstream in _git that is autorev?17:05
khemdo it via a config metadata17:05
khemit will be parsed and bitbake will puke if it can not access17:06
rburtonyeah i think even as a default in devupstream it will still cause a network op17:06
qschulzah, that I didn't know... mmm that's bad17:06
rburtonbut you can set a sha and if you want autorev its easily changed from local.conf or similar17:06
rburtonpaging jonmason as we're talking about meta-arm :)17:06
*** reboji <reboji!~reboji@194.189-204-138.bestelclientes.com.mx> has joined #yocto17:09
jonmasonif there are going to be two recipes that are _git, one with and one without autorev, then why not keep a versioned one and do the devupstream in the git.bb?17:10
qschulznot sure to follow, are you suggesting renaming v2.11 recipe into _git and have devupstream in there?17:12
rebojihii, i tried adding libgpiod to my yocto build, and i have the (libgpiod) v2.1.2, but when i try to use gpioset and so, this message comes up: gpioset: invalid line value: 'gpiochip2' . does anyone know if I have to add another package or change version?17:13
jonmasonqschulz: your proposal was " _git which is stable and a devupstream in _git that is autorev", that is 2 recipes, right?17:13
qschulzjonmason: one file but two recipes from bitbake PoV yes17:14
*** rob_w <rob_w!~rob@2001:a61:13e4:b701:3dde:3787:71f0:23bb> has quit IRC (Quit: Leaving)17:16
jonmasonOkay, I think I'm missing something fundamental17:18
jonmasonSo, this seems to be a problem of everything git based17:18
jonmasonshould they all be _git.bb's, so that people can run the latest code?17:19
jonmasonsaid differently, why is this something that is unique to tfa?17:20
qschulzjonmason: recipe_version.bb with _version being _git isn't a requirement17:21
qschulzI would say it makes sense when a project doesn't go releases and is versioned by git17:22
qschulzor if you're in between versions17:22
jonmasonI understand that, but if everything is "free float" that is git, even if it's versioned, then why not switch to it17:22
qschulzwe already have multiple recipes in meta-arm for tf-a, the lts variant and the latest version17:22
qschulzjonmason: failing to get the argument but it's getting late so maybe a case of brainfarting :)17:23
jonmasonI think the disconnect is on my end17:23
qschulzconsidering we already have 2 versions of the same recipe, adding a third one and handling all of this in one recipe file seems like some very difficult to maintain recipe17:24
qschulzand **I** wouldn't even know how to do this properly17:24
jonmasonmeta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.10.4.bb is really just SHAs with a common inc file17:24
qschulz(there's devupstream BBCLASSEXTEND but even that isn't that entirely clear to me how to properly make use of it, seems to be very permissive)17:24
qschulzjonmason: correct, same for 2.11.017:25
jonmasonso the maintenance of multiple isn't hard for versioned17:25
jonmasonand you want a 3rd that is a _git.bb?17:26
qschulzI want to be able to build something that isn't a release17:26
jonmasonand devtool is too much?17:26
jonmasonlike, you want it in your layer or something?17:27
jonmasonand bbappend with SHA is not good?17:27
qschulzok I see :)17:27
jonmasonagain, I'm probably just not understanding17:27
qschulznow we can start talking since I understood your point :)17:28
qschulzso, it essentially boils down to "i'll do it once, does anyone want that in some layer or do I just keep this to myself"17:28
jonmasongotcha, you are already going to do this...17:28
qschulzAND, I assume meta-arm **MIGHT** have some interest in automatically testing before the release happens17:29
qschulzhence why I was suggesting this to rburton during the YP Dev Day last week17:29
jonmasonhe tells me nothing17:29
jonmasonjust makes fun of my new flowing locks of hair17:29
qschulzwell, he paged you just now ;) :D17:29
qschulzrburton: how dare you17:30
jonmasonoh crap, oe happy hour17:30
qschulzwill sign off then, let's discuss some more another day :)17:30
jonmasonnaa, just joining now17:31
jonmasonI mean, I'd be happy to see the patch and am not necessarily against it17:32
*** Kubu_work <Kubu_work!~kubu@lfbn-nan-1-335-137.w82-120.abo.wanadoo.fr> has joined #yocto17:32
qschulzit's not because someone does some work that it's valuable to other people though ;)17:33
qschulzand I also understand that adding one more recipe (or a variant of it) is adding some more work to already busy maintainers ;)17:33
*** ned_72 <ned_72!~ned@188.130.237.101> has joined #yocto17:37
*** ned_72 <ned_72!~ned@188.130.237.101> has left #yocto17:37
*** gspbirel56 <gspbirel56!~chrrreeee@user/gspbirel56> has quit IRC (Quit: WeeChat 4.3.3)17:44
*** reboji <reboji!~reboji@194.189-204-138.bestelclientes.com.mx> has quit IRC (Quit: Client closed)18:27
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)18:40
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 246 seconds)18:42
*** sugoi <sugoi!~Thunderbi@user/sugoi> has joined #yocto19:08
*** goliath <goliath!~goliath@user/goliath> has joined #yocto19:19
*** jmd <jmd!~user@2001:a61:2b0b:2c01:58dc:32d:3d4c:e7a> has quit IRC (Remote host closed the connection)19:20
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto19:22
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)19:46
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 246 seconds)19:48
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has joined #yocto19:48
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has joined #yocto19:48
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 248 seconds)19:52
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 255 seconds)19:53
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has joined #yocto19:56
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Ping timeout: 252 seconds)20:07
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has joined #yocto20:13
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has joined #yocto20:13
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has quit IRC (Quit: Haxxa flies away.)20:15
*** enok <enok!~Thunderbi@c-4550e353.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 260 seconds)20:15
*** Haxxa <Haxxa!~Haxxa@116.255.4.123> has joined #yocto20:18
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 252 seconds)20:40
*** ecdhe__ <ecdhe__!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 252 seconds)20:40
*** dmoseley <dmoseley!~dmoseley@129.222.253.147> has quit IRC (Quit: ZNC 1.9.1 - https://znc.in)20:47
*** dmoseley <dmoseley!~dmoseley@129.222.253.147> has joined #yocto20:49
*** Chaser <Chaser!~Chaser@user/chaser> has quit IRC (Quit: My Unrecognized Mac has gone to sleep. ZZZzzz…)20:50
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has quit IRC (Remote host closed the connection)20:52
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has joined #yocto20:53
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has quit IRC (Remote host closed the connection)20:54
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has joined #yocto20:54
*** dmoseley <dmoseley!~dmoseley@129.222.253.147> has quit IRC (Ping timeout: 248 seconds)20:59
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Ping timeout: 276 seconds)21:00
*** florian_kc <florian_kc!~florian@78.48.12.45> has joined #yocto21:05
*** Guest46 <Guest46!~Guest46@2001:871:216:aeef:9173:3d69:4538:17f0> has joined #yocto21:07
*** Guest46 <Guest46!~Guest46@2001:871:216:aeef:9173:3d69:4538:17f0> has quit IRC (Client Quit)21:08
*** amitk <amitk!~amit@58.84.60.140> has quit IRC (Ping timeout: 252 seconds)21:09
jonmasonkhem: your TC_CXX_RUNTIME change seems to fix it (took forever to build though).  I'll roll through CI to verify21:14
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)21:18
*** Xagen <Xagen!~Xagen@4.14.206.69> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)21:31
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has quit IRC (Ping timeout: 245 seconds)21:31
*** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has joined #yocto21:33
khemjonmason:ok cool22:01
khemjonmason:it does mean there is a bug in libgcc+clang case22:01
*** dmoseley <dmoseley!~dmoseley@129.222.255.203> has joined #yocto22:03
*** pbsds37 <pbsds37!~pbsds@84.20.102.94> has joined #yocto22:06
*** pbsds3 <pbsds3!~pbsds@84.20.102.94> has quit IRC (Ping timeout: 265 seconds)22:08
*** pbsds37 is now known as pbsds322:08
*** Kubu_work <Kubu_work!~kubu@lfbn-nan-1-335-137.w82-120.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)22:09
*** florian_kc <florian_kc!~florian@78.48.12.45> has quit IRC (Ping timeout: 245 seconds)22:24
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto22:36
*** chep <chep!chep@gateway/vpn/airvpn/chep> has quit IRC (Ping timeout: 252 seconds)23:10

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!