**** BEGIN LOGGING AT Sat Oct 03 02:59:57 2009 Oct 03 04:31:43 Does any one else make android other then Koolu for Neo FreeRunner Oct 03 05:17:39 is there a stand for the freerunner? Oct 03 05:18:40 or some type of dock? Oct 03 05:27:21 i have a stang i salvaged from somewhere Oct 03 05:27:26 here's a quick sketch i just made to show what i was thinking of: http://imagebin.ca/img/nD1g6Wi.png Oct 03 05:27:44 something that brings it eye level while i have my usb keyboard attached to it Oct 03 05:28:01 more like a CLAW Oct 03 05:28:41 it could also be a docking station if you made appropriate adjustments, use your imagination :) Oct 03 05:28:51 opkg upgrading Oct 03 05:29:16 hopefully Oct 03 05:41:19 Slaxxer: opkg? Oct 03 09:05:01 hi um is shr ok for use atm Oct 03 09:05:03 like the latest ... Oct 03 09:08:32 hi Oct 03 10:09:15 hi there Oct 03 10:09:39 can i plug fr to the usb, so it can charge while i flash the modem firmware with the uSD? Oct 03 10:10:10 zear: why not? Oct 03 10:10:17 lindi-, just wanted to be sure Oct 03 10:10:27 i mean. during the process Oct 03 10:10:31 it's flashing right now Oct 03 10:23:43 PaulFertser, hi there. I've reflashed my modem software to moko11, and i still can't make * calls Oct 03 10:23:58 still getting the GSM.SIM.NotReady Oct 03 11:04:25 zear: moko11 (as any new modem fw) is not supposed to change sim.notready issue Oct 03 11:05:29 zear: only known sim issue which can be fixed with update of FW is the "3G"-simcard not working thing Oct 03 11:05:29 DocScrutinizer-8, i was told to flash the firmware to the newest version before asking of this problem Oct 03 11:05:48 that's been a good advice anyway Oct 03 11:05:50 so yeah, now i have it in the current version, and would like to know if there is a fix for my problem ;) Oct 03 11:06:26 yeah, the firmware i had before was in version moko8 ;) Oct 03 11:06:36 probably an issue with your sim and provider. Did you try with other phone to use the sim? Oct 03 11:06:46 yes Oct 03 11:06:59 different sims and distros on freerunner Oct 03 11:07:02 which distro and version? Oct 03 11:07:30 don't remember the details, but it was SHR testing and something else Oct 03 11:07:35 that debian thingy Oct 03 11:07:53 uhh, testing is bitrotten to dust Oct 03 11:07:54 i can call * numbers with that sim from other phones Oct 03 11:08:46 though that's not a reason for your problem afaik, nevertheless I recommend to try 0808 version of shr-u, as listed in #chan topic Oct 03 11:09:10 i have the current one, dunno what version it is Oct 03 11:09:25 actually, the lack of * numbers support in my fr kills the whole idea of using fr as a phone Oct 03 11:09:50 please make sure you're using image as of 0808 (or 0906) Oct 03 11:09:54 as i need to call * numbers to recharge my prepaid account, or to get information about my account stats Oct 03 11:10:25 DocScrutinizer-8, can i somehow find it out on the freerunner? as i don't have the images anymore Oct 03 11:10:47 err, please elaborate on your problem. I think I don't get the whole picture Oct 03 11:11:22 DocScrutinizer-8, you mean the one with being unable to call * starting numbers? Oct 03 11:11:37 what's "* numbers"? can you call other numbers? Oct 03 11:11:49 can you accept inbound calls? Oct 03 11:11:53 i mean numbers that look like that: *101# Oct 03 11:12:02 i can call all the standard numbers Oct 03 11:12:07 and recieve texts Oct 03 11:12:22 but i can't call any special numbers that start with * Oct 03 11:12:28 zear: so update to 0808 please Oct 03 11:12:59 this is an issue that's been fixed long ago in shr-u Oct 03 11:13:23 well, i have the newest version of shr-unstable Oct 03 11:13:30 from two days ago Oct 03 11:13:42 i mean, i flashed it two days ago, but it's a version from september Oct 03 11:13:48 there's no image of 2 days ago Oct 03 11:14:06 hmm, dunno then Oct 03 11:14:11 here it works Oct 03 11:14:15 besides, i can't call that numbers even by directly passing them with AT commands Oct 03 11:15:34 ok, it's shr-full-glibc-ipk--20090906-om-gta02.rootfs.jffs2 i have Oct 03 11:16:26 shr-U as of 0808 (with some older upgrades but that doesn't matter here): calling "*101#" on german O2 loop prepaid gives me correct answer (screnn pops up saying "your account: xy.zz€" Oct 03 11:17:11 well, for me on two polish networks, "era" and "play" simply returns to the dialer app Oct 03 11:20:29 please try "*31# Oct 03 11:21:12 you mean any normal number so i can call someone? Oct 03 11:21:31 yep Oct 03 11:22:08 the above sequence should dial that number but suppress your own number-signaling (CLIR) Oct 03 11:22:35 it makes a valid call Oct 03 11:22:53 so the issue is with your provider it seems Oct 03 11:23:21 but *101# works fine with that card on other phones Oct 03 11:23:43 hmm Oct 03 11:23:47 besides, it's not the first sim card that prevents me from calling *101# on freerunner Oct 03 11:23:58 try "*#61#" Oct 03 11:24:14 what will that do? Oct 03 11:24:24 it should reply an empty "data:" Oct 03 11:24:36 which is a bug but anyway Oct 03 11:25:08 i can hear in my speakers it tries to contact the network, but nothing happenes Oct 03 11:25:24 strange Oct 03 11:26:07 should i launch mickeyterm and see what it returns when i call *101# ? Oct 03 11:26:42 zear: that's no issue of modem firmware. It *might* be a problem of FSO framework. We need mickey for that. He'll be back on Monday Oct 03 11:27:21 DocScrutinizer-8, but i remember i was getting an "ERROR" respond then i was trying to call this number via mickeyterm Oct 03 11:27:51 zear: please join #openmoko-cdevel and rise the issue there Oct 03 11:28:11 DocScrutinizer-8, ok, will dod that Oct 03 11:28:52 zear: preferrably on Monday when Mickeyl is back (and online) ;-) Oct 03 11:31:09 zear: you could pastebin a copy of a mickeyterm session where you do a ATD*101# though. I might have a short look at it Oct 03 11:32:18 zear: please include a "ATD" which should show a "BUSY" as result Oct 03 11:38:44 freesmartphone.org: 03mickey 07cornucopia * r2637a41756b6 10/fsogsmd/src/ (10 files in 2 dirs): fsogsmd: implement org.freesmartphone.GSM.Device.{Get|Set}SimBuffersSms() Oct 03 11:38:45 freesmartphone.org: 03mickey 07cornucopia * r2aed1bd88603 10/fsogsmd/src/ (4 files in 3 dirs): fsogsmd: modem: channelForCommand is abstract hence MUST be implemented by the modem plugin Oct 03 11:38:48 zear: here ATD*101# works Oct 03 11:38:53 freesmartphone.org: 03mickey 07phonesim * r4b555cb99b10 10/modems/generic.xml: generic.xml: properly implement +CNMI Oct 03 11:39:33 zear: ATD*234# gives "ERROR" (as it's a non-supported code) Oct 03 12:00:29 for some time now my openmoko doesn't emit a sound anymore when ringing Oct 03 12:00:38 runnig shr-unstable, is this a know problem? Oct 03 12:04:10 jaj: opkg remove -force-depends speech-dispatcher? Oct 03 12:06:33 hmm yeah indeed that might be it :) Oct 03 12:07:25 !logs Oct 03 12:07:26 Channel logs for #openmoko are archived at: Oct 03 12:07:27 http://hentges.net/tmp/logs/irc/%23openmoko Oct 03 12:07:28 Live-logs are available at Oct 03 12:07:30 http://hentges.net/tmp/logs/irc/livelogs/%23openmoko.livelog Oct 03 12:07:32 See ?? help-logs for usage instructions Oct 03 12:07:49 grrrrrrrrrrrrrrrrrrr for speech-dispatcher Oct 03 12:12:11 CoreDump: what about an ultracool patch to cdbot, to listen for "~logs" (sic) and make that an "alias" of "sleep 5; !logs" ;-D Oct 03 12:13:44 the problem is that ~ usually interferes with apt, ibot and friends =) Oct 03 12:13:55 yep Oct 03 12:14:20 that's why I suggested to specifically grep for "~logs" Oct 03 12:15:22 CoreDump: and give apt a "sleep 5" to finish his thing first Oct 03 12:16:19 ibot is listening to ~logs as well, so the shortcut would need to be manually enabled for any channel ibot / apt is not in. Oct 03 12:17:08 CoreDump: I have no idea how cdbot could care about whether there is apt or not. Oct 03 12:17:30 I've I ever get sufficiently bored, I shall have a look =) Oct 03 12:18:01 but yes it's kinda hackish and not compatible to each channels setup for cdbot Oct 03 12:18:12 exactly Oct 03 12:19:00 as ibot/apt *might* use different shortcut than "~" Oct 03 12:20:12 so if cdbot is only bot on a channel and already listens to "~" it would be kinda annoying to also listen to "~logs" and do same thing twice Oct 03 12:20:44 right. Highly annoying. I speak from experience =) Oct 03 12:20:59 in channels with apt listening to e.g. % it would fail Oct 03 12:22:08 though timriker told me apt always is configured to listen to ~ Oct 03 12:23:46 CoreDump: would you mind to add cdbot to #openmoko-cdevel? Oct 03 12:24:28 not at all. Let me see if I have one more spare channel. Freenode does not allow cdbot to join more than 20 heh Oct 03 12:24:46 we already got nslu logs there, but anyway Oct 03 12:24:57 duh Oct 03 12:30:51 freesmartphone.org: 03mickey 07specs * r896563e12805 10/ (4 files in 3 dirs): Oct 03 12:30:51 freesmartphone.org: org.freesmartphone.GSM.Device: Add new API org.freesmartphone.GSM.Device.SetFunctionality( s:level ) -> () Oct 03 12:30:51 freesmartphone.org: NOTE: This deprecates org.freesmartphone.GSM.SetAntennaPower! Oct 03 12:31:21 let me know when there are any problems in -cdevel. The channel is pretty much off my radar usually ;) Oct 03 12:34:29 freesmartphone.org: 03mickey 07libfso-glib * rae45e89e5f35 10/src/ (3 files): regenerate Oct 03 12:42:28 zear: i'm sorry that reflashing to the newest version didn't help but otoh i'm sure nobody should be using old versions unless there's _very_ good reason to do so. Oct 03 12:43:08 zear: and i've to admit that your issues looks extremely weird, it's like "it just can't be like that". Oct 03 13:02:45 freesmartphone.org: 03mickey 07cornucopia * r44a757f3ca90 10/fsogsmd/src/ (4 files in 2 dirs): Oct 03 13:02:45 freesmartphone.org: fsogsmd: prepare for org.freesmartphone.GSM.Device.{Get|Set}Functionality Oct 03 13:02:46 freesmartphone.org: NOTE: Need to integrate fsogsmd with resource system before we can implement this Oct 03 13:09:09 PaulFertser: yep. I'm still waiting for the mickeyterm "log" Oct 03 13:09:52 sounds like "pebkac" Oct 03 13:10:31 wrong "number" or sth. Or maybe simply provider does not support the function anymore Oct 03 13:22:58 hi Oct 03 13:25:44 how do I restore the NAND mtdparts to factory-state? Oct 03 16:43:11 freesmartphone.org: 03seba.dos1 07dos/opimd-tracking * r89df0861123f 10framework/framework/subsystems/opimd/ (4 files): opimd: SQLite-*: use FLOAT type in database for Timestamps and Duration fields Oct 03 16:45:46 freesmartphone.org: 03seba.dos1 07dos/opimd-tracking * r1a30891d8ea4 10framework/framework/subsystems/opimd/docs/TODO: opimd: update TODO Oct 03 16:46:39 hallo i crosscompiled kernel for openmoko, everything worked, but in the tar.gz for modules i cant find ar6000 for wireless ( i used andy-tracking ), can anybody explain me how is it that i missed those drivers? Oct 03 16:48:22 the kernel runs correctly ( i even patched cpufreq against it), targzed alla modules -C /, but on /lib/modules/`uname -r` i find no trace of ar6000.ko Oct 03 16:48:32 do any of u had experience with it? Oct 03 16:50:23 Guest80031: maybe you have it built into kernel? Oct 03 16:51:37 ok tnx Oct 03 16:51:39 you were right Oct 03 16:51:46 being blind today Oct 03 16:59:28 mhm, ok just another question, how is it that my kernel is bigger then 2 mb (having modules in it.. ok).. but how can i manage to create a smaller kernel? Oct 03 17:06:01 openmoko: 03rehar * r5666 10/trunk/gta02-core/modules/ (INFO STATUS fa2012.fpd mkloe): added FA2012 footprint Oct 03 17:11:51 gps seems not to work Oct 03 17:12:02 does it relay on some modules? Oct 03 17:13:57 even after echo 1 > Oct 03 17:14:48 i get absolutly no device for gps Oct 03 17:15:47 what hardware? Oct 03 17:15:51 oh - nvm Oct 03 17:16:09 the GPS is on /dev/ttySAC1 I think - it's a nomrla serial port Oct 03 17:16:15 yeah Oct 03 17:16:18 is not there Oct 03 17:16:49 you mean you have no serail devices? Oct 03 17:16:55 So GSM doesn't work ither? Oct 03 17:17:10 nope Oct 03 17:17:23 well - you need to load a serial module Oct 03 17:17:34 or build it in Oct 03 17:17:44 which is Oct 03 17:17:56 dunno Oct 03 17:18:15 i just build andy-tracking Oct 03 17:18:24 so i guess, something is going wrong with this kernel Oct 03 17:18:40 If there are modules built, then instlal them all Oct 03 17:20:49 can you give me a lsmod Oct 03 17:20:52 on yours ? Oct 03 17:22:14 not got FT Oct 03 17:22:15 FR Oct 03 17:22:29 and the neo1973 I does have ahas it as a builtin I think Oct 03 17:22:40 go through menuconfig and look for things that say serial Oct 03 18:13:00 how to put neo on suspend mode from ssh Oct 03 18:16:00 DocScrutinizer, PaulFertser.. sorry for such a late respond, but anyway, i've launched the ATD*101# command via mickeyterm and i got a valid respond Oct 03 18:16:32 before i was using a different command in mickeyterm, that's probably why I didn't succeed Oct 03 18:16:39 zear: ATD? ussd are supposed to work with other command, yes. Oct 03 18:18:03 nah USSD work with ATD just fine Oct 03 18:18:06 i still can't call that number from the gui however Oct 03 18:18:39 here it works Oct 03 18:18:47 zear: that's because GUI uses framework and it uses that dedicated command. Oct 03 18:19:09 nope it doesn't, on three digit commands Oct 03 18:19:29 oh well, if I can call that number via mickeyterm, it's all i need ;) Oct 03 18:19:44 just a question, how can i do that via bash script? Oct 03 18:19:50 i'd like to have a simple command for that Oct 03 18:19:57 DocScrutinizer: at least Zhone did ussd for anything that started with * iirc. Oct 03 18:20:19 btw it also doesn't work on two digit commands, otherwise the result on dialing *#61# was "Disabled" and not an empty screen Oct 03 18:21:41 PaulFertser: USSD is the response handling, for actual cmd fso needs to find the command in a list and select the corresponding dedicated AT-cmd instead of ATD Oct 03 18:22:04 there is no USSD specs for 3-digit Oct 03 18:22:53 and obviously fso doesn't know aout the "*#xx#" ones (the query cmds) Oct 03 18:23:42 anyway with SHR-U88 dialing *101# works here, from mickeyterm as well as from dialer Oct 03 18:24:31 DocScrutinizer: FSO always uses +CUSD=1,"%s",15 to send ussd. Oct 03 18:24:34 and as long as I don't see the mickeyterm ATD result, I won't bother anymore as it's useless guess effort Oct 03 18:25:00 oh well, whatever Oct 03 18:25:01 PaulFertser, that's the command that results in ERROR for me Oct 03 18:25:22 zear: i understand. Let me tell you the cli method to do ATD Oct 03 18:25:30 no wonder, it's invalid for 3digit numbers Oct 03 18:25:55 wtf?! it WORKS here Oct 03 18:26:05 nah, bye Oct 03 18:28:55 zear: dbus-send --type=method_call --print-reply --system --dest=org.freesmartphone.ogsmd /org/freesmartphone/GSM/Call org.freesmartphone.GSM.Call '*102#' voice Oct 03 18:29:35 PaulFertser, thanks Oct 03 18:29:40 zear: does it work? Oct 03 18:29:44 and thank you all guys for finding the solution Oct 03 18:29:52 haven't checked yet, just assumed it does ;D Oct 03 18:30:27 PaulFertser, ah, nope Oct 03 18:30:33 bus-send: Data item "*101#" is badly formed Oct 03 18:34:37 zear: i've got the same problem here Oct 03 18:35:51 h4v, ah, so i'm not alone. That's good, maybe a fix can be produced if there is more of us :D Oct 03 18:36:12 zear: "string(*101#)"? Oct 03 18:36:24 zear: oh sorry Oct 03 18:36:28 zear: dbus-send, of course Oct 03 18:37:02 zear: "string:*101#" Oct 03 18:48:47 PaulFertser, you mean org.freesmartphone.GSM.Call 'string:*101' voice Oct 03 18:50:02 openmoko: 03rehar * r5667 10/trunk/gta02-core/ (8 files): added footprint names to components Oct 03 18:54:50 zear: yes, if you intend to call *101 Oct 03 18:55:10 that returns dbus-send: Data item "voice" is badly formed Oct 03 18:55:37 org.freesmartphone.GSM.Call 'string:*101' 'sring:voice' ? Oct 03 18:55:37 should i remove the voice parameter? Oct 03 18:56:50 Kagee, nah, that just leads to another error Oct 03 18:56:50 Error org.freedesktop.DBus.Error.UnknownMethod: Method "Call" with signature "ss" on interface "org.freesmartphone.GSM" doesn't exist Oct 03 18:57:01 zear: yes string:voice Oct 03 18:57:55 PaulFertser, http://pastebin.com/m5d3ea214 Oct 03 18:58:09 zear: dbus-send --type=method_call --print-reply --system --dest=org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Call.Initiate 'string:*102#' string:voice Oct 03 18:58:54 PaulFertser, ok, that does something Oct 03 18:59:40 the command is being executed and returns to the console, while i can hear via the speakers some data is being send Oct 03 18:59:58 but nothing is being returned either on the TTY, or in the gui Oct 03 19:00:46 http://pastebin.com/m4f2eba19 Oct 03 19:00:51 zear: i'm not sure it's supposed to be. Because you're using non-ussd method for ussd. Oct 03 19:01:00 :P Oct 03 19:20:46 I'd like to thank you guys for your help somehow Oct 03 19:20:51 so have this little game i ported: http://91.192.165.7:8002/powder111_fr.tar.bz2 Oct 03 19:27:37 zear: please don't recommend non-free software here :( Oct 03 19:28:04 lindi-, hey, it's free Oct 03 19:28:08 wI have no problem as long as it's stated to be non-free Oct 03 19:28:10 the source is open Oct 03 19:28:13 it's just not GPL Oct 03 19:28:36 zear: it says 'Do not modify the POWDER binary nor accompanying files.' Oct 03 19:28:47 i didn't modify them in a bit Oct 03 19:28:51 i just recompiled them ;) Oct 03 19:29:19 zear: can I modify powder binary? Oct 03 19:29:37 lindi-, the author encourages people to port his game to new platforms Oct 03 19:29:46 zear: that did not answer my question Oct 03 19:29:56 lindi-, i'd say read the license Oct 03 19:30:06 zear: i did Oct 03 19:30:11 zear: it looks non-free to me Oct 03 19:30:49 lindi-, i've played it on so many platforms so i can say the author has nothing against about using his code Oct 03 19:31:02 zear: that does not help if he is not giving the permission in writing Oct 03 19:32:22 lindi-, oh right, i almost forgot, the code is on Creative Commons Sampling Plus license Oct 03 19:32:31 zear: how could I know that? ;) Oct 03 19:32:53 not my problem, he should have put it in the readme Oct 03 19:33:14 http://www.zincland.com/powder/index.php?pagename=release here's where you can get the code and find out about the license Oct 03 19:33:14 zear: where can I get the source? Oct 03 19:33:17 ;D Oct 03 19:33:56 now I need to figure out if that CC license is free Oct 03 19:35:30 just look at the changelog, there are so many contriburors and ports, that this game must be Stallman-friendly ;) Oct 03 19:35:54 zear: the COPYING says "1) This is *NOT* an Open Source license. This code is not "free"." Oct 03 19:36:12 and where does it say "You can't port it to a new platform"? Oct 03 19:36:38 zear: where does it say that I can modify it? Oct 03 19:37:06 oh c'mon, why don't you start enjoy playing this game instead? :D Oct 03 19:37:10 zear: eh? Oct 03 19:37:21 zear: you are trying to trick me into running non-free software? Oct 03 19:37:41 lindi-, i can send a mail to the author and ask him for the permission, if thay'll make you feel better ;) Oct 03 19:37:54 zear: well the author itself says that it is not free Oct 03 19:37:57 zear: so why bother? Oct 03 19:38:07 because it's a nice game? Oct 03 19:38:11 zear: the author should should change license to one of the "free software", otherwise it's disappointing. Oct 03 19:38:13 zear: it's a non-free game Oct 03 19:38:13 and runs on your favoutite phone? Oct 03 19:38:37 zear: do you understand that freedom matters more than "nice games" to some people? Oct 03 19:38:41 oh like freerunner is all open-source Oct 03 19:38:53 http://triplane-class.sf.net is a nice game that we liberated and ported (GPLv3+) Oct 03 19:38:54 zear: except the firmware Oct 03 19:39:04 yeah, that's what i'm talking about ;) Oct 03 19:39:11 and lack of 3d chip support Oct 03 19:39:22 zear: why did you say that the game is free? Oct 03 19:39:45 i agree with you that opensource is the best solution, but it's his game and he can license it however he wants Oct 03 19:40:02 because this game is free, he doesn't charge you for it Oct 03 19:40:36 zear: so you have a different definition for free software? how can you be on this IRC network? Oct 03 19:41:03 according go CC sampling plus 1.0 license: "You are free to perform, display, and distribute copies of this whole work for noncommercial purposes (e.g., file-sharing or noncommercial webcasting)." Oct 03 19:41:22 lindi-, no, i love GPL as much as you guys Oct 03 19:41:55 just if the code is licensed under the CC+1.0, it means it is free to some extent Oct 03 19:42:12 zear: according to COPYING the code is not "free" or "open source" Oct 03 19:42:40 so why is it released on CC+ license? Oct 03 19:42:50 zear: there are multiple licenses Oct 03 19:42:58 zear: I haven't yet even analyzed them all Oct 03 19:43:04 and that means i can choose the one i like, right? Oct 03 19:43:23 zear: no, different licenses have been granted to different parts of it Oct 03 19:43:52 ok, i'll send a mail to the author, asking him if we're allowed to run this game on fr Oct 03 19:43:56 zear: but if the author says that it is "not an open source license" I don't think I bother to review it Oct 03 19:44:12 zear: running is only freedom 0 Oct 03 19:44:23 zear: i want freedoms 1, 2 and 3 too Oct 03 19:44:32 I want freedom 7! Oct 03 19:44:39 lindi-, maybe you should read the last section of the LICENSE.TXT ;) Oct 03 19:45:17 zear: it just makes things even more unclear Oct 03 19:45:25 :P Oct 03 19:46:15 oh well, i can port another game if you don't like this one :P Oct 03 19:46:38 zear: i might like the game, I just want to be able to share and change the software I use :) Oct 03 19:47:29 lindi-, i've been observing this project for a longer time and i know that the author encourages people to modify the code, and port it to new platforms Oct 03 19:47:42 just look at the changelog, there are many contributors Oct 03 19:47:46 zear: he should express that in writing Oct 03 19:47:50 or she Oct 03 19:47:52 lindi-, i agree Oct 03 19:48:55 zear: if you really think so please ask him to pick an already existing license Oct 03 19:49:18 zear: MIT, LGPL, GPL, Apache -- something Oct 03 19:49:26 lindi-, i'll mail him, as i plan to release this port as .ipk and maybe upload it on opkg.org or something Oct 03 19:49:53 lindi-, if you have nothing against, i might include this conversation in the mail, what you think? Oct 03 19:49:54 zear: having a custom license is very suspicious Oct 03 19:49:58 zear: sure Oct 03 19:50:11 zear: include my email address too. timo.lindfors@iki.fi Oct 03 19:50:16 hehe, ok Oct 03 19:51:13 lindi-, but so far, please, if you have time, check this game out and report any problems Oct 03 19:51:39 so far it looks 100% playable on the touchscreen, but i haven't really tested it yet Oct 03 19:52:01 zear: thanks but no thanks, i don't want to run non-free stuff :( Oct 03 19:52:11 lindi-, :P Oct 03 19:57:17 lindi-: btw, i think that emergency shutdown is done by hardware in some pcf50633 versions but i'm not sure what gta versions used that. Oct 03 20:13:02 hmm Oct 03 20:13:45 * DocScrutinizer-8 tries to grep for emergency shutdown Oct 03 20:18:22 openmoko: 03rehar * r5668 10/trunk/gta02-core/ (cpu-power.sch cpu.sch modem.sch sd-sim.sch wlan.sch): added more footprint names to components Oct 03 20:28:38 DocScrutinizer-8: probably it was a feature of pcf50606 even Oct 03 20:28:47 DocScrutinizer-8: i mean you hold pwr for some time and it shuts off. Oct 03 20:29:14 hard shutdown after 8sec is a hw-feature afaik Oct 03 20:30:10 MAYbe I recall incorrect and it's a feature of 50606 only, but I can't believe that Oct 03 20:33:48 actually I seem to remember it a kind of watchdog which you can stop by actively writing to some register, otherwise it will shutdown hard after 8sec Oct 03 20:34:26 also iirc: you need to setup tha "watchdog" Oct 03 20:35:11 DocScrutinizer-8: i know that in the latest kernel it's implemented as a pure software feature. Oct 03 20:35:51 yep, "pressed for 1 sec" "...2 sec" ... Oct 03 20:36:04 dunno why Oct 03 20:38:28 DocScrutinizer-8: hardware feature of pcf50633 is described at page 20 Oct 03 20:38:40 though that printk (if it even is) doesn't proove that's the kernel which does actual shutdown Oct 03 20:39:17 PaulFertser: you know how to lure me in ;-) Oct 03 20:40:58 if onkey_mode control bits configured accordingly; see Table 12). Oct 03 20:41:26 8 seconds, the PCF50633 enters Standby mode if no action is taken by the host controller Oct 03 20:41:29 :-) Oct 03 20:41:33 DocScrutinizer: sure but i'm still puzzled why that 8 sec software thing was introduced. Oct 03 20:41:44 I love it when I was right :-P Oct 03 20:42:10 PaulFertser: no idea. Where do you cnclude from it's a software thing? Oct 03 20:42:15 DocScrutinizer, if the GSM is on and you switch off the divice, maybe you must all the gsm_dev_off function? Oct 03 20:42:16 DocScrutinizer: hehe Oct 03 20:42:37 panicking: for gta01 yes. for 02 no Oct 03 20:42:38 panicking: hm, seems to be right but not applicable to gta02 Oct 03 20:42:42 :D Oct 03 20:43:28 DocScrutinizer, but yesterday some boy sead that is direct connect to the battery Oct 03 20:43:36 and it's switch off using a gpio Oct 03 20:43:39 panicking: on gta01 it is Oct 03 20:43:48 panicking: on gta02 only RF part is directly connected. Oct 03 20:43:58 ok thanks PaulFertser Oct 03 20:44:07 panicking: I don't care what some boys say about "my" schametics ;-P Oct 03 20:44:24 DocScrutinizer: + /* Some revisions of the chip don't have a 8s standby mode on Oct 03 20:44:28 + * ONKEY1S press. We try to manually do it in such cases. */ Oct 03 20:44:32 (from the sources) Oct 03 20:44:44 By Balaji Oct 03 20:45:01 bah, what's THAT??? Oct 03 20:45:29 I wonder where balaj got that info from?? o.O Oct 03 20:45:52 Please ignore everything I say Oct 03 20:45:58 At all times. Oct 03 20:46:07 huh? Oct 03 20:46:14 * SpeedEvil was thinking of gta01 when I said the above. Oct 03 20:46:16 SpeedEvil: you're well? Oct 03 20:46:44 SpeedEvil: yu said what? Oct 03 20:47:08 aaah, you were "the boy"? :-DD Oct 03 20:47:10 something about Gsm being connected direclty to battery Oct 03 20:47:41 SpeedEvil: afaik it's correct for *you*, no? Oct 03 20:47:49 yes Oct 03 20:48:10 Though not now, as battery not installed Oct 03 20:48:36 PaulFertser: well, no harm in kernel trying to behave as well ;-) Oct 03 20:49:07 PaulFertser: nevertheless we should take care the ""onkey_mode control bits configured accordingly"" Oct 03 20:49:44 DocScrutinizer: the datasheet puzzles me. I can't easily find description of differences of different variants. Though it looks like only reset values depend on that anyway. Oct 03 20:50:48 PaulFertser: and we should proceed on scrupulous interogation of balaj for that nonsense Oct 03 20:51:42 PaulFertser: http://people.openmoko.org/joerg/pcf50633/pcf50633-variants.txt et al Oct 03 20:54:22 http://people.openmoko.org/joerg/pcf50633/PCF50633HN-09-N3rev0.1.pdf Oct 03 20:54:29 DocScrutinizer: nice Oct 03 20:54:29 PaulFertser: o.O Oct 03 20:54:37 imo there is no 'special' handling required to prevent hardware 8s timeout Oct 03 20:54:37 DocScrutinizer: but looks like it affects reset values only. Oct 03 20:54:43 maybe balaj is right Oct 03 20:55:08 DocScrutinizer: how so? Oct 03 20:55:16 no he isn't. Sure that's only reset defaults Oct 03 20:55:52 larsc: we don't want to prevent it ;-D Oct 03 20:55:55 DocScrutinizer: probably we should introduce a sysfs node to make that behaviour configurable and remove pure software solution. Oct 03 20:56:00 we want to *enable* it Oct 03 20:56:25 PaulFertser: sounds sensible to me Oct 03 20:56:32 PaulFertser: can you do that? Oct 03 20:57:27 DocScrutinizer: lindi- wants to Oct 03 20:57:33 DocScrutinizer: technically, yes, practically not sure, too many things i've already promised and haven't done :-/ Oct 03 20:57:53 same here :-/ Oct 03 20:57:58 larsc: so to prevent it we can just disable it, no need to reset watchdog or whatever. Oct 03 20:58:12 lindi is welcome to give some love to that topic Oct 03 21:00:19 so you want the device to be turned of after pressing the power key for 8s? Oct 03 21:01:22 larsc: some people want, lindi- doesn't. I don't care much but i'd like users to have a choice. Oct 03 21:01:38 PaulFertser: start of p.21 is highly interesting Oct 03 21:02:16 larsc: but if i needed to choose between options, i'd disable that emergency shutdown because it's the same as to pull out the battery which is trivial (and even faster). Oct 03 21:02:40 veto Oct 03 21:02:57 I love a decent switch to power down uncond Oct 03 21:03:39 DocScrutinizer: it's nice to have that stuff on my sandisk sansa because there i'd need some disassembly to physically pull the plug. Not an issue on gta. Oct 03 21:03:54 and there's a whole bunch of situations where you can't "simply remove bat" Oct 03 21:04:55 DocScrutinizer: if one wants to just avoid hard lockup he'll use hardware watchdog in SoC i guess. Oct 03 21:05:50 I never used hardware watchdog so far, as nobody made that a simple opt-in at config Oct 03 21:06:14 * DocScrutinizer mumbles ramconsole, ramconsole... Oct 03 21:06:21 DocScrutinizer: on debian it's as simple as "apt-get install watchdog" or something like that. Oct 03 21:06:40 if the soc is locked up the hw timeout will work anyway Oct 03 21:07:01 at least if i understand the manual correctly Oct 03 21:07:16 let's change the POV -- why would anybody get rid of that feature?? Oct 03 21:07:54 larsc: if onkey_mode control bits configured accordingly Oct 03 21:08:16 DocScrutinizer: i'm not to sure about that Oct 03 21:08:25 but I am Oct 03 21:09:03 ONKEY_MODE ONKEY mode selection 00 (Wake-up by Oct 03 21:09:05 (7,6) 00: Wake-up by falling edge only falling edge only) Oct 03 21:09:06 01: Wake-up by falling edge, next 1 sec. Oct 03 21:09:08 low sets the time-out timer to 8 seconds. Oct 03 21:09:09 10: Wake-up by falling edge, rising edge Oct 03 21:09:11 sets the time-out timer to 8 seconds. Oct 03 21:09:12 11: Reserved Oct 03 21:09:58 DocScrutinizer: to be able to use pwr button the only that can be used to wake up the device for special purposes, e.g. lindi- wants to initiate recording of a voicenote and continue until it's depressed. Oct 03 21:10:10 larsc: we have default of "00" (on HN09-N3 variant) and we need "01" Oct 03 21:11:20 DocScrutinizer: watchdog is superior solution that is already works and has benefits comparing to this pcf50633 feature, at least it seems so to me. Oct 03 21:11:28 s^ is^^ Oct 03 21:11:45 well, we could do that with HOLD button, but yes I see the usecase. No problem to change ONKEY_MODE then Oct 03 21:12:19 DocScrutinizer: yes, hold button but i'm not sure how to properly leave mic bias on during suspend. Oct 03 21:12:20 PaulFertser: nope. I don't want uninvited boot Oct 03 21:12:37 I want forced unconditional shutdown on my command Oct 03 21:13:00 DocScrutinizer: when is possible to hold power but not possible to pull out the battery? Oct 03 21:13:29 (leave on) duh hat's simple: power WM8753 and set according #control Oct 03 21:14:04 e.g when you can't use both hands Oct 03 21:14:07 during car driving Oct 03 21:14:16 DocScrutinizer: atm i'm trying just that: pulling out the battery with one hand Oct 03 21:14:20 esp if device is in a cradle Oct 03 21:14:23 etc etc Oct 03 21:14:26 DocScrutinizer: works if i use my chest too :) Oct 03 21:14:45 can you press both buttons at the same time with one hand? Oct 03 21:15:15 larsc: i can Oct 03 21:15:22 nope, no admittance from HW and system architects department for disabling hard shutdown by default Oct 03 21:15:36 DocScrutinizer: ok :) Oct 03 21:15:44 anyway. imo it's not the kernel who should device whether to turn of the device or not but userspace Oct 03 21:16:04 s/device/decide/ Oct 03 21:16:04 larsc meant: anyway. imo it's not the kernel who should decide whether to turn of the device or not but userspace Oct 03 21:17:34 if someone doesn't like the behaviour then (s)he can reprogram OOCMODE - OOC mode register (address 10h) 7:6 onkey_mode quite easily Oct 03 21:18:18 sure Oct 03 21:19:14 I agree we should get rid of, or make en/disable-able the kernel sw-"watchdog" for the 8sec press Oct 03 21:19:38 and ask balaj WTH he thought when writing this patch Oct 03 21:20:39 that's *very* unpolite to state things like "not all variants of 50633 have..." and NOT provisioning any reference Oct 03 21:21:39 DocScrutinizer: probably it was copied from an earlier driver, who knows. Oct 03 21:22:02 If I were boss of a project, I'd ask a coworker to meet me in my room for 15min talk, on such a patch without reference Oct 03 21:25:32 anyway, a sysfs node to change OOCMODE - 7:6 to 00 or 01, called sth power/pwrbutton_hard_shutdown with values enabled for 01 and disabled for 00 is easily implemented I think Oct 03 21:25:36 only 15 minutes? Oct 03 21:26:01 anothe similar one for kernel-timer was nice :-) Oct 03 21:26:24 ndnihil: probably only 5, as there's rather few to say on that Oct 03 21:26:53 hm... wouldn't it be better to set it always to 01 and make the use of totrst configurable? Oct 03 21:26:58 either they know their way around after 5min, or probably another 10 won't help Oct 03 21:27:23 err what's totrst?? Oct 03 21:27:40 read section 8.1.6.3 Oct 03 21:29:34 hmm, that is more like a "feeding the watchdog". Not sure if we need that Oct 03 21:30:10 DocScrutinizer: i've checked, there was no comment in the old driver, looks like Balaji introduced it. Oct 03 21:30:39 of course it would be a much smarter way if lindi's recording app would feed the dog, and if it hangs we still get usual hard shutdown Oct 03 21:32:06 but eventually we need to reset the shutdown condition anyway I guess, otherwise I dunno what exactly happens after we release pwrbutton after 30sec and feeding the dog stops Oct 03 21:36:16 a recording app shouldn't bother about the special features of some random power supply device Oct 03 21:37:05 heh, if I read correctly, the 8sec timer is *triggered* after 1sec of pwrbutton press, but it's not a condition for the transition to standby to hold the button after that Oct 03 21:38:36 yup Oct 03 21:39:08 so it's up to the kernel anyway to watch the button stays being pressed, by doing a totrst every second, and after 8sec to shutdown gracefully. If kernel fails to do that at least once in 8sec, then hw-shutdown will trigger Oct 03 21:40:08 maybe make that timeout configurable via sysfs. Oct 03 21:41:45 yes, the 8sec is just an arbitrary timeout to give kernel a chance to react. But actual duration to press pwrbutton is determined by kernel anyway (except if kernel hangs in which case a 1 sec press should suffice to shutdown 8sec later) Oct 03 21:42:27 this kernel timeout (actually kind of a loop counter) is easily configurable via sysfs, a 0 might mean disable Oct 03 21:43:19 aka "infinite reset of pwrbutton timer" Oct 03 21:43:30 yes Oct 03 21:43:47 :-) Oct 03 21:44:14 I *love* a clear short easy spec Oct 03 21:48:10 so who's c&p this to a ticket now? probably that's up to lindi- , no? ;-D Oct 03 21:52:29 aah, and: writing to this sysnode resets kernel counter/timer to whatever that value is that's been written (means a e.g 8sec timeout that's half expired gets reset to 8sec on writing "8" to that sysnode). This way lindis recording app could behave cute and readout the default that's been set by whomever from that sysnode, and on pwrbutton press detection the app would periodically write back that value (e.g "8") to same node, to Oct 03 21:52:31 prevent shutdown Oct 03 21:52:55 larsc: i disabled that 8 sec timeout in my kernel completely Oct 03 21:53:37 lindi-: that's fine but won't make it "upstream" ;-P Oct 03 21:54:14 make the default kill the device but supply a /sys node to disable it would be fine for me Oct 03 21:54:14 I think it's better to fix that for good, in a most flexible and powerful manner Oct 03 21:55:55 lindi-: you can write "0" to that sysnode (if youre nasty and lazy ;-P), or you read out the initial value and write that value back periodically to abort shutdown timeout whenever you detect the powerbutton is pressed Oct 03 21:55:56 the most flexible and powerful way to solve this would be to remove the timeout from the kernel completly and let some userspace daemon mointor the input device and turn the device of after some amount of time Oct 03 21:56:07 or present a shutdown dialog to the user Oct 03 21:56:10 or whatever Oct 03 21:57:01 larsc: perhaps. and then also additionally use hardware watchdog to detect kernel lockup (which would be better than what we currently do) Oct 03 21:57:12 (we = what most be people do) Oct 03 21:57:29 larsc: btw, about the patch, is it in some git branch already? Oct 03 21:58:40 lindi-: as elaborated above (most clearly I hope) we NEED a kernel driver to periodically reset the powerbutton timer in PMU anyway. So I think it's a really bad idea to delegate such most important and highlevel function to userland Oct 03 21:59:21 DocScrutinizer: is that an issue on gta02 too? my device stays running even though I disabled that 8 sec shutdown Oct 03 21:59:35 DocScrutinizer: I just set #define PCF50633_ONKEY1S_TIMEOUT -1 Oct 03 21:59:39 lindi-: no Oct 03 21:59:43 larsc: ok. Oct 03 22:00:06 DocScrutinizer: and after that I can hold power button down as long as I want without shutdown Oct 03 22:00:17 anyways, i need some sleep now, it's 1 am already Oct 03 22:00:22 lindi-: I'm only talking about pcf50633 atm, though I think pcf50606 may be similar Oct 03 22:01:02 lindi-: I have no idea what that define does Oct 03 22:01:15 I know what PCF50633 does though Oct 03 22:02:17 if we don't enable OOCMODE - OOC mode register (address 10h) 7:6 by setting it to "01" then hw shutdown doesn't work at all Oct 03 22:03:01 guys how is it that andy-tracking compiled kernel is > 2.3 mb? Oct 03 22:03:15 where can i find a .config for less then 2mb Oct 03 22:03:16 ? Oct 03 22:04:37 Guest80031: though the last 1h might look different, this isn't probably the channel to ask this. /join #openmoko-cdevel ;-) Oct 03 22:04:47 Guest80031: https://dev.openwrt.org/browser/trunk/target/linux/s3c24xx/config-2.6.30 Oct 03 22:05:29 or that :-D **** ENDING LOGGING AT Sun Oct 04 02:59:56 2009