**** BEGIN LOGGING AT Mon Jul 28 03:00:01 2014
Jul 28 08:50:26 <ant_work> bluelightning: hello
Jul 28 08:50:32 <bluelightning> hi ant_work
Jul 28 08:51:03 <ant_work> opie master is ok on poodle wrt calibration
Jul 28 08:51:09 <ant_work> any other patch
Jul 28 08:52:15 <ant_work> I can test anarsoul's patch and see if it breaks...
Jul 28 08:52:17 <ant_work> ;)
Jul 28 08:53:13 <ant_work> or maybe if it helps collie (desespair flowing)
Jul 28 08:54:44 <bluelightning> doesn't seem like it will if the problem is kernel-related as you mentioned over the weekend...
Jul 28 08:58:41 <ant_work> ah, no, that's our private problem
Jul 28 08:58:47 <ant_work> linux-yocto only...
Jul 28 08:59:02 <ant_work> see http://pastebin.com/jrX5XzD4
Jul 28 08:59:14 <ant_work> 3 vanilla -rc does boot fine with ts
Jul 28 08:59:32 <ant_work> same toolchain, same defconfig
Jul 28 08:59:52 <ant_work> I'll bother Bruce in a few hours
Jul 28 09:00:33 <ant_work> honestly I don't see any ddangerous patch added by Yocto
Jul 28 09:00:36 <ant_work> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/tree/patches
Jul 28 09:11:54 <ant_work> bluelightning: at this point I doubt it is agcc bug
Jul 28 09:43:56 <ant_work> bluelightning: one issue I've had while switching kernel on already built rootfs
Jul 28 09:44:23 <ant_work> after changing the kernel preferred provider
Jul 28 09:44:24 <ant_work> Configuring run-postinsts.
Jul 28 09:44:24 <ant_work> Collected errors:
Jul 28 09:44:24 <ant_work>  * satisfy_dependencies_for: Cannot satisfy the following dependencies
Jul 28 09:44:24 <ant_work> for packagegroup-core-boot:
Jul 28 09:44:24 <ant_work>  *     kernel-3.16.0-rc6-yocto-standard *
Jul 28 09:44:25 <ant_work> kernel-image-3.16.0-rc6-yocto-standard *
Jul 28 09:44:27 <ant_work>  * opkg_install_cmd: Cannot install package packagegroup-core-boot.
Jul 28 09:44:45 <ant_work> so each time I did -cleansstate that one ^
Jul 28 09:46:38 <ant_work> note that to avoid issues with sysroot I was wiping tmpdir and rebuilding from sstate
Jul 28 09:49:11 <bluelightning> ah yes... the issue there is that packagegroups assume they don't need to rebuild when packages they depend upon change
Jul 28 09:49:38 <bluelightning> unfortunately that is not true if one of those packages is the kernel because the package name includes the version number...
Jul 28 09:50:06 <ant_work> I admit is atypical situation
Jul 28 09:50:51 <ant_work> and btw I got somewhere a warning using a recipe called linux_3.16-rc7.bb
Jul 28 09:51:02 <ant_work> taht [linux] is reserved for overrides
Jul 28 09:51:06 <ant_work> since when ?
Jul 28 09:55:44 <bluelightning> it's always been that way, we just added the warning a few releases ago
Jul 28 09:56:14 <bluelightning> the problem is weird stuff will happen and it's not obvious as to why until you realise that overrides are happening where they shouldn't...
Jul 28 09:56:53 <bluelightning> in hindsight we probably should have made the override target-linux rather than linux, but that decision was made years and years ago
Jul 28 09:57:14 <ant_work> surprisingly most kernels were named just linux_
Jul 28 09:57:49 <ant_work> (un)surprisingly, it was like that in oe-classic ;)
Jul 28 10:00:43 <bluelightning> yep
Jul 28 10:02:23 <ant_work> one last note about obexftp, it had different config options in meta-opie
Jul 28 10:02:48 <ant_work> recipe should be converted to pkgconfig
Jul 28 10:03:29 <ant_work> I'll do some tests on poodle with bluetooth
Jul 28 10:05:30 <bluelightning> hmm, I didn't notice
Jul 28 12:48:15 <ant_work> bluelightning: casually found meta-meson, it is not listed in layers
Jul 28 13:19:06 <bluelightning> ant_work: I'm not sure if it is maintained...
Jul 28 13:20:10 <ant_work> here we have yet another "build system"
Jul 28 13:20:11 <ant_work> https://jpakkane.github.io/meson/
Jul 28 13:20:24 <ant_work> omonimy
Jul 28 13:23:39 <bluelightning> yeah, I saw that... its not clear but IIRC its more a cmake/autotools replacement
Jul 28 13:24:54 <ant_work> ah, ok
Jul 28 19:37:51 <ant_home> bluelightning: hey
Jul 28 19:38:04 <ant_home> good news: Bruce found the offending commit
Jul 28 19:38:30 <ant_home> bad news: it is a pending commit upstream, for 3.17 :/
Jul 28 19:40:12 <bluelightning> hi ant_home
Jul 28 19:40:14 <bluelightning> hmm :/
Jul 28 19:40:41 <bluelightning> I guess it would be worth getting your objections in now upstream then
Jul 28 19:40:58 <ant_home> yes, I've sent couple of mails
Jul 28 19:41:26 <ant_home> "I got this patch a while back from the Intel guys for minnowboard/baytrail:"
Jul 28 19:41:42 <ant_home> Subject: [PATCH 23/24] spi/pxa2xx: Add common clock framework support in PCI  glue layer
Jul 28 19:41:59 <ant_home> it would be enough if it remains in minnowboard branch
Jul 28 19:42:16 <bluelightning> except that's not ideal either
Jul 28 19:42:50 <ant_home> on 24 july Subject: [PATCH v2] spi/pxa2xx: Add common clock framework support in PCI glue layer
Jul 28 19:42:58 <ant_home> was sent
Jul 28 19:43:10 <ant_home> the one in Yocto is much older
**** ENDING LOGGING AT Tue Jul 29 03:00:00 2014