**** BEGIN LOGGING AT Sun Jul 29 02:59:59 2012
Jul 29 06:45:38 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r9c978ec4b55e 10/meta-fso/recipes-freesmartphone/cornucopia/libfsoframework.inc: libfsoframework: add libgsm0710 to DEPENDS
Jul 29 06:45:48 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r3d04e029083a 10/meta-fso/recipes-freesmartphone/cornucopia/cornucopia-base.inc: meta-fso: cornucopia: bump PR to rebuild agains newer libfso-glib
Jul 29 06:45:49 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r1d0387f6ac22 10/meta-shr/recipes-shr/shr/ (libphone-ui-shr_git.bb libphone-ui_git.bb phonefsod_git.bb): meta-shr: libphone-ui-shr, libphone-ui, phonefsod: bump PR to rebuild agains newer libfso-glib
Jul 29 06:45:49 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r978ac8abb891 10/meta-shr/conf/distro/include/preferred-shr-versions.inc: meta-shr: preferred-shr-versions: drop entries which are not needed now
Jul 29 07:26:19 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * rb4c59f0c2174 10/meta-shr/recipes-navigation/monav/monav_0.3.bb: monav: fix build with stricter shell
Jul 29 07:26:29 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r52d47409875c 10/meta-fso/recipes-freesmartphone/freesmartphone/libfso-qt_git.bb: meta-fso: libfso-qt: bump SRCREV to fix autora-daemon build
Jul 29 07:26:29 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * rbe3596011129 10/meta-shr/recipes-shr/3rdparty/ (6 files): meta-shr: add edje-native to some 3rdparty recipes
Jul 29 08:16:38 <CIA-69> SHR: 03shr-devel 07buildhistory * r03b5edc17225 10/packages/armv7a-vfp-neon-oe-linux-gnueabi/ (202 files in 202 dirs): packages: Build 201207290928 of shr 20120729 for machine om-gta04 on opmbuild
Jul 29 08:48:51 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r53bfed82b706 10/ (2 files in 2 dirs): meta-aurora: aurora-systemmanager: bump PR to rebuild agains newer libfso-glib
Jul 29 09:03:03 <CIA-69> SHR: 03Martin.Jansa 07libphone-ui * rc806456494b4 10/src/ (phoneui-utils-sound.c phoneui-utils.c): phoneui-utils-sound: make snd errors not critical
Jul 29 09:04:27 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r3b639855bfbf 10/meta-shr/recipes-shr/shr/libphone-ui_git.bb: libphone-ui: bump SRCREV, don't fail without snd card
Jul 29 09:20:41 <CIA-69> SHR: 03shr-devel 07buildhistory * r8dd5e0c6b14f 10/packages/armv7a-vfp-neon-oe-linux-gnueabi/monav/ (7 files in 7 dirs): packages: Build 201207291102 of shr 20120729 for machine crespo on opmbuild
Jul 29 10:14:14 <CIA-69> freesmartphone.org: 03morphis 07cornucopia * r7c534572b687 10/fsogsmd/src/lib/consts.vala: fsogsmd: lib: throw correct exception for +CME ERROR: 21; fixes #549
Jul 29 10:14:28 <CIA-69> freesmartphone.org: 03morphis 070.12 * rabc8bf85296b 10cornucopia/fsogsmd/src/lib/consts.vala: fsogsmd: lib: throw correct exception for +CME ERROR: 21; fixes #549
Jul 29 11:33:46 <CIA-69> SHR: 03Martin.Jansa 07meta-smartphone * r0b1f47ea1928 10/meta-shr/recipes-graphics/xorg-xserver/ (4 files in 4 dirs): meta-shr: xserver-xf86-config: add our own xorg.conf files for qemu machines, we expect Touchscreen input device
Jul 29 11:59:55 <morphis> JaMa: I currently have problems with compiling libxcb: http://pastie.org/4352949
Jul 29 12:00:02 <morphis> you know this one already?
Jul 29 12:01:51 <JaMa> nope, it built fine yesterday, can you try to cleansstate it and add inherit pythonnative to it?
Jul 29 12:03:21 <morphis> to xcb-proto.inc?
Jul 29 12:03:58 <morphis> xcb-proto.inc already has DEPENDS_append_virtclass-native = " python-native"
Jul 29 12:05:47 <JaMa> but this inherit does something else.. it adds python-native to PATH
Jul 29 12:05:55 <JaMa> otherwise it's using python from host
Jul 29 12:06:29 <JaMa> | /usr/bin/python ./c_client.py -p /OE/shr-core/tmp-eglibc/sysroots/crespo//usr/lib64/python2.7/site-packages /OE/shr-core/tmp-eglibc/sysroots/crespo//usr/share/xcb/xproto.xml
Jul 29 12:06:38 <JaMa> while xcbgen is installed only in your native sysroot
Jul 29 12:09:49 <morphis> ok
Jul 29 12:22:10 <morphis> JaMa: hm, that doesn't solve the problem
Jul 29 12:22:15 <morphis> it's using now the correct python
Jul 29 12:22:27 <morphis> but xcbgen is not available in tmp-eglibc/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/
Jul 29 12:22:37 <morphis> but xcb-proto-native is successfully build
Jul 29 12:24:03 <morphis> it's in tmp-eglibc/work/x86_64-linux/xcb-proto-native/xcb-proto-native-1.7.1-r0/image/OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/lib64/python2.7/site-packages/xcbgen/ but there is no lib64 folder in tmp-eglibc/sysroots/x86_64-linux/usr/
Jul 29 12:24:05 <morphis> hm
Jul 29 12:26:45 <JaMa> morphis: there is also http://patchwork.openembedded.org/patch/31977/ for xcb-proto I thought this was applied already
Jul 29 12:27:04 <morphis> it's not
Jul 29 12:27:15 <morphis> at least not in our shr branch of oe-core
Jul 29 12:29:02 <JaMa> shr branch was rebased today
Jul 29 12:29:21 <JaMa> but it should be inherited anyway meta/classes/distutils-base.bbclass:inherit distutils-common-base pythonnative
Jul 29 12:30:06 <JaMa> ah no it's not using distutils
Jul 29 12:33:07 <JaMa> morphis: can you try to rebuild it with pw-am.sh.oe-core 31977 31987 ?
Jul 29 12:36:49 <morphis> yes
Jul 29 12:37:09 <JaMa> will start the same after current image is finished
Jul 29 12:38:54 <morphis> ok
Jul 29 12:42:28 <morphis> JaMa: compiles fine with both patches applied
Jul 29 12:43:17 <JaMa> ok will add it to SHR branch 
Jul 29 12:43:20 <JaMa> thanks
Jul 29 12:43:42 <morphis> no problem
Jul 29 12:59:28 <CIA-69> SHR: 03Martin.Jansa 07shr-wizard * r8b397539e332 10/python/shr-wizard.py: shr-wizard: replace homogenous_set with homogeneous_set
Jul 29 13:16:22 <CIA-69> SHR: 03shr-devel 07buildhistory * rba40474f28bc 10/packages/ (444 files in 444 dirs): packages: Build 201207291305 of shr 20120729 for machine om-gta02 on opmbuild
Jul 29 13:53:58 <morphis> GNUtoo|laptop: heyho
Jul 29 13:57:49 <GNUtoo|laptop> morphis, hi
Jul 29 13:58:09 <morphis> GNUtoo|laptop: sorry I was off so quickly yesterday
Jul 29 13:58:45 <GNUtoo|laptop> np
Jul 29 13:58:58 <morphis> GNUtoo|laptop: what quirks for bluetooth are need for gta04?
Jul 29 14:00:24 <GNUtoo|laptop> it depend on the kernel we are targetting
Jul 29 14:00:36 <GNUtoo|laptop> do we drop 3.4 and target 3.5?
Jul 29 14:15:03 <CIA-69> SHR: 03shr-devel 07buildhistory * r1f83fb586cc7 10/packages/ (21 files in 21 dirs): packages: Build 201207291537 of shr 20120729 for machine om-gta02 on opmbuild
Jul 29 14:15:14 <CIA-69> SHR: 03shr-devel 07buildhistory * r2930ce48869a 10/images/om_gta02/eglibc/ (22 files in 2 dirs): images: Build 201207291537 of shr 20120729 for machine om-gta02 on opmbuild
Jul 29 14:32:41 <morphis> GNUtoo|laptop: don't know what the plan regarding kernel version for the GTA04 is
Jul 29 14:32:57 <morphis> GNUtoo|laptop: but what in detail we have to do to get bluetooth working?
Jul 29 14:33:13 <GNUtoo|laptop> it depend if we target 3.4 or 3.5
Jul 29 14:33:20 <GNUtoo|laptop> all are documented on gta04 wiki
Jul 29 14:33:49 <GNUtoo|laptop> http://projects.goldelico.com/p/gta04-kernel/doc/
Jul 29 14:34:31 <GNUtoo|laptop> basically it's in configure
Jul 29 14:34:37 <GNUtoo|laptop> inside http://projects.goldelico.com/p/gta04-kernel/page/Wireless/
Jul 29 14:34:37 <morphis> so if we enable WiFi we enable bluetooth too?
Jul 29 14:34:47 <GNUtoo|laptop> I think it's separated now
Jul 29 14:35:07 <GNUtoo|laptop> do you want me to try
Jul 29 14:35:55 <morphis> we need a list of steps we have to do to enable bluetooth
Jul 29 14:36:06 <morphis> so we can assign to the several FSO components
Jul 29 14:36:10 <GNUtoo|laptop> ok
Jul 29 14:36:16 <GNUtoo|laptop> let me try then
Jul 29 14:37:04 <morphis> bluez takes care about handling the rfkill I think
Jul 29 14:37:26 <GNUtoo|laptop> no idea
Jul 29 14:37:31 <GNUtoo|laptop> I'll look a bit later
Jul 29 14:37:41 <GNUtoo|laptop> now I've to buy the serial connector for crespo
Jul 29 14:37:50 <morphis> ok
Jul 29 15:01:13 <GNUtoo|laptop> now let me try
Jul 29 15:01:43 <GNUtoo|laptop> the big problem is that USB seem broken in gta04
Jul 29 15:14:22 <GNUtoo|laptop> morphis, we can have shorter init sequence for bt
Jul 29 15:14:45 <GNUtoo|laptop> if we ask gta04 A3 owners to set their bt device to 3M
Jul 29 15:15:19 <GNUtoo|laptop> qtmoko already does that
Jul 29 15:16:52 <GNUtoo|laptop> morphis, does wifi works for you on gta04?
Jul 29 15:16:58 <GNUtoo|laptop> because I've to ifconfig wlan0 up now
Jul 29 15:29:07 <GNUtoo|laptop> hmmm
Jul 29 15:29:21 <GNUtoo|laptop> when I play with bluetooth my gta04 blocks
Jul 29 15:29:24 <GNUtoo|laptop> I'll look with serial
Jul 29 15:30:30 <morphis> GNUtoo|laptop: USB ist broken?
Jul 29 15:32:02 <GNUtoo|laptop> for me I've error -71
Jul 29 15:32:09 <GNUtoo|laptop> on my latpop
Jul 29 15:32:11 <GNUtoo|laptop> with GTA04
Jul 29 15:32:16 <GNUtoo|laptop> with GTA02 no errors
Jul 29 15:32:35 <GNUtoo|laptop> error -71 is the following error:
Jul 29 15:32:55 <GNUtoo|laptop> #define	EPROTO		71	/* Protocol error */
Jul 29 15:37:23 <morphis> ok
Jul 29 15:37:38 <morphis> I thought something in SHR itself is broken about USB
Jul 29 15:37:40 <morphis> like kernel
Jul 29 15:41:21 <GNUtoo|laptop> morphis, it works now
Jul 29 15:41:24 <GNUtoo|laptop> (bluetooth)
Jul 29 15:41:27 <morphis> GNUtoo|laptop: I didn't tried wifi on gta04 for a long time
Jul 29 15:42:13 <GNUtoo|laptop> morphis, possible about kernel but it's specific to GTA04
Jul 29 15:42:17 <GNUtoo|laptop> I'll try gta02 master
Jul 29 15:42:21 <GNUtoo|laptop> because it was not master
Jul 29 15:42:25 <GNUtoo|laptop> on gta02
Jul 29 15:42:29 <GNUtoo|laptop> and it was master with gta04
Jul 29 15:43:01 <morphis> GNUtoo|laptop: so the steps described on the wiki page are still working?
Jul 29 15:43:30 <GNUtoo|laptop> not exactly, here's are my steps:
Jul 29 15:43:33 <GNUtoo|laptop> 1) enable wifi
Jul 29 15:44:11 <GNUtoo|laptop> http://pastie.org/private/ycdmeggnltnolcgqttlafw
Jul 29 15:44:21 <GNUtoo|laptop> in echo bluetoothd I launch bluetoothd by hand
Jul 29 15:44:53 <morphis> ok
Jul 29 15:45:12 <morphis> can this work while bluetoothd is already running?
Jul 29 15:45:41 <morphis> as on my laptop bluetooth is off but hci0 is available
Jul 29 15:45:56 <GNUtoo|laptop> yes
Jul 29 15:46:04 <GNUtoo|laptop> I guess so
Jul 29 15:46:12 <morphis> so can we keep bluetoothd running and hci0 available but the bluetooth device in suspend/power-off mode?
Jul 29 15:46:37 <GNUtoo|laptop> no idea
Jul 29 15:46:49 <GNUtoo|laptop> maybe
Jul 29 15:47:17 <GNUtoo|laptop> the manual says that:
Jul 29 15:47:25 <GNUtoo|laptop> Remember to activate where necessary the bluetooth device via the rfkill switches after launching hciatttach.
Jul 29 15:47:50 <morphis> so it's on suspend mode when rfkill is unblocked
Jul 29 15:47:55 <GNUtoo|laptop> I think so
Jul 29 15:47:58 <GNUtoo|laptop> not sure
Jul 29 15:48:28 <GNUtoo|laptop> also with what I pasted we must update the manual
Jul 29 15:48:35 <GNUtoo|laptop> to make people setup their bt at 3M
Jul 29 15:50:29 <morphis> ok
Jul 29 15:50:51 <morphis> as bluetoothd has it own power management logic as far as I know with using the rfkill
Jul 29 15:51:02 <morphis> so we can configure bluetooth on boot
Jul 29 15:51:10 <morphis> keep hci0 and launch bluetoothd
Jul 29 15:56:08 <morphis> GNUtoo|laptop: what do you think?
Jul 29 15:57:20 <GNUtoo|laptop> yes could be an option
Jul 29 15:57:38 <GNUtoo|laptop> we ask in gta04 ml if it has impacts on power managements
Jul 29 15:57:40 <GNUtoo|laptop> ?
Jul 29 15:57:46 <GNUtoo|laptop> *power management
Jul 29 15:57:53 <GNUtoo|laptop> but note that it works until 3.4 kernel
Jul 29 15:58:02 <GNUtoo|laptop> 3.5 has totally changed its power management
Jul 29 16:01:18 <GNUtoo|laptop> morphis, I should also add XV?
Jul 29 16:14:02 <morphis> XV?
Jul 29 16:17:31 <morphis> GNUtoo|laptop: hm, 3.5 with the patches from neil seems to be a little bit problematic to me
Jul 29 16:18:36 <morphis> I really like the idea of handing over the power management to bluez
Jul 29 16:20:06 <morphis> I have to reboot
Jul 29 16:26:50 <GNUtoo|laptop> but in another hand:
Jul 29 16:26:58 <GNUtoo|laptop> 1) it's the upstream way to go
Jul 29 16:27:07 <GNUtoo|laptop> 2) it's compatible with every program
Jul 29 16:27:11 <GNUtoo|laptop> 3) it works out of the box
Jul 29 16:27:20 <GNUtoo|laptop> we just disable some plugins
Jul 29 16:27:24 <GNUtoo|laptop> and I guess it'll work
Jul 29 16:27:33 <morphis> it's the upstream way?
Jul 29 16:27:34 <GNUtoo|laptop> at least I hope
Jul 29 16:27:48 <GNUtoo|laptop> I guess so
Jul 29 16:27:54 <morphis> I thought handling rfkill is the common way
Jul 29 16:28:06 <GNUtoo|laptop> I heard rfkill was not for power management
Jul 29 16:28:12 <GNUtoo|laptop> think of it like airplane mode
Jul 29 16:28:19 <GNUtoo|laptop> for instance for wifi
Jul 29 16:28:28 <GNUtoo|laptop> I know the wifi story
Jul 29 16:28:34 <GNUtoo|laptop> I was here when it happened
Jul 29 16:28:46 <GNUtoo|laptop> for wifi there was the omap zoom platform
Jul 29 16:28:48 <GNUtoo|laptop> it's a device
Jul 29 16:29:18 <GNUtoo|laptop> so some person wanted to add a new way to handle wifi power management with sdio
Jul 29 16:29:26 <GNUtoo|laptop> so at the end they added callbacks
Jul 29 16:29:31 <GNUtoo|laptop> to make it work automatically
Jul 29 16:29:34 <GNUtoo|laptop> when you do
Jul 29 16:29:37 <GNUtoo|laptop> ifconfig wlan0 up
Jul 29 16:29:41 <GNUtoo|laptop> it powers on the wifi card
Jul 29 16:31:11 <morphis> ok
Jul 29 16:31:15 <morphis> thats great
Jul 29 16:31:22 <morphis> hm
Jul 29 16:31:37 <morphis> but in case of bluetooth we have to run hciattach
Jul 29 16:31:41 <morphis> and then launch bluetoothd
Jul 29 16:32:21 <morphis> in case of wifi we can start using it after powering up the interface
Jul 29 16:32:30 <morphis> I thinking more in a system context
Jul 29 16:32:36 <morphis> who is responsible for this
Jul 29 16:34:21 <morphis> if we have now a bluetooth resource in our FSO context
Jul 29 16:34:41 <morphis> should we only run hciattach there?
Jul 29 16:36:32 <GNUtoo|laptop> hmmm
Jul 29 16:37:01 <GNUtoo|laptop> it could also run in machine init script
Jul 29 16:37:32 <GNUtoo|laptop> xv is motion compensation video acceleration btw
Jul 29 16:37:43 <GNUtoo|laptop> it's in xf86-video-omapfb
Jul 29 16:37:46 <GNUtoo|laptop> but it requires:
Jul 29 16:37:54 <GNUtoo|laptop> *)3 framebuffers
Jul 29 16:38:20 <GNUtoo|laptop> *) some xorg extensions
Jul 29 16:38:33 <GNUtoo|laptop> *) enough video memory
Jul 29 16:38:45 <GNUtoo|laptop> like 640x480x32 / 4
Jul 29 16:38:49 <GNUtoo|laptop> opops
Jul 29 16:38:54 <GNUtoo|laptop> like 640x480x32 / 8
Jul 29 16:39:25 <morphis> GNUtoo|laptop: let's stay with bluetooth for the moment
Jul 29 16:39:36 <GNUtoo|laptop> ok
Jul 29 16:39:40 <morphis> if I look at how ubuntu handles this: there is the bluetooth applet
Jul 29 16:39:43 <GNUtoo|laptop> I'm doing xv right now tough
Jul 29 16:39:47 <morphis> you can activate/deactivate bluetooth
Jul 29 16:39:51 <GNUtoo|laptop> ok
Jul 29 16:40:00 <morphis> by rfkill
Jul 29 16:40:21 <morphis> it blocks/unblocks the rfkill for you when you set the option
Jul 29 16:40:27 <GNUtoo|laptop> ok
Jul 29 16:40:30 <morphis> bluetoothd is running all the time
Jul 29 16:40:51 <morphis> but no hciattach is used in this case
Jul 29 16:41:25 <GNUtoo|laptop> http://neil.brown.name/blog/20120724060722
Jul 29 16:41:27 <GNUtoo|laptop> hmmm
Jul 29 16:41:33 <GNUtoo|laptop> read the part on bt
Jul 29 16:41:48 <GNUtoo|laptop> The bluetooth is automatically powered up when /dev/ttyO0 is opened, and [...]
Jul 29 16:42:02 <morphis> bluetooth on kernel side
Jul 29 16:42:13 <morphis> but if we're launching the bluez daemon on boot
Jul 29 16:42:19 <morphis> bluetooth is always powerd up
Jul 29 16:42:24 <GNUtoo|laptop> not sure
Jul 29 16:42:30 <morphis> (if we run hciattach too)
Jul 29 16:42:33 <GNUtoo|laptop> ah ok
Jul 29 16:42:43 <GNUtoo|laptop> we should kill hciattach before suspend
Jul 29 16:42:48 <GNUtoo|laptop> and re-launch it
Jul 29 16:42:56 <morphis> no
Jul 29 16:43:09 <GNUtoo|laptop> ah?
Jul 29 16:43:20 <morphis> why should we?
Jul 29 16:43:37 <GNUtoo|laptop> because else we will have to modify the future kenrels
Jul 29 16:43:41 <GNUtoo|laptop> or stay with 3.4
Jul 29 16:43:42 <morphis> if we're using neil's approach the kernel takes care about suspending the bluetooth chip even when /dev/tty.. is opened
Jul 29 16:43:52 <GNUtoo|laptop> read what he said
Jul 29 16:43:59 <GNUtoo|laptop> The bluetooth is automatically powered up when /dev/ttyO0 is opened, and powered down when it is closed. This is much nicer (more automatic) than having an 'rfkill' device. So running hciattach /dev/ttyO0 any will power on the device, and killall hciattach will turn it off. Simple. Power is turned off when the device suspends too so you don't need to kill hciattach before suspend. 
Jul 29 16:44:14 <GNUtoo|laptop> ah ok
Jul 29 16:44:15 <GNUtoo|laptop> sorry
Jul 29 16:44:20 <GNUtoo|laptop> so we suspend nicely then
Jul 29 16:44:24 <morphis> "Power is turned off when the device suspends too so you don't need to kill hciattach before suspend."
Jul 29 16:44:28 <GNUtoo|laptop> yes
Jul 29 16:44:28 <morphis> yes
Jul 29 16:44:31 <GNUtoo|laptop> I just read it now
Jul 29 16:44:34 <GNUtoo|laptop> sorry
Jul 29 16:44:34 <morphis> :)
Jul 29 16:44:59 <morphis> it moves the control point for the user here
Jul 29 16:45:27 <morphis> the user has to launch the bluetooth daemon (let's assume launching the bluetooth daemon includes hciattach) rather then just setting a switch
Jul 29 16:45:55 <GNUtoo|laptop> ok
Jul 29 16:46:05 <morphis> so we have less work on the userland side
Jul 29 16:46:17 <GNUtoo|laptop> yes
Jul 29 16:46:28 <morphis> as we only need to set the rfkill which can be easily done by the UI or a resource in our FSO system
Jul 29 16:46:32 <GNUtoo|laptop> and also it's more generally compatible with other stuff than fso
Jul 29 16:46:39 <morphis> yes
Jul 29 16:46:53 <GNUtoo|laptop> that easier the switch to for instance general deamons as backend
Jul 29 16:46:55 <morphis> it nicely integrates with fsousaged+kernel26_rfkill plugin of fsodeviced
Jul 29 16:47:16 <GNUtoo|laptop> for instance if you want to use something else than iliwi you can
Jul 29 16:47:18 <GNUtoo|laptop> etc...
Jul 29 16:47:26 <morphis> I removed the lines relevant for starting bluetoothd from kernel26_rfkill anyway
Jul 29 16:47:29 <GNUtoo|laptop> like an enlightenment plugin for instance
Jul 29 16:47:29 <GNUtoo|laptop> ok
Jul 29 16:47:49 <GNUtoo|laptop> where did the start move?
Jul 29 16:48:01 <morphis> nowhere
Jul 29 16:48:04 <morphis> it's removed
Jul 29 16:48:17 <GNUtoo|laptop> so it's broken?
Jul 29 16:48:26 <GNUtoo|laptop> gor gta02
Jul 29 16:48:28 <morphis> kernel26_rfkill?
Jul 29 16:48:28 <GNUtoo|laptop> *for
Jul 29 16:48:44 <GNUtoo|laptop> gta02 needs bluetoothd to be launched somehow
Jul 29 16:48:47 <morphis> yes
Jul 29 16:48:49 <GNUtoo|laptop> for instance by udev
Jul 29 16:49:03 <morphis> but it's not the right way to do this inside of kernel26_rfkill
Jul 29 16:49:09 <GNUtoo|laptop> yes
Jul 29 16:49:10 <morphis> it was a hack
Jul 29 16:49:12 <GNUtoo|laptop> maybe trough udev
Jul 29 16:49:13 <GNUtoo|laptop> yes
Jul 29 16:49:27 <morphis> GNUtoo|laptop: why not launching bluetoohd on system boot?
Jul 29 16:49:37 <morphis> GNUtoo|laptop: look at this http://pastie.org/4353991
Jul 29 16:49:43 <GNUtoo|laptop> yes possible too
Jul 29 16:49:46 <morphis> thats what ubuntu does
Jul 29 16:49:49 <GNUtoo|laptop> ok
Jul 29 16:50:20 <morphis> thats the way I would like to see it too for a FSO based system
Jul 29 16:50:27 <morphis> so we have the rfkill resource for bluetooth only
Jul 29 16:50:33 <GNUtoo|laptop> ok
Jul 29 16:51:34 <morphis> I don't know how well the bluetooth drivers for several android devices is implement and if it hurts their battery live if we have bluetoothd running all the time and just using the rfkill for power management
Jul 29 16:52:03 <morphis> but thats the way to go in my eyes
Jul 29 16:52:16 <morphis> s/eyes/mind/
Jul 29 16:52:51 <GNUtoo|laptop> ok
Jul 29 16:53:46 <morphis> and as I read somewhere having bluetooth in idle mode should not take more than 1.8mW
Jul 29 16:54:21 <GNUtoo|laptop> ok
Jul 29 16:55:04 <GNUtoo|laptop> basically neil works with upstream , so I think we should do something that is compatible with his kernel
Jul 29 16:56:59 <morphis> maybe we should remove this commit here: http://git.freesmartphone.org/?p=linux-2.6.git;a=commit;h=c002d540f5c87e592bdaae2340a706865395fa5a
Jul 29 16:57:29 <morphis> we should use his kernel
Jul 29 16:57:40 <morphis> as for example the GPS related stuff is very nice
Jul 29 16:57:41 <GNUtoo|laptop> maybe we :
Jul 29 16:57:45 <GNUtoo|laptop> 1) drop the commit
Jul 29 16:57:47 <GNUtoo|laptop> 2)use it
Jul 29 16:57:55 <GNUtoo|laptop> 3) tell we dropped it on gta04 ml
Jul 29 16:58:14 <GNUtoo|laptop> or 0) tell we intend to drop that commit
Jul 29 16:58:19 <GNUtoo|laptop> and see how to work with him
Jul 29 16:58:29 <morphis> yeah, we should start discussing this issue on the ML
Jul 29 16:58:39 <morphis> we're using 3.4 right now?
Jul 29 16:58:44 <GNUtoo|laptop> yes
Jul 29 16:58:55 <morphis> ok, so I would propose
Jul 29 16:59:00 <morphis> let's stay with 3.4 for now
Jul 29 16:59:04 <GNUtoo|laptop> Linux om-gta04 3.4.6 #1 PREEMPT Thu Jul 26 17:59:03 CEST 2012 armv7l GNU/Linux
Jul 29 16:59:17 <morphis> start bluetooth daemon on boot
Jul 29 16:59:30 <morphis> and experiment with the usage of kernel26_rfkill a bit
Jul 29 16:59:37 <GNUtoo|laptop> ok
Jul 29 17:00:26 <morphis> if disabling the auto-magic is only about reverting one commit that shouldn't we a huge issue for everyone
Jul 29 17:00:49 <GNUtoo|laptop> ok
Jul 29 17:00:56 <morphis> as you have to think about another aspect: we have to keep this in sync with the other devices we support
Jul 29 17:01:06 <GNUtoo|laptop> yes
Jul 29 17:01:06 <morphis> neil only needs to support the gta04
Jul 29 17:01:23 <morphis> but we have at least gta02, gta04, n900 and crespo
Jul 29 17:05:12 <morphis> GNUtoo|laptop: hm there is not system service file for bluez yet
Jul 29 17:05:23 <GNUtoo|laptop> ah ok
Jul 29 17:05:27 <GNUtoo|laptop> we should create one then
Jul 29 17:06:01 <morphis> there is still the init.d script
Jul 29 17:06:05 <morphis> which should be executed too
Jul 29 17:06:21 <GNUtoo|laptop> hmmm
Jul 29 17:06:26 <GNUtoo|laptop> fsodeviced failed on gta02
Jul 29 17:07:25 <GNUtoo|laptop> plugin.vala:29.1-29.39: error: `Router.Qdsp5' does not implement abstract method `FsoFramework.AbstractObject.repr'
Jul 29 17:07:28 <GNUtoo|laptop> we should drop theses
Jul 29 17:07:44 <GNUtoo|laptop> it's useless and the code is apache 2.0 dependant
Jul 29 17:11:15 <morphis> GNUtoo|laptop: ok
Jul 29 17:11:21 <morphis> with AUTOREV?
Jul 29 17:11:42 <GNUtoo|laptop> yes
Jul 29 17:11:55 <morphis> ok, will fix that
Jul 29 17:11:56 <GNUtoo|laptop> I must go very very soon
Jul 29 17:11:59 <GNUtoo|laptop> ok
Jul 29 17:12:14 <morphis> GNUtoo|laptop: the init logic for bluetooth will be a little bit more complex
Jul 29 17:12:26 <morphis> as you have to differ between the different hciattach approaches
Jul 29 17:12:37 <morphis> for example the crespo uses this brcm... utility
Jul 29 17:13:21 <GNUtoo|laptop> ok
Jul 29 17:13:24 <GNUtoo|laptop> it works for crespo?
Jul 29 17:13:41 <morphis> it's the same thing that android uses to initialize bluetooth
Jul 29 17:14:14 <GNUtoo|laptop> yes but does bluetooth work for crespo
Jul 29 17:14:14 <morphis> I autotoolized it some time ago here: http://git.freesmartphone.org/?p=utilities.git;a=tree;f=android/brcm_patchram_plus;h=f6a8ef34f754df832e3e6bacf94847cb42cc9149;hb=HEAD
Jul 29 17:14:17 <GNUtoo|laptop> I know that thing
Jul 29 17:14:21 <GNUtoo|laptop> yes I saw it
Jul 29 17:14:30 <GNUtoo|laptop> does it works out of the box?
Jul 29 17:14:55 <morphis> yes
Jul 29 17:15:02 <morphis> you need the firmware files
Jul 29 17:15:03 <GNUtoo|laptop> wow nice
Jul 29 17:15:09 <morphis> but then it works
Jul 29 17:15:26 <GNUtoo|laptop> ok 
Jul 29 17:16:10 <GNUtoo|laptop> I'll go bye
Jul 29 17:16:13 <GNUtoo|laptop> bbl
Jul 29 17:16:15 <GNUtoo|laptop> maybe
Jul 29 17:16:16 <morphis> bye
Jul 29 17:16:20 <GNUtoo|laptop> bye
Jul 29 17:17:29 <CIA-69> SHR: 03GNUtoo 07meta-smartphone * r5cece2e655b3 10/meta-openmoko/ (2 files in 2 dirs): meta-openmoko: make xv possible in the gta04 kernel.
Jul 29 17:17:31 <GNUtoo|laptop> now that commit is pushed I'll go
Jul 29 17:36:01 <CIA-69> freesmartphone.org: 03morphis 07cornucopia * r1976427616e0 10/fsodeviced/ (6 files in 3 dirs): fsodeviced: drop router_qdsp5 plugin; it's not used anymore
Jul 29 17:37:51 <CIA-69> freesmartphone.org: 03morphis 070.12 * rdf2d30523018 10cornucopia/fsodeviced/ (6 files in 3 dirs): fsodeviced: drop router_qdsp5 plugin; it's not used anymore
Jul 29 17:53:09 <CIA-69> SHR: 03shr-devel 07buildhistory * re0bd3654d87c 10/images/nokia900/eglibc/ (22 files in 2 dirs): images: Build 201207291657 of shr 20120729 for machine nokia900 on opmbuild
Jul 29 17:53:23 <CIA-69> SHR: 03shr-devel 07buildhistory * rdeba92673ac9 10/packages/ (264 files in 264 dirs): packages: Build 201207291657 of shr 20120729 for machine nokia900 on opmbuild
Jul 29 19:19:37 <CIA-69> SHR: 03shr-devel 07buildhistory * rcb83162f1317 10/packages/om_gta04-oe-linux-gnueabi/xserver-xf86-config/ (7 files in 7 dirs): packages: Build 201207292046 of shr 20120729 for machine om-gta04 on opmbuild
Jul 29 19:19:48 <CIA-69> SHR: 03shr-devel 07buildhistory * r69c06ea41ab1 10/images/om_gta04/eglibc/ (22 files in 2 dirs): images: Build 201207292046 of shr 20120729 for machine om-gta04 on opmbuild
Jul 29 20:37:49 <CIA-69> SHR: 03shr-devel 07buildhistory * r170b7011f6c2 10/packages/crespo-oe-linux-gnueabi/xserver-xf86-config/ (7 files in 7 dirs): packages: Build 201207292204 of shr 20120729 for machine crespo on opmbuild
Jul 29 20:38:00 <CIA-69> SHR: 03shr-devel 07buildhistory * r9634c3e0b6c0 10/images/crespo/eglibc/ (22 files in 2 dirs): images: Build 201207292204 of shr 20120729 for machine crespo on opmbuild
**** ENDING LOGGING AT Mon Jul 30 02:59:58 2012