**** BEGIN LOGGING AT Mon Oct 19 02:59:57 2020 Oct 19 05:53:09 Hi, my issue goes away when I replace INHERIT_raspberrypi3 += "mender-full" with INHERIT_append_raspberrypi3 = " mender-full". I apparently have some more understanding to do of _append vs. +=. Oct 19 06:04:36 From the mega manual: Note: Avoiding "+=" and "=+" and using machine-specific _append and _prepend operations is recommended as well. Okay sure :) Oct 19 06:44:10 good morning Oct 19 06:54:54 yo dudX and mckoan :) Oct 19 06:55:05 hey LetoThe2nd **** BEGIN LOGGING AT Mon Oct 19 02:54:02 2020 **** ENDING LOGGING AT Mon Oct 19 02:59:57 2020 **** BEGIN LOGGING AT Mon Oct 19 02:59:57 2020 Oct 19 03:06:37 hi i'm hardware eng i have some question about creating a new dts file Oct 19 03:07:52 alban_: just ask, as concisely as possible. if somebody knows, you'll get an answer. Oct 19 03:10:41 ok i'm using variscite dart. it works on the devkit. now i create my own dts to match my board. i want to bitbake compile it and deploy it. i modified the /conf/machine file and add an entry into the dts/Makefile, but bitbake doesnt see anything. did i miss something ? thanks Oct 19 03:13:34 alban_: 1) you added your custom dt to the kernel trees repository that you are building for? 2) does it get built when you manually run "make dtbs" in the kernel build process? Oct 19 03:16:17 i added the file into ~/var-fslc-yocto/build_fb/tmp/work-shared/imx6ul-var-dart/kernel-source/arch/arm/boot/dts but make dtbs gives nothing Oct 19 03:16:59 alban_: "gives nothing"? Oct 19 03:17:16 "make: *** Aucune règle pour fabriquer la cible « dtbs ». Arrêt. Oct 19 03:17:18 " no rules Oct 19 03:17:27 alban_: thats the wrong place to add stuff, this is a transient directory. Oct 19 03:17:34 qschulz: its more like your kind of expertise. Oct 19 03:17:35 okay Oct 19 03:18:04 alban_: make ARCH=arm dtbs Oct 19 03:18:20 but usually, i would manually build the kernel until satiesfied, and only then commit stuff to either a patch carried in the layer or to the source repo Oct 19 03:18:35 where do you run it from? (~/var-fslc-yocto/build_fb/tmp/work-shared/imx6ul-var-dart/kernel-source ?) Oct 19 03:18:59 ~/var-fslc-yocto/build_fb/tmp/work-shared/imx6ul-var-dart/kernel-source/arch/arm/boot/dts Oct 19 03:19:09 alban_: yeah nah, from ~/var-fslc-yocto/build_fb/tmp/work-shared/imx6ul-var-dart/kernel-source Oct 19 03:19:41 (don't forget ARCH=arm because that's how the Makefile knows which architectrues's dts to build Oct 19 03:27:08 looks like i put my dts at the wrong place. thanks anyway. i will read some docs Oct 19 03:27:27 alban_: no, your dts is in the correct place Oct 19 03:27:50 (arch/arm/boot/dts is where it should be) Oct 19 03:28:05 not sure about work-shared though Oct 19 03:28:26 alban_: https://www.yoctoproject.org/pipermail/yocto/2019-May/045115.html should help you getting your changes in Yocto afterwards Oct 19 03:28:28 i get this . i will try to figure out Oct 19 03:28:47 https://paste.gnome.org/p03aylbjm Oct 19 03:29:24 alban_: that's a weird one, I didn't think one would need to use a defconfig for that Oct 19 03:29:47 alban_: so find which defconfig is being used by your recipe and then: make ARCH=arm my_defconfig Oct 19 03:29:53 then make ARCH=arm dtbs Oct 19 03:30:13 alban_: you could also make use of devtool for modifying your kernel sources Oct 19 03:30:21 ok Oct 19 03:31:10 (devtool modify virtual/kernel; go in the devtool workspace, add DTS and modify maekfiel there, then bitbake your image as usual, the new kernel will be used) Oct 19 03:32:02 (still need the change in conf/machine though (if the layer does not belong to you, you need to create a new machine in your own layer, but that's for later)) Oct 19 03:32:54 alban: thought I had drown you with info :) Oct 19 03:33:33 hello, does anyone here know whether any OEM uses Yocto for producing images for routers? Oct 19 03:34:22 would it make sense for them to use Yocto instead of forking OpenWrt or using something developed in-house (like Cisco does)? Oct 19 03:34:22 thanks a lot ! i'm harware guy i only scrath the surface of linux. i'm a user only but i'm in charge of providing a working device tree to my fellow software guys Oct 19 03:35:21 found this https://www.codeaurora.org/projects/yocto-for-ipq Oct 19 03:36:05 alban: if you plan to do iterative development, I'd probably go for devtool (the issue with modifying /var-fslc-yocto/build_fb/tmp/work-shared/imx6ul-var-dart/kernel-source is that it can disappear if there's a change in the kernel recipe or any other recipe (or even conf file) that it depends on) Oct 19 03:36:23 got it Oct 19 03:36:34 alban: you got this, just say if something isn't clear, or if you get lost on the way Oct 19 03:36:39 has anyone tried using Yocto for something like Qualcomm IPQ SoCs? Oct 19 03:37:10 hello. I'm having problems with `IMAGE_FEATURES += "dev-pkgs"`, `PACKAGE_EXCLUDE_append=" grub-dev"` and `PACKAGE_CLASSES = "package_deb"`, where despite of the package has the "Pin-Priority: -1" in /apt/preferences, apt-get install still tries to install it. Oct 19 03:37:10 alban: we have extensive documentation: https://docs.yoctoproject.org maybe that can help too Oct 19 03:37:20 alban: we have extensive documentation: https://docs.yoctoproject.org maybe that can help too Oct 19 03:38:56 do i need to create my own layer and so on ? Oct 19 03:39:25 it's just a variant of a board Oct 19 03:39:35 alban: yes you will need at one point. be it only for patching the kernel sources Oct 19 03:39:50 alban: "just" is a never "just" :p Oct 19 03:39:54 -a Oct 19 03:39:58 lol thanks Oct 19 03:41:22 RP: yann : we should use links from https://elinux.org/ELC_2017_Presentations instead. i will update the wiki Oct 19 03:43:46 fixed now. i added links to the video as well (youtube) while at it. Oct 19 03:48:05 eduardas: https://source.codeaurora.org/quic/qyocto/oss/system/recipes/meta-ipq/ doesn't seem to be too crazy. but generally anything off codeaurora is often a bit demanding to get the head around. Oct 19 04:12:39 gg wp ndec :) **** ENDING LOGGING AT Mon Oct 19 04:25:06 2020