**** BEGIN LOGGING AT Tue Nov 30 02:59:57 2010 Nov 30 08:51:57 damn, ofono doesn't work with my huawei e1552, again Nov 30 09:08:38 ofono is not working good to my huawei as well ~ Nov 30 15:16:15 denkenz: Do you happen to know anything about the geoclue ofono provider code ? Nov 30 15:16:57 denkenz: Is it actually working ? Nov 30 15:17:49 first I heard of it Nov 30 15:18:45 same here. I'm looking into passing the regulatory information to our wifi chips from the GSM MCC, and it seems geoclue is doing half of it already. Nov 30 15:19:00 at least that's what the code seems to be doing. Nov 30 16:03:15 sameo_: ofono and udev should work with most Nokia phones with "PC Suite" or "Ovi Suite" mode Nov 30 16:04:07 holtmann did not like my udev rule patch for detecting the Nokia phones with just vendor id but it should work Nov 30 16:04:35 ATTRS{idVendor}=="0421", ATTRS{idProduct}=="060e", ENV{OFONO_DRIVER}="nokia" Nov 30 16:04:38 oops. Nov 30 16:04:58 pessi: ok, good. Would you mind giving http://bugs.meego.com/show_bug.cgi?id=2708 a look then ? Nov 30 16:05:12 ATTRS{idVendor}=="0421", ENV{OFONO_DRIVER}="isigen", ENV{OFONO_ISI_ADDRESS}="16" Nov 30 16:09:27 sameo_: commented, you can propably say it is alreadyfixed? Nov 30 16:10:05 pessi: thx Nov 30 16:16:53 pessi: apparently it still doesnt work with 1.1 Nov 30 18:19:57 denkenz: i implemented radio-settings for huawei... so i had to touch drivers/huawei/ and plugins/huawei.c Nov 30 18:20:04 denkenz: do i commit them together? Nov 30 18:20:26 no, one patch per directory Nov 30 18:21:12 ok... and about spliting patches, a word about this in doc would be good... Nov 30 18:21:19 don't know where to put Nov 30 18:21:24 maybe in HACKING ? Nov 30 18:21:40 i can write something Nov 30 18:24:46 yeah, HACKING is fine Nov 30 19:04:18 sameo_: 1.1 has ofono 0.26? Nov 30 19:10:59 pessi: as per the repo,1.1 has ofono 0.26-2 Nov 30 19:13:33 pessi: I'm not sure about it. Most likely not 0.31 though. Nov 30 19:35:25 holtmann: what do you think about combatibility of python scripts with python3? Nov 30 19:35:45 holtmann: i can make most of them compatible with both versions Nov 30 19:36:01 holtmann: is it worth the work? Nov 30 19:36:52 Sure. Why not. If it is easy. Nov 30 19:37:35 holtmann: there will be some scripts that will need some more thinking, particularly those that use raw_input() Nov 30 19:38:09 but most of the conversion is just a matter of converting print "aaa" to print("aaa"), which should work on python 2.6 too Nov 30 19:45:53 Sure. Then go ahead. Nov 30 20:49:40 denkenz: ping Nov 30 20:57:34 denkenz/holtmann: do you have a particular preference for where the description for a set of patches should go? In a separate email preceding the patch set or in the description field of the first patch in the series? Nov 30 20:59:36 darasd: a separate email first is better Nov 30 21:00:31 darasd: you can sue git format-patch --cover-letter to have a template for that e-mail Nov 30 21:00:51 ah great - thank you padovan Nov 30 21:06:39 darasd: you can also use git send-email --compose *.patch Nov 30 21:09:57 Jeevaka: I was used to use --compose until know about --cover-letter :) Nov 30 21:10:31 --cover-letter gives you a diff stat for free Nov 30 21:12:08 padovan: nice. I didn't know that. i'll start using the --cover-letter as well then **** ENDING LOGGING AT Wed Dec 01 02:59:57 2010