**** BEGIN LOGGING AT Mon Sep 22 02:59:57 2008 Sep 22 03:27:49 mwester: monday is cold and wet here :-( Sep 22 03:28:23 ? Sep 22 03:28:31 must be an adelaide thing Sep 22 03:28:32 nice here Sep 22 03:28:33 btw Sep 22 03:28:40 anyone ever tried using at on oe? Sep 22 03:28:45 its nicely broken Sep 22 03:28:55 and doesnt wake things from sleep by setting an rtc wake time Sep 22 03:29:02 in fact - it doesnt even get that far Sep 22 03:29:08 but doenst have code to do it anyway Sep 22 03:31:03 Yep, there should be a bug (now closed, IIRC) on that. Sep 22 03:31:15 Apparently it's not supposed to work. (IIRC) Sep 22 03:31:34 rwhitby: But it's getting warmer for you folks every day now... Sep 22 03:32:07 mwester: I'm camping this weekend, so I hope it's warmer then Sep 22 03:32:29 :) Cool, hope you have fun on the trip! Sep 22 03:33:31 it's actually a training course on how to take scouts camping. you have to go camping in course groups to pass the course :-) Sep 22 03:35:00 That could be fun -- as long as they don't spend most of the time doing classroom type stuff on legal liabilities, policies, procedures, etc. (That's probably what they do here) Sep 22 03:35:40 no, that was a different course, held in a residential setting Sep 22 03:36:13 mwester: its not meant to work" wtf? Sep 22 03:36:29 at not meant to? Sep 22 03:36:35 thats.. bizarre? Sep 22 03:36:42 so what is the alternative for doign things like Sep 22 03:36:58 ":please wake up he system from sleep and sound an alarm at time x"? Sep 22 03:37:04 dotn tell me i have to go write it Sep 22 03:37:06 raster: I might be wrong. But there was something quite bizarre like that, and it sticks in my mind that it was the "at" command. Sep 22 03:37:23 * raster prepares to look up the /dev/rtc ioctl magic for that baby Sep 22 03:37:37 well at is quite broken in oe (fso) Sep 22 03:37:49 no compile (as it finds no mta to use on compile this breaks) Sep 22 03:37:51 fixed that Sep 22 03:37:53 raster: You'll probably not only have to write it, but debug it as well. There are also reports that wakeup alarms from the RTC are unreliable. Sep 22 03:38:04 then runtime - atrm is broken ":permission denined" to unlink jobs Sep 22 03:38:12 whihc is bizarre.. as ti runs as root Sep 22 03:38:20 and atd just seems to exit on its own Sep 22 03:38:23 and not keep running Sep 22 03:38:34 bugger Sep 22 03:38:38 fugger Sep 22 03:38:39 ok Sep 22 03:38:50 we do need a system service that lets us wake up using an rtc Sep 22 03:38:57 especially fore alarm clocks for example Sep 22 03:39:06 iun fact anything that may want to poll while suspended needs it too Sep 22 03:39:20 eg every 30 secs wake up and check wifi ap's Sep 22 03:39:31 at only has 1min granularity Sep 22 03:39:38 whihc isnt great for sub-1min wakeups Sep 22 03:39:39 Yes. We also need a kernel service that does the same, to check on things (like the battery) periodically, and then go back to sleep -- without the cost in battery current of bringing up the display, audio, and all that. Sep 22 03:40:27 FR has a low-batt IRQ, but not the neo, and as you observe, we need it for other things too. Sep 22 03:40:27 technically that can be done without the kernel Sep 22 03:40:33 if device stuff was done in userspace Sep 22 03:40:38 ie wakeup didnt bring display on Sep 22 03:40:40 etc. Sep 22 03:40:49 wakupe just turned cpu, ram and disk on Sep 22 03:41:01 it then is userspace's job to do the rest Sep 22 03:41:30 a "wake up every 10 mines to check battery level" from userspace i think is ok Sep 22 03:41:40 as long as the kernel doesnt go bringin everythign up Sep 22 03:41:45 right now for backlight its ok Sep 22 03:41:48 hats the worst offender Sep 22 03:41:54 if it was off on suspend Sep 22 03:41:56 its off on resume Sep 22 03:42:09 that way u can wake up without being noticed Sep 22 03:42:13 quickyl poll/check your stuff Sep 22 03:42:23 instnantly go "ok boys = job done. sleep!" Sep 22 03:42:32 though i'd much rather vote for zero-clock... Sep 22 03:42:41 and never suspend Sep 22 03:43:19 The audio still clicks on suspend/resume, though -- so the backlight is not sufficient, really. Sep 22 03:44:02 true Sep 22 03:44:17 * mwester imagines a meeting with an executive -- there is silence in the room as the speaker takes the podium, except for an annoying "click!" from mwester's pocket... every 30 seconds... Sep 22 03:44:21 i'd be happy if we had to bring audio up in userspace Sep 22 03:44:33 It would crash the kernel less. Sep 22 03:45:13 if we move mroe of this to userspace- kernel work is simpler Sep 22 03:45:16 more reliable Sep 22 03:45:27 it takes less work to get things runnign on a new system/soc Sep 22 03:45:42 if we do zero-clock Sep 22 03:46:00 then its onyl a matter of how many devices we can then reliably bring up/down at will (from userspace) Sep 22 03:46:07 I don't know what Andy is working on for the new version of the kernel; but I thought he was writing something that would manage the suspend/resume sequence more closely. Sep 22 03:46:09 and u can knockt them over one by one Sep 22 03:46:25 so as u get more of them to turn off/go int low power mode the better the battery life Sep 22 03:46:37 instead of having to manage to get them ALL to suspend/resume reliably all at once Sep 22 03:46:58 so as such lets say we have nothing Sep 22 03:47:05 we save some power by zero-clocking cpu/ram Sep 22 03:47:14 but everything else remains 100% fully powered up Sep 22 03:47:23 And yes, a zero-clock is ideal -- but has always been more expensive in terms of hardware. Which gets to another topic near and dear to my heart, which is that hardware people are d*** good at excel spreadsheets with BOMs and costs, and software people can't seem to convey the cost of sofware to financial people. Sep 22 03:47:37 then one thing at a time (backlignt, then glamo, then gsm then audio etc.) we manage to bring up/down reliably Sep 22 03:47:46 and so add it into the userspace powermanagement Sep 22 03:49:31 Along with a SoC that supports zero-clock, it would be nice if the drivers could change other things as well -- e.g. do we really need 640x480 resolution all the time -- do we save power if the normal phone display (dialer, status page) runs at a lower resolution? Sep 22 03:50:44 I think theres so much that can yet be done, but we cannot do it if we have to let the existing "almost random" suspend/resume logic remain in charge. JMO. :) Sep 22 03:50:57 mwester: then you loose flesh tones on the today screen wallpaper ;-) Sep 22 03:51:27 hmm Sep 22 03:51:29 * mwester thinks about that for a few seconds... ;) Sep 22 03:51:31 changing res is possible Sep 22 03:51:41 but a lot more complicated as its not just the app affected Sep 22 03:51:43 its everyt app Sep 22 03:51:46 they whole screen Sep 22 03:51:52 u dont just lose fidelity Sep 22 03:52:01 layout details likely change Sep 22 03:52:18 but thats another matter Sep 22 03:52:28 entirely Sep 22 03:52:40 most userpsac esoftware just isnt good at all at dynamic resolution changes Sep 22 03:52:43 Hmm.. ok, so probably not a good tradeoff. But can we do anything to lower the clock speed to save power on the Glamo? Sep 22 03:53:01 on the glamo - no idea Sep 22 03:53:08 though likely any saving is not worht it Sep 22 03:53:22 i think the glamo is like <100mw Sep 22 03:53:26 like mroe the 50mw range Sep 22 03:53:31 socs is 200+ Sep 22 03:53:36 * mwester thinks of maybe a mono screen, or a sloppy screeen, or even a flickering screen, that would become the normal resolution upon first tap on the touchscreeen. Sep 22 03:53:38 better to focus on soc Sep 22 03:53:47 backlight is trivial and eats a lot of power Sep 22 03:54:05 "dminishing returns" Sep 22 03:54:08 :) Sep 22 03:54:18 i would worry about things that would apply to future cpus/soc's Sep 22 03:54:26 at least in principle Sep 22 03:56:35 I'm like a pit-crew mechanic; I worry about winning *this* race. Sep 22 03:56:53 hehehehe Sep 22 03:56:59 i worry about winning the wra Sep 22 03:57:02 not the battle :) Sep 22 03:57:14 but you need both types to win in the end Sep 22 03:58:03 That line has always bothered me, because it's something that only the general from the rear of the brigade can say -- the guy carrying the machine gun in the mud is VERY focused on winning the battle... Sep 22 04:15:35 i'm not sure there needs to be a difference Sep 22 04:15:43 some peolpe prefetr to focus on the here and now issues Sep 22 04:15:53 other on the logner term ones and not the here-and-now ones Sep 22 04:16:10 btw anyone here tried om/oe/angstorm on a treo650? Sep 22 04:16:23 * rwhitby is waiting to do so ... Sep 22 04:16:43 rwhitby: on yours? Sep 22 04:17:01 zedstar is sending me an old one of his, so i can use it to develop on. Sep 22 04:17:19 couple of weeks time probably Sep 22 04:18:11 looks like flash is not accesisble currently Sep 22 04:18:26 that disk-onchip thing Sep 22 04:18:35 i've seen them before Sep 22 04:18:38 * mwester checked eBay; still pretty pricey. Sep 22 04:18:50 mwester: theres one on ebay.au Sep 22 04:19:00 right now its going for $1 Sep 22 04:19:01 :) Sep 22 04:19:47 raster: you'd want to boot from SD card anyway due to space considerations Sep 22 04:20:00 rwhitby: i know Sep 22 04:20:12 and currently u have to boot via palmos with cocoboot anyway Sep 22 04:20:19 Hmm.. so is the internal flash then left alone (i.e. PalmOS)? Sep 22 04:20:19 so DoC flash acessibility is not too relevant Sep 22 04:20:20 so u'd need a working palmos Sep 22 04:20:30 mwester: yeah Sep 22 04:20:37 that makes it quite sane to hack with Sep 22 04:20:40 and use as a phone Sep 22 04:20:41 Ok. SD cards are cheap. Sep 22 04:20:46 just har-dreset to go back to palmos Sep 22 04:21:00 phone calls even work Sep 22 04:21:08 tho seems audio is a bit fucked (one-sided calls) Sep 22 04:21:26 i was more looking at it as somethnig to play with for phone ui stuff Sep 22 04:21:30 raster: going price on ebay.au seems to be around $200 for the times I've looked recently Sep 22 04:21:31 that has touchscreen AND a keypad Sep 22 04:21:44 rwhitby: yeah. is ee ones "for sale" for $170 Sep 22 04:21:48 (and up) Sep 22 04:22:05 rwhitby: i'll see how that auction goes Sep 22 04:22:58 hmm Sep 22 04:23:04 another one for $99 Sep 22 04:23:06 You can buy a new-in-box one from a reputable dealer (physical storefront) for $150 Sep 22 04:23:21 http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3476985&Sku=P175-1074 Sep 22 04:23:28 Not sure if they ship to au though Sep 22 04:24:26 hmm Sep 22 04:24:28 i choudl check Sep 22 04:25:02 I'm sure we could find a shipping agent ;-) in the US to buy it for you ... Sep 22 04:25:31 hehe Sep 22 04:26:30 "Received this item in record time. Only took 6 days for arrival to an APO box overseas." - one of the reviews Sep 22 04:31:05 http://cgi.ebay.com.au/NEW-PALM-TREO-650-UNLOCKED-BLUETOOTH-CAMERA-GSM-PHONE_W0QQitemZ170263709408QQihZ007QQcategoryZ1503QQssPageNameZWDVWQQrdZ1QQcmdZViewItem Sep 22 04:31:15 $162 Sep 22 04:31:23 if i feel lazy Sep 22 04:31:31 I was hoping that since I already have all the accessories (and a spare battery) for the 650, I could snag a cheap one that was missing that stuff from eBay, but even those are pricey - one closed at $70 for just the phone, and the seller wouldn't even guarantee it could place a call. Sep 22 04:32:26 interesting Sep 22 04:32:29 so they stil go for a bit Sep 22 04:33:01 http://cgi.ebay.com.au/Palm-Treo-650-unlocked-GSM-with-accessories_W0QQitemZ270278284872QQihZ017QQcategoryZ161653QQssPageNameZWDVWQQrdZ1QQcmdZViewItem Sep 22 04:33:01 it's a bloody good phone, that's why. Sep 22 04:33:04 loosk good Sep 22 04:33:06 $0.99! Sep 22 04:33:07 :) Sep 22 04:33:23 rwhitby: it is? Sep 22 04:33:47 yep. I haven't found an open or closed source phone better than the Treo650. Sep 22 04:34:59 I had the Sprint version of it from my last employer; when I moved to my current job, I ended up buying the GSM version of it out of my own pocket -- no regrets at all. Sep 22 04:35:03 you obviously havent joine the "let me suck steve jobs's testicles" fan club Sep 22 04:35:25 so the hw is solid? Sep 22 04:35:34 just a question of making linux work... Sep 22 04:35:37 yep Sep 22 04:35:48 good Sep 22 04:35:57 i like it if i know the hw is MEANT to work Sep 22 04:36:00 my phone has lots of paint scratched off it from lots of use :-) Sep 22 04:36:02 and KNONW to Sep 22 04:36:03 :) Sep 22 04:36:29 and it's been dropped onto carpet many times Sep 22 04:37:09 * mwester confesses to dropping it onto a concrete sidewalk -- more than once. Sep 22 04:37:33 oh, the connector on the base doesn't work anymore for data transers, but that's just cause it's all corroded on the connector. still works for power, and I hotsync via bluetooth anyway Sep 22 04:38:03 * mwester wonders if that's what the problem is on his connector. Sep 22 04:38:08 methnks i want my data connector to work for hackin' Sep 22 04:38:40 No salt water near me; my connector is clean. Sep 22 04:39:07 raster: note that the connector worked fine for over 3 years :-) Sep 22 04:39:18 and I could probably clean it if I bothered Sep 22 04:39:25 thats a good life for a phone Sep 22 04:39:27 so, running straight qtopia, what can I use with python to talk to the display? Sep 22 04:39:34 i think the regular lifespan is about 1-1.5 Sep 22 04:40:12 I thought pygame would work but seems no Sep 22 04:40:23 I've had a Treo of some sort for 6 years now Sep 22 04:41:14 poor palm Sep 22 04:41:19 180, 270, 600, 650. Sep 22 04:41:21 so early into the game Sep 22 04:41:30 and yet... now so fucked Sep 22 04:41:31 :( Sep 22 04:41:39 opportunity lost :( Sep 22 04:41:49 * raster ponders why with the zillions fo palm apps... Sep 22 04:41:53 If they had a Treo650 with wifi and 3G, and no other changes (including software), I'd buy it in a minute. Sep 22 04:42:08 well ok not lost Sep 22 04:42:16 but definitely not king of the hill by a country mile Sep 22 04:42:21 as they should have been Sep 22 04:42:29 a poor fourth or lower by now Sep 22 04:42:38 yeah Sep 22 04:42:40 what killed them Sep 22 04:42:43 the os/dev env? Sep 22 04:42:48 or ugliness? Sep 22 04:42:57 they always have simpl3e and functional stuff Sep 22 04:43:05 palmos was painful to code for tho Sep 22 04:43:14 i dug into it when i had a clie nx80 Sep 22 04:43:21 man was that not easy Sep 22 04:43:31 Treo Chatter Email is still the best email app on any mobile device Sep 22 04:43:33 everythnig was static, IIRC Sep 22 04:43:33 especially since u couldnt do a 100% native arm app Sep 22 04:43:52 u nedt o bootstrap with 68k then do subroutines in arm with magic jump goop Sep 22 04:44:11 mwester: yeah - that was an interesting adaption to their original hw Sep 22 04:44:15 but didnt scale Sep 22 04:44:15 1 click to open and get new mail, 1 click to delete message and read next, Sep 22 04:44:29 a lot fo crap was bolted onto palmos to make it look vaguely modern Sep 22 04:45:07 But for a phone/palmtop, it worked well on some pretty small hardware. Sep 22 04:45:19 sure Sep 22 04:45:25 considering where it came grom Sep 22 04:45:30 ie 68k Sep 22 04:45:34 with no disk Sep 22 04:45:39 * mwester owned the original Palm Sep 22 04:45:43 (simple rom only - everythign else in ram) Sep 22 04:45:59 for a while plam totally owned the space Sep 22 04:46:06 * rwhitby implemented the synthesizable 68k core on the PalmV and most of the Clie range while working at Mot Sep 22 04:46:12 again - i wodner what the fatal flaw was Sep 22 04:46:15 just not being sexy? Sep 22 04:46:42 rwhitby: what that the dragonball, then? Sep 22 04:46:46 yep Sep 22 04:46:55 cool Sep 22 04:46:58 * raster has fond memories of his 68k asm days Sep 22 04:47:06 man that was a nice cpu arch Sep 22 04:47:50 I led a team of 5 which took the 4micron custom 68K core and turned it into a 0.25micron synthesizable fully-static and fully-scan implementation Sep 22 04:48:13 Austin? Sep 22 04:48:19 Adelaide Sep 22 04:48:22 Ah. Sep 22 04:48:29 working for Austin Sep 22 04:48:34 da 'laid Sep 22 04:49:03 I still have the *original* 1970-vintage microcode flowcharts for the 68k :-) Sep 22 04:50:49 rwhitby: your starting to scare me o_0 Sep 22 04:51:19 kgoetz: I wasn't there in 1970's - the flowcharts were "handed down" to us to assist in the reimplementation Sep 22 04:51:46 rwhitby: ah, that explains it Sep 22 04:51:49 we did the project in 95 Sep 22 04:52:34 hmm Sep 22 04:52:42 no /sys/class/rtc ... bugger Sep 22 08:03:08 hi guys Sep 22 08:04:06 how do we handle getopt() when porting to ARM? Sep 22 08:04:11 any ideas and tips Sep 22 08:05:47 ? Sep 22 08:05:55 wqhy should that be an issue? Sep 22 08:07:01 because it messes my output with utilities that use it Sep 22 08:07:20 in what way? Sep 22 08:08:00 it returns an extra -? for all inputs Sep 22 08:10:22 odd Sep 22 08:10:26 glibc? Sep 22 08:10:28 or uclibc? Sep 22 08:10:33 raster: yes Sep 22 08:10:38 glibc Sep 22 08:11:25 brb Sep 22 08:14:18 strange Sep 22 08:14:30 * raster doesnt use getops... much easier just to walk the argv... Sep 22 08:51:07 raster: Guess you are right :) Sep 22 08:51:54 But what do we do with all the shit that needs to be handled Sep 22 08:51:57 ? Sep 22 09:52:12 shaz_: sounds like a bug... Sep 22 10:51:56 Weiss: I think its the difference in the way char data type is handled by ARM and x86. Sep 22 10:52:20 hmm? Sep 22 10:52:26 char declaration means unsigned char on ARM and signed on x86 Sep 22 10:53:16 so a comparison resulted in that silly output Sep 22 10:53:48 I did the way raster told me to walk the arguments and it worked out fine for a start :) Sep 22 10:57:13 hm.. but if the character codes are low, then it shouldn't make any difference (sign bit will always be unset) Sep 22 11:11:00 i dont see any reason arguments shouldnt be low Sep 22 11:11:03 ie normal ascii Sep 22 11:11:39 u dont make cmd-line arguments like -金魚 Sep 22 11:12:01 or -œøb Sep 22 11:12:02 :) Sep 22 11:12:32 raster: :-) Sep 22 11:21:04 * rwhitby wonders if anyone has tried qemu lately, cause both fso-testing and openmoko daily gta01 images fail to get past u-boot ... Sep 22 11:23:12 alphaone: boo! Sep 22 11:24:33 raster: heya Sep 22 11:26:27 do u guys have anything in fso so far for scheduled jobs Sep 22 11:26:28 ie at? Sep 22 11:28:02 no. everything time/scheduled events/wakeup is still missing. Sep 22 11:28:12 bbiab, dinner Sep 22 11:30:43 ok Sep 22 11:30:51 well looks like yet another thing i am busy implementing Sep 22 11:30:57 if u want it... i have it Sep 22 11:30:58 or the start Sep 22 11:31:00 api is done Sep 22 11:34:32 raster: Sounds nice. How is the API? Sep 22 11:35:07 really simple Sep 22 11:35:09 dbus Sep 22 11:35:23 e_dbus_interface_method_add(iface, "List", "", "a(i)", Sep 22 11:35:23 request_method_List); Sep 22 11:35:23 e_dbus_interface_method_add(iface, "Add", "iiss", "", Sep 22 11:35:23 request_method_Add); Sep 22 11:35:23 e_dbus_interface_method_add(iface, "Del", "i", "", Sep 22 11:35:24 request_method_Add); Sep 22 11:35:44 list just lists job id #'s Sep 22 11:35:49 u delete by job id # Sep 22 11:36:21 i assume if u added a job u know its job id # (you stored it - return from Add) Sep 22 11:36:22 is there a race between list and delete? Sep 22 11:36:27 (oops missed in return type list) Sep 22 11:36:55 lindi-: someone else deletes it before you do Sep 22 11:36:56 nb Sep 22 11:37:03 job #'s wont change once assigned Sep 22 11:37:11 i'll just make them monotonically increasing Sep 22 11:37:55 so u'd get a list like: 7, 24, 6778, 6779, 7032, 9434 Sep 22 11:38:02 for example Sep 22 11:43:24 any more input Sep 22 11:43:26 throw it now Sep 22 11:43:28 i'm building it Sep 22 11:43:31 i need it Sep 22 11:43:34 at doesnt do what i need Sep 22 11:43:57 (no rtc wakup support, broken on oe/om anyway, also only has minute resolution, not seconds) Sep 22 11:51:08 ok Sep 22 11:51:12 more funeral work... Sep 22 12:38:52 Hmm - so I try out the testing image from downloads.openmoko.org/daily on a GTA01, and usb networking doesn't work for some reason. Of course there is no terminal application installed, and the stupid boots stop you seeing any errors from the kernel during boot, so you have absolutely no way of diagnosing or fixing the problem. Sep 22 12:40:19 and /etc/resolv.conf is missing, so you can't even use the installer out of the box. Sep 22 12:40:51 d'oh Sep 22 12:42:32 ok, looks like a reboot fixes the usb problem. Sep 22 12:43:42 now in the installer program, the phone goes into suspend in the middle of updating the package lists Sep 22 12:43:56 and then you have applications who's names are so long that the extend off the edge of the screen Sep 22 12:44:22 so you have three apps called "qtopia-phone-x11-..." and don't know what each one really is Sep 22 12:45:02 well, after 5 minutes with om2008.9, all it does is reaffirm why I use fso-testing ... Sep 22 12:46:21 heh, now it suspends in the middle of installing an application ... Sep 22 12:47:21 cool, Categories/Miscellaneous has no less than 6 applications all called "qtopia-phone-x11-"(edge of screen) Sep 22 12:49:27 then packagekitd preventing running opkg manually until you kill it is just completely idiotic Sep 22 12:51:21 and of course the classic "Install a terminal program, but you don't get a virtual keyboard with that ..." Sep 22 12:52:22 and suspending when you're ssh'd into the phone via usb Sep 22 12:53:21 * rwhitby keeps tapping the screen, so that opkg can complete successfully Sep 22 13:20:07 Hey Sep 22 13:24:15 Ainulindale, here? :) Sep 22 13:47:00 quickdev: yes Sep 22 13:47:05 I was looking for you Sep 22 13:47:27 fine..I've got some questions Sep 22 13:47:48 Sorry for the delay I've been quite busy this week end Sep 22 13:48:00 no problem..sorry for disturbing that often Sep 22 13:48:39 I'd like to extend libframeworkd-glib for led interface usage..for example the vibrator Sep 22 13:49:13 atm the files are named wrong in my opionion. frameworkd-glib-device.c should be frameworkd-glib-gsm-device.c, shoudn't it? Sep 22 13:49:36 Yes it should, I thought about that in the beginning of the project Sep 22 13:49:41 But I was far too lazy Sep 22 13:50:07 ok Sep 22 13:50:14 I'd rather name them by their correspondent interface Sep 22 13:50:16 how about my patch? reviewed? if not...no problem ;) Sep 22 13:50:27 i.e. ogsmd/frameworkd-glib-ogsmd-device.c Sep 22 13:50:37 and the same thing for the headers of course Sep 22 13:50:43 yeah.. Sep 22 13:50:48 but it's not a real urgent matter Sep 22 13:50:58 yes, it isn't Sep 22 13:51:28 Your patch is good, no problem with that indeed Sep 22 13:52:02 could you apply it? Sep 22 13:52:18 I could but I won't, just to annoy you Sep 22 13:52:19 :-) Sep 22 13:52:59 where's the prob? ;) Sep 22 13:53:24 Weird, I have fuzz Sep 22 13:54:58 fuzz? what does that mean? Sep 22 13:55:16 Use of uninitialized value $module in concatenation (.) or string at /usr/local/bin/ciabot.pl line 182. Sep 22 13:55:19 Weird Sep 22 13:55:20 quickdev: applying the patch Sep 22 13:55:54 ciabot? mh? ;) Sep 22 13:56:08 mickey|dinner: problem with freesmartphone git Sep 22 13:56:20 just ignore that message Sep 22 13:56:24 freesmartphone.org: 03ainulindale 07libframeworkd-glib * r7b5afc2fc30a 10/src/ (frameworkd-glib-dbus.c frameworkd-glib-dbus.h): Applied quickdev error handling patch for dbus internal errors. Thanks quickdev ! Sep 22 13:56:24 freesmartphone.org: 03ainulindale 07libframeworkd-glib * r7b5afc2fc30a 10/src/ (frameworkd-glib-dbus.c frameworkd-glib-dbus.h): Applied quickdev error handling patch for dbus internal errors. Thanks quickdev ! Sep 22 13:56:53 Ainulindale, fine, thanks Sep 22 13:57:41 mickey|tw: how's taipei ? Sep 22 13:57:52 warm Sep 22 13:57:54 just arrived today Sep 22 13:57:56 pretty tired Sep 22 13:57:59 going to bed soon Sep 22 13:58:02 I guess so Sep 22 13:58:17 mickey|tw, how long did you fly? Sep 22 13:58:35 quickdev: ~12.5 hours Sep 22 13:58:49 mickey|tw: found anything interesting in the log?;) Sep 22 13:59:11 yes Sep 22 13:59:24 big thing i omitted Sep 22 13:59:31 dunno how you could trigger the state Sep 22 13:59:37 but i need to add it Sep 22 13:59:37 :) Sep 22 14:00:09 right, nice, thanks; I'll try to set up frameworkd from git in the mean time, then Sep 22 14:03:36 i completely forgot one state in my call state handler :) Sep 22 14:03:49 will add that this week Sep 22 14:21:25 mickey|tw: spotted you on linkedin :-) Sep 22 14:21:35 and rwhitby Sep 22 14:23:10 Ainulindale, is it just another community? Sep 22 14:25:23 it's a social network for professionals Sep 22 14:25:32 It may or may not be useful, it depends Sep 22 14:25:50 It is useful to me as the identity & access management field is pretty tiny these days, but growing and growing Sep 22 14:40:48 Ainulindale, in order to send the PIN from phonegui to ophonekitd I implemented a phonegui_provide_pin(char* pin) method. That's ok, isn't it? (Considering the whole concept) Sep 22 14:41:08 For this kind of thing, I don't think so Sep 22 14:41:25 It's another layer, could be useful, yes, considering what I told you before Sep 22 14:41:27 Ainulindale, how to do it otherwise? Sep 22 14:41:29 But for this kind of calls Sep 22 14:41:35 I think it is just some overhead Sep 22 14:41:41 I think you should use directly lfg Sep 22 14:41:43 do it directly? Sep 22 14:41:48 ok Sep 22 14:41:55 That's my opinion and just mine Sep 22 14:42:07 I think things have to go through ophonekitd for non user generated events Sep 22 14:42:14 Such as "incoming call" Sep 22 14:42:22 But that's all Sep 22 14:42:28 Doing more is doing overhead, to my eyes Sep 22 14:42:40 ophonekitd is there just to link the UI to dbus and manage events Sep 22 14:42:47 the ui do its stuff internally as it wants Sep 22 14:42:51 +oes Sep 22 14:42:59 Man my english is awful today Sep 22 14:43:30 Ainulindale, and the ui application has to handle wrong sim aswell? I mean...it isn't redisplayed if PIN is wrong, right? Sep 22 14:44:30 Nope Sep 22 14:44:45 Err Sep 22 14:44:51 In fact it depends :-p Sep 22 14:45:04 You'll be able to give lfg a callback Sep 22 14:45:08 and it will return Sep 22 14:45:18 but the only way to know PIN isn't right Sep 22 14:45:23 is through an event Sep 22 14:45:39 so it's ophonekitd which will tell to the ui PIN is wrong (or PUK is mandatory) Sep 22 14:45:50 If the current sim auth status is PIN_REQUIRED and the PIN is wrong, ophonekitd will not be informed, because auth status is the same. If the third PIN is wrong, ophonekitd will be informed about PUK_REQUIRED and the phonegui is displayed. That sounds not very well? Sep 22 14:46:05 wrong Sep 22 14:46:15 the signal will be fired again Sep 22 14:46:29 when will it be fired again? after pin is wrong? Sep 22 14:46:32 yep Sep 22 14:46:46 ophonekitd doesn't know about a wrong pin Sep 22 14:46:54 because the sim status is the same...no trigger Sep 22 14:46:57 He just know PIN is needed Sep 22 14:47:03 And he knows there's a signal for it Sep 22 14:47:06 So he will ask for it Sep 22 14:47:13 No matter what Sep 22 14:47:19 And by he I mean it obviously Sep 22 14:48:00 quickdev: Problem is Sep 22 14:48:04 If you set the wrong pin Sep 22 14:48:13 You can't know if you have to type in PIN or PUK Sep 22 14:48:23 Only thing which will give you that is the signal Sep 22 14:48:30 Because the error is just "wrong pin" Sep 22 14:48:39 And not "wrong pin, need puk" Sep 22 14:49:13 And I can't remember if the signal is refired with each try or not Sep 22 14:49:18 I don't really get you. Do I have to do sim_send_auth_code(pin, callback) directly and pass a ophonekitd callback? Sep 22 14:49:27 No :-) Sep 22 14:49:32 I'll explain it more "slowly" Sep 22 14:49:35 First thing to know : Sep 22 14:49:42 Ainulindale, it isn't refired - that's the prob Sep 22 14:49:48 Error message just tells you your authentication went bad Sep 22 14:49:54 So you know the authentication went bad Sep 22 14:49:56 yeah Sep 22 14:50:08 If you need the same code, then no signal Sep 22 14:50:11 Then ophonekitd won't tell anything Sep 22 14:50:16 But the UI knows the code is bad Sep 22 14:50:20 so it will redisplay itself Sep 22 14:50:30 Let's say PIN is wrong but PUK is needed Sep 22 14:50:34 Only ophonekitd will know that Sep 22 14:50:39 Hence ophonekitd receives a signal Sep 22 14:50:49 And forwards it to the UI by asking to display the PUK ui Sep 22 14:51:18 You'll also have a SIM BLOCKED error Sep 22 14:51:31 So if you have SIM_BLOCKED Sep 22 14:51:35 You have to wait for the signal Sep 22 14:51:44 Which will ask phonegui to redisplay the UI Sep 22 14:51:58 Thus what I would do is display a message "SIM blocked. Waiting for necessary code" Sep 22 14:52:03 ok, redisplaying by ophonekitd is completely clear Sep 22 14:52:21 And close this message, redisplay the UI (refreshing it) with "PUK" instead of "PIN" Sep 22 14:52:34 try to have a look at the way lfp-gtk was done Sep 22 14:52:44 the callback auf sim_send_auth_code is the callback of the sim-auth-status ui then? Sep 22 14:52:57 s/auf/of/ Sep 22 14:52:58 exactly Sep 22 14:53:11 that's the thing i wanted to know ;) Sep 22 14:53:14 the UI has to know if its call went bad Sep 22 14:53:24 To do the appropriate warning/error message Sep 22 14:53:32 In fact in lfp-gtk Sep 22 14:53:37 yes - redirect that to ophonekitd atm...but ok Sep 22 14:53:37 There's a static variable for the code to ask Sep 22 14:53:46 "Redisplaying" the UI just modify this code Sep 22 14:53:51 so if there's an error Sep 22 14:54:01 the code to ask will be different, thus changing the label of the text Sep 22 14:54:11 but it's pure UI management there Sep 22 14:54:17 You should ask MarcOChapeau about that Sep 22 14:54:22 yes, that's all done - the only thing to change is the callback in ui code Sep 22 14:54:37 Only thing to know : don't give ophonekitd callbacks Sep 22 14:54:41 Implement your own callbacks Sep 22 14:54:45 But don't implement signals Sep 22 14:54:52 PUK, PIN, incoming call already works ;) Sep 22 14:54:53 Signals has to be managed in ophonekitd Sep 22 14:54:57 Nice :-) Sep 22 14:56:09 quickdev, evening, if i am not mistaken..you were looking at porting some init system to OE (minit) Sep 22 14:56:11 ? Sep 22 14:56:29 Sup3rkiddo, I played a little bit with it Sep 22 14:56:47 quickdev, so progress? Sep 22 14:57:39 quickdev: nice work :-) Sep 22 14:58:10 quickdev: by the way did you subscribe to shr-devel ? Sep 22 14:58:12 Sup3rkiddo, much of the time was used by kernel and I haven't even compiled a kernel for my neo so far ;) Sep 22 14:58:35 Ainulindale, no, only smartphone userland ml Sep 22 14:58:44 will do it Sep 22 15:00:06 quickdev, can i get some data regarding this, like bootchart?... Sep 22 15:00:45 Sup3rkiddo, count the seconds till "init started." appears - that's where the kernel has its things done Sep 22 15:00:49 quickdev: I'm sorry I'm quite unavailable these times Sep 22 15:00:54 It will change by the end of the week Sep 22 15:19:03 Ainulindale, will sim_send_auth_code() indicate if PIN is right or wrong? It won't, right? Sep 22 15:24:03 Ainulindale, one last question Sep 22 15:26:03 sim_send_auth_code won't indicate anything but if what you did went through Sep 22 15:26:25 and it isn't use just for PIN Sep 22 15:26:27 +d Sep 22 15:26:36 It is also used for PIN2, as an example Sep 22 15:26:53 Even if in our world it won't truly be used :-p Sep 22 15:27:24 Ainulindale, you said that the ui won't know know if the pin is wrong...I need to know it - but how? Sep 22 15:28:08 may I use sim_get_auth_status() after sim_send_auth_code() ? Sep 22 15:29:27 If the ui is closed...ok...pin was right....but I cannot catch the event: UI still runs, pin wrong Sep 22 15:31:33 Yes you will Sep 22 15:31:42 Because the callback for set_auth_code will return an error Sep 22 15:31:54 Error being "wrong pin" Sep 22 15:32:32 Ainulindale, you mean the callback of sim_send_auth_code() or sim_get_auth_status() - only the latter one says pin wrong Sep 22 15:32:39 => SIM_ERROR_AUTH_FAILED Sep 22 15:33:04 sim_send_auth_code will, on a wrong pin, return "SIM_ERROR_AUTH_FAILED" if I'm correct Sep 22 15:34:02 ok, then it's clear Sep 22 15:34:35 http://rafb.net/p/AK0v3U29.html Sep 22 15:34:39 example Sep 22 15:37:32 quickdev: is it clearer ? Sep 22 15:37:38 yes, it is Sep 22 15:37:40 thanks. Sep 22 15:52:26 Hi! Does anybody can compile current version of qemu? ( svn co https://svn.openmoko.org/trunk/src/host/qemu-neo1973 ) I'm getting this error : http://www.everfall.com/paste/id.php?v49h7dj6s47p Sep 22 17:05:48 Ainulindale, AndreasD_, call_release() does not seem to work. Is that known? Sep 22 17:06:47 quickdev: nope Sep 22 17:07:58 quickdev: what happens? Sep 22 17:08:05 AndreasD_, nothing ;) Sep 22 17:09:11 AndreasD_, call_release(NULL, call_id, NULL, NULL); Sep 22 17:10:12 quickdev: have you checked zhone? Sep 22 17:10:27 AndreasD_, there, release works - it's a frameworkd-glib issue Sep 22 17:11:02 quickdev: I was wondering if they set a message Sep 22 17:11:15 AndreasD_, just thinking about the same.. Sep 22 17:11:25 ogsmd/objects.py Sep 22 17:12:02 AndreasD_, http://git.freesmartphone.org/?p=framework.git;a=blob;f=framework/subsystems/ogsmd/objects.py;h=3be3a6c9eb33a2c21ac6349b8c8145d841fd076a;hb=HEAD Sep 22 17:12:27 AndreasD_, release seems to take nothing than an index, or am I wrong? Sep 22 17:12:45 then the specs are wrong (documentation) Sep 22 17:14:14 quickdev: from the source code of zhone it also seems only to take a index Sep 22 17:14:28 AndreasD_, I'll try changing libframeworkd-glib Sep 22 17:15:29 quickdev: might be worth asking mickey when he wakes up if its an error in specs or implementation Sep 22 17:16:38 AndreasD_, I'm not sure, but I think I asked him some weeks ago and he said. Not yet implemented. But libframeworkd-glib should work with the current version, shouldn't it? Sep 22 17:18:04 that would be great, you could simply change the call.xml and regenerate call.h Sep 22 17:18:45 but keep message argument in call_release until we know if it's an error in spec or implementation Sep 22 17:19:07 AndreasD_, ok - how do I create the call.h from call.xml? Sep 22 17:19:20 yes Sep 22 17:20:47 AndreasD_, how? Sep 22 17:21:18 using dbus-binding-tool, but from what I recall the version in hardy is too old Sep 22 17:21:49 I got Ainulindale to regenerate them once Sep 22 17:23:46 quickdev: any help? Sep 22 17:24:15 AndreasD_, I will try.. Sep 22 17:24:51 quickdev: great :-) Sep 22 17:26:04 AndreasD_, do you know how to add a file to git? git add src/file does not mention it when calling git diff Sep 22 17:27:37 AndreasD_, ah, solved it - git diff doesn't display it Sep 22 17:35:54 AndreasD_, dbus-binding-tool call.xml - version too old? Sep 22 17:35:55 Unable to load "%s": Attribute "xmlns:doc" is invalid on element in this context Sep 22 17:36:27 quickdev: yes :-( Sep 22 17:36:35 ok, will get it from source Sep 22 17:37:42 quickdev: could be great to be able to generate them on Hardy Sep 22 17:38:20 yeah, but how to do it? build a package? and then? ;) Sep 22 17:39:30 you could try to get a unstable debian package and rebuild it for ubuntu Sep 22 17:39:42 but if you've got other stuff to work on this can probably wait Sep 22 17:40:08 maybe some nice gentoo guy could regenerate them? Sep 22 17:41:12 gentoo uses the same package system as ubuntu? Sep 22 17:41:45 no, the version in gentoo is probably newer than in ubuntu Sep 22 17:42:19 yes, probably ;) Sep 22 17:42:42 from what I recall dbus-binding-tool had to be >0.74 Sep 22 17:43:12 maybe 0.75 Sep 22 17:43:24 I took the newest, it's compiling Sep 22 17:43:44 great :-) Sep 22 17:55:21 Ainulindale, dbus-binding-tool call.xml doesn't do anything..hm Sep 22 17:55:25 How did you run it? Sep 22 17:58:35 got it: dbus-binding-tool --mode=glib-client call.xml Sep 22 18:01:47 quickdev: sounds good :-) Sep 22 18:20:58 AndreasD_, call_release() works now :) Sep 22 18:21:38 quickdev: great work :-) Sep 22 18:25:02 Ainulindale, you got a mail Sep 22 18:40:46 AndreasD_, openmoko-dialer3 contains much gtk code, which shoudln't go there. Do you think I may remove that or is that active somehow? Sep 22 18:41:26 quickdev: I really don't know, but I can try and take a look Sep 22 18:45:05 what is libmokoui for? Sep 22 18:45:31 quickdev: what code are you thinking of? Sep 22 18:45:42 openmoko-dialer3 Sep 22 18:45:58 AndreasD_, libmokoui question or gtk question? Sep 22 18:46:17 from what I can see there isn't much gtk code in openmoko-dialer3 Sep 22 18:46:34 most of it is in libframeworkd-phonegui-gtk Sep 22 18:47:22 libmokoui contains shared ui code for gtk moko applications for instance finger scroll Sep 22 18:48:41 shared ui code for gtk applications...but I'd like to build something with efl ;) Sep 22 19:30:14 AndreasD_, here to discuss something? Sep 22 19:31:15 quickdev: if needed :-) Sep 22 19:33:24 AndreasD_, atm the ophonekitd gui library name is configured in /etc/ophonekitd/gui. What about openmoko-dialer3. Do you share my opinion, that they should share a config file? Sep 22 19:34:32 quickdev: yes Sep 22 19:34:52 AndreasD_, but what directory name to choose? Sep 22 19:35:06 quickdev: ophonekitd Sep 22 19:35:10 that is the question Sep 22 19:35:15 Since it's the one that always has to be there Sep 22 19:35:29 the dialer could theoretically be a different program than openmoko-dialer3 Sep 22 19:35:55 If I've understood properly how Julien broke that up Sep 22 19:35:56 wurp2|working, the dialer could run without ophonekitd Sep 22 19:36:11 wurp2|working, yes, it could Sep 22 19:36:45 If the dialer ran w/o opkd, it would need something else to bring up the "talking" ui when the connection is made Sep 22 19:37:16 I agree that could be done, but the dialer is written expecting that opkd or something very like it will exist Sep 22 19:37:30 again, if I understood Julien's structure properly Sep 22 19:37:39 I think you do Sep 22 19:37:47 I agree with ophonekitd Sep 22 19:38:20 It is a somewhat arbitrary choice, but it feels better than the other way around Sep 22 19:38:50 yes, correct - I'll use that destination Sep 22 19:38:54 openmoko-messages3 should probably also someday have some guid stuff in libframeworkd-phonegui-gtk Sep 22 19:39:21 -d Sep 22 19:40:23 wurp2|working, atm ophonekitd uses a different part of libframeworkd-phonegui-efl than the dialer. I don't see too much similarities between incoming call dialog and the dialer(/outgoing call dialogs). Sep 22 19:40:49 quickdev: that makes sense to me Sep 22 19:41:05 AndreasD_: that makes sense Sep 22 19:41:20 wurp2|working, what makes sense? combine incoming call and dialer? Sep 22 19:41:55 quickdev: splitting it Sep 22 19:42:00 yes, ok Sep 22 19:42:12 Incoming call dialog is more like the in-call dialog to me than the dialer Sep 22 19:42:19 and it's not very much like the in-call dialog :-) Sep 22 19:43:27 it's my first open source and c project - I hope some acceptable code will be the result Sep 22 19:44:19 quickdev: Cool! Sep 22 19:44:31 C is tough to get right Sep 22 19:45:17 because it's easy to make a mistake and often hard to find the mistake - lots of problems may be symptom free for ages, then start crashing the program Sep 22 19:45:25 unless you use a tool like valgrind or purify on it Sep 22 19:47:35 motivation ;) luckily I haven't had many big errors so far, because it's quite simple atm Sep 22 20:06:35 quickdev: simple is best, if you can pull it off :-) Sep 22 21:51:26 * [Rui] waves Sep 22 21:51:39 <[Rui]> anyone here manages projects.openmoko.org ? Sep 22 21:51:48 <[Rui]> does it support greylisting when it sends the activation link? Sep 22 22:02:44 [Rui]: Nah, this is for community developers Sep 22 22:02:59 You'd be more likely to see managers of p.om.org in #openmoko Sep 22 22:04:26 <[Rui]> wurp2|working: thanks Sep 22 22:04:44 <[Rui]> I've discovered a "resend" and used it **** ENDING LOGGING AT Tue Sep 23 02:59:58 2008