**** BEGIN LOGGING AT Wed Mar 07 02:59:58 2012
Mar 07 12:36:08 <CIA-19> SHR: 03GNUtoo 07meta-smartphone * r6a275b18e1e4 10/meta-samsung/recipes-kernel/linux/linux-samsung-crespo_git.bb: meta-samsung: linux-samsung-crespo: bump SRCREV
Mar 07 18:47:35 <nschle85> GNUtoo: hello :-)
Mar 07 18:48:48 <nschle85> GNUtoo: have you tried staging image 30 for N900 ? I cannot get it working after reboot it starts and xserver stays with white screen.
Mar 07 18:55:55 <GNUtoo> no
Mar 07 18:56:05 <GNUtoo> but I've built my own image *very recently*
Mar 07 18:56:08 <GNUtoo> so it's like post 32
Mar 07 18:56:48 <nschle85> i did not found 31 and 32 images for n900 have i overseen something ?
Mar 07 18:57:20 <GNUtoo> 32 has been built very recently
Mar 07 18:57:25 <GNUtoo> and is totally broken
Mar 07 18:57:35 <GNUtoo> libtiff issues
Mar 07 18:57:40 <GNUtoo> so basically the GUI may come up
Mar 07 18:57:48 <GNUtoo> but telephony will be broken
Mar 07 18:57:58 <GNUtoo> that means an SHR daemon
Mar 07 18:58:05 <GNUtoo> like libphone-ui or something like taht
Mar 07 18:58:53 <nschle85> ok, i installed the image with gtar package on n900 (not busybox) so i hope its not an installation issue, because i wont open/close the phone so often
Mar 07 19:01:41 <GNUtoo> ok
Mar 07 19:01:48 <GNUtoo> else wait for newer images
Mar 07 19:03:47 <nschle85> GNUtoo: since days i wanted to get ca-certificates fixed in meta-oe but nobody merges the available fixes... so i think shr is also broken
Mar 07 19:04:21 <nschle85> GNUtoo: i am writing in mailing lists, irc but nothing happens
Mar 07 19:04:44 <nschle85> GNUtoo: do you know what else i can do ?
Mar 07 19:05:29 <nschle85> GNUtoo: does oe has a bug tracker ?
Mar 07 19:05:46 <GNUtoo> which mailing list
Mar 07 19:05:49 <GNUtoo> else I can look
Mar 07 19:05:53 <GNUtoo> but JaMa is away
Mar 07 19:06:01 <GNUtoo> mrmoku said he would be back and he isn't
Mar 07 19:06:04 <nschle85> openebedded-devel and angstrom
Mar 07 19:06:11 <GNUtoo> the active devs are:
Mar 07 19:06:13 <GNUtoo> * me
Mar 07 19:06:17 <GNUtoo> * dos1 
Mar 07 19:06:26 <GNUtoo> * slyon
Mar 07 19:06:35 <GNUtoo> I meant current active devs
Mar 07 19:06:39 <nschle85> GNUtoo: JaMa already knows 
Mar 07 19:07:27 <nschle85> GNUtoo: even koen Koi told me send apach, i dit it but nothing happens
Mar 07 19:07:44 <nschle85> 'a patch'
Mar 07 19:09:25 <GNUtoo> did you send the patch?
Mar 07 19:15:49 <GNUtoo> ah I didn't see
Mar 07 19:15:55 <GNUtoo> how's your patch named?
Mar 07 19:18:48 <GNUtoo> hi morgner 
Mar 07 19:18:49 <GNUtoo> oops
Mar 07 19:18:50 <GNUtoo> sorry
Mar 07 19:18:54 <GNUtoo> hi morphis 
Mar 07 19:19:04 <GNUtoo> morphis, did you see my commits about the wifi?
Mar 07 19:19:41 <morphis> heyho
Mar 07 19:19:45 <morphis> GNUtoo: no
Mar 07 19:20:04 <GNUtoo> basically:
Mar 07 19:20:17 <morphis> GNUtoo: this one http://git.freesmartphone.org/?p=linux-2.6.git;a=commit;h=7ae1282f5b3b80bda87ef9aa1d8bf582875ffb67 ?
Mar 07 19:20:30 <GNUtoo> http://www.pastie.org/private/q1gv7imttasddilnkyxa
Mar 07 19:20:41 <GNUtoo> yes
Mar 07 19:20:45 <GNUtoo> it's a bit dirty
Mar 07 19:20:51 <GNUtoo> but the driver was dirty
Mar 07 19:21:01 <GNUtoo> and it would have needed a rework 
Mar 07 19:21:59 <GNUtoo> morphis, btw I sent you a mail telling that I had no voice during calls
Mar 07 19:22:05 <GNUtoo> I'll look if I have an answer
Mar 07 19:23:32 <morphis> no
Mar 07 19:23:35 <morphis> I just saw the mail
Mar 07 19:23:45 <morphis> you tested with 0x8000?
Mar 07 19:23:55 <GNUtoo> yes still no sound
Mar 07 19:24:02 <morphis> ok
Mar 07 19:24:05 <GNUtoo> and 0x8000 + revert -> still no sound
Mar 07 19:24:17 <morphis> but before that commit it worked?
Mar 07 19:24:23 <GNUtoo> yes long time ago
Mar 07 19:24:38 <morphis> ok, I will check
Mar 07 19:24:38 <GNUtoo> I did a phone call even before replicant got sound during phone calls
Mar 07 19:24:44 <GNUtoo> and it works in replicant
Mar 07 19:24:48 <GNUtoo> so if you need a trace
Mar 07 19:24:57 <GNUtoo> and replicant does produce verbose logs
Mar 07 19:25:12 <GNUtoo> including the hex of what's sent when volume change
Mar 07 19:25:22 <nschle85> GNUtoo: this is what i sent to angstrom: http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005756.html
Mar 07 19:25:39 <GNUtoo> but I don't know which is which between volume + path, I must look
Mar 07 19:26:14 <GNUtoo> nschle85, you sent to the wrong ml
Mar 07 19:26:44 <GNUtoo> and the commit message seem badly formated
Mar 07 19:26:46 <nschle85> GNUtoo: and this is waht in oe exists
Mar 07 19:26:48 <nschle85> http://thread.gmane.org/gmane.comp.handhelds.openembedded
Mar 07 19:27:42 <GNUtoo> http://article.gmane.org/gmane.comp.handhelds.openembedded/50963/match=ca+certificates
Mar 07 19:27:48 <GNUtoo> there is that one:
Mar 07 19:27:54 <GNUtoo> http://thread.gmane.org/gmane.comp.handhelds.openembedded/50963
Mar 07 19:28:52 <GNUtoo> and it didn't get in because it had style issues with the recipe
Mar 07 19:28:59 <GNUtoo> maybe you could fix the style issues
Mar 07 19:29:16 <GNUtoo> but first I didn't understand your problem
Mar 07 19:29:24 <GNUtoo> ssl doesn't work because of that?
Mar 07 19:29:32 <morphis> GNUtoo: I will try to fix that
Mar 07 19:30:24 <GNUtoo> morphis, ok thanks a lot
Mar 07 19:30:36 <GNUtoo> maybe I will switch from replicant to SHR when that works
Mar 07 19:30:43 <nschle85> GNUtoo: the build is broken, thats the problem, the certificates are gone on server
Mar 07 19:30:43 <GNUtoo> I also need to fix some segfaults
Mar 07 19:30:49 <GNUtoo> because everything segfault currently
Mar 07 19:30:51 <GNUtoo> firefox
Mar 07 19:30:52 <GNUtoo> iliwi
Mar 07 19:30:55 <GNUtoo> midori
Mar 07 19:31:07 <GNUtoo> eve(not at first start tough)
Mar 07 19:31:13 <GNUtoo> ffalarms
Mar 07 19:31:15 <GNUtoo> etc...
Mar 07 19:32:21 <GNUtoo> nschle85, you could ask for someone to mirror them
Mar 07 19:32:21 <GNUtoo> in #oe
Mar 07 19:32:21 <GNUtoo> that's the fastest way
Mar 07 19:32:22 <nschle85> GNUtoo: hmm i thought first repair the build then the style 
Mar 07 19:32:52 <GNUtoo> morphis, btw where's the key to resume?
Mar 07 19:32:57 <GNUtoo> in what config?
Mar 07 19:34:06 <morphis> which key for resume?
Mar 07 19:34:21 <GNUtoo> how do you resume for crespo?
Mar 07 19:34:26 <GNUtoo> using the power key right?
Mar 07 19:34:43 <GNUtoo> ahhh
Mar 07 19:34:44 <GNUtoo> [fsodevice.herring_quirks]
Mar 07 19:34:48 <GNUtoo> but it doesn't work anymore
Mar 07 19:34:51 <GNUtoo> with 3.0
Mar 07 19:35:12 <GNUtoo> and still it's 2 and 116
Mar 07 19:35:25 <GNUtoo> # evtest event2 
Mar 07 19:35:32 <GNUtoo> Event: time 2946.419386, type 1 (Key), code 116 (Power), value 1
Mar 07 19:36:10 <GNUtoo> maybe something broke it
Mar 07 19:36:20 <GNUtoo> but maybe telephony first
Mar 07 19:44:53 <morphis> GNUtoo: look at fsodeviced.conf
Mar 07 19:45:01 <GNUtoo> yes I looked there
Mar 07 19:45:07 <GNUtoo> <GNUtoo> [fsodevice.herring_quirks]
Mar 07 19:45:32 <GNUtoo> and at the end I concluded that resume with the power key was broken
Mar 07 19:45:38 <GNUtoo> for an unknown reason
Mar 07 19:45:46 <GNUtoo> and that the config was right
Mar 07 19:46:12 <morphis> can you please open a ticket for this in FSO trac?
Mar 07 19:46:14 <GNUtoo> also 3) did you think about the GPS of the gta04?
Mar 07 19:46:19 <GNUtoo> ok
Mar 07 19:46:20 <morphis> otherwise I will lost the overview for all those bugs
Mar 07 19:47:39 <morphis> GNUtoo: I opened one for the not working sound during calls here: http://trac.freesmartphone.org/ticket/665
Mar 07 19:49:31 <GNUtoo> Internal Server Error
Mar 07 19:49:34 <GNUtoo> I'll retry
Mar 07 19:49:55 <GNUtoo> it seem that I can't view the old bugs
Mar 07 19:50:02 <GNUtoo> to be sure mine has not already been reported
Mar 07 19:50:14 <GNUtoo> http://trac.freesmartphone.org/report/1
Mar 07 19:53:43 <morphis> should work now
Mar 07 19:55:35 <GNUtoo> ok
Mar 07 20:03:12 <morphis> GNUtoo: you added the bug?
Mar 07 20:03:17 <GNUtoo> yes both
Mar 07 20:04:29 <GNUtoo> http://trac.freesmartphone.org/ticket/667
Mar 07 20:04:33 <GNUtoo> http://trac.freesmartphone.org/ticket/666
Mar 07 20:05:01 <GNUtoo> should I integrate gpsd for the gta04?
Mar 07 20:05:07 <GNUtoo> like everything but the sysfs?
Mar 07 20:08:22 <morphis> does gpsd help us with our problem?
Mar 07 20:09:35 <GNUtoo> yes
Mar 07 20:10:00 <GNUtoo> if everything is ready gpsd side you just have to think about how to read from it and write the sysfs
Mar 07 20:10:19 <GNUtoo> or should I go for quirk and implement a quirk?
Mar 07 20:10:46 <GNUtoo> because what you have to do is:
Mar 07 20:10:55 <GNUtoo> 1) read from gpsd to see if it's on or off
Mar 07 20:11:06 <GNUtoo> 2) write or not to the sysfs
Mar 07 20:15:58 <morphis> ok
Mar 07 20:16:06 <morphis> where should this be implemented on FSO side?
Mar 07 20:16:09 <morphis> the reading from the node?
Mar 07 20:16:29 <GNUtoo> what do you mean by the node?
Mar 07 20:16:33 <GNUtoo> gpsd?
Mar 07 20:16:38 <morphis> yes
Mar 07 20:16:40 <morphis> sorry
Mar 07 20:17:03 <GNUtoo> ahh I start to remember
Mar 07 20:17:08 <GNUtoo> to start GPS you need:
Mar 07 20:17:17 <GNUtoo> 1) to read the status from gpsd
Mar 07 20:17:22 <GNUtoo> 2) to write to sysfs
Mar 07 20:17:30 <GNUtoo> 3) to enable the rfkill plugin
Mar 07 20:17:38 <GNUtoo> I'll correct the bug
Mar 07 20:17:47 <GNUtoo> because rfkill is involved too
Mar 07 20:17:56 <GNUtoo> and originally I wanted to bloat rfkill plugin
Mar 07 20:18:05 <GNUtoo> or to copy rfkill plugin in a quirk
Mar 07 20:19:23 <morphis> baaah, that sounds not like a nice solution
Mar 07 20:19:35 <morphis> I don't like both
Mar 07 20:19:44 <morphis> bloating the rfkill plugin or copying it
Mar 07 20:19:53 <GNUtoo> I tought about oe-style stuff
Mar 07 20:19:59 <GNUtoo> do_configure_append()
Mar 07 20:20:07 <GNUtoo> do_configure_prepend()
Mar 07 20:20:10 <GNUtoo> to override in quirk
Mar 07 20:20:35 <morphis> ?
Mar 07 20:20:45 <morphis> in the plugin of fsodeviced?
Mar 07 20:20:54 <GNUtoo> no
Mar 07 20:21:02 <GNUtoo> basically you have rfkill plugin
Mar 07 20:21:13 <GNUtoo> and you provide hooks to overrides
Mar 07 20:21:21 <morphis> hm
Mar 07 20:21:29 <GNUtoo> like before and/or after that the rfkill plugin does his job
Mar 07 20:21:33 <GNUtoo> for instance:
Mar 07 20:21:40 <GNUtoo> override_me();
Mar 07 20:21:48 <GNUtoo> echo 1 > /sys/class/rfkill/status
Mar 07 20:21:49 <morphis> yes, thats something I already thought about
Mar 07 20:21:54 <GNUtoo> override_me()
Mar 07 20:21:58 <GNUtoo> ;
Mar 07 20:22:15 <morphis> but I don't really like it to couple the implementation of the rfkill plugin with the direct consequence for the system
Mar 07 20:22:23 <morphis> it should be something more like:
Mar 07 20:22:56 <morphis> fsodeviced activates the rfkill -> fsoeventsd catches the event that rfkill is activate and launches now according to the rule everything needed
Mar 07 20:23:41 <GNUtoo> is that efficent?
Mar 07 20:23:50 <GNUtoo> because that involves dbus
Mar 07 20:24:01 <GNUtoo> the override doesn't involve dbus, only vala
Mar 07 20:24:08 <GNUtoo> and it stay in the same plugin
Mar 07 20:24:15 <GNUtoo> no inter-plugin dependencies
Mar 07 20:24:27 <GNUtoo> s/same plugin/same daemon/
Mar 07 20:25:19 <morphis> is it such a lost of performance that dbus is involved?
Mar 07 20:25:30 <morphis> it's a cleaner solution in my eyes
Mar 07 20:25:43 <morphis> as currently we're adding more and more functionality to the rfkill plugin
Mar 07 20:26:41 <GNUtoo> ok
Mar 07 20:26:47 <GNUtoo> then if it's cleaner let's go for it
Mar 07 20:27:01 <GNUtoo> I don't care that much about the devil that is in the details
Mar 07 20:27:08 <GNUtoo> I just want something that does work
Mar 07 20:27:10 <morphis> GNUtoo: you can try if you can get everything working with oeventsd and catching the signal
Mar 07 20:27:14 <GNUtoo> and I need it soon enough
Mar 07 20:27:30 <morphis> GNUtoo: maybe you have to add another trigger
Mar 07 20:27:38 <GNUtoo> trigger?
Mar 07 20:27:53 <GNUtoo> where?
Mar 07 20:27:58 <GNUtoo> what do you mean exactly?
Mar 07 20:28:04 <morphis> you now oeventsd?
Mar 07 20:28:11 <GNUtoo> no
Mar 07 20:28:13 <GNUtoo> not at all
Mar 07 20:28:30 <morphis> ok
Mar 07 20:28:36 <morphis> in general you have a trigger
Mar 07 20:28:41 <morphis> like CallStatusTrigger
Mar 07 20:28:51 <morphis> which triggers when it received a call status update over dbus
Mar 07 20:28:55 <morphis> look here http://git.freesmartphone.org/?p=framework.git;a=blob;f=framework/subsystems/oeventsd/fso_triggers.py;h=5afd195eff22c0cbc49b17b067a6948356a9959b;hb=HEAD
Mar 07 20:29:06 <morphis> when a trigger triggers there are filters
Mar 07 20:29:17 <morphis> and if all filters are passed there are actions to be executed
Mar 07 20:29:38 <morphis> http://git.freesmartphone.org/?p=framework.git;a=blob;f=etc/freesmartphone/oevents/rules.yaml;h=695f5ff7a7c323a36fe13bbec3e7c1356d7e5122;hb=HEAD
Mar 07 20:29:55 <GNUtoo> hmmm
Mar 07 20:30:00 <GNUtoo> seem like oeventsd
Mar 07 20:30:15 <morphis> it's oeventsd
Mar 07 20:30:23 <GNUtoo> ok
Mar 07 20:30:32 <GNUtoo> the yaml thing is different then
Mar 07 20:30:36 <GNUtoo> sorry for the confusion
Mar 07 20:30:44 <GNUtoo> rules.yaml
Mar 07 20:31:01 <GNUtoo> ah right you pasted rules.yaml too
Mar 07 20:31:21 <GNUtoo> ahh it's the old python thing
Mar 07 20:31:24 <GNUtoo> it's that one
Mar 07 20:31:25 <morphis> you just need to implement a trigger for the powercontrol
Mar 07 20:31:25 <GNUtoo> sorry
Mar 07 20:31:28 <GNUtoo> ok
Mar 07 20:31:49 <GNUtoo> when you told me about it I was talking in #oe at the same time and tough it was a new fso deamon
Mar 07 20:31:50 <GNUtoo> sorry
Mar 07 20:31:53 <morphis> listen for this signal: http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.PowerControl.html;hb=HEAD#Power
Mar 07 20:31:59 <morphis> ah ok
Mar 07 20:32:08 <GNUtoo> so there is no vala replacement yet for that
Mar 07 20:32:15 <morphis> no I started working on fsoeventsd but it is far away from being functional
Mar 07 20:32:21 <morphis> not really
Mar 07 20:32:22 <GNUtoo> ok
Mar 07 20:33:27 <morphis> and can you open a bug for the DTMF bug too?
Mar 07 20:33:35 <GNUtoo> ok I'll do
Mar 07 20:34:05 <morphis> great
Mar 07 20:34:14 <morphis> so I have to leave
Mar 07 20:34:15 <morphis> gn8
Mar 07 21:29:56 <GNUtoo> dos1, hi
Mar 07 21:30:15 <dos1> hello
Mar 07 21:30:19 <dos1> i have some bad luck
Mar 07 21:30:24 <GNUtoo> ah?
Mar 07 21:30:51 <dos1> every time my problem with disabled backlight happends
Mar 07 21:31:03 <GNUtoo> disabled backlight?
Mar 07 21:31:09 <dos1> i have usb0 interface turned down
Mar 07 21:31:12 <dos1> so i can't debug it ;x
Mar 07 21:31:16 <GNUtoo> ok
Mar 07 21:31:24 <GNUtoo> do you remember frameworkd?
Mar 07 21:31:41 <dos1> yes, sometimes i can see under light that there is some content on screen
Mar 07 21:31:45 <dos1> and it changes when clicking AUX
Mar 07 21:32:03 <GNUtoo> ok
Mar 07 21:32:10 <dos1> so it works, but backlight is for some reason off and not turned on whatever i do
Mar 07 21:32:20 <GNUtoo> hmmm strange
Mar 07 21:32:24 <dos1> but it happens when:
Mar 07 21:32:27 <dos1> a) i can't debug it
Mar 07 21:32:28 <dos1> or
Mar 07 21:32:31 <GNUtoo> can you fill a bug?
Mar 07 21:32:36 <dos1> b) when i have usb interface disabled
Mar 07 21:32:38 <GNUtoo> because I don't understand the problem
Mar 07 21:32:39 <dos1> so i can't debug it
Mar 07 21:32:40 <dos1> :D
Mar 07 21:32:52 <dos1> and what about frameworkd?
Mar 07 21:32:55 <GNUtoo> http://www.pastie.org/private/qkmt2dssqw7oh1zblkm8g
Mar 07 21:33:09 <GNUtoo> I added that to fso_triggers.py
Mar 07 21:33:13 <GNUtoo> in oeventsd
Mar 07 21:33:27 <GNUtoo> and it prints nothing
Mar 07 21:33:36 <GNUtoo> I don't see INFO test
Mar 07 21:33:38 <GNUtoo> in the logs
Mar 07 21:34:20 <dos1> GNUtoo: do you have this trigger used in your rules.yaml?
Mar 07 21:34:26 <GNUtoo> no
Mar 07 21:34:31 <dos1> so that's why
Mar 07 21:34:32 <GNUtoo> I don't
Mar 07 21:34:33 <GNUtoo> ok
Mar 07 21:34:39 <GNUtoo> I'll add it then
Mar 07 21:34:42 <dos1> instance of this class is never created
Mar 07 21:34:42 <GNUtoo> thanks a lot
Mar 07 21:46:14 <GNUtoo> I guess the cond ? "true" : "false" don't work in python
Mar 07 21:47:15 <GNUtoo> ah ok there is an alternative syntax
Mar 07 21:47:19 <GNUtoo> found it on wikipedia
Mar 07 21:47:56 <GNUtoo> also could you describe your backlight problem
Mar 07 21:48:01 <GNUtoo> I don't remember what it was
Mar 07 21:48:41 <dos1> dunno
Mar 07 21:49:03 <dos1> just sometimes i tap screen
Mar 07 21:49:10 <dos1> and nothing happens
Mar 07 21:49:14 <dos1> so i think "oh, it suspended"
Mar 07 21:49:20 <dos1> i click on power button
Mar 07 21:49:25 <dos1> and nothing happens
Mar 07 21:49:55 <dos1> but when i look under a light
Mar 07 21:50:06 <dos1> then i see that there is something displayed on screen
Mar 07 21:50:14 <dos1> and when i click AUX, i can see that it changes
Mar 07 21:50:24 <dos1> but it's too dark to see anything more than "something"
Mar 07 21:50:46 <lindi-> dos1: what's backlight brightness set to?
Mar 07 21:51:11 <dos1> the thing is i've always had bad luck when it happened
Mar 07 21:51:24 <dos1> so eihter there was no pc i could connect FR to and check
Mar 07 21:51:32 <dos1> or i had usb interface disabled
Mar 07 21:51:38 <dos1> so i couldn't check it
Mar 07 21:52:04 <lindi-> there's wifi, bluetooth, gprs..
Mar 07 21:52:33 <dos1> yeah, but i'd have to turn it on
Mar 07 21:52:40 <dos1> and it's very hard without backlight :D
Mar 07 21:52:52 <dos1> it happens very rarely
Mar 07 21:53:22 <dos1> and i don't know how to reproduce it
Mar 07 21:55:58 <lindi-> dos1: gsm should be on normally?
Mar 07 21:57:19 <dos1> lindi-: yes, but how would you enable GPRS connection and check IP with permanently disabled backlight and no USB/WiFi/bluetooth connection active?
Mar 07 21:57:42 <lindi-> dos1: I just call my phone from a specific number to initiate gprs
Mar 07 21:57:54 <lindi-> dos1: it'll then send me its ip address so that I can connect
Mar 07 21:58:10 <dos1> so i'd have to setup such script
Mar 07 21:58:15 <lindi-> yep
Mar 07 21:58:16 <dos1> as i don't have it now ;)
Mar 07 21:58:29 <dos1> so still, that's for future
Mar 07 21:58:30 <lindi-> what if you lose your phone? how do you find it?
Mar 07 21:58:44 <dos1> as i couldn't do that without such script
Mar 07 22:10:57 <GNUtoo> dos1, should I push or do you want to review the resource state trigger?
Mar 07 22:11:38 <GNUtoo> ihttp://www.pastie.org/private/cvbqudqlrxh15aozvcs5uq
Mar 07 22:13:17 <dos1> GNUtoo: if it works then push ;)
Mar 07 22:13:23 <GNUtoo> ok thanks
Mar 07 22:13:29 <GNUtoo> it works
Mar 07 22:13:33 <GNUtoo> no tracebacks
Mar 07 22:13:45 <dos1> maybe remove logger.info("test"); line
Mar 07 22:13:50 <GNUtoo> ah oops
Mar 07 22:13:53 <dos1> ;)
Mar 07 22:16:25 <CIA-19> freesmartphone.org: 03GNUtoo 07framework * r2a88fe0ef929 10/framework/subsystems/oeventsd/fso_triggers.py: 
Mar 07 22:16:25 <CIA-19> freesmartphone.org: oeventsd: add fso Resource State trigger
Mar 07 22:16:25 <CIA-19> freesmartphone.org: Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Mar 07 22:18:02 <GNUtoo> ok now the gpsd config
Mar 07 22:18:10 <GNUtoo> and at the end the plugin as morphis said
Mar 07 22:37:41 <GNUtoo> does someone have an idea on how to make PREFERRED_PROVIDER_gpsd machine specific?
Mar 07 22:37:58 <GNUtoo> ah maybe that's not used
Mar 07 22:38:38 <GNUtoo> RDEPENDS_${PN}-fso = "[...] fso-gpsd [...]"
Mar 08 00:08:30 <CIA-19> SHR: 03Martin.Jansa 07shr-chroot * r5dd9fbe4fd3f 10/ (2508 files in 198 dirs): system upgrade
Mar 08 00:10:13 <CIA-19> SHR: 03Martin.Jansa 07shr-chroot * r0e1c9d9cdb21 10/ (33 files in 9 dirs): bitbake upgrade
Mar 08 01:30:05 <CIA-19> SHR: 03shr-devel 07buildhistory * r212c876008cf 10/images/nokia900/eglibc/ (14 files in 2 dirs): Build 201203072344 of shr 20120307 for machine nokia900 on opmbuild
**** ENDING LOGGING AT Thu Mar 08 02:59:58 2012