Monday, 2020-08-17

*** awe002 <awe002!~awe00@unaffiliated/awe00> has quit IRC00:11
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC00:13
*** Klox04 <Klox04!> has joined #yocto00:20
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC00:46
*** otavio <otavio!~otavio@debian/developer/otavio> has joined #yocto00:50
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has joined #yocto01:03
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:39
*** Klox04 <Klox04!> has quit IRC02:33
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC02:34
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has joined #yocto03:05
*** mbulut <mbulut!> has joined #yocto03:26
*** mbulut <mbulut!> has joined #yocto03:27
*** stacktrust <stacktrust!> has quit IRC04:05
*** stacktrust <stacktrust!> has joined #yocto04:38
*** ibinderwolf <ibinderwolf!> has joined #yocto05:01
*** jobroe <jobroe!> has joined #yocto05:25
*** kiwi_29 <kiwi_29!> has joined #yocto05:27
*** kiwi_29_ <kiwi_29_!> has joined #yocto05:30
*** kiwi_29 <kiwi_29!> has quit IRC05:30
*** kaspter <kaspter!~Instantbi@> has quit IRC05:37
*** kaspter <kaspter!~Instantbi@> has joined #yocto05:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:41
*** AndersD <AndersD!> has joined #yocto05:51
*** rcrudo <rcrudo!~rcrudo@2001:16b8:c24e:600:46c3:cbfb:8490:d6a6> has joined #yocto05:58
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto05:59
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC06:10
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto06:20
*** rcoote <rcoote!> has joined #yocto06:23
*** kiwi_29_ <kiwi_29_!> has quit IRC06:24
*** agust <agust!> has joined #yocto06:33
erbogood morning06:39
*** frsc <frsc!> has joined #yocto06:39
*** Sandrita <Sandrita!d0586e2e@gateway/web/cgi-irc/> has quit IRC06:41
mbulutmorning dude06:41
*** goliath <goliath!> has joined #yocto06:43
*** fl0v0 <fl0v0!~fvo@> has joined #yocto06:43
*** hankyban <hankyban!b92ed46e@> has joined #yocto06:52
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC06:54
*** gtristan <gtristan!~tristanva@> has quit IRC06:56
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has joined #yocto06:58
*** gtristan <gtristan!~tristanva@> has joined #yocto07:04
*** gsalazar <gsalazar!5e3dbd6b@gateway/web/cgi-irc/> has joined #yocto07:05
mcfriskhi, is SRC_URI supposed to be complete in "bitbke -e" output? I'm wondering why I see SRC_URI="" for a recipe with 20 or so patches being applied correctly on zeus..07:14
*** beneth <beneth!> has joined #yocto07:18
*** mckoan|away is now known as mckoan07:26
*** JaMa <JaMa!> has joined #yocto07:26
mckoangood morning07:26
*** jmiehe <jmiehe!> has joined #yocto07:27
LetoThe2ndmostly, yes.07:29
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC07:38
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto07:53
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:00
*** goliath <goliath!> has quit IRC08:00
*** ant__ <ant__!> has joined #yocto08:10
mcfriskI can't see SRC_URI properly set for clang from meta-clang. trying to add a bbappend to BSP layer to remove 0020-clang-Enable-SSP-and-PIE-by-default.patch08:18
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC08:23
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC08:27
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto08:31
*** osullivan99 <osullivan99!> has joined #yocto08:36
*** kaspter <kaspter!~Instantbi@> has quit IRC08:40
*** kaspter <kaspter!~Instantbi@> has joined #yocto08:41
*** goliath <goliath!~goliath@> has joined #yocto08:43
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto09:00
*** chris_ber <chris_ber!~quassel@> has joined #yocto09:07
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC09:10
*** awafaa <awafaa!sid716@gateway/web/> has quit IRC09:10
*** dagmcr <dagmcr!sid323878@gateway/web/> has quit IRC09:10
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC09:11
*** rsalveti <rsalveti!sid117878@gateway/web/> has quit IRC09:11
*** AndersD <AndersD!> has quit IRC09:15
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto09:15
*** sh00p <sh00p!> has joined #yocto09:15
*** dagmcr <dagmcr!sid323878@gateway/web/> has joined #yocto09:16
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto09:17
*** rsalveti <rsalveti!sid117878@gateway/web/> has joined #yocto09:18
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto09:18
sh00pWe support two separate, but similar, hardware platforms. So therefor we have two separate machine builds in our distribution. But they are driver incompatible. If I flash one type of hardware with the wrong build it won't be reachable over wifi anymore for example.09:19
*** awafaa <awafaa!sid716@gateway/web/> has joined #yocto09:20
sh00pIs there an idiomatic way of migrating the two builds into just _one_ and linux itself can figure out what drivers needs to be loaded depending on hardware it finds?09:20
sh00pFor PC this is the standard way for sure09:20
sh00pBut on arm?09:20
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC09:28
snoRP: busybox init is already in OE-core09:28
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto09:28
snoRP: so it's not the intension to introduce just one more init system, it's the intension to improve the usability of busybox-init09:29
RPsno: you were talking about lots of other init systems so its hard to know what you're intending09:31
*** PaowZ_ <PaowZ_!~Vince@> has quit IRC09:31
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto09:31
snoRP: I didn't want to add them into OE-core - there is another layer and Khem asked for improved busybox init support09:32
RPsno: ok, fair enough09:32
snoRP: so I take a look and detected, that e.g. volatile isn't provided when busybox provides init process - which causes issues in my default test environment etc. :)09:33
snoRP: and maybe busybox init or sysvinit would both have benefits from configuring what is desired on startup09:34
snoRP: can you answer to my mail with this in mind? Here is fine - I just want to get an idea of the direction to move09:35
*** kaspter <kaspter!~Instantbi@> has quit IRC09:40
*** kaspter <kaspter!~Instantbi@> has joined #yocto09:41
*** mckoan is now known as mckoan|away09:41
*** awe002 <awe002!~awe00@unaffiliated/awe00> has joined #yocto09:46
LetoThe2ndsh00p: device tree overlays, usually09:52
LetoThe2ndsh00p: start up with the common one, then detect at runtime which additions you need.09:52
LetoThe2ndsh00p: if you can already detect in the bootloader, then its a bit easier: ship a build with two device trees.09:53
sh00pLetoThe2nd, thanks for your input, we're using u-boot09:53
*** fbre <fbre!91fdde45@> has joined #yocto09:53
sh00pLetoThe2nd, perhaps it has support for something like that09:54
marexU-Boot surely has support for DT, for at least two decades09:54
sh00pright, but for hardware detection marex ?09:54
marexeven for DTOs09:54
LetoThe2ndsh00p: it doesn't really depend on which bootloader you use, it depends on if you have some means to detect which kernel/devicetree you need. this often requires patching it a little to detect HW revisions, or such.09:54
marexsh00p: depends on the hardware and how you discern it09:55
LetoThe2ndmarex: we use resisors!09:55
fbreHi! Is "zeus" a stable yocto release of NXP? (see
marexfbre: its a release code name, NXP has their own set of OE layers on top, which are compatible with that release09:56
fbreAnd does "zeus" support the realtime kernel patch?09:57
LetoThe2ndfbre: it is "still" stable, but halfwas on the way out, and expected to drop into community support within two months time. so if you have the choice, go for dunfell.09:57
fbreLetoThe2nd: I cannot see dunfell mentioned here:
LetoThe2ndfbre: like i said: "if you have the choice"10:00
LetoThe2ndfbre: and preempt-rt is also not depending on the yocto version, only on what your BSP provides.10:01
fbreActually I was on NXP release "sumo". But as soon as I activate  INITRAMFS_IMAGE and  INITRAMFS_IMAGE_BUNDLE the .sdcard image is not generated anymore, but I need such initramfs. So my hope is NXP fixed that in later versions.10:02
LetoThe2ndfbre: that ".sdcard" thing was a custom image type which was deprecated in favor of wic10:03
LetoThe2ndfbre: so no, that certainly will not be "fixed". you will have to work out how to use wic.10:03
fbreoh. I'm struggling with all that stuff for 2 weeks now, and I'm almost burned out X) . Since I've read the NXP PDFs I know how to bunzip an .sdcard file and how to dd that to sd card. Hmm... OK, so I should start to learn an alternative way.... '=(10:06
LetoThe2ndfbre: go blame nxp for handing you a BSP that is based on an outdated state.10:08
*** hpsy <hpsy!~hpsy@> has joined #yocto10:35
*** d__ep__th <d__ep__th!2bf2d0f8@> has joined #yocto10:44
*** NiksDev <NiksDev!~NiksDev@> has quit IRC10:47
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto10:47
LetoThe2ndfbre: by the way, this might be of interest to you:
mcfriskhow to remove a patch in meta-clang version of clang via bbappend in a BSP layer? a simple clang_%.bbappend with SRC_URI_remove = "file://0020-clang-Enable-SSP-and-PIE-by-default.patch" doesn't work?10:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:51
mcfriskI can see the bbappend changing output of bitbake -e for clang-cross-aarch64 but the change is not taking effect. I could drop the patch from meta-clang directly but surely this should also work from a bbappend?10:53
*** yann <yann!> has joined #yocto10:56
*** osullivan99 <osullivan99!> has quit IRC10:59
*** kpo_ <kpo_!> has quit IRC11:03
*** osullivan99 <osullivan99!> has joined #yocto11:04
mcfriskI must conclude that modifying SRC_URI in a bbappend with _remove doesn't work on zeus. Or can a BSP layer bork that... and I have to modify meta-clang to drop that one patch. this is odd.11:05
*** d__ep__th <d__ep__th!2bf2d0f8@> has quit IRC11:15
fbreLetoThe2nd: That sources/meta-openembedded/meta-initramfs contains just debug stuff and tools for that. But I saw sources/poky/meta/recipes-core/images/ which calls sources/poky/meta/recipes-core/initrdscripts/ which then calls11:24
fbresources/poky/meta/recipes-core/initrdscripts/files/  That does that overlayfs mount.11:24
*** ant__ <ant__!> has quit IRC11:24
fbreLetoThe2nd: The plan is to bundle such core-image-tiny-initramfs to the kernel. Therefore I can define INITRAMFS_IMAGE = "core-image-tiny-initramfs" and INITRAMFS_IMAGE_BUNDLE = "1" in my local.conf.11:26
*** gtristan <gtristan!~tristanva@> has quit IRC11:26
LetoThe2ndfbre: sounds pretty much like a generic usecase of an initramfs.11:27
fbreLetoThe2nd: I even managed to bitbake such configuration, but the question is how to get the image on sd card. Because: as soon as I add those INITRAMFS_IMAGE and INITRAMFS_IMAGE_BUNDLE variables to my local.conf file, bitbake does not result in such typical NXP output files anymore. It seems to break the NXP way of building an .sdcard file. In11:30
fbresuch case I just get Image.....bin files. Somehow I need to find out how to put that in the right way on my sd card.11:30
LetoThe2ndfbre: like i said: learn how to use wic, or demand support from your trustworthy sales rep/FAE that provides your hardware.11:31
fbreLetoThe2nd: hmm yes... Usually you just have contact to FAEs which do not have a clue about such special topics. So you usually end up finding it out by yourself. I think I should learn to understand that wic thingy as next step.11:33
fbreLetoThe2nd: My hope was just today "zeus" can handle initramfs bundling better than my current version "sumo" because of a chance that NXP may have improved their layers in the meanwhile.11:38
LetoThe2ndfbre: your wording reversed to your expectations. they really improved in getting rid of their own, homebrewn .sdcard implementation and are using the common technique called "wic.11:39
LetoThe2ndfbre: the problem is that you know only the old, "wrong" way.11:39
LetoThe2ndso whatever you would have hoped for would be the exact opposite for all the rest of the world, because nobody wants to got back to the ages where each and every BSP vendor would ship custom magic for the image formats.11:40
LetoThe2ndfbre: see:
fbreLetoThe2nd: yes, that's useful information that you tell me they dropped .sdcard support in the meanwhile. This makes my decision to get on the wic track11:42
LetoThe2ndlooks good to me. all the partitioning etc. magic nicely canned up.11:42
LetoThe2ndso, just guessing, it might be even enough to copy one or two additional files to the boot partition.11:43
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:45
*** berton <berton!~berton@> has joined #yocto12:11
fbreNow I hacked sources/poky/meta/recipes-core/images/ and added   aarch64. Hmm well, the bitbake build runs a bit further now but stopped with error: Failed to spawn fakeroot worker to run No such file or directory:12:11
fbreSeems "zeus" also does weird things with sdcard and does not support my aarch6412:12
fbreI go back to "sumo" and the wic...12:14
osullivan99hello everybody, i have a TQMa57xx and want to find out where I can find u-boot 2019.04 in yocto. can anybody help me please?12:17
osullivan99there must be somethin like a config file where it is decided which u-boot is used, but I dont know which one12:18
*** retoatwork <retoatwork!~retoatwor@> has quit IRC12:24
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto12:24
LetoThe2ndosullivan99: somewhere in the bsp layer provided by the company that sells this "TQMa57xx"12:35
osullivan99yeah that's where I think it is. how would you try to find out?12:39
LetoThe2ndosullivan99: by looking at it?12:42
fbreLetoThe2nd: Thanx a lot! Bye Bye for today12:42
*** ericch <ericch!> has joined #yocto12:42
LetoThe2ndosullivan99: i would guess: recipes-bsp/u-boot-xxx .....12:42
osullivan99LetoThe2nd: there are only recipes inside, 4 *.bb files12:45
LetoThe2ndosullivan99: i would expect that, yes.12:45
*** fbre <fbre!91fdde45@> has quit IRC12:45
LetoThe2ndosullivan99: the recipes define which version is used. which was your question, not?12:45
osullivan99i already know which u-boot is used as i can see in in the docu12:45
osullivan99but I want to know where to configure the correct version12:46
LetoThe2ndosullivan99: "config file where it is decided which u-boot is used" thats what you asked. the recipes are that file. you cannot choose freely at will.12:46
LetoThe2ndor, you can, if you provide alternate recipes for the version you want.12:47
osullivan99my boss wants me to port yocto on an other board, so first i wanted to find out where to configure which u boot version is used12:47
LetoThe2ndosullivan99: if there is more than one u-boot recipe, then the higher version is automatically picked. if you want to override that, based on machine compatibility, then you can do that in the machine config file. but there is no file where you would just write "xxx.yy.z", and then u-boot-xxx.yy.z will be used.12:48
osullivan99i see12:49
osullivan99that makes sense12:49
*** paulg <paulg!> has joined #yocto12:56
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:57
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto13:01
*** kaspter <kaspter!~Instantbi@> has quit IRC13:08
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC13:09
*** lucaceresoli <lucaceresoli!> has joined #yocto13:15
*** creich <creich!> has quit IRC13:17
*** creich <creich!> has joined #yocto13:18
*** kaspter <kaspter!~Instantbi@> has joined #yocto13:19
*** kpo_ <kpo_!> has joined #yocto13:25
*** matthewzmd <matthewzmd!> has joined #yocto13:31
*** rcrudo <rcrudo!~rcrudo@2001:16b8:c24e:600:46c3:cbfb:8490:d6a6> has quit IRC13:33
*** kaspter <kaspter!~Instantbi@> has quit IRC13:38
*** eduardas <eduardas!~eduardas@> has joined #yocto13:44
*** stbenz6 <stbenz6!> has quit IRC13:47
*** stbenz6 <stbenz6!> has joined #yocto13:48
*** yoctonoob <yoctonoob!~yoctonoob@> has joined #yocto13:53
*** yoctonoob <yoctonoob!~yoctonoob@> has quit IRC13:55
*** hankyban <hankyban!b92ed46e@> has left #yocto13:58
*** marka <marka!> has joined #yocto13:58
*** ant__ <ant__!> has joined #yocto14:00
*** paulg_ <paulg_!> has joined #yocto14:00
*** rcrudo <rcrudo!> has joined #yocto14:05
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC14:10
*** PaowZ_ <PaowZ_!~Vince@> has joined #yocto14:14
*** mi99 <mi99!~asd@> has joined #yocto14:15
*** vmeson <vmeson!> has joined #yocto14:27
*** jrdn <jrdn!> has joined #yocto14:27
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto14:29
*** goliath <goliath!~goliath@> has quit IRC14:30
*** zandrey <zandrey!~zandrey@> has joined #yocto14:34
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has joined #yocto14:45
*** jobroe <jobroe!> has quit IRC14:52
*** rcoote <rcoote!> has quit IRC14:54
*** mckoan|away is now known as mckoan14:56
*** rcoote <rcoote!> has joined #yocto14:56
*** NiksDev <NiksDev!~NiksDev@> has quit IRC14:57
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto14:57
osullivan99does anybody know how to port yocto target from one ARM processor to an other one?15:07
*** rcoote <rcoote!> has quit IRC15:08
*** eduardas <eduardas!~eduardas@> has quit IRC15:16
*** j241 <j241!> has joined #yocto15:16
LetoThe2ndosullivan99 make a bootloader work, make the kernel work, pour everything into a new bsp layer. use an existing bsp layer as blueprint.15:17
LetoThe2ndosullivan99: also see
osullivan99LetoThe2nd: i know that guide, but i want to know how to tell the compiler which CPU is used (e.g. ARM v8 vs ARM v15)15:20
osullivan99otherwise I could just put the same sd cards into differnt boards but i dont think different CPUs understand same binary files15:21
LetoThe2ndosullivan99: look at how the machine confs include stuff from here:
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC15:22
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto15:23
osullivan99oops i'm wrong15:29
osullivan99this one is new target15:29
*** goliath <goliath!> has joined #yocto15:30
marexosullivan99: if you compile stuff for CA8, it will run on pretty much anything newer15:33
marexit will not run in optimal way though15:33
osullivan99marex: i'm porting from A15 to A815:35
marexosullivan99: I presume thats some TI platform ?15:36
osullivan99yes it is, new board is based on am335x15:38
*** matthewzmd <matthewzmd!> has quit IRC15:38
osullivan99marex: porting am57xx -> am335x15:39
*** matthewzmd <matthewzmd!> has joined #yocto15:39
marexthen yeah, you want to tweak the tunes15:40
*** gtristan <gtristan!~tristanva@> has joined #yocto15:40
osullivan99marex: do you know how? i can only find qemu flag in local.conf15:43
*** fl0v0 <fl0v0!~fvo@> has quit IRC15:43
osullivan99how do i refer to .inc files?15:44
marex$ cat conf/machine/include/dh-stm32mp1-common.inc15:44
marexDEFAULTTUNE ?= "cortexa7thf-neon-vfpv4"15:44
marexrequire conf/machine/include/tune-cortexa7.inc15:44
marexthats for CA7 for example15:44
marexyou want something similar for CA815:44
marexah, wait15:44
marexDEFAULTTUNE ?= "cortexa8thf-neon"15:45
marexrequire conf/machine/include/tune-cortexa8.inc15:45
marexthat should work for CA8 , at least for iMX53 it does15:45
osullivan99marex i guess it is different here, i cant find those includes15:46
osullivan99all from the board manufacturer15:46
osullivan99but now i think i have an idea15:46
marexthey are in OE-core, no ?15:47
marexoe-core$ find . -name tune-cortexa8.inc15:47
*** roussinm <roussinm!> has joined #yocto15:48
osullivan99yeah it was my fault, i've looked inside board specific layer15:49
*** hpsy <hpsy!~hpsy@> has quit IRC15:49
*** hpsy <hpsy!~hpsy@> has joined #yocto15:49
*** gsalazar <gsalazar!5e3dbd6b@gateway/web/cgi-irc/> has quit IRC15:50
kergothRP: do we have a way to force a signature checksum to a particular/current value yet, in cases where we know our changes won't affect the output? I know we used to have the lock functionality, but iirc that just made it fatally error if there was a mismatch rather than forcing it to use an existing sstate archive15:51
*** matthewzmd <matthewzmd!> has quit IRC15:51
*** gsalazar <gsalazar!5e3dbd6b@gateway/web/cgi-irc/> has joined #yocto15:52
*** matthewzmd <matthewzmd!> has joined #yocto15:52
*** jmiehe <jmiehe!> has quit IRC15:57
osullivan99marex: MACHINE=cortexa8thf-neon is invalid. Please set a valid MACHINE in your local.conf, environment or other configuration file.16:00
osullivan99on my configuration i have several layers, board specific layer might require MACHINE keyword instead of DEFAULTTUNE if I understand correctly16:02
kergothyou should never be setting DEFAULTTUNE directly except for specific and temporary testing16:04
kergoththe machine sets that16:04
osullivan99kergoth: so how do i set correct MACHINE?16:05
kergothif you're working with new unsupported hardware, you need to be creating the conf/machine/yourmachine.conf and setting MACHINE to that, and adjusting the tuning in the machine .conf to what you require16:06
osullivan99makes sense16:08
*** zandrey <zandrey!~zandrey@> has quit IRC16:13
*** mbulut <mbulut!> has quit IRC16:14
*** mckoan is now known as mckoan|away16:14
osullivan99kergoth: seems to work now, at least compiling16:17
marexkergoth: which machine sets DEFAULTTUNE ?16:20
kergothmarex: I don't understand the question. Every machine sets it one way or another. Either they include the tune file and let that define it, or they define it themselves instead16:21
marex16:04 < kergoth> you should never be setting DEFAULTTUNE directly except for specific and temporary testing16:21
kergothevery tune has a DEFAULTTUNE ?= line16:21
marex16:04 < kergoth> the machine sets that16:21
marexthis ^16:21
kergothyes, every machine16:21
marexkergoth: I think osullivan99 is writing a machine config16:21
marexkergoth: so it should have that line, no?16:21
kergoththat's what a machine *is*, it defines what the target is, first by including the needed tune file16:23
kergoththe original question implied that they were setting DEFAULTTUNE *instead* of MACHINE16:23
kergothbut that doesn't make sense, if they're defining them in the same context (local.conf), it's wrong16:23
kergothit's not either/or, it's both16:23
marexall right, I think we're on the same page16:24
kergothagreed, wasn't entirely clear what was being done, but they seem to be making progress, so it's all good :)16:25
*** frsc <frsc!> has quit IRC16:30
*** matthewz_ <matthewz_!~user@> has joined #yocto16:48
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:48
*** matthewzmd <matthewzmd!> has quit IRC16:49
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC16:59
*** lucaceresoli <lucaceresoli!> has quit IRC17:01
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC17:09
osullivan99thank you guys, compiling finished, see you17:13
*** osullivan99 <osullivan99!> has quit IRC17:13
*** rcrudo <rcrudo!> has quit IRC17:23
*** hipr_c <hipr_c!Thunderbir@gateway/vpn/nordvpn/hiprc/x-57922908> has joined #yocto17:36
*** vineela <vineela!~vtummala@> has joined #yocto17:49
*** stephano <stephano!> has joined #yocto17:50
*** hipr_c <hipr_c!Thunderbir@gateway/vpn/nordvpn/hiprc/x-57922908> has joined #yocto17:57
*** gsalazar <gsalazar!5e3dbd6b@gateway/web/cgi-irc/> has quit IRC18:02
*** Saur <Saur!pkj@nat/axis/x-rdhrzjonxrrxxode> has quit IRC18:08
*** kiwi_29 <kiwi_29!> has joined #yocto18:18
*** j241 <j241!> has quit IRC18:41
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC19:03
*** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto19:03
*** aidanh_ is now known as aidanh19:04
*** roussinm <roussinm!> has quit IRC19:13
*** King_In4 <King_In4!~King_InuY@> has joined #yocto19:15
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC19:16
*** kiwi_29_ <kiwi_29_!> has joined #yocto19:18
*** kiwi_29 <kiwi_29!> has quit IRC19:18
*** roussinm <roussinm!> has joined #yocto19:26
*** NiksDev <NiksDev!~NiksDev@> has quit IRC19:38
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto19:38
*** kiwi_29_ <kiwi_29_!> has quit IRC19:58
*** kiwi_29 <kiwi_29!> has joined #yocto20:03
*** matthewz_ <matthewz_!~user@> has quit IRC20:05
khemRP: the -mfpu= failure seen in perf is seen with genericx86-64 and beaglebone edgerouter etc. seems to occur with meta-yocto-bsp kernels but qemu versions all work fine20:09
khemzeddii: whats the difference ?20:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:36
zeddiithere's no difference, if you are using the updated SRCREVs, they are all building from the same branches.20:52
zeddiiRP mentioned his hacked up patch. That would have been bumping the SRCREVs20:52
*** bluelightning <bluelightning!~pauleg@pdpc/supporter/professional/bluelightning> has joined #yocto20:53
*** zandrey <zandrey!> has joined #yocto20:59
*** awe002 <awe002!~awe00@unaffiliated/awe00> has quit IRC21:12
*** beneth <beneth!> has left #yocto21:13
*** kiwi_29 <kiwi_29!> has quit IRC21:17
*** berton <berton!~berton@> has quit IRC21:21
*** kiwi_29 <kiwi_29!> has joined #yocto21:29
*** vineela <vineela!~vtummala@> has quit IRC21:32
*** awe002 <awe002!~awe00@unaffiliated/awe00> has joined #yocto21:34
JaMapaulbarker: Hi, did you get the necessary permissions to install the PR closing app on openembedded github?21:35
*** vineela <vineela!~vtummala@> has joined #yocto21:36
paulbarkerJaMa: Not yet, I need to ping Crofton|cloud again but I've been busy21:38
JaMapaulbarker: OK, thanks for update21:38
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has joined #yocto21:41
JaMazeddii: talking about meta-virt compatibility, is every linux-yocto kernel supposed to have cfg/virtio.scc in kernel-meta?21:42
JaMazeddii: it's included in but seems like new 5.4 linux-raspberrypi kernel doesn't have this and fails because of it21:43
*** bluelightning <bluelightning!~pauleg@pdpc/supporter/professional/bluelightning> has quit IRC22:00
RPkhem, zeddii: I don't understand why those were failing :(22:00
*** bluelightning <bluelightning!~pauleg@2406:e003:13a8:9001:7805:4668:5be2:914e> has joined #yocto22:01
*** bluelightning1 <bluelightning1!~pauleg@> has joined #yocto22:03
*** bluelightning <bluelightning!~pauleg@2406:e003:13a8:9001:7805:4668:5be2:914e> has quit IRC22:06
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC22:08
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto22:10
*** agust <agust!> has quit IRC22:12
*** kiwi_29_ <kiwi_29_!> has joined #yocto22:14
*** kiwi_29 <kiwi_29!> has quit IRC22:14
*** leon-anavi <leon-anavi!~Leon@> has quit IRC22:23
*** goliath <goliath!> has quit IRC22:37
*** kiwi_29_ <kiwi_29_!> has quit IRC23:02
*** codusnocturnus <codusnocturnus!~codusnoct@2600:8800:a601:3a00:f535:83b2:312e:b124> has quit IRC23:08
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC23:08
*** paulg_ <paulg_!> has quit IRC23:11
*** bluelightning1 <bluelightning1!~pauleg@> has quit IRC23:16
*** bluelightning1 <bluelightning1!~pauleg@2406:e003:13a8:9001:9dbb:c35:74e6:a468> has joined #yocto23:16
*** vineela <vineela!~vtummala@> has quit IRC23:22
*** vineela <vineela!~vtummala@> has joined #yocto23:30
*** bluelightning1 <bluelightning1!~pauleg@2406:e003:13a8:9001:9dbb:c35:74e6:a468> has quit IRC23:39

Generated by 2.17.2 by Marius Gedminas - find it at!