**** BEGIN LOGGING AT Wed Oct 29 02:59:57 2008 Oct 29 03:00:35 BobOfDoom: is it sdio? Oct 29 03:00:50 no Oct 29 03:00:51 CF Oct 29 03:00:59 or PCMCIA Oct 29 03:01:07 or whatevery you want to call it Oct 29 03:01:43 BobOfDoom: Thanks! :) Oct 29 09:45:20 gm Oct 29 09:55:54 Sleep_Walker: morning Oct 29 09:56:10 oh, I forgot to merge my branch Oct 29 09:56:21 Sleep_Walker: have you gotten 680's modem to be happy when it wasn't turned on in palmos before booting? Oct 29 09:56:36 BobOfDoom: I'm not sure Oct 29 09:56:41 Sleep_Walker: when I boot with it on.. everything is happy.. gpio 57 acts as wake Oct 29 09:57:23 weird Oct 29 09:57:27 Sleep_Walker: when I boot with it off.. I set 14 to input, then set 40 and 87 high and it talks briefly but stops responding very quickly, also AT+CFUN=1 stops it responding (it doesn't ok that) Oct 29 09:57:43 is it possible to have IrDA enable and GSM wake connected ? :/ Oct 29 09:57:46 gpio 57 appears to have no efefct when in that situation Oct 29 09:58:00 why do you think 57 has something do with IrDA? Oct 29 09:58:55 I found it somewhere in GPIOtrace, but if you think that it is not - I'll redump Oct 29 09:59:09 hmm ok Oct 29 09:59:16 well I haven't really tested IRDA Oct 29 09:59:26 I observe 115 havinf something to do with it Oct 29 09:59:52 but I haven't tried beaming something while gpiotrace is running Oct 29 10:00:15 I think it's unlikely that they'd multiplex irda stuff with gsm.. but who knows.. Oct 29 10:00:18 hmmmmmmm Oct 29 10:12:38 weird Oct 29 10:12:42 I can't see it now Oct 29 10:19:43 probably coincidence Oct 29 10:24:40 so 57 is GPIO wake? Oct 29 10:24:50 that means it won't stop responding? Oct 29 10:25:13 btw. have you found any other purpose of 79 than red led? Oct 29 10:25:31 when I control GSM, red led is always on Oct 29 10:28:16 hmm Oct 29 10:29:12 dunno Oct 29 10:29:15 yeah Oct 29 10:29:19 57 is wake Oct 29 10:29:26 well when palmos has inited it Oct 29 10:29:38 it doesn't behave right when we turn on from in linux Oct 29 10:29:54 I've been going through every other output GPIO Oct 29 10:30:01 but I can't find any difference Oct 29 10:35:05 I'll boot and try Oct 29 11:29:38 hmmm, I can't Oct 29 13:58:20 BobOfDoom: I can get answer from GSM chip, but it falls asleep quickly I think Oct 29 14:01:21 echo "0" > /sys/class/leds/red/brightness &&echo "1" > /sys/class/leds/red/brightness &&echo "0" > /sys/bus/platform/devices/treo680-pm/gsm_power_on && echo "1" > /sys/bus/platform/devices/treo680-pm/gsm_power_on && echo "0 " > /sys/bus/platform/devices/treo680-pm/gsm_wake && echo "1" > /sys/bus/platform/devices/treo680-pm/gsm_wake && minico Oct 29 14:01:39 not all is probably important Oct 29 14:02:01 btw. I added `AT+CFUN=1' into minicom init string to have quick response Oct 29 14:02:11 but is still falls asleep quickly Oct 29 14:02:26 *MRDY: 1 Oct 29 14:02:27 OK Oct 29 14:02:29 OK Oct 29 14:02:30 +CREG: 2 Oct 29 14:02:32 +CGREG: 2 Oct 29 14:02:33 *MRDY: 4 Oct 29 14:02:35 *MTSMENU: "Vodafone", 0, 3 Oct 29 14:02:36 1:"Info&Zabava",0 Oct 29 14:02:38 2:"M-Banka",0 Oct 29 14:02:39 3:"M-Platby",0 Oct 29 14:02:41 AT Oct 29 14:02:43 *MTZ: 1, "VodafoneCZ" Oct 29 14:02:47 *MTZ: 2, "10/29/2008, 15:00:47+04", 0 Oct 29 14:02:49 OK Oct 29 14:02:51 +CREG: 1 Oct 29 14:02:55 and then I can't get any response Oct 29 15:07:02 huh, finally pushed :b **** ENDING LOGGING AT Thu Oct 30 01:32:09 2008 **** BEGIN LOGGING AT Thu Oct 30 01:32:37 2008 **** ENDING LOGGING AT Thu Oct 30 02:59:57 2008