**** BEGIN LOGGING AT Mon Mar 31 03:00:00 2014
Mar 31 07:18:56 <ant_work> gm bluelightning
Mar 31 07:49:12 <ant_work> bluelightning: 3.14 is finally committed
Mar 31 07:49:29 <bluelightning> yep saw that
Mar 31 07:49:31 <bluelightning> \o/
Mar 31 07:49:59 <ant_work> now I think we could live with 3.14 alone in meta-hh
Mar 31 07:50:06 <ant_work> i.e. dropping -next
Mar 31 07:51:31 <ant_work> I'll rebase the patches and will find some hack to stage them only once in meta-hh
Mar 31 07:51:44 <ant_work> thinking about a generic linux-yocto dir
Mar 31 07:52:21 <ant_work> -kexecboot will use the same patches
Mar 31 07:53:13 <ant_work> now, don't you think it is time to archive the old never supported 2.x kernels?
Mar 31 08:14:02 <ant_work> bluelightning: I noticed some jolly expression in the bbappend like
Mar 31 08:14:16 <ant_work> meta-systemd/oe-core/recipes-core/util-linux/util-linux_%.bbappend
Mar 31 08:14:26 <ant_work> how safe is it?
Mar 31 08:29:37 <bluelightning> ant_work: dropping -next in favour of 3.14 sounds OK to me
Mar 31 08:31:02 <bluelightning> ant_work: that's the new bbappend wildcard support; it's had a fair amount of testing/fixing by now so it should be safe to rely upon
Mar 31 08:31:49 <bluelightning> obviously it's only suitable for changes that aren't likely to break with newer versions; bbappends that apply patches probably don't qualify in most cases
Mar 31 08:32:52 <ant_work> heh
Mar 31 08:34:00 <ant_work> we have a couple who are (maybe) worth, formfactor, kexecboot,...
Mar 31 08:35:22 <ant_work> and afaik Ross said we could discard xserver-xf86-config_0.1.bbappend
Mar 31 12:02:23 <ant_work> lumag: hi, are you around or is just the bot?
Mar 31 12:03:27 <lumag> hello ant_work
Mar 31 12:03:33 <lumag> I'm a bot
Mar 31 12:03:43 <ant_work> EHLO
Mar 31 12:04:04 <ant_work> I'll rebase soon all the patches around for 3.14
Mar 31 12:04:14 <lumag> Great.
Mar 31 12:04:24 <ant_work> about locomo-spi, is it enough stable for kexecboot?
Mar 31 12:04:31 * lumag didn't have time for anything except work several last weeks
Mar 31 12:04:49 <ant_work> almost the same here...
Mar 31 12:05:03 <ant_work> you said it was not 100%
Mar 31 12:06:58 <lumag> My friend once brought me a card (real MMC card) that locomo-spi(mmc-spi) was not able to understand
Mar 31 12:09:48 <lumag> All my SD cards just work.
Mar 31 12:10:01 <lumag> Maybe it is a problem of timings and relaxing SPI clock would help.
Mar 31 12:21:32 <ant_work> there is a well known table of the timings isn't?
Mar 31 12:50:10 <lumag> ant_work, don't remember atm
Mar 31 13:49:54 <ant_work> only the clocks...
Mar 31 13:51:30 <ant_work> Clock frequency can be selected from among 15 bands (24.576MHz -
Mar 31 13:51:31 <ant_work> 2.304MHz and 384 kHz - 288 KHz).
Mar 31 13:51:45 <ant_work> but only 3 are used (both in old driver and service man)
Mar 31 13:51:53 <ant_work> +#define CLOCK_18MHZ	    0		/* 18,432 MHz clock 	*/
Mar 31 13:51:53 <ant_work> +#define CLOCK_22MHZ	    1		/* 22,5792 MHz clock	*/
Mar 31 13:51:53 <ant_work> +#define CLOCK_25MHZ	    2		/* 24,576 MHz clock	*/
Mar 31 13:53:37 <ant_work> I guess the delays have been extimated
Mar 31 16:07:30 <ant_work> bbl
Mar 31 20:47:20 <ant_home> lumag: heh, funny failure of 3.10
Mar 31 20:47:23 <ant_home> setup.c:564:1: error: expected expression before '>>' token
Mar 31 20:47:23 <ant_home> |  >>>>>>> v3.10.34
Mar 31 20:47:36 <ant_home> gitAUTOINC+df3aa753c8_c7739be126-r0/linux/arch/arm/kernel/setup.c:564:11: error: too many decimal points in number
Mar 31 20:47:36 <ant_home> |  >>>>>>> v3.10.34
Mar 31 21:35:04 <ant_home> well, merge-conflicts...
Mar 31 21:35:15 <ant_home> I'll wait for 3.14 (tomorrow?)
Mar 31 22:10:19 <ant_home> too bad, committed now...late
Mar 31 22:10:50 <ant_home> bluelightning: pls merge the two patches for meta-initramfs when you have 5 mins
Mar 31 22:10:51 <ant_home> gn
**** ENDING LOGGING AT Tue Apr 01 02:59:59 2014