**** BEGIN LOGGING AT Wed Sep 08 02:59:59 2010 Sep 08 07:42:45 I'm still trying to get my shine new f3706gw (Mini PCIe card) running. Do I need to attache the antenna? I used to work with 802.11 hardware, where an attana isn't really needed for local testing. But I can imagine that an atenna is required with those 3g cards. Any ideas? Sep 08 08:18:53 found a pigtail and an atenna. now there is a new problem. the modem disapears and I see in the kernel logs: ehci_hcd 0000:00:1a.7: dma_pool_free buffer-2048, ffff880037826200/37826200 (bad dma) Sep 08 12:37:30 the problem I see might be related to modemswitch https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch-data/+bug/451787 Sep 08 12:37:44 at least it looks like something is removing the modem Sep 08 12:37:59 are there any known issues with udev and mbm modems? Sep 08 12:41:57 the good knew is that I see that the NetworkRegistration status changes from 'unknown' to 'searching' but then there happends this dma_pool_free thing Sep 08 15:43:23 interesting. after removing the external atenna and just having the pigtail added to the card, it now works. of course only with a vodafon sim but it works Sep 08 15:44:08 at least I see a NetworkRegristration status=registered Sep 08 15:44:30 activate-context still fails Sep 08 15:46:13 I guess the firmware crashed due to too good signal :) Sep 08 18:35:26 denkenz: We forgot to fix the API for ModemAdded, ModemRemoved and GetModems? Sep 08 18:35:32 This is still racy. Sep 08 19:27:59 holtmann: We did Sep 08 19:30:18 We didn't. Sep 08 19:30:47 How did we forget about this one? Sep 08 19:31:57 denkenz: We should be doing GetModems() and have signals for ModemAdded and ModemRemoved. Sep 08 19:32:21 I meant we did forget Sep 08 19:32:30 Okay. Sep 08 19:32:45 So do you have time to fix this quickly. I don't wanna break more APIs later. Sep 08 19:33:01 quickly as in by when? Sep 08 19:33:14 Ten minutes ago when I discovered it. Sep 08 19:33:37 I am pretty sure we talked about it, but must have slipped our mind when writing it down. Sep 08 19:33:55 I don't recall actually discussing modem interface at all Sep 08 19:34:15 I am getting old then :( Sep 08 19:34:20 So I think we simply forgot ;) Sep 08 19:34:26 Possible as well. Sep 08 19:34:51 Can you have a quick look and check how long it would take. I update the API docs in the meantime. Sep 08 19:35:47 It won't take long, the problem is I'm in the middle of refactoring sim cache code Sep 08 19:36:01 Oops. Sep 08 19:36:10 When do you want this? Sep 08 19:36:44 I want it quickly. Samuel is pushing Pekka's patches for the API change. And I am looking through the online support patches. Sep 08 19:36:56 By tomorrow I want this back in sync. Sep 08 19:37:29 don't we need 0.28 then? Sep 08 19:37:38 Yes. Sep 08 19:37:43 As quickly as possible. Sep 08 19:38:10 See I wanted sim cache in 0.28 since it potentially breaks serialization Sep 08 19:38:24 give me until end of day tomorrow Sep 08 19:38:28 Maybe sooner Sep 08 19:38:32 Sure. Sep 08 19:38:59 I push the doc change now since I am finishing them. Sep 08 19:39:27 nod Sep 08 19:43:54 denkenz: Done. Sep 08 21:36:19 denkenz: I happened to pull tip and see lots of API change showing up in 0.27+ Sep 08 21:36:44 Am I correct in my understanding that 1.1 will still be 0.26 though? Sep 08 21:37:24 IOW, I don't need to plan for major API breakage before code freeze by end of sept, right ?!?! Sep 08 21:37:25 yep Sep 08 21:37:35 * sabotage sighs in relief Sep 08 21:37:58 even connman is broken by .27 Sep 08 21:38:14 planned rough patch as holtmann puts it Sep 08 21:38:21 BTW, I can't manage to keep up on all the ML's, so I only seem to hear about these when I pull from git, which is not regular Sep 08 21:38:53 I'm not intentionally ignoring ya'll in other words Sep 08 21:39:19 no prob Sep 08 21:43:13 hmm, my attempts at searching ML seem to fail at finding any email announcements or RFC's on the VoiceCallManager API changes... Sep 08 21:43:26 have a msgid handy or was there no email? Sep 08 21:47:27 sabotage: Actually we never discussed it on the ML Sep 08 21:47:52 I actually wanted to write an announce email about it, but forgot Sep 08 21:48:06 In the future we will try to list any major pitfalls whenever releasing a new version Sep 08 21:48:17 nod Sep 08 21:49:01 so other than git diff, is there any summary of the API changes between 0.26 and 0.27 and those planned for 0.28? Sep 08 21:53:25 See ChangeLog Sep 08 21:54:11 sabotage: We're not quite good with planned changes, sort of depends on what lands in git Sep 08 21:55:04 * sabotage noticed ;) Sep 08 21:55:58 denkenz: backport plans for 1.1 (ofono 0.26)? Sep 08 21:56:36 We have no stable tree and no branches Sep 08 21:56:38 IOW, since 1.1 is in feature freeze, whats the plan/process for fixes in 0.27+ getting into meego 1.1 Sep 08 21:56:47 heh Sep 08 21:56:56 So for now we rely on QA to apply any critical fixes Sep 08 21:57:15 * sabotage not asking... but channeling someone nearby :P Sep 08 21:57:38 We get that a lot, but until EoY you won't see a stable tree Sep 08 21:57:51 Simply too many things to do Sep 08 21:58:17 nod Sep 08 23:40:13 denkenz: Most of the online mode patches are now upstream. Some of them need more work and testing. Sep 08 23:43:43 pessi: I hope you have Huawei and MBM hardware to fix the issues with these. Sep 09 02:25:58 holtmann: any comments for btio.[ch] patches? **** ENDING LOGGING AT Thu Sep 09 02:59:57 2010