**** BEGIN LOGGING AT Tue Oct 02 02:59:58 2012
Oct 02 06:51:53 <ant_work> bluelightning: gm, early there today
Oct 02 06:52:48 <bluelightning> hi ant_work
Oct 02 06:53:04 <bluelightning> yes, I've started work from home this morning
Oct 02 06:53:45 <ant_work> a question: do you know about plans to reflect MACHINE_FEATURES in KERNEL_FEATURES ?
Oct 02 06:54:10 <ant_work> (I'm sure I've already asked you time ago...)
Oct 02 06:54:51 <ant_work> now I have beautiful pieces of kernel config like USB WIFI which could be made dependent on MACHINE_FEATURES
Oct 02 06:55:14 <ant_work> (atm with ugly conditional SRC_URI manipulation)
Oct 02 06:56:26 <ant_work> I don't think the match is perfect, nor 1:1, but could make sense the day you start to convert ipaq to linux-yocto
Oct 02 07:02:25 <bluelightning> I'm going to see if I can convince the linux-yocto folks to make that work, yes
Oct 02 07:02:35 <bluelightning> in the 1.4 timeframe if they think it's a good idea
Oct 02 07:08:22 <ant_work> there are parts which are machine specific (the driver) but most of the code can be shared
Oct 02 20:43:57 <ant____> hi dromede
Oct 02 20:44:23 <ant____> I've read you found that GPIO renaming bug
Oct 02 20:44:38 <dromede> yeah
Oct 02 20:44:46 <ant____> great!
Oct 02 20:44:56 <dromede> that's what caused the suspend/resume bug
Oct 02 20:45:16 <ant____> I've seen, the other func is at 0, gpio is 1 now...
Oct 02 20:45:48 <ant____> ..I've read today there will be some gpio rework for 3.7...
Oct 02 20:46:09 <ant____> let's hope won't break things again
Oct 02 20:46:49 <dromede> well the gpio renaming bug was a subtle one
Oct 02 20:47:16 <dromede> caused by ambiguous gpio naming in now gone pxa-regs.h
Oct 02 20:48:20 <dromede> and today i found out exactly why the charger led turns on/off when you insert the charger cable
Oct 02 20:48:28 <ant____> ah
Oct 02 20:49:01 <dromede> for some reason, when you insert the charger cable, it will naturally trigger the AC_IN interrupt and start the charger
Oct 02 20:49:23 <dromede> and then right after that, the charge_full interrupt will trigger O_o
Oct 02 20:49:45 <dromede> meaning that the battery is full, even when it isn't
Oct 02 20:50:07 <dromede> i'm still investigating why this happens
Oct 02 20:51:03 <dromede> and i'm also slowly writing documentation on the ZGrom google code page
Oct 02 20:52:18 <dromede> how's your 3.4 yocto-kernel doing?
Oct 02 20:55:12 <ant____> well, I've exhagerated with the split...I fear
Oct 02 20:55:14 <ant____> http://paste.debian.net/195497/
Oct 02 20:56:18 <ant____> now I'm reassembling the pure hardware lines to rebuild a spitz.cfg valid for 3.x kernels
Oct 02 20:56:42 <ant____> all the files with 'common' are indeed shared by all models
Oct 02 20:56:56 <ant____> the ones with 'pxa' meaning no-collie
Oct 02 20:57:13 <ant____> the usb extras are for akita+spitz+tosa only
Oct 02 20:57:40 <ant____> (I've done that for all models :)
Oct 02 20:57:44 <dromede> heh
Oct 02 20:58:01 <dromede> i must say, this does look a bit too fragmented :)
Oct 02 20:59:09 <dromede> yesterday i tested my offline charging patch
Oct 02 20:59:18 <dromede> i left my akita to offline charge for about 4 hours
Oct 02 20:59:23 <ant____> then I have now to match the non-hw fragments with the ones provisded by yocto
Oct 02 20:59:32 <dromede> it resumed properly with an almost full battery :)
Oct 02 20:59:41 <ant____> wow
Oct 02 20:59:45 <dromede> today i'm gonna leave it to offline charge overnight
Oct 02 21:00:02 <dromede> and if it doesn't explode, i'll push the patch to my github kernel tree
Oct 02 21:00:13 <ant____> now, that code had only one reason for tosa if I read correctly
Oct 02 21:00:51 <dromede> you mean the spitz_pm code?
Oct 02 21:00:54 <ant____> "Only tosa used the RDY signal for it's tc6393tx chip"
Oct 02 21:01:01 <ant____> found the msg
Oct 02 21:01:02 <dromede> yes
Oct 02 21:01:15 <dromede> but tosa doesn't use sharpsl_pm
Oct 02 21:01:28 <ant____> he
Oct 02 21:01:48 <dromede> so i don't know why RP put that line in spitz_pm
Oct 02 21:01:53 <dromede> works just fine without it
Oct 02 21:02:08 <dromede> but i'm not gonna push for it's removal
Oct 02 21:02:36 <dromede> just want to push the gpio array ordering patch into mainline
Oct 02 21:02:48 <ant____> well, for sure we can host in meta-hhh such pending patches
Oct 02 21:03:06 <dromede> agreed
Oct 02 21:03:22 <dromede> at least the ones that fix sharsl_pm bugs
Oct 02 21:03:29 <dromede> *sharpsl_pm
Oct 02 21:10:45 <ant____> any idea about
Oct 02 21:10:46 <ant____> #
Oct 02 21:10:46 <ant____> # USB Host Controller Drivers
Oct 02 21:10:46 <ant____> #
Oct 02 21:10:46 <ant____> CONFIG_USB_SL811_HCD=m
Oct 02 21:10:47 <ant____> CONFIG_USB_SL811_CS=m
Oct 02 21:10:50 <ant____> ?
Oct 02 21:11:32 <ant____> googling seems a debug board
Oct 02 21:12:29 <dromede> no idea what that is
Oct 02 21:12:57 <ant____> somehow is for devices with usb host
Oct 02 21:13:30 <ant____> I find that only for spitz/akita/tosa
Oct 02 21:13:55 <dromede> wel, SL811 as you said, is a small debug board with a usb host/slave chip
Oct 02 21:14:05 <dromede> i never saw those modules loaded on my machine
Oct 02 21:14:16 <dromede> doesn't hurt to leave them as modules
Oct 02 21:15:10 <ant____> seems not coming from yocto, neither
**** ENDING LOGGING AT Wed Oct 03 02:59:59 2012