**** BEGIN LOGGING AT Wed Jun 18 02:59:59 2014 Jun 18 06:58:27 Hi All Jun 18 06:58:50 Can i use yocto for I.MX6 solotite processor. Jun 18 06:58:50 ? Jun 18 06:59:31 jags, yes im prettu sure of it Jun 18 06:59:48 jags, check out support the machine in the meta-fsl-arm/meta-fsl-arm-extra layers Jun 18 07:00:12 I am new to yocto, How can i check? Jun 18 07:00:14 jags, what board are you using ? Jun 18 07:00:51 We have developed custom board with i.MX6 solotite processor. Jun 18 07:02:38 kroon? Jun 18 07:03:24 jags, you might want to consider writing your own machine bsp then. There are existing imx6 sololite machines in meta-fsl-arm: imx6slevk, imx6solosabreauto, imx6solosabresd Jun 18 07:03:36 jags, in meta-fsl-arm-extra: wandboard-solo Jun 18 07:04:03 i will take imx6slevk as reference. Jun 18 07:04:09 jags, have a look at the conf/machine/* files Jun 18 07:04:16 How can i get yocto source code? Jun 18 07:04:22 latest Jun 18 07:05:22 means meta-fsl-arm and other folders Jun 18 07:05:39 sorry for dumb ques. but i am completely new Jun 18 07:06:26 http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Jun 18 07:06:33 jags, then you have some reading up to do :) Jun 18 07:07:24 jags, The "Building an Image" section explains how to get the latest poky sources Jun 18 07:08:09 jags, well, the daisy release at least Jun 18 07:08:24 ./repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b daisy ./repo sync Jun 18 07:08:29 i am doing like this Jun 18 07:08:32 is it fine? Jun 18 07:08:51 ./repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b daisy Jun 18 07:08:53 and then Jun 18 07:08:57 repo sync Jun 18 07:10:08 jags, looks like Freescale's way of setting things up. Personally I would for bare poky, and add Freescale layer support as a second step Jun 18 07:10:58 If i will follow http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html this Jun 18 07:11:01 then how can i add freescale layer support? Jun 18 07:14:24 Kroon: After bare poky, How can i add support for freescale layer(Imx6slevk)? Jun 18 07:15:46 jags, clone the layers, looking at http://layers.openembedded.org/layerindex/branch/master/layers/, and update your bblayers.conf Jun 18 07:54:09 I have an embedded system with rootfs on emmc (block device). Rootfs is currently squashfs and I'd like to experiment with BTRFS, but it has to be compressed. Is there any way to create a compressed btrfs rootfs? The mkfs.btrfs command doesn't document any way to enable compression, nor do I see any materials in google. Jun 18 08:44:00 morning all Jun 18 08:58:02 <_valle_> Morning! Jun 18 08:58:51 <_valle_> I'm struggling with shipping files in a bbappend recipe. What am I missing? http://pastebin.com/h0Jh8zT5 Jun 18 09:08:47 _valle_: I think the problem is there is no ${PN} package in a kernel recipe Jun 18 09:09:15 you'll need to use one of the packages in the value of PACKAGES for the kernel recipe to make it work Jun 18 09:24:09 morning all, when I build my udev package, I have got some unneeded rules (e.g. 61-accelerometer.rules) can I desactivate it with a makefile option? like --no-rules? Jun 18 09:24:54 TuTizz: you can use a bbappend to delete them in a do_install_append() Jun 18 09:25:45 rburton, ok ty Jun 18 09:29:23 <_valle_> bluelightning: I don't understand Jun 18 09:29:43 <_valle_> bluelightning: Can you show in an example? Jun 18 09:30:18 _valle_: the ${PN} part in FILES_${PN} specifies which package the files should go into Jun 18 09:31:07 _valle_: in other recipes, ${PN} (i.e. the recipe name) in this context refers to the main package for the recipe; but kernel recipes don't have an ${PN} package Jun 18 09:32:50 if you do bitbake -e | grep ^PACKAGES= you'll probably get: Jun 18 09:32:53 PACKAGES="kernel kernel-base kernel-vmlinux kernel-image kernel-dev kernel-modules kernel-devicetree" Jun 18 09:33:23 _valle_: so instead of FILES_${PN} you probably want FILES_kernel-base or something like that Jun 18 09:35:07 <_valle_> bluelightning: Thank you! Jun 18 11:19:06 In Yocto, inside core-image-minimal, recipes-multimedia is not available, how can i build it with core-image-minimal? Jun 18 12:07:24 How to enable multimedia recipes in yocto? Jun 18 12:28:51 re, in meta/recipe-core/udev/udev-extraconf there is a script named network.sh, I think it is depreciate (presence of /dev/udev_network_queue and /etc/network/options, no longer available) what should I do to correct that? Jun 18 14:58:57 kergoth: were those gcc checksum mismatches you were seeing always the preconfigure task? Jun 18 15:00:04 I wasn't the one seeing the gcc checksum mismatches. we saw issues where bitbake -S printdiff showed a delta but bitbake didn't rebuild anything from scratch, but all our builds are external. it was someone else that hit problems like that with gcc-cross. Jun 18 15:00:29 kergoth: ok, I think I've figured out the gcc problems at least... Jun 18 15:00:34 nice Jun 18 15:59:19 is it kosher to define a PREFERRED_PROVIDER outside of a .conf file? Jun 18 16:00:17 what do you mean? Jun 18 16:01:09 as in i'd really like it to be image-specific Jun 18 16:01:20 that really doesn't make any sense Jun 18 16:01:26 bitbake reads those vars from the config metadata, not random recipes Jun 18 16:01:38 what are you actually trying to accomplish? Jun 18 16:01:48 we should really have a FAQ entry on this... it does get asked a lot Jun 18 16:02:11 so two different images built from the same config can't have a different provider for something? Jun 18 16:02:44 or maybe that's not the right way... Jun 18 16:04:04 i have an alternate xserver-nodm-init provider but it gets used globally Jun 18 16:05:05 there must be a better way but it seems like the right thing is to override VIRTUAL-RUNTIME_graphical_init_manager Jun 18 16:06:15 but when i use VIRTUAL-RUNTIME_graphical_init_manager = "foo" in one image it gets pulled into a core image that should have the default one Jun 18 16:06:34 does that make sense? Jun 18 16:06:54 I'm pretty sure the answer is Don't Do That Jun 18 16:07:03 * kergoth wanders off to a conference call Jun 18 16:07:06 don't do which? Jun 18 16:14:09 nerdboy: PREFERRED_PROVIDER is meant to select between mutually-exclusive *build-time* providers of something Jun 18 16:14:18 when it gets to the package level, that is runtime Jun 18 16:15:18 if you have two recipes producing two separately named packages that can be built side-by-side in the same configuration, then you absolutely can select one in one image and the other in the other Jun 18 16:15:33 but that wouldn't be done using PREFERRED_PROVIDER Jun 18 16:36:12 with update-alternatives, is there anything to allow selection of the alternative at runtime, or is it just delete and recreate the link? Assuming both packages providing the binary are on the image already Jun 18 16:37:12 update-alternatives can be dynamically reconfigured at runtime. by default it selects the highest priority alternative, but the user can change that after they boot the image. Jun 18 16:37:43 bluelightning: the only example i can find in the main recipes is efl/entrance which does it that way Jun 18 16:38:45 bluelightning: okay, entrance doesn't RRPOVIDE, just replace/conflict Jun 18 16:40:44 you're best off using virtual-runtime rather than runtime provides, as there's no way to express your runtime preferences to the binary package manager at do_rootfs-time today Jun 18 16:42:04 so far i only see that in packagegroup-core-x11.bb Jun 18 16:42:28 ? Jun 18 16:42:40 VIRTUAL-RUNTIME_graphical_init_manager ?= "xserver-nodm-init" Jun 18 16:43:09 there are quite a few VIRTUAL-RUNTIME variables, used in a number of different places Jun 18 16:53:08 kergoth, with your conditional bbappend setup, do you think there should be any problems expanding it to support .bb files as well? Jun 18 16:54:04 nope, we've done that too. it's useful from time to time for new recipes that include a .inc that only exists in some bsp layer, for example, so they aren't parsable otherwise Jun 18 16:54:09 should work fine Jun 18 16:55:11 https://github.com/MentorEmbedded/meta-mentor/pull/218 Jun 18 17:15:42 anyone able to give me an understanding of LICENSE_FLAGS_WHITELIST? I had a request to include chromium in an image, which I found, but it depends on libav, which has this GPLv2 license followed by a commercial license flags. What gives? Jun 18 17:16:39 blloyd: LICENSE_FLAGS is meant to highlight recipes that may have other legal concerns if used commercially Jun 18 17:17:05 e.g. codecs potentially requiring some form of additional license within some jurisdictions Jun 18 17:17:14 (for commercial use) Jun 18 17:18:03 by setting LICENSE_FLAGS_WHITELIST you are declaring "yes, I have done my due diligence, so you can build those things" Jun 18 17:19:02 ok, so it's not necessarily flagging the gplv2 as much as look at this package closely. So for LICENSE_FLAGS_WHITELIST, for this libav for instance I would put LICENSE_FLAGS_WHITELIST="libav"? Jun 18 17:19:45 blloyd: the LICENSE_FLAGS_WHITELIST value has to match up with the value in LICENSE_FLAGS Jun 18 17:20:59 so it would be LICENSE_FLAGS_WHITELIST = "commercial" Jun 18 17:21:24 or I guess you could be more selective by doing something like LICENSE_FLAGS_WHITELIST_pn-libav = "commercial" Jun 18 17:22:18 hmm actually there is built-in provision for per-recipe setting in that variable Jun 18 17:22:26 thanks, that made sense, and makes me nervous. So I start my due dilligence now on libav, set that flag (dilligence will be done before anything is ever given to someone else) Jun 18 17:22:38 see: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#enabling-commercially-licensed-recipes Jun 18 17:23:19 presumably an alternative approach would be to disable libav-using functionality in chromium, assuming that's possible Jun 18 17:23:27 thank you. I was off in another area, which discussed WHITELIST but didn't mention that item. Jun 18 17:24:57 interestingly that variable is absent from the variable reference... Jun 18 17:24:58 todo++ Jun 18 17:25:16 I'll put a bug report in. Jun 18 17:26:31 thanks... I've added it to my todo list to bug Scott about but tracking it there also works Jun 18 18:42:07 Alright, I've got a strange situation on my hands: Jun 18 18:42:11 I'm building a kernel for beaglebone Jun 18 18:42:13 and everything works fine Jun 18 18:42:24 except that it only loads kernel modules on the first boot Jun 18 18:42:35 and then I have to reflash the SD card to get usb / SPI working again Jun 18 18:42:44 has anyone seen something like this before? Jun 18 19:40:36 mkeeter, try flashing the sd card, copying the initrd off the sd card, doing your first boot, and then checking if the initrd has changed Jun 18 19:40:56 or alternately your grub setup **** ENDING LOGGING AT Thu Jun 19 02:59:59 2014