**** BEGIN LOGGING AT Sat Jan 09 02:59:57 2010
Jan 09 04:04:29 <denkenz> tmzt: what should be in the GUI application?  You can have non-X oFono clients just fine
Jan 09 04:05:20 <tmzt> audio routing
Jan 09 04:05:36 <tmzt> it was suggested that it's gui's responsibiliity
Jan 09 04:05:52 <tmzt> I need calls with sound to work from non-X
Jan 09 04:08:09 <denkenz> the two most common ways audio is handled is
Jan 09 04:08:15 <denkenz> a) It is done in hardware
Jan 09 04:08:21 <denkenz> b) It is done in PulseAudio
Jan 09 04:08:30 <denkenz> Neither preclude the use of non-X clients
Jan 09 04:13:44 <tmzt> pulse supports routing with asoc, or worst case, an open .so library we are writing
Jan 09 04:13:49 <tmzt> ?
Jan 09 04:14:09 <tmzt> okay, but what sends an event to pulse when making a voice call
Jan 09 04:14:18 <tmzt> that's the question
Jan 09 04:15:26 <denkenz> that is completely up to you as a system integrator
Jan 09 04:15:55 <denkenz> You can have pulse driver listen to oFono signals or have oFono voicecall atom driver tell pulse something
Jan 09 04:16:52 <denkenz> If you're designing for something like the ARM devices (e.g. Freerunner) you flip some bits using ioctl
Jan 09 04:18:11 <tmzt> I would prefer a standard way
Jan 09 04:18:33 <tmzt> I'm used to how linux kernel does things, there's api and you write to it
Jan 09 04:20:50 <denkenz> There's nothing standard about audio on GSM modems
Jan 09 04:21:00 <denkenz> Maybe in a few years
Jan 09 04:28:01 <tmzt> right, but what's gained from writing this more than once?
Jan 09 10:26:41 <xorAxAx> hi, is it possible to implement a netmonitor using ofono?
Jan 09 10:26:44 <xorAxAx> and isimodem
Jan 09 20:21:04 <xorAxAx> hi, is it possible to implement a netmonitor using ofono via isimodem?
**** ENDING LOGGING AT Sun Jan 10 02:59:56 2010