**** BEGIN LOGGING AT Mon Jul 11 02:59:56 2011
Jul 11 09:21:29 <bluelightning> morning all
Jul 11 09:24:37 <RP__> morning all
Jul 11 09:28:15 <captainigloo> tehre is prebuild images for the crownbay platform ?
Jul 11 09:49:48 <RP__> captainigloo: For 1.0, http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/crownbay/
Jul 11 16:34:20 <jefferai> dvhart: ping
Jul 11 16:34:39 <dvhart> hey jefferai
Jul 11 16:35:20 <jefferai> hey there
Jul 11 16:35:25 <jefferai> any word on the changes that might fix usb/display?
Jul 11 16:35:48 <dvhart> I sent you an email on friday, they are in master
Jul 11 16:36:12 <dvhart> but, as I said, your symptoms may not be addressed by these
Jul 11 16:37:34 <jefferai> ah -- I don't see that email  :-|
Jul 11 16:37:37 <jefferai> I'll look again
Jul 11 17:09:36 <otavio> sgw: got the mail?
Jul 11 17:10:41 * zeddii has 1400 email to go. apologies if replies are delayed.
Jul 11 17:11:47 <otavio> heh
Jul 11 17:12:05 <sgw> otavio: thanks!  Can you do the tarball repackaging, and submit a patch for the libarchive recipe?
Jul 11 17:12:07 <otavio> sgw: RP__ I am on the way of cmake updating
Jul 11 17:12:20 <otavio> sgw: but how I send the tarball?
Jul 11 17:12:32 <otavio> sgw: and to whom?
Jul 11 17:14:09 <sgw> to me we will host it on http://autobuilder.yoctoproject.org/sources/...
Jul 11 17:14:38 <otavio> sgw: ok; hold a second then; will do it right now.
Jul 11 17:17:22 <otavio> sgw: ok; doing so.
Jul 11 17:17:33 <sgw> otavio: thanks again!
Jul 11 17:25:12 * sgw wonders if git.openembedded.org is working for anyone else?
Jul 11 17:29:05 <otavio> sgw: I sent it to you; I will post the patches on ml in two minutes
Jul 11 17:30:03 <sgw> otavio: tarball is posted, please verify your fetch works with the tarball.
Jul 11 17:30:54 <otavio> sgw: worked fine.
Jul 11 17:31:00 <otavio> sgw: posting patches
Jul 11 17:32:24 <otavio> sgw: sent
Jul 11 17:32:41 <sgw> otavio: thanks gain for your help and flexibility.
Jul 11 17:34:59 <otavio> sgw: no problem; i sent cmake 2.8.5 with the patchset too
Jul 11 18:14:50 <jefferai> dvhart: ok, so I'm using unmodified 2.6.37 from git://git.yoctoproject.org/linux-yocto-2.6.37, and in my BBLAYERS I have:
Jul 11 18:15:00 <jefferai>   /home/jmitchell/yocto/poky/meta \
Jul 11 18:15:00 <jefferai>   /home/jmitchell/yocto/poky/meta-yocto \
Jul 11 18:15:00 <jefferai>   /home/jmitchell/yocto/layers/poky-extras/meta-kernel-dev \
Jul 11 18:15:03 <jefferai> does that look right?
Jul 11 18:15:17 <dvhart> yes
Jul 11 18:16:25 <jefferai> then I'm running bitbake -k core-image-sato-sdk
Jul 11 18:16:59 <dvhart> ok
Jul 11 18:17:09 <dvhart> you need the sdk?
Jul 11 18:17:17 <dvhart> (makes the build longer)
Jul 11 18:17:34 <jefferai> I guess eventually it'll be useful
Jul 11 18:17:36 <jefferai> but for now, no
Jul 11 18:17:40 <dvhart> right
Jul 11 18:19:56 <jefferai> hm
Jul 11 18:20:08 <jefferai> http://pastie.org/2197973
Jul 11 18:28:54 <dvhart> jefferai, yeah... I wonder why I haven't hit that
Jul 11 18:28:59 <dvhart> jefferai, just delete that file
Jul 11 18:29:11 <dvhart> I'll fix it now
Jul 11 18:31:26 <jefferai> ok
Jul 11 18:31:31 <dvhart> jefferai, hrm actually
Jul 11 18:31:33 <dvhart> weird
Jul 11 18:31:41 <jefferai> I haven't deleted it yet if yoh
Jul 11 18:31:44 <jefferai> poky-extras
Jul 11 18:31:46 <jefferai> I didn't notice
Jul 11 18:31:51 <jefferai> I haven't pulled that tooo recently
Jul 11 18:31:51 <jefferai> sec
Jul 11 18:32:04 <dvhart> this is a different problem from what I thought
Jul 11 18:32:09 <jefferai> oh, nope, up-to-date
Jul 11 18:32:13 <dvhart> that recipe depends on meta-rt
Jul 11 18:32:16 <dvhart> hrm
Jul 11 18:32:20 <jefferai> okay
Jul 11 18:32:23 <dvhart> same solution for now though
Jul 11 18:32:29 <dvhart> you can delete it - or you can add meta-rt
Jul 11 18:32:50 <dvhart> it won't impact your build
Jul 11 18:33:04 <dvhart> zeddii, any thoughts on how to handle that?
Jul 11 18:33:16 <dvhart> zeddii, meta-kernel-dev depends on meta-rt for the linux-yocto-rt recipe?
Jul 11 18:33:21 <dvhart> s/?$//
Jul 11 18:34:07 * dvhart wonders if linux-yocto-rt should be part of meta since the kernel type exists in linux-yocto.git already
Jul 11 18:34:45 <zeddii> I just hit that today as well!
Jul 11 18:34:55 <dvhart> what changed?
Jul 11 18:35:04 <zeddii> something did. I updated after a week away and it broke.
Jul 11 18:35:06 <dvhart> does bitbake now fail on missing recipes for bbappends?
Jul 11 18:35:42 * jefferai is happy to stir the bug-pot :-)
Jul 11 18:36:07 <zeddii> my solution is to keep the bbappend in the same layer as the base recipe, but this is a classic layer dependency issue.
Jul 11 18:36:47 <zeddii> dvhart, the issue is likely triggered by the compat being too broad. since it always appears that the recipe is 'unused' (which it largely is), but gets parsed and throws the error (Which is annoying).
**** ENDING LOGGING AT Mon Jul 11 20:00:49 2011

**** BEGIN LOGGING AT Mon Jul 11 20:02:14 2011
Jul 11 20:14:59 <RP__> dvhart: yes, bitbake does now get upset about missing .bbappend files
Jul 11 20:15:14 <RP__> dvhart: it can be turned off with some BB_ variable fwiw
Jul 11 20:15:49 <dvhart> RP__, ok, hrm... we should find out how to make meta-kernel-dev work... perhaps just adding that BB_ magic to the layer.conf for meta-kernel-dev would be appropriate...
Jul 11 20:16:23 <RP__> dvhart: I'm not adversed to that, as long as people realise the risk it entails
Jul 11 20:16:46 <dvhart> Right, I think for this type of layer (purely for development) it is tolerable
Jul 11 20:16:56 <RP__> (I agreed defaulting to erroring out about that stuff was a good idea)
Jul 11 20:17:14 <dvhart> and probably better than having to create multiple kernel dev layers
Jul 11 20:17:55 <RP__> dvhart: agreed
Jul 11 20:19:09 <dvhart> 7a2a24de094ce8f2e2068bbee6709dfc2cdc69b9 ?
Jul 11 20:19:17 <dvhart> BB_DANGLINGAPPENDS_WARNONLY
Jul 11 20:19:24 <RP__> dvhart: that sounds like it
Jul 11 20:19:34 <dvhart> that's an awesome var name :)
Jul 11 20:19:48 <RP__> I really couldn't resist that one :)
Jul 11 21:48:12 <mgross> core-image-minimal-initramfs for n450 serial console not working for me.  what configs could I tweak to change the console configuration?
Jul 11 21:49:59 <incandescant> dvhart, is your man for n450
Jul 11 21:51:15 <incandescant> though aiui that should be set at a machine level
Jul 11 21:51:58 <incandescant> and indeed we do set some things in meta-intel/meta-n450/conf/machine/n450.conf
Jul 11 21:52:04 <incandescant> :-/
Jul 11 21:52:11 * dvhart looks up
Jul 11 21:52:40 <dvhart> mgross, do other images - such as minimal-live - work for you?
Jul 11 21:52:54 * incandescant did wonder at initramfs
Jul 11 21:52:56 <dvhart> mgross, if not, you may need to validate your serial connection
Jul 11 21:53:07 * dvhart hasn't run an initramfs image
Jul 11 21:53:57 <dvhart> mgross, but the serial config settings are in machine/n450.conf:
Jul 11 21:53:59 <dvhart> SYSLINUX_OPTS = "serial 0 115200"
Jul 11 21:53:59 <dvhart> SERIAL_CONSOLE = "115200 ttyS0"
Jul 11 21:53:59 <dvhart> APPEND += "console=ttyS0,115200 console=tty0"
Jul 11 22:00:32 <mgross> dd
Jul 11 22:00:46 <mgross> dvhart I have not tried minimal-live yet.  I have those ttyS0 lines but the initrd doesn't provide a console
Jul 11 22:01:28 <mgross> I'll try the minimal-live. now.
Jul 11 22:02:16 <dvhart> mgross, do you get bios text over the serial line?
Jul 11 22:02:18 <dvhart> syslinux?
Jul 11 22:05:30 <mgross> yes I get all the kernel messages just no serial console
Jul 11 22:06:04 <mgross> I even get some udeve and "Waiting for removalble media" stuff clearly form user mode.
Jul 11 22:06:31 * mgross thinks I'm missing a getty or console.
Jul 11 22:06:54 <mgross> any advice for how to add one to minimal-init-rc?
Jul 11 22:10:22 <dvhart> check inittab
Jul 11 22:10:28 <dvhart> is there an agetty there?
Jul 11 22:10:38 <dvhart> hrm... what is the last thing you see?
Jul 11 22:13:55 <mgross> [   17.979672] udevd used greatest stack depth: 6320 bytes left
Jul 11 22:14:49 <mgross> its a bbox build.  I don't think there is an inittab is there?
Jul 11 22:31:41 <dvhart> there should be
Jul 11 22:31:45 <dvhart> there is in minimal
Jul 11 22:41:16 <ant__> dvhart: hey, I've finished to write the book ^_^
Jul 11 22:48:19 <dvhart> ant__, congrats
Jul 11 22:49:22 <RP__> mgross: what are you using as init?
Jul 11 22:50:17 <mgross> its the script that is used by the core-image-minimal-initramfs
Jul 11 22:50:17 <ant__> dvhart:  now, the bad news is that kernel+cpio.lzma built with gcc4.6 seems freezing on init :/
Jul 11 22:50:46 <mgross> I just rebuilt to try the minimal live image so I can't say for sure anymore.
Jul 11 22:51:28 <dvhart> mgross, how did the minimal live do?
Jul 11 22:51:49 <mgross> sigh.. the live image is complaining about the kernel (Of course I'm not using the yocto kernel for my project)
Jul 11 22:52:06 <dvhart> no VFAT or LOOP support?
Jul 11 22:52:13 <dvhart> that's a typical one for live
Jul 11 22:52:16 <mgross> I just need the rootfs build and I hand place my custome kernel.
Jul 11 22:53:09 <mgross> Ok, so you don't get too far with assumptions : I'm trying to use yocto to build a root file system to test on mfld icdk.
Jul 11 22:53:21 <mgross> Its point is to test my kernel.
Jul 11 22:53:36 <mgross> as you may know mfld is not a normal PC boot.
Jul 11 22:54:15 <mgross> So ideally I need a yocto build to build without any kernel.
Jul 11 22:54:32 <mgross> I will put my own in and use it to test the platform.
Jul 11 22:54:38 <dvhart> you can add your kernel recipe and change the PREFERRED_PROVIDER
Jul 11 22:55:26 <mgross> yeah, I was hoping to avoid that until after I get some of the startup debuggin figured out.
Jul 11 22:55:51 <dvhart> mgross, iterative devel inside yocto isn't too bad
Jul 11 22:56:08 <dvhart> mgross, you can just keep doing "bitbake mykernel -c compile
Jul 11 22:56:20 <dvhart> tweak from the source dir as needed, repeat
Jul 11 22:56:44 <dvhart> makes using the cross toolchain pretty trivial
Jul 11 22:56:50 <dvhart> but I understand wanting to work outside the tree
Jul 11 22:57:08 <dvhart> need a -f on the bitbake cmd of course
Jul 12 00:14:55 <mgross> thanks dvhart!  I think I'm pretty close to having what I need.  FWIW I don't think core-image-minimal-initramfs even has a getty ;)  I'll switch over to the simply minimal image and see about adding a kernel recipe for my special snowflake kernel.
**** ENDING LOGGING AT Tue Jul 12 02:59:57 2011