*** adca <adca!~adca@193.202.22.66> has quit IRC | 00:09 | |
Tartarus | I ask since right now'ish we're about to mark that board Orphan in U-Boot | 00:15 |
---|---|---|
Tartarus | And the main thing that's needed to have it not be orphan is someone with a board willing to boot U-Boot from time to time | 00:16 |
Tartarus | Which is kinda something the Yocto person with the board needs to do anyhow :) | 00:16 |
*** martinkelly1 <martinkelly1!~martin@205.175.119.34> has quit IRC | 00:22 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 00:37 | |
*** kaspter <kaspter!~Instantbi@183.134.100.75> has joined #yocto | 00:38 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 00:40 | |
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC | 00:40 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 00:42 | |
*** Bunio_FH <Bunio_FH!~bunio@156.17.239.1> has quit IRC | 01:00 | |
*** majuk_ <majuk_!~majuk@75-163-182-137.clsp.qwest.net> has joined #yocto | 01:02 | |
*** majuk <majuk!~majuk@75-163-182-137.clsp.qwest.net> has quit IRC | 01:05 | |
*** majuk_ <majuk_!~majuk@75-163-182-137.clsp.qwest.net> has quit IRC | 01:07 | |
*** Guest45773 <Guest45773!95c73efe@gateway/web/freenode/ip.149.199.62.254> has quit IRC | 01:10 | |
*** armpit <armpit!~armpit@2601:202:4000:1184:2cf6:ec2c:db92:7477> has quit IRC | 01:14 | |
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC | 01:20 | |
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto | 01:25 | |
*** armpit <armpit!~armpit@2601:202:4000:1184:29c7:2ead:a5b2:6da1> has joined #yocto | 01:27 | |
*** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::2> has quit IRC | 01:30 | |
*** nemunaire <nemunaire!~nemunaire@ra.nemunai.re> has joined #yocto | 01:31 | |
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has quit IRC | 01:33 | |
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC | 02:00 | |
*** tlwoerner <tlwoerner!~Trevor@206.248.190.95> has joined #yocto | 02:02 | |
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto | 02:02 | |
*** kaspter <kaspter!~Instantbi@183.134.100.75> has quit IRC | 02:43 | |
*** majuk <majuk!~majuk@75-163-182-137.clsp.qwest.net> has joined #yocto | 03:04 | |
*** kaspter <kaspter!~Instantbi@183.128.191.7> has joined #yocto | 03:06 | |
*** majuk <majuk!~majuk@75-163-182-137.clsp.qwest.net> has quit IRC | 03:08 | |
*** ctlnwr <ctlnwr!~catalin@89.121.200.102> has quit IRC | 03:38 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 03:50 | |
-YoctoAutoBuilder- build #968 of build-appliance is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/build-appliance/builds/968 | 04:03 | |
*** ctlnwr <ctlnwr!~catalin@89.121.200.102> has joined #yocto | 04:06 | |
-YoctoAutoBuilder- build #978 of nightly-no-x11 is complete: Failure [failed BuildImages] Build details are at https://autobuilder.yocto.io/builders/nightly-no-x11/builds/978 | 04:22 | |
*** stephano <stephano!~stephano@134.134.139.72> has quit IRC | 04:27 | |
*** Bunio_FH <Bunio_FH!~bunio@156.17.239.1> has joined #yocto | 04:29 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 04:30 | |
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC | 04:39 | |
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has quit IRC | 04:40 | |
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto | 04:40 | |
*** pk <pk!c6af4424@gateway/web/freenode/ip.198.175.68.36> has joined #yocto | 04:40 | |
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has joined #yocto | 04:40 | |
*** yourfate <yourfate!~yourfate@unaffiliated/yourfate> has quit IRC | 04:40 | |
pk | how can i modify recipe and upgrade "PR" for 'm4' | 04:41 |
*** gtristan <gtristan!~tristanva@110.11.179.72> has joined #yocto | 04:42 | |
*** yourfate <yourfate!~yourfate@unaffiliated/yourfate> has joined #yocto | 04:43 | |
*** oob <oob!~paulg@partnervpn-ala.windriver.com> has joined #yocto | 04:45 | |
*** paulg_ <paulg_!~paulg@128.224.252.2> has quit IRC | 04:49 | |
*** OnkelUlla <OnkelUlla!~uol@ptx.hi.pengutronix.de> has quit IRC | 04:49 | |
*** OnkelUlla <OnkelUlla!~uol@ptx.hi.pengutronix.de> has joined #yocto | 04:52 | |
*** paulg_ <paulg_!~paulg@128.224.252.2> has joined #yocto | 05:06 | |
*** oob <oob!~paulg@partnervpn-ala.windriver.com> has quit IRC | 05:10 | |
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.192.94.34.34> has quit IRC | 05:20 | |
*** agust <agust!~agust@p50887D26.dip0.t-ipconnect.de> has joined #yocto | 05:38 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 05:57 | |
yocti | New news from stackoverflow: do_rootfs: Can't install packagegroup-core-x11-utils-1.0-r40@all: no package provides xserver-nodm-init <https://stackoverflow.com/questions/37266581/do-rootfs-cant-install-packagegroup-core-x11-utils-1-0-r40all-no-package-pro> | 05:57 |
*** frieder <frieder!~frieder@mue-88-130-69-093.dsl.tropolys.de> has joined #yocto | 06:05 | |
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has quit IRC | 06:11 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 06:11 | |
*** dlan <dlan!~dennis@58.246.136.202> has joined #yocto | 06:13 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 06:13 | |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-ynidzcagajpepsrn> has quit IRC | 06:13 | |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-frqmitfpmmiywdcf> has quit IRC | 06:19 | |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-zxbfctdyeuvpwhge> has joined #yocto | 06:19 | |
*** mdnneo <mdnneo!~umaucher@217.89.178.116> has joined #yocto | 06:22 | |
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has joined #yocto | 06:26 | |
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has joined #yocto | 06:28 | |
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 06:36 | |
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 06:41 | |
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 06:43 | |
*** mckoan|away is now known as mckoan | 06:55 | |
*** fl0v0 <fl0v0!~fvo@229-134-142-46.pool.kielnet.net> has joined #yocto | 06:56 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 07:03 | |
*** mckoan <mckoan!~marco@host48-40-static.9-79-b.business.telecomitalia.it> has quit IRC | 07:04 | |
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has joined #yocto | 07:04 | |
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has joined #yocto | 07:07 | |
*** rajm <rajm!~robertmar@167.98.27.229> has joined #yocto | 07:12 | |
*** vdehors <vdehors!~vdehors@91.162.62.2> has joined #yocto | 07:15 | |
*** fancer <fancer!sid180736@gateway/web/irccloud.com/x-fsfvxewbyuyenxkz> has joined #yocto | 07:18 | |
pk | anyone know how to upgrade PR service of m4 recipe | 07:22 |
*** clement_ <clement_!~clement@LNeuilly-657-1-4-190.w81-250.abo.wanadoo.fr> has joined #yocto | 07:34 | |
*** acrap <acrap!~acrap@host-85-237-33-147.dsl.sura.ru> has joined #yocto | 07:36 | |
acrap | Hi, folks! | 07:36 |
vladzouth | <vladzouth> Hi i am facing some issue about installing linuxrc script on my rootfs, the error is : miscellaneous-0.1-r0 do_package: QA Issue: miscellaneous: Files/directories were installed but not shipped in any package: /linuxrc. Here is my recipe file https://pastebin.com/0SZzYWPF. Anyone know how to work around this issue? | 07:36 |
acrap | I can get list of recipes with "bitbake -s", but how can I get it with license information? '-s' gives me only name of recipe, version and revision | 07:37 |
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has joined #yocto | 07:39 | |
*** mm_ <mm_!5aa14b7c@gateway/web/freenode/ip.90.161.75.124> has joined #yocto | 07:46 | |
nayfe | vladzouth: what is "MY_FILES"? you cannot add something that is not in SRC_URI | 07:49 |
nayfe | acrap: oe-pkgdata-util package-info -e LICENSE <package> | 07:50 |
nayfe | acrap: or bitbake -e <recipe> | grep ^LICENSE | 07:51 |
*** vishnu_nk <vishnu_nk!~vishnunk@2001:420:5244:1300:b9c2:a00d:76ad:90d2> has joined #yocto | 07:53 | |
vladzouth | nayfe: "My_FILE" is the directory where the linuxrc script is. | 07:54 |
nayfe | vladzouth: you can look at https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#building-software-from-an-external-source to replace MY_FILES, and after that, you'll need in do_install() to replace install ... ${MY_FILES} by "install -m 0755 ${S}/linuxrc ${D}/linuxrc" | 07:55 |
*** prabhakarlad <prabhakarlad!~prabhakar@194.75.40.178> has joined #yocto | 07:55 | |
*** morphis <morphis!~morphis@213.61.67.157> has joined #yocto | 07:55 | |
nayfe | in fact you don't need MY_FILES variable as it is in layer | 07:56 |
nayfe | just replace it by ${S} | 07:56 |
nayfe | it will search the correct path automatically | 07:57 |
vladzouth | nayfe: OK, thanks! | 07:57 |
*** lfa <lfa!~lfa@217.19.35.51> has quit IRC | 07:57 | |
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto | 07:59 | |
nayfe | <vladzouth> finally in FILES_${PN}, you have to remove ${D} | 07:59 |
*** tz <tz!~tz@orange.tzarc.io> has quit IRC | 08:01 | |
nayfe | vladzouth: but, if you already have a linuxrc file provided by busybox for instance, you cannot create a "patch" recipe to replace it, you have to bbappend that recipe or patch linuxrc at the very end with https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-ROOTFS_POSTPROCESS_COMMAND | 08:02 |
*** gtristan <gtristan!~tristanva@110.11.179.72> has quit IRC | 08:03 | |
*** tz <tz!~tz@orange.tzarc.io> has joined #yocto | 08:05 | |
vladzouth | nayfe: In fact, i don't have a linuxrc provided by busybox in my images. Indeed, is there a way to tell busybox to include the linuxrc script file? | 08:05 |
acrap | nayfe: thanks | 08:08 |
*** vishnu_nk <vishnu_nk!~vishnunk@2001:420:5244:1300:b9c2:a00d:76ad:90d2> has left #yocto | 08:09 | |
*** clement_ <clement_!~clement@LNeuilly-657-1-4-190.w81-250.abo.wanadoo.fr> has quit IRC | 08:10 | |
nayfe | vladzouth: ok so your recipe will be ok after corrections | 08:13 |
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC | 08:21 | |
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has joined #yocto | 08:22 | |
vladzouth | nayfe: i still have the same issue after adding INHERIT="externalsrc" on my local.conf, defining EXTERNALSRC on my recipe file and changing the do_install function with what you told me | 08:23 |
*** peacemem_ <peacemem_!~textual@128.130.84.221> has joined #yocto | 08:27 | |
nayfe | <vladzouth: in fact you dont need externalsrc stuff, i was mistaken, all you need to do from original recipe is remove MY_FILES definition, in do_install(), replace MY_FILES by ${S} and in FILES_${PN} line remove ${D} | 08:28 |
*** peacemem_ <peacemem_!~textual@128.130.84.221> has quit IRC | 08:29 | |
vladzouth | nayfe: it works, thank you! | 08:36 |
nayfe | vladzouth: np | 08:38 |
nayfe | acrap: np | 08:38 |
*** adca <adca!~adca@193.202.22.66> has joined #yocto | 08:53 | |
*** majuk <majuk!~majuk@75-163-182-137.clsp.qwest.net> has joined #yocto | 09:02 | |
*** majuk <majuk!~majuk@75-163-182-137.clsp.qwest.net> has quit IRC | 09:07 | |
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto | 09:15 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 09:15 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 09:16 | |
prabhakarlad | Hi all, I am using the default network manager provided by yocto I want create a hotspot (AP) for my wifi interface, are ther any recipes to do that or any pointer for getting it working ? | 09:21 |
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has quit IRC | 09:22 | |
LetoThe2nd | prabhakarlad: http://layers.openembedded.org/layerindex/recipe/28409/ | 09:22 |
*** ant_work <ant_work!~ant__@host136-176-dynamic.27-79-r.retail.telecomitalia.it> has joined #yocto | 09:22 | |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 09:23 | |
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has joined #yocto | 09:24 | |
*** lfa <lfa!~lfa@217.19.35.54> has joined #yocto | 09:29 | |
prabhakarlad | LetoThe2nd: thank you for the pointer :) | 09:36 |
*** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has quit IRC | 09:37 | |
*** diembed <diembed!~diembed@ip-62-235-26-45.dsl.scarlet.be> has joined #yocto | 09:37 | |
*** d3r3k <d3r3k!uid190567@gateway/web/irccloud.com/x-yomummwnakawtwpx> has quit IRC | 09:40 | |
*** jmk <jmk!~julien@130.93.18.230> has joined #yocto | 09:43 | |
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has quit IRC | 09:50 | |
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC | 10:09 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 10:12 | |
*** anujm <anujm!anujm@nat/intel/x-pkiinskpapwruvit> has joined #yocto | 10:23 | |
*** morphis <morphis!~morphis@213.61.67.157> has quit IRC | 10:25 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 10:26 | |
*** lfa <lfa!~lfa@217.19.35.54> has quit IRC | 10:44 | |
-YoctoAutoBuilder- build #979 of nightly-no-x11 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-no-x11/builds/979 | 10:46 | |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto | 11:16 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 11:18 | |
*** armpit <armpit!~armpit@2601:202:4000:1184:29c7:2ead:a5b2:6da1> has quit IRC | 11:21 | |
*** morphis <morphis!~morphis@213.61.67.157> has joined #yocto | 11:25 | |
*** morphis <morphis!~morphis@213.61.67.157> has quit IRC | 11:33 | |
*** acrap <acrap!~acrap@host-85-237-33-147.dsl.sura.ru> has quit IRC | 11:36 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 11:38 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 11:48 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 11:49 | |
*** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has joined #yocto | 11:53 | |
*** anujm <anujm!anujm@nat/intel/x-pkiinskpapwruvit> has quit IRC | 11:54 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 11:56 | |
yocti | New news from stackoverflow: Yocto - Bitbake - Example recipe to add a line in /etc/inittab file <https://stackoverflow.com/questions/42281409/yocto-bitbake-example-recipe-to-add-a-line-in-etc-inittab-file> | 11:58 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 12:01 | |
*** peacememories <peacememories!~textual@e255-130.eduroam.tuwien.ac.at> has joined #yocto | 12:02 | |
*** clement_ <clement_!~clement@LNeuilly-657-1-4-190.w81-250.abo.wanadoo.fr> has joined #yocto | 12:02 | |
pk | while running build-appliance-image it resulted in - ERROR: libx11-native-1_1.6.5-r0 do_configure: autoreconf execution failed. | 12:07 |
*** diembed <diembed!~diembed@ip-62-235-26-45.dsl.scarlet.be> has quit IRC | 12:13 | |
*** aratiu <aratiu!~adi@80.97.64.55> has quit IRC | 12:19 | |
*** aratiu <aratiu!~adi@80.97.64.55> has joined #yocto | 12:19 | |
-YoctoAutoBuilder- build #1005 of nightly-musl is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-musl/builds/1005 | 12:22 | |
*** gtristan <gtristan!~tristanva@110.11.179.89> has joined #yocto | 12:24 | |
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has quit IRC | 12:25 | |
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has joined #yocto | 12:29 | |
*** hackeron <hackeron!~hackeron@gentoo/user/hackeron> has joined #yocto | 12:39 | |
hackeron | Hi, apologies for the ignorant question, I'm trying to choose a platform for an IoT Hub: I'm looking at Ubuntu Core and Yocto (and ResinOS also looks great). What would you say are the advantages/differences of Yocto over Ubuntu Core? | 12:41 |
LetoThe2nd | its basically source-based, development host build (yocto) versus binary-based, in-target (ubuntu) | 12:42 |
LetoThe2nd | not absolutely, there are of course intersections. but basically its that. | 12:42 |
paulbarker | Configurability and a good license compliance workflow are the advantages of Yocto for me | 12:44 |
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.192.94.34.34> has joined #yocto | 12:44 | |
hackeron | ah, ok, so Yocto is more low level, allowing you to build exactly what you want and ubuntu-core is more of a higher level package, trying to tie you into their cloud services and container type? | 12:44 |
Ramose | https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-optee/recipes-security/optee/optee-os_git.bb?h=master#n46 its "{D}/usr/include/optee/export-user_ta/" not getting created on my rootfs | 12:45 |
paulbarker | ResinOS would be good if you want to use Docker containers, but again, those docker containers won't be as configurable and you won't have the same tools you get with Yocto | 12:45 |
Ramose | when I run this recipe | 12:45 |
paulbarker | hackeron: yep, I'd say that's fair | 12:45 |
*** eduardas_m <eduardas_m!~eduardas@213.197.143.19> has joined #yocto | 12:46 | |
hackeron | paulbarker: I see, thank you :) - from what I understand ResinOS is basically Yocto with a few customisation, so it should be possible to keep/remove anything that's useful for the specific requirement? | 12:46 |
paulbarker | Not sure, you'd need to talk to them about it | 12:47 |
Son_Goku | hackeron, Yocto is probably a better platform for this stuff | 12:48 |
Son_Goku | between the two choices, Yocto is easier to customize, and it isn't that difficult to get started | 12:48 |
Son_Goku | it's supported by a number of companies, offering Yocto-based distributions that help you get off the ground quickly | 12:49 |
Son_Goku | whereas Ubuntu Core significantly lacks in diversity | 12:49 |
LetoThe2nd | Son_Goku: despite being a yocto supporter, i actually have to disagree | 12:49 |
Son_Goku | really? | 12:50 |
LetoThe2nd | the only requirement we saw so far is "iot gateway", i firmly believe that theres absolutely no way for anybody to make a proper recommendation on that buzzword alone. | 12:50 |
LetoThe2nd | ah no, "iot hub" | 12:50 |
LetoThe2nd | i'm sorry. | 12:50 |
Son_Goku | :P | 12:50 |
*** marka <marka!~masselst@184.175.21.48> has joined #yocto | 12:51 | |
Son_Goku | LetoThe2nd, judging by what they're comparing, they're looking for a way to build a minimal platform that's relatively easy to maintain going forward | 12:51 |
LetoThe2nd | Son_Goku: assumptions, assumptions, assumptions. | 12:51 |
Son_Goku | hackeron, there's also Wind River Linux: https://github.com/WindRiver-Labs/wrlinux-x | 12:52 |
Son_Goku | fully audited, supportable, and integrated platform | 12:52 |
Son_Goku | and most of the heavy lifting is done for you | 12:53 |
LetoThe2nd | the only really good advice one can give is to really (and i mean, really!) evaluate the specific use case and extract the requirements, then see what fits best. it might be any of the choices that have been named, or something different still | 12:53 |
LetoThe2nd | (and no, "we want to start out with a minimal thing" does *not* count as a proper requirement) | 12:54 |
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 12:54 | |
otavio[m] | Tartarus: I think Stephano has it. | 12:56 |
hackeron | Son_Goku: that's exactly what we're looking for - there are thousands of Gigabyte Brix and Raspberry Pi units at various locations, some on farms using solar panel. Currently we use Ubuntu Sever but a few times per month, the root filesystem inevitably gets corrupt and we need to send a replacement hard drive or SD card. So yes, looking for something that will address this but still won't require manual | 12:57 |
hackeron | firmware updates when we update the app (currently we just rsync the rails source, run bundle install and do a zero downtime restart) | 12:57 |
hackeron | Son_Goku: hmm, is Wind River one of those Yocto based projects? | 12:58 |
Son_Goku | yes | 12:58 |
LetoThe2nd | hackeron: then you actually want a proper update mechanism first, totally independent from the underlying distribution | 12:58 |
LetoThe2nd | hackeron: look at swupdate, rauc.io, mender.io | 12:58 |
Son_Goku | hackeron, RPM-OSTree is a supported update option as well | 12:58 |
Son_Goku | WRLinux offers it as an option, so you can use traditional infra to build software packages and compose it into immutable, atomic updates | 12:59 |
LetoThe2nd | its true that anything openembedded based leans itself more easy to those mechanisms, but the real problem certainly is device management and updates., | 12:59 |
nayfe | otavio[m]: hey, you'r there? | 13:00 |
LetoThe2nd | which again also suggests to look at resin.io, indeed. | 13:00 |
Ramose | can anyone point me out why "install -d ${D}/usr/include/optee/export-user_ta/" do not create optee/export-user_ta/ in rootfs ? | 13:00 |
otavio[m] | nayfe: yes | 13:01 |
otavio[m] | LetoThe2nd: we also offer updatehub.io | 13:01 |
LetoThe2nd | Ramose: assuming that this is inside the do_install stage, you've probably not added it to FILES | 13:02 |
Ramose | yes its in do_install | 13:02 |
nayfe | Did you see my message on mfgtools recipe? | 13:02 |
LetoThe2nd | otavio[m]: there are certainly a variety of more options, absolutely agreed. | 13:02 |
otavio[m] | nayfe: I did not | 13:02 |
otavio[m] | nayfe: what is it? | 13:02 |
hackeron | LetoThe2nd: that's one thing where ubuntu-core looks quite nice, they have unattended automated fill OS update | 13:02 |
nayfe | i just made a recipe for Freescale Mfgtools Linux (master) branch, it runs well on ARM https://github.com/nefethael/meta-random/tree/master/recipes-devtools/mfgtools . Recipe's quite dirty but do you think it makes sense to make a PR on meta-freescale? | 13:03 |
LetoThe2nd | hackeron: don't get me wrong, i'm not trying to get you away from anything. its just that my impression is that your *actual* requirements are something that is not really an ubuntu vs. OE vs. anything question | 13:03 |
hackeron | LetoThe2nd: in terms of device management, all the units are on an OpenVPN and provisioned by Ansible, there's an in house web interface that shows all the health stats and other metrics | 13:04 |
Ramose | LetoThe2nd: What exactly you mean by , you've probably not added it to FILES ? | 13:04 |
otavio[m] | nayfe: Sure. Please prepare a PR so we review it | 13:04 |
LetoThe2nd | Ramose: just what the sentence says. you have probably not added it to the FILES variable of the package, hence it is not packaged and installed to the rootfs, but only to the staging area. | 13:05 |
LetoThe2nd | Ramose: look up FILES in the yocto ref-manual :) | 13:05 |
otavio[m] | hackeron: Usually I prefer to have ready to use images built from Yocto so no changes are need after installation; | 13:06 |
hackeron | LetoThe2nd: sure, I'm just trying to understand what are the different components. So with resin-os you get the device management, which I don't necessarily need, with Yocto I guess I can plug my own in. So if I need to upgade the operating system, say to a new version of the kernel, I guess it's up to me to build that with Yocto? | 13:06 |
nayfe | otavio[m] ok i'll do it when i have time :p | 13:07 |
Ramose | LetoThe2nd: this task https://git.linaro.org/openembedded/meta-linaro.git/tree/meta-optee/recipes-security/optee/optee-os_git.bb?h=master#n44 runs well and packed images in rootfs of same recipe | 13:07 |
otavio[m] | hackeron: that allows for reproducibility in long term | 13:07 |
otavio[m] | and I see this as a critical thing | 13:07 |
hackeron | aratiu: so once built, you never really update the kernel or anything like that? | 13:07 |
LetoThe2nd | hackeron: well, the real power of OE is to create complete images, so no software deployment through pacakges or stuff is required on top | 13:07 |
Ramose | LetoThe2nd: install -m 644 ${B}/out/arm-plat-${OPTEEOUTPUTMACHINE}/core/*.bin ${D}${nonarch_base_libdir}/firmware/, It runs well | 13:08 |
otavio[m] | nayfe: thanks I look forward to it. mfgtools is a nightmare :-) | 13:08 |
Ramose | I guess you are talking about FILES_${PN} ? | 13:09 |
hackeron | LetoThe2nd: in my case I want to push software updates multiple times per week, possible per day - but I guess there can be containers on top of the OS. In terms of US that generally is only updated once every 1-2 years, I guess this is the bit that would be difficult? | 13:09 |
hackeron | in terms of the OS* | 13:10 |
*** JaMa <JaMa!~martin@217.30.68.212> has quit IRC | 13:11 | |
nayfe | otavio: indeed :) i just saw yesterday that a new "uuu" is coming, hope it will be better ... I prefer imx_usb_loader, but when legacy stuff comes into game, it is hard to break it ... and it's quite funny to flash a board from another one :) | 13:11 |
LetoThe2nd | hackeron: i'd say it depends a bit on the architecture. given a writeable rootfs, there's certainly nothign keeping you from deploying smaller updates as a package stream | 13:11 |
LetoThe2nd | which on the other hand breaks more easily | 13:12 |
otavio[m] | nayfe: for sure. | 13:12 |
nayfe | you prefer PR or mailing-list? | 13:12 |
hackeron | LetoThe2nd: from what I understand there are 2 read-only root filesystems, so you can always revert if an update fails? | 13:13 |
otavio[m] | nayfe: I think we can start on a PR; so we can go over the review process. | 13:14 |
hackeron | LetoThe2nd: so in terms of the software packages, that will just be say a docker container, which also handles revert, etc -- I'm more curious how the kernel updates happen and how to prevent bricking the units, hmmm | 13:14 |
otavio[m] | nayfe: depending on how big it is, we can send it for ML | 13:14 |
LetoThe2nd | hackeron: thats a common method, yes. but its actually part of the update strategy, not of yocto/OE. those do just buld those rootfs | 13:14 |
otavio[m] | nayfe: otherwise I can pull it and send. | 13:14 |
nayfe | k PR will do | 13:14 |
Ramose | LetoThe2nd: Cool, it gets created when I replace FILES_${PN}-dev = "/usr/include/optee" with FILES_${PN} = "/usr/include/optee" | 13:15 |
otavio[m] | nayfe: remember, github is a mirror for meta-freescale | 13:15 |
LetoThe2nd | hackeron: try to not think of the kernel as a singular thing to update. think of it (and anything else) as part of a monolithic OS image that is either updated in full, or not at all. | 13:15 |
otavio[m] | hackeron: the A/B system is indeed the most secure way of update. | 13:15 |
otavio[m] | hackeron: it allows you to revert manually or automatically | 13:16 |
otavio[m] | hackeron: as LetoThe2nd said, usually we deal with the system as a single unit. So the kernel is part of it | 13:16 |
otavio[m] | hackeron: the only exception is the bootloader. In updatehub case we detect the running version and update it only when it changes as it is the tricker part of it | 13:17 |
hackeron | otavio[m]: LetoThe2nd: sure, that makes a lot of sense - but with Yocto, I'm guessing there isn't a kind of standard version that I can just go from Yocto 1.0 to Yocto 1.1 which will upgrade this one single unit, including kernel/code libs, etc? | 13:17 |
nayfe | otavio[m]: sorry, which means? PR should be done on other git repo than github? | 13:17 |
LetoThe2nd | hackeron: you're still thinking of yocto as a distribution, with updates. this is jsut not the reight thing. it creates a distribution image, with whatever content you like. | 13:19 |
otavio[m] | hackeron: you can upgrate from 1.0 to 10.0 if need. But you are responsible to handle migrations from the apps yourself. | 13:19 |
LetoThe2nd | hackeron: you have to get your head around the point that yocto is *NOT* running on the target. it is a tool that *CREATES* the image that runs on your target. | 13:19 |
otavio[m] | hackeron: as LetoThe2nd said, you deal it as an atomic version. | 13:20 |
LetoThe2nd | and of course you can feed new versions into that tool, then roll out a newer image. | 13:20 |
otavio[m] | hackeron: not upgrade in package level | 13:20 |
otavio[m] | hackeron: but a full move from A to B | 13:20 |
* otavio[m] sent a long message: otavio[m]_2018-05-03_13:21:30.txt <https://matrix.org/_matrix/media/v1/download/matrix.org/zdZOvGCXJwWAbcTEVIAdfKwG> | 13:21 | |
*** stephano <stephano!~stephano@134.134.139.72> has joined #yocto | 13:21 | |
hackeron | LetoThe2nd: otavio[m]: No, no, I get that, but say I rolled my own image, it has kernel 4.16, it has docker to run my containers, etc -- I then want to update my kernel and docker version and roll a new image. How do I do that? - do I need to go in and manually download the linux kernel sources and any other libraries that I might need to modify and then build a new image? - or is there a kind of base I | 13:24 |
hackeron | can start with that will give me the latest kernel, with sensible defaults and modules, etc? | 13:24 |
LetoThe2nd | hackeron: the upstream state of poky respectively meta-openembedded is basically that base with sensible defaults. | 13:25 |
otavio[m] | Yocto Project usually comes with fairly recent versions. So you'll need to upgrade your base version and use it as base. | 13:26 |
otavio[m] | your base Yocto Project version | 13:26 |
otavio[m] | HOWEVER you are free to do changes, if need. | 13:27 |
hackeron | LetoThe2nd: ah, ok, so I just get the latest poky/meta-opembedded and hopefully my modifications on top of that will still build a working image (or not, lol) | 13:27 |
LetoThe2nd | hackeron: thats the plan, in a nutshell. correct. | 13:27 |
LetoThe2nd | your modifications/addons are located in a so-called layer, that gets added on top | 13:27 |
otavio[m] | That is exactly why Yocto Project serves better embedded devices than Ubuntu, Debian and others. It is very easy to customize whatever is need. | 13:28 |
otavio[m] | hackeron: take a look on the first book I gave the link; it explains this very well | 13:28 |
hackeron | ok, thank you, I'l do more research and experiment, it's making a lot more sense now :) | 13:29 |
LetoThe2nd | hackeron: grab a sandwich and some coolaid, then watch and properly digest https://www.youtube.com/watch?v=bJVYxlkHees&list=PLGYJ6-t7fDZ6VgbKPTeAXOBcnAk9Fonr_&index=6 | 13:29 |
*** armpit <armpit!~armpit@50-233-148-156-static.hfc.comcastbusiness.net> has joined #yocto | 13:29 | |
LetoThe2nd | hackeron: thats the basically bare bones version of the yocto dev day beginner track. and depending on what your timeframe and location are, you might want to join one of the sessions in real life. | 13:29 |
hackeron | aratiu: sorry I missed the book link, is it this? < https://matrix.org/_matrix/media/v1/download/matrix.org/zdZOvGCXJwWAbcTEVIAdfKwG | 13:30 |
hackeron | LetoThe2nd: that's fantastic, thank you, grabbing a coffee and some pork scratchings :P | 13:31 |
*** peacememories <peacememories!~textual@e255-130.eduroam.tuwien.ac.at> has quit IRC | 13:31 | |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-gzakhbbkxsiqmukh> has joined #yocto | 13:31 | |
LetoThe2nd | hackeron: shameless plug: if you're based in germany near cologne, i'm doing a training early in june https://www.buildingiot.de/veranstaltung-6616-erste-schritte-mit-dem-yocto-project.html?id=6616 | 13:32 |
hackeron | LetoThe2nd: Based in London, UK :( - but I'll watch out fo anything yocto related in and around London :) | 13:32 |
*** tf <tf!~tomas@r-finger.com> has joined #yocto | 13:32 | |
LetoThe2nd | hackeron: ELC-E is coming to edinburgh in late october, there probably will be dev day again | 13:33 |
*** tf <tf!~tomas@r-finger.com> has quit IRC | 13:34 | |
*** tf <tf!~tomas@r-finger.com> has joined #yocto | 13:34 | |
armpit | LetoThe2nd, we are trying | 13:35 |
hackeron | LetoThe2nd: what's ELC-E? | 13:35 |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-zxbfctdyeuvpwhge> has quit IRC | 13:36 | |
LetoThe2nd | ELCE: your annual chance to personally blame all OE devs! | 13:36 |
Crofton|work | lol | 13:36 |
*** jmk <jmk!~julien@130.93.18.230> has quit IRC | 13:37 | |
hackeron | lol, sorry, what's OE devs? | 13:37 |
Crofton|work | https://events.linuxfoundation.org/events/elc-openiot-europe-2018/ | 13:37 |
hackeron | oh, OpenEmbedded? | 13:37 |
Crofton|work | The guys that do all the work on the YP :) | 13:37 |
hackeron | got it :) - thank you | 13:37 |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-sfkddcxbyktyehpr> has joined #yocto | 13:37 | |
mckoan | OpenEmbedded, that weird thing which is the foundation of Yocto Project :-D | 13:38 |
Crofton|work | I need to bitch about Active COmmunity members getting labled as hobbyists | 13:38 |
hackeron | So wrlinux-x is built on top of Yocto which is built in top of OpenEmbedded? | 13:39 |
LetoThe2nd | i usually go like this: i blame everybody for breaking everything, making everything overly complicated, and generally being stupid and ugly. then we all get shitfaced. | 13:39 |
LetoThe2nd | (ELCE in a nutshell) | 13:39 |
Crofton|work | lol | 13:41 |
Crofton|work | And LetoThe2nd brings me beer. At least if he doesn't have to fly | 13:41 |
otavio[m] | hackeron: yes, thatis the book link | 13:41 |
Crofton|work | hackeron, basically :) | 13:41 |
Crofton|work | and we get shitfaced, we argue about the meaning of words | 13:42 |
LetoThe2nd | ok, that actually was a bit exaggerated, we're all pretty nice guys. | 13:42 |
Crofton|work | except for me | 13:42 |
LetoThe2nd | but it sounds way more cool | 13:42 |
LetoThe2nd | and i can say with absolute certainty that i have never been sober to the yocto BoF! | 13:43 |
Crofton|work | also there will very likely be an OpenEmbedded developer meeting Sunday before | 13:43 |
Son_Goku | hackeron, yes, WRLinux -> Yocto -> OE | 13:43 |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 13:43 | |
* armpit OE -> MSDos ? | 13:44 | |
mckoan | WRLinux is Yocto for rich people | 13:44 |
*** peacememories <peacememories!~textual@e255-130.eduroam.tuwien.ac.at> has joined #yocto | 13:44 | |
eduardas_m | hello, has anyone successfully generated an SDK with rocko and meta-qt5 (Qt 5.10)? | 13:44 |
armpit | mckoan, the 1% | 13:44 |
mckoan | eduardas_m: yes, of course | 13:45 |
eduardas_m | something broke when moving from Qt 5.9.4 to Qt 5.10 | 13:45 |
eduardas_m | mckoan: I can no longer export the environment correctly | 13:45 |
mckoan | eduardas_m: how do you generate the SDK? | 13:45 |
LetoThe2nd | armpit: \o/ | 13:46 |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 13:46 | |
eduardas_m | mckoan: -c populate_sdk | 13:46 |
mckoan | eduardas_m: nah | 13:46 |
*** stephano <stephano!~stephano@134.134.139.72> has quit IRC | 13:46 | |
LetoThe2nd | i think we need badges here. who's working for which company. :) | 13:46 |
mckoan | eduardas_m: meta-toolchain-qt5 | 13:46 |
*** stephano <stephano!~stephano@134.134.139.72> has joined #yocto | 13:46 | |
RP | armpit: I merged rocko, thanks! | 13:47 |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 13:47 | |
LetoThe2nd | RP: i merged rock into my hifi, does that count too? </SCNR> | 13:47 |
armpit | RP, I saw. thank you | 13:47 |
eduardas_m | mckoan: I was told once by wise Yocto people that Yocto project does not care about that since it's a meta-qt5-specific method | 13:47 |
*** dlan <dlan!~dennis@58.246.136.202> has joined #yocto | 13:48 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 13:48 | |
* mckoan bows to wide people | 13:48 | |
LetoThe2nd | rly? oO | 13:48 |
mckoan | s/wide/wise | 13:48 |
LetoThe2nd | ah. | 13:48 |
eduardas_m | mckoan: it also has the downside of not pulling in everything in the target sysroot | 13:48 |
*** jmk <jmk!~julien@130.93.18.230> has joined #yocto | 13:49 | |
eduardas_m | like v4l2 libraries, etc. | 13:49 |
armpit | RP, pyro is segfaulting in musl ruby, but rocko is not so I suspect fix in later version of ruby | 13:49 |
mckoan | eduardas_m: you could customize the meta-toolchain-qt5 though | 13:49 |
RP | armpit: quite likely, ruby seems to be good at faulting :( | 13:49 |
LetoThe2nd | mckoan: i hereby declare that "typo of the day." | 13:49 |
mckoan | LetoThe2nd: people on diet may become upset | 13:50 |
Crofton|work | if something is worth doing, it is worth doing well. Even segfaulting | 13:50 |
otavio[m] | eduardas_m: you can inherit populate_sdk_qt5 in your custom image and use it instead | 13:50 |
LetoThe2nd | mckoan: thats the point, right | 13:50 |
eduardas_m | otavio[m]: that is exactly what I am doing | 13:50 |
otavio[m] | and what is failing? | 13:51 |
* RP decides he probably doesn't want to think about what meta-qt5 is doing :/ | 13:51 | |
eduardas_m | otavio[m]: the problem is when executing qt5.sh | 13:51 |
otavio[m] | nayfe: I reviewed it. Some comments. | 13:52 |
eduardas_m | otavio[m]: something like qmake -query QT_INSTALL_LIBS gets me an "Empty filename passed to function" | 13:52 |
otavio[m] | eduardas_m: check if it is included inside the environment.d | 13:52 |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 13:52 | |
eduardas_m | otavio[m]: the qt5.sh script itself is definitely there | 13:52 |
otavio[m] | eduardas_m: that is inside master / sumo? | 13:52 |
otavio[m] | eduardas_m: or rocko? | 13:53 |
mckoan | RP: why? | 13:53 |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 13:53 | |
otavio[m] | mckoan: hehe Qt does some black magic to make it all work ;-) | 13:53 |
otavio[m] | RP: so do I; but I can't heh | 13:54 |
eduardas_m | otavio[m]: I am using the meta-qt5 branch for Qt 5.10 currently mainatined by Qt comapny, but same thing used to happen with community meta-qt5 on master (when it was on Qt5.10) | 13:54 |
LetoThe2nd | RP: have you looked at behans intro to bitbake/yp from ELC? | 13:54 |
otavio[m] | eduardas_m: well if you are using Qt company's layer so ask them to support it. | 13:54 |
otavio[m] | eduardas_m: I don't use it myself (but for customers) | 13:55 |
RP | LetoThe2nd: no... | 13:55 |
eduardas_m | otavio[m]: same thing happens with "mainline" meta-qt5 on master last time I used it | 13:55 |
otavio[m] | eduardas_m: if it fails in meta-qt5's layer, in our branches, I can take a look | 13:55 |
otavio[m] | eduardas_m: today? | 13:56 |
LetoThe2nd | RP: citation: ".. its so complex that I doubt anybody knows all about it. Well, maybe except RP." | 13:56 |
otavio[m] | eduardas_m: please check, if it fails I can look at it. | 13:56 |
RP | LetoThe2nd: I'm not sure any of us know all of the system ;-) | 13:57 |
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has quit IRC | 13:57 | |
eduardas_m | otavio[m]: ok, will try with master...will take long to build though... what is the best way to get in touch after checking? | 13:57 |
LetoThe2nd | RP: hehe, it just kinda stuck :) | 13:57 |
otavio[m] | eduardas_m: ping me here or pvt message | 13:58 |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 13:58 | |
eduardas_m | otavio[m]: thank you, will try tomorrow morning with master since my work hours are pretty much over today | 13:59 |
*** dlan <dlan!~dennis@58.246.136.202> has joined #yocto | 13:59 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 13:59 | |
nayfe | otavio[m]: thanks i'll correct PR tomorrow | 13:59 |
otavio[m] | eduardas_m: that's fine. | 14:00 |
otavio[m] | nayfe: sure. | 14:00 |
otavio[m] | nayfe: I think it is simple to fix the build system to properly build the cli and use a single recipe for it | 14:00 |
*** eduardas_m <eduardas_m!~eduardas@213.197.143.19> has quit IRC | 14:00 | |
otavio[m] | nayfe: did you prepare an image for its use? | 14:01 |
nayfe | indeed, but I didn't want to go deeper in that CMakeList.txt :D | 14:01 |
*** peacememories <peacememories!~textual@e255-130.eduroam.tuwien.ac.at> has quit IRC | 14:01 | |
otavio[m] | nayfe: it'll buy some time later, for sure. Also I can push NXP to apply it for next release | 14:01 |
nayfe | build is quite awfull, with plain Makefile that calls cmake, do some copy, relaunch cmake etc :) | 14:02 |
otavio[m] | So think if putting it into the cmake only does not make it simpler. If it does, fork the repository and prepare the changes | 14:03 |
otavio[m] | we can use your fork in meanwhile or fork it inside our orga if you prefer | 14:03 |
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has joined #yocto | 14:03 | |
nayfe | not sure i'll have time for this rework this month is plenty of holidays :) | 14:08 |
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC | 14:11 | |
otavio[m] | nayfe: I hope you do :-D | 14:11 |
*** behanw <behanw!uid110099@gateway/web/irccloud.com/x-hgqlyspciwtyzeuk> has joined #yocto | 14:29 | |
nayfe | there is also the "native" part that could be added too to run it on host ... | 14:29 |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-sfkddcxbyktyehpr> has quit IRC | 14:32 | |
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-lwhcchhdgwmvgccs> has joined #yocto | 14:32 | |
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has quit IRC | 15:03 | |
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has joined #yocto | 15:07 | |
*** martinkelly1 <martinkelly1!~martin@174-21-182-65.tukw.qwest.net> has joined #yocto | 15:16 | |
*** AbleBacon_ <AbleBacon_!~AbleBacon@unaffiliated/ablebacon> has joined #yocto | 15:20 | |
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC | 15:23 | |
*** AbleBacon_ is now known as AbleBacon | 15:23 | |
Tartarus | Hmmm, can INITRAMFS_FSTYPES even theoretically be a list? I don't see anyone doing more than one off hand | 15:25 |
*** martinkelly1 <martinkelly1!~martin@174-21-182-65.tukw.qwest.net> has quit IRC | 15:25 | |
Tartarus | and documentation uses singular words | 15:25 |
ant_work | INITRAMFS_FSTYPES ?= "cpio.gz cpio.xz" works beautifully | 15:26 |
khem | clear | 15:27 |
ant_work | hi khem | 15:27 |
khem | hey ant_work | 15:27 |
khem | howdy | 15:27 |
ant_work | sorry for bothering you by mail | 15:28 |
ant_work | but one of the two klibc devs is 'krank', the other disappeared/offline...so you get the idea | 15:28 |
Tartarus | ant_work: Define works please | 15:29 |
Tartarus | bitbake certainly won't blow up | 15:29 |
Tartarus | But does anything that comes back and plays with INITRAMFS_FSTYPES work as expected? | 15:29 |
ant_work | Tatarus: in use since 5-6 years | 15:29 |
Tartarus | ant_work: where? | 15:29 |
Tartarus | I do believe they will be produced, yes | 15:29 |
ant_work | since kernel could decompress xz intramfs's | 15:29 |
Tartarus | But will wic work or just use the first one found? | 15:30 |
Tartarus | or blow up | 15:30 |
ant_work | you get the two, the kernel recipe defines which one to use | 15:30 |
Tartarus | ant_work: Ah, via which variable? | 15:30 |
Tartarus | Or just a loop and guess? | 15:31 |
ant_work | CONFIG_INITRAMFS_SOURCE="initramfs.cpio.xz" | 15:31 |
ant_work | see meta-handheld layer | 15:31 |
Tartarus | ant_work: OK, any particular machine too? | 15:32 |
ant_work | sure | 15:32 |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-gzakhbbkxsiqmukh> has quit IRC | 15:34 | |
ant_work | well, note you have to define INITRAMFS_IMAG | 15:34 |
ant_work | E | 15:34 |
Tartarus | Yeah | 15:34 |
ant_work | in our case we do force INITRAMFS_TASK = "${INITRAMFS_IMAGE}:do_image_complete" | 15:35 |
Tartarus | RIght | 15:35 |
Tartarus | So, I'm kicking https://github.com/jiazhang0/meta-secure-core/blob/master/meta/recipes-core/images/kernel-initramfs.bb#L39 to be more robust | 15:36 |
Tartarus | And use update-alternatives too in the non-bundled case | 15:36 |
Tartarus | And with your hints, I think the answer is that no, I can't assume INITRAMFS_FSTYPES is singular | 15:36 |
Tartarus | And i need to drop that break out, and continue not using the update-alternatives class directly | 15:36 |
ant_work | I lost track of the last changes butnowadays it should be possible to build two kernel flavours whithout issues | 15:37 |
Tartarus | Or study busybox a bit more | 15:37 |
Tartarus | For dynamic playing with the alternatives list | 15:37 |
Tartarus | thanks | 15:37 |
ant_work | yw | 15:37 |
*** rajm <rajm!~robertmar@167.98.27.229> has quit IRC | 15:47 | |
*** kaspter <kaspter!~Instantbi@183.128.191.7> has quit IRC | 15:47 | |
*** scottrif <scottrif!~scottrif@191.97.80.22> has joined #yocto | 15:55 | |
*** stephano <stephano!~stephano@134.134.139.72> has quit IRC | 15:58 | |
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 15:58 | |
*** ant_work <ant_work!~ant__@host136-176-dynamic.27-79-r.retail.telecomitalia.it> has quit IRC | 16:04 | |
*** fl0v0 <fl0v0!~fvo@229-134-142-46.pool.kielnet.net> has quit IRC | 16:16 | |
*** lusus <lusus!~lusus@62.91.23.180> has quit IRC | 16:19 | |
*** mckoan is now known as mckoan|away | 16:20 | |
*** gnac <gnac!~gnac@or-71-0-52-80.sta.embarqhsd.net> has quit IRC | 16:26 | |
*** lucaceresoli <lucaceresoli!~lucaceres@45.11.168.109.cust.ip.kpnqwest.it> has quit IRC | 16:28 | |
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has quit IRC | 16:29 | |
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has joined #yocto | 16:29 | |
*** Snert_ <Snert_!~snert_@65.74.8.146> has quit IRC | 16:35 | |
*** Snert_ <Snert_!~snert_@65.74.8.146> has joined #yocto | 16:35 | |
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has joined #yocto | 16:44 | |
*** abelal <abelal!~quassel@110.93.212.98> has quit IRC | 16:51 | |
*** abelal <abelal!~quassel@110.93.212.98> has joined #yocto | 16:52 | |
*** vdehors_ <vdehors_!~vdehors@91-162-62-2.subs.proxad.net> has joined #yocto | 16:53 | |
*** vdehors <vdehors!~vdehors@91.162.62.2> has quit IRC | 16:56 | |
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:f8d9:318d:e1a0:814d> has joined #yocto | 16:57 | |
*** vladzouth <vladzouth!500c5411@gateway/web/freenode/ip.80.12.84.17> has quit IRC | 17:02 | |
*** mdnneo <mdnneo!~umaucher@217.89.178.116> has quit IRC | 17:20 | |
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto | 17:37 | |
*** vdehors_ <vdehors_!~vdehors@91-162-62-2.subs.proxad.net> has quit IRC | 17:44 | |
*** aarcane <aarcane!~Christ@173.75.115.107> has joined #yocto | 17:49 | |
*** sbach <sbach!~sbach@8.12.22.97> has joined #yocto | 18:14 | |
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 18:22 | |
*** rob_gries <rob_gries!~rob@96.72.222.9> has quit IRC | 18:37 | |
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:f8d9:318d:e1a0:814d> has quit IRC | 18:40 | |
*** frieder <frieder!~frieder@mue-88-130-69-093.dsl.tropolys.de> has quit IRC | 18:42 | |
*** gtristan <gtristan!~tristanva@110.11.179.89> has quit IRC | 18:50 | |
*** HavoK__ <HavoK__!~neilshivk@97-64-166-118.client.mchsi.com> has joined #yocto | 19:19 | |
HavoK__ | Hey | 19:19 |
HavoK__ | I added new kernel modules and this caused me to have a new kernel package. I used smart PM to update the packages and I can see the modules present under the folder for the new kernel. | 19:20 |
HavoK__ | My question is how can tell the machine to boot using the new kernel. when i put uname -r it seems to be using the old one still | 19:21 |
*** JaMa <JaMa!~martin@217.30.68.212> has joined #yocto | 19:24 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:35 | |
*** bavery_fn <bavery_fn!~bavery@134.134.139.73> has joined #yocto | 19:36 | |
*** HavoK__ <HavoK__!~neilshivk@97-64-166-118.client.mchsi.com> has left #yocto | 19:41 | |
kergoth | that depends on what bootloader you're using | 19:49 |
kergoth | you haven't told us anything about what you're doing, distro, machine, anything | 19:49 |
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:56 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 20:00 | |
*** Bunio_FH <Bunio_FH!~bunio@156.17.239.1> has quit IRC | 20:33 | |
*** fischerm <fischerm!~mfischer@207.114.172.147> has quit IRC | 20:53 | |
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has quit IRC | 20:55 | |
*** marka <marka!~masselst@184.175.21.48> has quit IRC | 20:59 | |
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has joined #yocto | 21:00 | |
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has quit IRC | 21:07 | |
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has joined #yocto | 21:08 | |
*** fischerm <fischerm!~mfischer@207.114.172.147> has joined #yocto | 21:29 | |
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC | 21:40 | |
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has quit IRC | 21:55 | |
-YoctoAutoBuilder- build #987 of nightly-qa-extras is complete: Failure [failed Running Sanity Tests_7] Build details are at https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/987 | 22:00 | |
*** JaMa <JaMa!~martin@217.30.68.212> has quit IRC | 22:01 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 22:03 | |
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto | 22:20 | |
*** d3r3k <d3r3k!uid190567@gateway/web/irccloud.com/x-nmpfwdkxkexfpvsf> has joined #yocto | 22:24 | |
*** Bunio_FH <Bunio_FH!~bunio@156.17.239.1> has joined #yocto | 22:28 | |
*** nathani_ <nathani_!~nathani@mail.validmanufacturing.com> has quit IRC | 22:36 | |
*** nathani_ <nathani_!~nathani@mail.validmanufacturing.com> has joined #yocto | 22:36 | |
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-nzavbhrhjppmaols> has joined #yocto | 22:42 | |
*** anujm <anujm!~anujm@192.198.146.171> has joined #yocto | 22:47 | |
fischerm | trying to decide for the correct place for network configuration files for systemd. It seems like my BSP layer is the wrong place. Any way to make these kind of things specific to an image? | 23:00 |
*** sysdef <sysdef!~sysdef@debiancenter/founder.developer/pdpc.professional.sysdef> has quit IRC | 23:12 | |
*** RP <RP!~RP@5751f4a1.skybroadband.com> has quit IRC | 23:16 | |
*** Bunio_FH <Bunio_FH!~bunio@156.17.239.1> has quit IRC | 23:40 | |
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC | 23:59 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!