**** BEGIN LOGGING AT Mon Oct 01 03:00:00 2012
Oct 01 10:02:40 * ant_work is getting bored processing kernel .config fragments
Oct 01 10:03:32 <ant_work> now I've split the defconfigs in over 30 fragments
Oct 01 10:03:47 <ant_work> good news, 19 are common to all Z
Oct 01 10:40:26 <ant_work> hi dromede
Oct 01 10:40:46 <dromede> hi ant
Oct 01 10:46:17 <ant_work> I'll need some more time with the defconfigs split
Oct 01 10:46:30 <dromede> ok
Oct 01 10:46:32 <ant_work> even, I'll need some opinions
Oct 01 10:46:59 <ant_work> i.e. the usb/net/bt modules to build
Oct 01 10:47:13 <ant_work> I was hoping we can justuse the policies in
Oct 01 10:47:14 <ant_work> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/tree/
Oct 01 10:47:30 <ant_work> we use ktypes -> standard/base
Oct 01 10:47:46 <ant_work> the fragments are in /cfg and /features
Oct 01 10:48:32 <ant_work> for the non-hardware part, I'm trying to match the pieces I've split with those
Oct 01 10:49:30 <dromede> i can't say anything about net/bt modules
Oct 01 10:49:32 <dromede> but usb
Oct 01 10:49:55 <dromede> ohci-hcd, pxa27x_udc and all the usb gadget drivers should be built, imho
Oct 01 10:50:30 <ant_work> ideally we should use  http://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/tree/features/usb
Oct 01 10:50:42 <ant_work> and ofc add the drivers in the 'hardware' .cfg
Oct 01 10:50:57 <dromede> and i'm still not familiar with the linux-yocto build system so i can't help you there
Oct 01 10:51:12 <dromede> i still build my kernel outside of OE
Oct 01 10:51:21 <dromede> i will eventually move to linux-yocto kernel
Oct 01 10:52:52 <ant_work> linux-yocto can accept an old-style defconfig or only one minimal part (hw-specific) and rely on the policies of ktype
Oct 01 10:53:10 <ant_work> this latter has many advantages
Oct 01 10:53:27 <ant_work> i.e. we reduce the mainainance
**** ENDING LOGGING AT Tue Oct 02 02:59:58 2012