**** BEGIN LOGGING AT Sat Mar 22 02:59:59 2014 Mar 22 05:46:23 khem, ping Mar 22 07:00:02 Anyone know of a paper or document comparing yocto/buildroot/oe-lite ? I need ammunition for defending why we should pick yocto.. **** BEGIN LOGGING AT Sat Mar 22 14:01:45 2014 Mar 22 16:11:23 kroon: look at some of presentations from ELCE Mar 22 16:11:29 in 2012 Mar 22 16:11:53 kroon: what kind of products are you targetting Mar 22 16:12:19 khem, will do, thanks. its medical devices Mar 22 16:13:20 kroon: I helped deploy yocto in a medical device just recently Mar 22 16:14:06 khem, cool Mar 22 16:14:09 kroon: architecture is also important sometimes Mar 22 16:14:20 one build system might work better compared to others Mar 22 16:14:47 but off late OE has been in good shape for wide variety of arches Mar 22 16:15:25 to me it just looks like all the big companys are putting work into OE Mar 22 16:15:34 and linuxfoundation Mar 22 16:15:35 medico's like small systems, so mdev/busybox/uclibc worked out well in this case Mar 22 16:15:58 yes thats there too a big community Mar 22 16:18:08 I was actually wondering if you had any comments on https://lists.yoctoproject.org/pipermail/meta-freescale/2014-March/007715.html, if you have any easy tips on where I should start looking Mar 22 16:19:21 I'll try reverting the systemd upgrade first, and see if that helps Mar 22 16:19:25 seems like udev is taking too long Mar 22 16:19:41 tty is not available for it to start console Mar 22 16:20:46 if it happens on subsquent boots there is something with postinstalls Mar 22 16:21:05 probably getting the tty names written wrongly or some such Mar 22 16:21:56 ok thanks. i'll poke around and see what I can find Mar 22 16:22:01 mmc errors are most probably due to systemd-fsck now tryin to run on it Mar 22 16:22:48 is mmc initialised properly ? Mar 22 16:22:53 by the time Mar 22 16:24:03 khem, yeah i should think so, the rootfs is on mmc partition 2, a small vfat on the first one, with the kernel and dtb files Mar 22 16:24:43 those messages seems to be from kernel though to me Mar 22 17:09:02 goddammit. always check which terminal you write "reboot" into Mar 22 17:12:28 khem, no mmc hang or error messages, and no hang on ttymxc0 with systemd 208 at least Mar 22 17:12:39 going back to 211 to poke some more Mar 22 17:15:58 kroon: there are always new features that come in with systemds Mar 22 17:16:07 so it could be a latent issue in past Mar 22 17:19:35 khem, im suspecting its the "support for the Discoverable Partitions Specification" stuff in 211 thats causing the mmc problems. read something about people complaining about it Mar 22 17:19:51 yes that could be it Mar 22 17:19:58 although its a good feature Mar 22 17:20:40 and tty is ok after first boot, not on subsequent Mar 22 17:21:06 yeah Mar 22 17:43:35 kroon: ssh into box and see the journal Mar 22 17:44:49 khem, I see it, but I cant parse systemd output.. "Timed out waiting for device dev-ttymxc0.device". But /dev/ttymxc0 clearly exists Mar 22 17:51:02 and the kernel keeps outputting to the tty. But getty wont connect to it **** ENDING LOGGING AT Sun Mar 23 02:59:58 2014