**** BEGIN LOGGING AT Thu Oct 30 03:00:00 2014 Oct 30 08:09:40 Hello all! Can anyone help me with some newbie questions, how to build at91sam bootloader for sd card? Oct 30 08:10:50 good morning Oct 30 08:11:02 If I just use at91sam9m10g45ek machine recipes, it builds only nand-flash bootstrap Oct 30 08:12:13 And my board (quite old picosam9 from minibox.com ) has some troubles with NAND, it's recommended to use SD card for load. Oct 30 08:12:52 leon_ti: probably you need to specify another target for the bootstrap and uboot builds Oct 30 08:13:02 no idea if meta-atmel provides those already Oct 30 08:13:34 leon_ti: try asking in #at91 channel Oct 30 08:13:39 leon_ti: http://www.at91.com/linux4sam/bin/view/Linux4SAM/U-Boot Oct 30 08:14:52 yes, there are plenty of manuals how to build bootstrap/uboot/kernel from the scratch; I hope it is possible to build them using yocto... Oct 30 08:15:00 thanks for pointing to #at91 Oct 30 08:15:18 leon_ti: you have to modify include/configs/at91sam9m10g45ek.h Oct 30 08:16:02 leon_ti: it certainly is, like i said: you probably need to tweak the recipes for other targets. usually this would be done by a bbappend in your own layer Oct 30 08:16:52 leon_ti: that is, assuming the the bootstrap and uboot sources already have valid targets for your usecase. if not, you need to patch them first. Oct 30 08:16:57 leon_ti: follow this setting CONFIG_SYS_USE_NANDFLASH Oct 30 08:18:52 Is it somewhere here: yocto/poky/meta-atmel/recipes-bsp/at91bootstrap ? Oct 30 08:20:45 leon_ti: you have to be aware that we are talking about two different things here. mckoan points out what has to be done *IN* the sources of bootstrap and u-boot, while i'm talking about the recipes that build all together Oct 30 08:21:07 leon_ti: for the recipe part, the path you mentioned looks like a worthwhile starting point Oct 30 08:23:08 Doesn't yocto take care about applying necessary patches to source code? As I know, bootstrap code can be compiled either for NAND or for SD; so the only thing I need is to provide necessary compile-time config. Oct 30 08:23:34 And this is yocto job, if I understand things correctly Oct 30 08:24:15 if the bootstrap code is already properly prepared and its just a matter of selecting the correct build target, then its the job of bitbake, yes. Oct 30 08:24:32 or if you already *have* a patchset for your machine. Oct 30 08:25:01 leon_ti: AFAIK there is no options to boot from SD with u-boot for at91sam9m10g45ek, so you will have to modify the code, not yocto stuff Oct 30 08:25:18 its not bitbakes/poky/yoctos duty to go beyond applying exiting patches. Oct 30 08:26:13 leon_ti: so even if its not what you want to hear: the correct way is to make everything work by hand *first*, without build automation, and once you know the steps/configuration/patches necessary, have the build replay those accordingly Oct 30 08:26:41 Ok, thanks. Oct 30 08:29:55 LetoThe2nd: +1 Oct 30 08:30:08 Btw, yocto built for me a kernel packaged in zImage and separate dtb. How can I get uImage for them? Oct 30 08:30:35 leon_ti: the state of the art for AT91 boards is to use zImage Oct 30 08:31:17 ... and if you still want uimage, set KERNEL_IMAGETYPE accordingly Oct 30 08:31:37 you'd still get a separate dtb, so not much of a change here. Oct 30 08:46:30 Btw, can I use old pre-compiled bootloader which came from a board vendor? I have binary bootstrap which can load uimage kernel Oct 30 08:47:47 morning all Oct 30 08:48:10 aic Oct 30 08:48:17 ack Oct 30 08:48:21 morning .* Oct 30 08:48:38 I can spell even Oct 30 08:59:52 Huh. Oct 30 09:09:22 Is this under bitbake, or are you running stuff directly on the command line? Oct 30 09:11:44 *thinks* Are there any symlinks in the path? Like, what do you get from 'readlink -f' on that directory? Oct 30 09:13:28 pseudo will generally use fully canonicalized paths. Oct 30 09:25:40 Huh. When I try to run the host's setfiles I get errors to do with failing to load libpseudo.so, but that doesn't seem to be the same thing. Oct 30 09:39:26 I'm trying to figure out how to not package the .la files. Yocto complains about it and i don't even want them: ERROR: QA Issue: dsm: Files/directories were installed but not shipped: /usr/lib/idevive/gbus.la Oct 30 09:42:44 irontia: just delete them in a do_install (or do_install_append if you aren't already defining your own do_install in the recipe) Oct 30 09:43:03 i.e. rm ${D}${libdir}/idevive/*.la Oct 30 10:54:25 I am trying to build core-image-minimal with Yocto master branch and DISTRO_FEATURES += "systemd". systemd seems to depend on glibc, which doesn't build: Oct 30 10:54:25 ERROR: Nothing PROVIDES 'glibc' Oct 30 10:54:25 ERROR: glibc was skipped: missing required distro feature 'ipv4' (not in DISTRO_FEATURES) Oct 30 10:54:25 ERROR: Required build target 'core-image-minimal' has no buildable providers. Oct 30 10:54:25 Missing or unbuildable dependency chain was: ['core-image-minimal', 'glibc'] Oct 30 10:55:18 pohly: is this a bare poky with nothing mixed in? Oct 30 10:55:50 I started adding DISTRO_FEATURES, but that just doesn't feel right. Looking at meta/recipes-core/glibc/glibc-options.inc I see that all of these features should be optional (at least the way I understand the code). Oct 30 10:56:21 LetoThe2nd: almost - let me remove the one layer that I added with a custom .bbclass and try again. Oct 30 10:57:10 pohly: well i'd be iterative here. 1) build with plain, unmodified poky. 2) follow http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#selecting-an-initialization-manager, then rebuild Oct 30 10:57:19 pohly: 3) then re-add your changed. Oct 30 10:57:27 s/changed/changes/ Oct 30 10:59:10 I was missing VIRTUAL-RUNTIME_init_manager = "systemd". After adding it, the problem went away. Oct 30 10:59:49 That's good of course, but I'm still curious about the root cause of the somewhat strange error message. Oct 30 11:06:28 pohly: I think you'll find the cause of the issue there is that DISTRO_FEATURES += ends up setting DISTRO_FEATURES at that point, with the result that the later DISTRO_FEATURES ?= to set the default value does nothing Oct 30 11:07:21 this used to result in the (e)glibc build failing later because some of the libc features we have set up as optional apparently aren't Oct 30 11:07:54 the fix that was applied for that was to simply set REQUIRED_DISTRO_FEATURES in the (e)glibc recipe, which when not satisfied triggers that error Oct 30 11:08:03 I'm not too happy with that as a solution either to be honest Oct 30 11:44:37 bluelightning: you are right, as part of copy-and-pasting from the dev-manual I also changed "DISTRO_FEATURES +=" into "DISTRO_FEATURES_append. That this makes a difference is easier to understand (albeit not necessarily obvious either). Oct 30 13:07:02 Hi ! Oct 30 13:07:49 I'm currently building an image for genericx86, and bitbake is currently downloading linux-yocto-3.10.35+gitAUTOINC+7df9ef8ee4_2ee37bfe73-r0 Oct 30 13:08:19 and it's downloading at 15-20KB/s ... :( Oct 30 13:10:04 is it the regular cloning speed for this repo? Oct 30 13:11:17 CromFr: I think the server may be experiencing some issues at the moment unfortunately Oct 30 13:11:46 which server? Oct 30 13:13:35 i dont know, i'm quite new to yocto Oct 30 13:15:08 Using mkefidisk on the minnowboard I specified /dev/sda as the target disk for a usb drive. Now when I boot I get a blank grub shell/, I tried set root=(hd0,msdos2) \ linux (hd0,msdos1)/vmlinuz \ initd (hd0,msdos1)/efi/boot/bootx64.efi \ boot and that didn't workwhat am I missing? Oct 30 13:17:20 Crofton|work: git.yoctoproject.org Oct 30 13:18:20 I guess we'll need to poke halstead when he wakes up Oct 30 13:19:15 givemefive922: er, so are you saying you pointed mkefidisk at your build host's hard disk? or am I misunderstanding? Oct 30 13:20:15 no my host_device was the usb flash drive Oct 30 13:20:26 the target_device was a guess of /dev/sda Oct 30 13:21:56 When I boot from the efi shell, the grub2 shell comes up and I can see the boot, root and swap partitions, I set my kernel and initrd and then boot, the kernel loads and then crashes and says root fs could not be found Oct 30 13:26:21 this really does sound like a #minnowboard question (I know they punted you over here) Oct 30 13:26:50 the usual folks that could help probably won't be around for another couple of hours so you might try asking again there later Oct 30 13:27:07 I guess you have seen http://www.elinux.org/Minnowboard:MinnowMaxYoctoProject Oct 30 13:27:12 ok thanks Oct 30 13:27:15 that does say /dev/sda already though Oct 30 13:27:23 yeah, that's what I found Oct 30 13:27:23 brb Oct 30 15:58:31 Hello guys, simple question: qt 5.4 beta branch appeared recently. i have the meta-qt package. i saw that you guys already added it to the meta layer (https://github.com/meta-qt5/meta-qt5/commit/be2d4815efd7b8312700a426a5cafcd86a93666b). In meta-qt5/conf/distro/include/qt5-versions.inc I can set QT5_VERSION. What else do i have to set so that yocto gets built with Qt 5.4? Oct 30 16:00:14 Hi, I'm working on a custom board based on the nitrogen6x board. On my design I changed the IOMux settings, I want to apply those same change on yocto but I can't figure out how to proceed. Does anyone knows how I can achieve that? Does anyone have a good link explaining in details how dtb/s works? Oct 30 16:02:10 mtetreault: in general, prepare a patch that changes the dtb that gets created Oct 30 16:02:22 mtetreault: then the build process can apply that Oct 30 16:03:29 in the case of a dtb, that probably means you add a new one to the kernel sources you use Oct 30 16:04:07 LetoThe2nd: for a quick bring up can I use the .dts in the /build/tmp/sysroot..../boot/dts and manually compile it? Oct 30 16:04:39 mtetreault: for manual testing, sure. it just will not be reflected in the build process Oct 30 16:05:24 LetoThe2nd: Is there a complete guide on how the dtb works? I found several guide online but most of them seems to be incomplete... Oct 30 16:05:39 mtetreault: um, in respect to what? Oct 30 16:05:52 mtetreault: the content of the dts? Oct 30 16:06:56 LetoThe2nd: The content, the label of each items and in my case I have to multiplexed pins, how do I represent that in the dts file? Oct 30 16:07:34 mtetreault: -> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings Oct 30 16:08:56 LetoThe2nd: okay, so those are all the available label, right? I'm sorry if I ask that many questions, I'm fairly new to this kind of stuff! Oct 30 16:09:38 mtetreault: that *should* be all available label, always assuming that every driver developer has properly documented them. Oct 30 16:11:49 LetoThe2nd: Thank you, that should help me getting started! I really appreciate! :) Oct 30 16:12:07 have fun Oct 30 16:20:56 guys, i did a checkout on meta-qt for master-next and edited qt5-versions.inc to use 5.4 alpha - am i going the right way? Oct 30 16:39:55 hi guys, I'm looking for some iotdevkit repo feed with packages Oct 30 16:40:07 does such a place exist? Oct 30 16:41:06 Xz: http://iotdk.intel.com/repos/ I believe Oct 30 16:56:21 ea Oct 30 17:00:41 bluelightning: that looks good - is there any way to figure out which libc it was build on top of? Oct 30 17:00:50 bluelightning: I suppose it's eglibc anyway :) Oct 30 17:09:09 Xz: it's eglibc yes Oct 30 17:23:31 bluelightning: thanks Oct 30 17:37:47 anyone going to Embedded Conference Scandinavia next week? Oct 30 17:37:58 there were some Yocto talks in the program Oct 30 18:30:48 * nerdboy has a couple SCaLE abstracts with yocto in them, but not one *on* yocto Oct 30 18:31:04 probably should, though... Oct 30 18:32:37 an old geologist buddy from Bakersfield used to say things like "busier than a one-legged man at an ass-kicking contest" Oct 30 18:32:52 * nerdboy feels like that... Oct 30 18:45:38 nerdboy: that is gold! :D Oct 30 20:07:56 bluelightning: so i guess you never hung out with mud-loggers and roughnecks before? Oct 30 21:13:01 nerdboy: can't say that I have Oct 30 21:15:04 you should, just for shits 'n grins Oct 30 21:15:16 ^^ another charlie saying **** ENDING LOGGING AT Fri Oct 31 02:59:59 2014