**** BEGIN LOGGING AT Wed Jun 23 02:59:56 2010
Jun 23 04:39:50 <JaMa> mrmoku|away: ah, this happen only with very latest 2.6.34 right? I noticed it once, then I expected it was some other issue and didn't check it (and returned to 2.6.32 because of touchscreen filtering)
Jun 23 05:25:27 <leviathan> when I go into farnell livechat from switzerland I come to an australian guy
Jun 23 05:25:29 <leviathan> okee....
Jun 23 05:25:42 <leviathan> why australia?
Jun 23 05:25:51 <leviathan> and what exactly is technical live chat for?
Jun 23 05:25:57 <leviathan> questions over question
Jun 23 05:26:05 <leviathan> I wrote they should use irc ;-)
Jun 23 05:37:35 <mrmoku> JaMa: yeah, was with 2.6.34-oe4
Jun 23 05:41:44 <JaMa> mrmoku: then we should discuss it with ThibG 
Jun 23 05:42:32 <mrmoku> JaMa: ok
Jun 23 05:42:49 <JaMa> mrmoku: because I think only those glamo patches changed between oe3 and oe4
Jun 23 05:43:14 <mrmoku> JaMa: I want to attack the WSoD and try random numbers for the different mdelays in there (as suggested by Weiss) :P
Jun 23 05:48:15 <ThibG> yes?
Jun 23 05:54:50 <JaMa> ThibG: any hint why would be /sys/bus/platform/devices/gta02-pm-gsm.0/power_on gone after those glamo patches (which are already aplied in om git), I was thinking that moving from mfd is first changing of KCONFIGs..
Jun 23 05:56:13 <ThibG> did that work earlier (with the 2.6.34 branch)?
Jun 23 05:57:00 <JaMa> 80% yes
Jun 23 05:57:56 <JaMa> I can reboot back to oe3 tonight to be sure..
Jun 23 05:58:09 <ThibG> ok
Jun 23 05:58:10 <JaMa> Just wanted to ask if it's known or expected
Jun 23 05:58:21 <ThibG> neither known nor expected :/
Jun 23 05:58:45 <ThibG> the only change in Kconfig is to select GPIO_EXTEND64 afaik
Jun 23 05:59:11 <JaMa> I think that whole  gta02-pm-gsm.0/ was missing, but ie  gta02-pm-gps.0 was there
Jun 23 05:59:23 <JaMa> SHR root@gojama ~ $ zcat /proc/config.gz | grep S3C24XX_GPIO
Jun 23 05:59:23 <JaMa> CONFIG_S3C24XX_GPIO_EXTRA=64
Jun 23 05:59:23 <JaMa> CONFIG_S3C24XX_GPIO_EXTRA64=y
Jun 23 05:59:23 <JaMa> CONFIG_SPI_S3C24XX_GPIO=y
Jun 23 05:59:33 <JaMa> that was enabled here even before
Jun 23 05:59:37 <ThibG> yes
Jun 23 05:59:46 <ThibG> but you had to modify .config manually
Jun 23 06:00:00 <ThibG> (you can't even use the menu for that)
Jun 23 06:00:54 <ThibG> odd, gta02-pm-gsm is part of CONFIG_MACH_NEO1973_GTA02, so, it can't be because of a config issue...
Jun 23 06:01:43 <ThibG> and power_on is a device attribute, I don't really see how it can disappear if the module is loaded :/
Jun 23 06:01:58 <JaMa> but you're right about defconfig http://git.openmoko.org/?p=kernel.git;a=blobdiff;f=arch/arm/configs/gta02_drm_defconfig;h=e9665392b1bca5259337dd01e9d77edd7a04c0bb;hp=05aa1304af982027ff5d244b49ca5a0084db6a1d;hb=d63ade17a0274b3b3f662fa381c4bb496bbf2ca9;hpb=8b604bd0f2f3e097bb2fc8b558a0f4e6ca7bdb13 /CONFIG_S3C24XX_GPIO_EXTRA shows =0
Jun 23 06:03:27 <ThibG> huh? Odd, I wouldn't expect this to work
Jun 23 06:05:15 <JaMa> then let me first to confirm it on older build (oe[123]), I don't want to bother you if it is my defconfig issue in the end.. :)
Jun 23 06:06:10 <ThibG> well, if the problem is with power_on, it doesn't have to do with the config, I guess...
Jun 23 06:06:11 <JaMa> I'm pretty sure I did test call on some .34 build, but don't remember which version it was, so maybe it was before this defconfig update.. and I failed to notice this..
Jun 23 06:06:49 <JaMa> and maybe this config is "fixed" in make oldconfig (by some select statement somewhere)
Jun 23 06:07:50 <ThibG> if you haven't S3C24XX_GPIO_EXTRA64 selected, glamo-gpio should fail to register
Jun 23 06:07:58 <ThibG> and you won't have JBT working
Jun 23 06:08:16 <ThibG> but everything else should be ok
Jun 23 06:10:45 <JaMa> and without JBT I wouldn't have backlight right?
Jun 23 06:11:14 <JaMa> I'm pretty sure I did have backlight on while seeing gta02-pm-gsm.0 gone
Jun 23 06:11:16 <ThibG> not sure, I had, 'cause U-Boot was turning it on for me
Jun 23 06:11:26 <JaMa> I'm using qi
Jun 23 06:11:32 <JaMa> and kms
Jun 23 06:11:48 <ThibG> prior to the Kconfig change (http://git.openmoko.org/?p=kernel.git;a=commit;h=5909f8586cb94c2cbca9605282711f1eadbec5e1) I would expect make oldconfig to *unselect* EXTRA64
Jun 23 06:11:59 <ThibG> IMO, that's unrelated
Jun 23 06:12:32 <ThibG> (and you had display working? or white screen?)
Jun 23 06:19:23 <JaMa> it's working here, but mrmoku/Rui seen white quite a lot on same kernel builds..
Jun 23 06:21:08 <ThibG> Hm ok
Jun 23 06:23:02 <mrmoku> JaMa: correct the gps and bt power nodes were there
Jun 23 06:23:41 <mrmoku> JaMa: I can install oe3 and test
Jun 23 06:24:23 <ThibG> mrmoku, so, you confirm those nodes mysteriously disappeared?
Jun 23 06:24:32 <mrmoku> ThibG: only the gsm one
Jun 23 06:24:47 <ThibG> ok
Jun 23 06:24:58 <mrmoku> ThibG: were there with latest is what I wanted to say :)
Jun 23 06:25:06 * mrmoku switched back to old kernel
Jun 23 06:25:35 <ThibG> when did it disappear, so?
Jun 23 06:25:52 <DocScrutinizer> backlight and LCD via jbt6k74 are completely distinct functions
Jun 23 06:26:21 <mrmoku> ThibG: installing oe3 now to see if it is there
Jun 23 06:26:29 <ThibG> mrmoku, ok
Jun 23 06:27:31 <mrmoku> JaMa: which one to try? oe3 or oe4+git3 ?
Jun 23 06:28:27 <DocScrutinizer> backlight is controlled in PCF50633
Jun 23 06:28:50 <DocScrutinizer> with no connection to glamo or jbt
Jun 23 06:29:16 <ThibG> thanks, DocScrutinizer
Jun 23 06:29:20 <DocScrutinizer> yw
Jun 23 06:29:35 <ThibG> (btw, jbt is in drivers/video/backlight/, that feels really wrong to me...)
Jun 23 06:29:51 <DocScrutinizer> hmm :-S
Jun 23 06:29:57 <DocScrutinizer> sounds fishy
Jun 23 06:32:37 <JaMa> mrmoku: gitr3 should be also fine
Jun 23 06:37:07 <Weiss> yeah, I agree.. jbt6k74 doesn't belong in backlight
Jun 23 06:37:59 <ThibG> hi Weiss :)
Jun 23 06:38:27 <ThibG> <JaMa> but you're right about defconfig http://git.openmoko.org/?p=kernel.git;a=blobdiff;f=arch/arm/configs/gta02_drm_defconfig;h=e9665392b1bca5259337dd01e9d77edd7a04c0bb;hp=05aa1304af982027ff5d244b49ca5a0084db6a1d;hb=d63ade17a0274b3b3f662fa381c4bb496bbf2ca9;hpb=8b604bd0f2f3e097bb2fc8b558a0f4e6ca7bdb13 /CONFIG_S3C24XX_GPIO_EXTRA shows =0
Jun 23 06:38:34 <ThibG> can you comment on this?
Jun 23 06:41:46 <mrmoku> JaMa, ThibG: git3 is missing the gsm power node too
Jun 23 06:42:22 * mrmoku trying oe3 now
Jun 23 06:42:29 <ThibG> hm, drivers/video/backlight is "Backlight & LCD drivers configuration", it falls in the second directory
Jun 23 06:42:37 <ThibG> -directory+category
Jun 23 06:42:39 <Wonka> raaah!
Jun 23 06:42:40 <Wonka> /etc/ssh/sshd_config line 87: Unsupported option UsePAM
Jun 23 06:42:49 <ThibG> mrmoku, hm, ok
Jun 23 06:43:02 <Wonka> and I wonder why my changes to /etc/environment don't work...
Jun 23 06:43:40 <Weiss> ThibG: interesting... the DRM defconfig should be the same as the standard one, except it has DRM enabled, and Glamo-DRM instead of Glamo-FB
Jun 23 06:45:17 <Wonka> any hints on how to get LANG and LC_MESSAGES set in SHR?
Jun 23 06:45:44 <mrmoku> Wonka: /etc/profile?
Jun 23 06:47:06 <Wonka> mrmoku: mh... didn't really want to hear _that_, hoped there was a better way...
Jun 23 06:47:13 <mrmoku> JaMa: hmm... oe3 is missing it too
Jun 23 06:47:16 <mrmoku> Wonka: :P
Jun 23 06:47:34 <Wonka> mrmoku: also, http://wiki.openmoko.org/wiki/Localization doesn't say anything about editing files to activate locales...
Jun 23 06:47:38 <mrmoku> Wonka: /etc/profile.d/wonkas-locale-settings.sh ?
Jun 23 06:48:08 <Wonka> mrmoku: locale-base-de-de is installed, still my umlauts do not work - they did in a previous incarnation of SHR
Jun 23 06:48:18 <mrmoku> hmm
Jun 23 06:48:57 <Wonka> i can input them via my matchbox-keyboard layout and get literal "?"
Jun 23 06:49:12 <Wonka> via ssh they just don't show up
Jun 23 06:51:29 * mrmoku booting 2.6.32.13-oe3 now
Jun 23 06:53:59 <mrmoku> JaMa, ThibG: with 2.6.32.13-oe3 the gsm power node is there
Jun 23 06:54:39 <ThibG> you were on 2.6.34 earlier, just to be sure?
Jun 23 06:56:30 <mrmoku> ThibG: yep
Jun 23 06:56:50 <ThibG> ok
Jun 23 06:57:11 <mrmoku> ThibG: I tried dd122c5 was the _oldest_ 2.6.34 I tried
Jun 23 06:57:28 <mrmoku> looks like all 2.6.34 are missing the gsm power node
Jun 23 06:57:34 <ThibG> ok
Jun 23 06:57:42 <ThibG> that's really odd :/
Jun 23 06:58:04 <ThibG> are all the other nodes there?
Jun 23 06:58:25 <ThibG> reset, download, flowcontrolled
Jun 23 06:58:45 <mrmoku> root@om-gta02 ~ # ls -d /sys/devices/platform/*-pm-*
Jun 23 06:58:45 <mrmoku> /sys/devices/platform/gta02-pm-bt.0  /sys/devices/platform/gta02-pm-gps.0  /sys/devices/platform/gta02-pm-wlan.0
Jun 23 06:58:57 <mrmoku> the complete subdir for gsm is missing
Jun 23 06:59:19 <ThibG> ok, that's interesting :)
Jun 23 07:00:45 <mrmoku> Weiss: I diffed 2.6.29 jbt6k74.c with the new one... only difference is that exported jbt_action thing used by glamo-display
Jun 23 07:01:02 <mrmoku> Weiss: delays are all equal
Jun 23 07:01:27 <ThibG> mrmoku, do you have a "reg-fixed-voltage.1" somewhere?
Jun 23 07:01:55 <mrmoku> ThibG: in 2.6.34?
Jun 23 07:01:59 <ThibG> both
Jun 23 07:02:22 <mrmoku> root@om-gta02 /sys # find . -name reg-fixed-voltage.1
Jun 23 07:02:22 <mrmoku> ./devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1
Jun 23 07:02:25 <mrmoku> ./bus/platform/devices/reg-fixed-voltage.1
Jun 23 07:02:25 <mrmoku> for 2.6.32.13
Jun 23 07:02:28 * mrmoku rebooting
Jun 23 07:02:30 <mrmoku> ./bus/platform/drivers/reg-fixed-voltage/reg-fixed-voltage.1
Jun 23 07:06:05 <mrmoku> heh
Jun 23 07:06:26 * mrmoku getting kernel panic now probably due to missing rootdelay... did not have that before with the same kernel though :/
Jun 23 07:08:25 <ThibG> So: pm_gsm is a bit different than pm_{bt,gps,wlan}
Jun 23 07:08:49 <ThibG> it gets loaded after reg-fixed-voltage.1, which is loaded when pcf50633-gpio is ready
Jun 23 07:10:23 <Wonka> aaaaaaaaaah. busybox's sh's exec doesn't know neither -a nor -l
Jun 23 07:10:35 <JaMa> mrmoku: did you reflash qi (new has rootwait)
Jun 23 07:25:47 <Wonka> mrmoku: some script in /etc/profile.d/ doesn't cut it: I ssh in, try to type umlauts (nothing happens), execute "locale" (shows de_DE), do "exec sh", type umlauts again, works...
Jun 23 07:26:04 <Wonka> mrmoku: those variables need to be set before sh is executed...
Jun 23 07:26:38 <[Rui]> JaMa: ah, there's news in the Qi front? I should reflash it, then?
Jun 23 07:28:12 <JaMa> [Rui]: only change is s/rootdelay=1/rootwait/
Jun 23 07:28:54 <[Rui]> JaMa: well, it means one less step on the Linux 2.6.3x  tests :)
Jun 23 07:29:09 <JaMa> or one more - reflash your qi :)
Jun 23 07:29:24 * ThibG would be glad if Qi had support for multi-file and compressed u-boot images
Jun 23 07:29:27 <JaMa> and the step is still needed for u-boot users
Jun 23 07:29:36 <[Rui]> JaMa: but that's a one time only :)
Jun 23 07:30:50 <JaMa> [Rui]: my images don't need even swith-for-kernel call :)
Jun 23 07:31:14 <[Rui]> JaMa: yeah... what about stability and white screen?
Jun 23 07:31:27 <Wonka> mrmoku: but the /etc/profile.d/ script seems to be enough for shells in vala-terminal to do umlauts again :)
Jun 23 07:31:28 <[Rui]> oh, and you don't use it as a regular phone, too :)
Jun 23 07:31:30 <Defiant> uhm where to find latest qi?
Jun 23 07:31:38 <Wonka> mrmoku: and "AcceptEnv LANG LC_*" in /etc/ssh/sshd_config solves it for ssh...
Jun 23 07:34:19 <[Rui]> gtg
Jun 23 07:35:45 <mrmoku> Wonka: good... probably we should add that to the default sshd config
Jun 23 07:36:16 <mrmoku> Defiant: you find it in http://build.shr-project.org/shr-unstable/images/om-gta02/
Jun 23 07:36:41 <Defiant> mrmoku: thx
Jun 23 07:41:50 <ThibG> mrmoku, so?
Jun 23 07:54:56 <mrmoku> ThibG: not yet... daywork strikes back :/
Jun 23 07:59:55 <ThibG> ok
Jun 23 08:01:34 <mrmoku> ThibG: root@om-gta02 /sys # find . -name reg-fixed-voltage.1
Jun 23 08:01:34 <mrmoku> ./devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1
Jun 23 08:01:37 <mrmoku> ./bus/platform/devices/reg-fixed-voltage.1
Jun 23 08:01:40 <mrmoku> ./bus/platform/drivers/reg-fixed-voltage/reg-fixed-voltage.1
Jun 23 08:01:47 <mrmoku> JaMa: no, not yet (qi)
Jun 23 08:02:03 <ThibG> mrmoku, and there is no pm-gsm?
Jun 23 08:03:37 <mrmoku> root@om-gta02 /sys # ls -d devices/platform/*-pm-*
Jun 23 08:03:37 <mrmoku> devices/platform/gta02-pm-bt.0  devices/platform/gta02-pm-gps.0  devices/platform/gta02-pm-wlan.0
Jun 23 08:03:44 <mrmoku> no gsm
Jun 23 08:03:45 <ThibG> odd...
Jun 23 08:04:42 <ThibG> both (reg-fixed-voltage and gta02-pm-gsm) use the same mechanism, and gta02-pm-gsm should be loaded right after reg-fixed-voltage
Jun 23 08:05:54 <mrmoku> JaMa: heh... flashing Qi is soooo loong in the past for me that I don't even remember which one of the three :/
Jun 23 08:07:10 <pespin> # unset LC_ALL && fsoraw -fr CPU,GPS -- navit
Jun 23 08:07:10 <pespin> vehicle_gpsd:vehicle_gpsd_try_open:Trying to connect to localhost:default
Jun 23 08:07:11 <pespin> netlib_connectsock() returns socket on fd 4
Jun 23 08:07:11 <pespin> sh: gdb: not found
Jun 23 08:07:21 <pespin> that's all navit can do no for me :D
Jun 23 08:07:28 <pespin> any idea?
Jun 23 08:08:20 <Wonka> mrmoku: the s3c2442 probably, on GTA02 ;)
Jun 23 08:08:20 <ThibG> mrmoku, any error in dmesg?
Jun 23 08:08:24 <mrmoku> ThibG: anything one would see in dmesg when it is loaded?
Jun 23 08:08:28 <mrmoku> heh
Jun 23 08:08:44 <ThibG> no, it does only print errors :)
Jun 23 08:08:53 <ThibG> but you can add an ugly printk to see if it gets loaded
Jun 23 08:09:43 <pespin> btw, why is navit looking for gdb? is that because it's crashing and wants to make a trace?
Jun 23 08:10:08 <mrmoku> ThibG: ok, I will try now a kernel from Weiss' gdm-2.6.34 branch (which was what I wanted to do anyway)... Where would that printk have to go to?
Jun 23 08:10:31 <ThibG> arch/arm/mach-s3c2440/gta02-pm-gsm.c
Jun 23 08:10:49 <ThibG> in gta02_gsm_probe
Jun 23 08:11:20 <ThibG> oh, and another in gta02_gsm_init, might be interesting to see if it registers ok
Jun 23 08:11:35 <mrmoku> ThibG: ok
Jun 23 08:13:59 <mrmoku> Wonka: thanks :)
Jun 23 08:14:15 * mrmoku has problems to remember all those numbers :P
Jun 23 08:17:44 <pespin> uhm installed gdb, and here's the output: http://pastebin.ca/1889078
Jun 23 08:17:48 <mrmoku> Weiss: nvm my comment about nothing having changed in jbt6k74... need more coffee :/
Jun 23 08:18:49 <pespin> is the problem trying to acess a null pointer?
Jun 23 08:20:07 <pespin> JaMa, can navit  be upgraded on shr-u feeds?
Jun 23 08:31:25 <JaMa> pespin: ? there is almost the latest now
Jun 23 08:33:19 <JaMa> mrmoku: 2.6.34-oe[234] are "from" gdrm-2.6.34 branch..
Jun 23 08:34:06 <mrmoku> JaMa: ahh, ok
Jun 23 08:34:13 <mrmoku> ThibG: both printks are there
Jun 23 08:34:15 <mrmoku> [    0.445000] !!! initing GSM
Jun 23 08:34:19 <mrmoku> [    0.730000] !!! probing for GSM
Jun 23 08:34:23 <mrmoku> still no node
Jun 23 08:34:33 <ThibG> do you have warning/error after that?
Jun 23 08:34:33 <pespin> JaMa, navit is crashing for me, see pastebin above ;)
Jun 23 08:34:45 <pespin> have to go now, see ya :)
Jun 23 08:36:54 <mrmoku> ThibG: no warning or error
Jun 23 08:37:21 <mrmoku> and looking at the code there should be something for every failure I think
Jun 23 08:37:24 <mrmoku> hmm
Jun 23 08:42:45 <ThibG> can't see anything wrong :/
Jun 23 08:44:32 <ThibG> I can't see any reason for that, but maybe the module is removed later...?
Jun 23 08:45:23 <mrmoku> my guess would be it is built in... not 100% sure though
Jun 23 08:45:59 <ThibG> it is built-in, but probe is called, doesn't fail, so, the sysfs group should be there...
Jun 23 08:46:10 <JaMa> mrmoku: modprobe configs; zcat /proc/config.gz
Jun 23 08:46:10 <mrmoku> yeah :/&
Jun 23 08:46:54 <ThibG> JaMa, that's not even a separate config option, that's with MACHINE_GTA02
Jun 23 08:47:00 <ThibG> so, it has to be built-in
Jun 23 08:47:00 <mrmoku> JaMa: good to know
Jun 23 08:53:55 <mrmoku> ThibG: duuuhh
Jun 23 08:54:02 <mrmoku> it just is in a different place
Jun 23 08:54:07 <mrmoku> root@om-gta02 /sys # find . -name \*gsm\*
Jun 23 08:54:07 <mrmoku> ./bus/platform/drivers/gta02-pm-gsm
Jun 23 08:54:23 <mrmoku> and not in devices/platform
Jun 23 08:54:24 <ThibG> haha
Jun 23 08:57:09 <PaulFertser> mrmoku: if the driver is there but no device, it clearly means an omission in the machine definition file.
Jun 23 08:58:12 <mrmoku> PaulFertser: where is that?
Jun 23 08:58:49 <mrmoku> ThibG: and there is no power node in that dir
Jun 23 08:59:00 <ThibG> mrmoku, seriously?
Jun 23 08:59:13 <ThibG> what is in it, then?
Jun 23 08:59:21 <PaulFertser> mrmoku: gta02.c
Jun 23 08:59:37 <mrmoku> ThibG: just bind and unbind
Jun 23 08:59:46 <mrmoku> and uevent
Jun 23 08:59:55 <ThibG> PaulFertser, as far I understand, it was done this way in order to prevent the module to load before the regulator...?
Jun 23 08:59:59 <ThibG> mrmoku, ok
Jun 23 09:01:39 <PaulFertser> ThibG: i've not seen the code you're talking about, but i think the only way platform drivers can associate themselves with devices is by means of the platform definition. 
Jun 23 09:02:01 <ThibG> it's in the platform definition, yes
Jun 23 09:02:04 <ThibG> mach-gta02.c
Jun 23 09:02:48 <ThibG> mrmoku, find /sys -name 'gta02-pm-gsm.0'
Jun 23 09:03:41 <mrmoku> ThibG: heh... already rebooted
Jun 23 09:03:46 * mrmoku should do some daywork :P
Jun 23 09:03:54 * mrmoku reboots again anyway ;)
Jun 23 09:03:56 <ThibG> ok, np
Jun 23 09:04:13 <ThibG> PaulFertser, that said, there is a call to platform_add_devices anyway...
Jun 23 09:07:40 <mrmoku> ThibG: found nothing
Jun 23 09:07:54 <ThibG> mrmoku, erf ok
Jun 23 09:08:08 <ThibG> and with find /sys -name 'gta02-pm-gsm*'
Jun 23 09:08:09 <ThibG> ?
Jun 23 09:08:24 <mrmoku> root@om-gta02 ~ # find /sys -name 'gta02-pm-gsm*' 
Jun 23 09:08:24 <mrmoku> /sys/bus/platform/drivers/gta02-pm-gsm
Jun 23 09:09:19 <JaMa> ThibG: be aware that there is also this patch applied http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-openmoko-2.6.34/0002-usbhost.patch.patch 
Jun 23 09:10:56 <ThibG> thanks
Jun 23 09:11:56 <JaMa> so I should build it without any patches from OM repo first..
Jun 23 09:12:54 <ThibG> I don't think it would break it
Jun 23 09:13:26 <JaMa> ok
Jun 23 09:13:28 * ThibG has no clue about the mysterious sysfs group
Jun 23 09:14:57 <ThibG> mrmoku, maybe find /sys power_on?
Jun 23 09:15:17 <ThibG> that's my last attempt (at least for now)
Jun 23 09:20:05 <mrmoku> root@om-gta02 ~ # find /sys -name power_on
Jun 23 09:20:06 <mrmoku> /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1/gta02-pm-gsm.0/power_on
Jun 23 09:20:08 <mrmoku> /sys/devices/platform/gta02-pm-gps.0/power_on
Jun 23 09:20:11 <mrmoku> /sys/devices/platform/gta02-pm-bt.0/power_on
Jun 23 09:20:28 <mrmoku> hmm
Jun 23 09:20:48 * mrmoku rebooted meanwhile to plain gdrm-2.6.34 kernel
Jun 23 09:20:56 <mrmoku> and there he is :P
Jun 23 09:22:00 <ThibG> yeah! \o/
Jun 23 09:22:05 <ThibG> what I thought
Jun 23 09:22:30 <ThibG> the device is there, but it's a child of reg-fixed-voltage.1 which is a child of pcf50633-gpio
Jun 23 09:22:56 <mrmoku> and does not get linked into /sys/devices/platform
Jun 23 09:23:33 <mrmoku> JaMa: will retry now the one from shr buildhost to make sure it is _not_ there
Jun 23 09:25:39 <JaMa> mrmoku: try also oe3 or oe4-gitr2 please
Jun 23 09:26:18 <gena2x> hi all :) i am with next question about hardware :)
Jun 23 09:26:22 <mrmoku> JaMa: ok
Jun 23 09:27:01 <gena2x> so, according to last description, glamo internally locked while doing something with screen.
Jun 23 09:27:36 <gena2x> my questiong is: is it possible to reduce framerate?
Jun 23 09:28:10 <gena2x> to make glamo generate frame fast, and then add larger pause
Jun 23 09:28:10 <mrmoku> ok, with oe4+git4:
Jun 23 09:28:10 <mrmoku> root@om-gta02 ~ # find /sys -name power_on
Jun 23 09:28:10 <mrmoku> /sys/devices/platform/gta02-pm-gps.0/power_on
Jun 23 09:28:10 <mrmoku> /sys/devices/platform/gta02-pm-bt.0/power_on
Jun 23 09:29:26 <gena2x> as we anyway can't suppy 60hz of changing data anyway.
Jun 23 09:29:39 <ThibG> mrmoku, odd, what kernel/revision did you use last time?
Jun 23 09:29:52 <Weiss> gena2x: you're talking about the way the operations slow down when the screen is on?
Jun 23 09:30:09 <gena2x> Weiss: yes.
Jun 23 09:30:51 <gena2x> Weiss: i mean, that i glamo is 'busy' updating frame, why not to ask it to do less frames
Jun 23 09:31:10 <mrmoku> ThibG: the one having it is HEAD of gdrm-2.6.34 from git.bitwiz.org.uk
Jun 23 09:31:13 <mrmoku> without any patches
Jun 23 09:31:14 <Weiss> gena2x: do you have the LCD engine FIFO switched on? (top four bits of the display address) - that compensates for that quite a lot
Jun 23 09:31:24 <ThibG> mrmoku, ok, thanks
Jun 23 09:31:29 <mrmoku> ThibG: the not working one is from the same tree with some patches
Jun 23 09:31:43 <mrmoku> uImage-2.6.34-oe4+gitr4+5c40321e6e6a8ca8552c5c69d041d7f7f3205318-r0-om-gta02.bin
Jun 23 09:31:47 <gena2x> Weiss: where can i check this?
Jun 23 09:32:02 <gena2x> Weiss: (i can't recall sysfs node name)
Jun 23 09:32:17 <Weiss> easiest place is in the source code for the kernel you're using
Jun 23 09:32:55 <gena2x> Weiss: but where is lcm registers anyway?
Jun 23 09:33:13 <JaMa> ThibG: uImage-2.6.34-oe4+gitr4+5c40321e6e6a8ca8552c5c69d041d7f7f3205318-r0-om-gta02.bin is 5c40321e6e6a8ca8552c5c69d041d7f7f3205318 from om-gta02-2.6.34 + patches from gdrm-2.6.34 + other patches as listed here http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-openmoko-2.6.34_git.bb
Jun 23 09:33:26 <gena2x> Weiss: btw, have you any docs about LCM, or they are under NDA?
Jun 23 09:34:01 <Weiss> gena2x: they're NDA'd, but I have them under the OM FOSS NDA
Jun 23 09:34:18 <Weiss> gena2x: which kernel are you using? (KMS/non-KMS?)
Jun 23 09:34:32 <Weiss> all recent (since november) kernels should have the FIFO switched on
Jun 23 09:34:34 <ThibG> JaMa, thanks, I'm going to have a look
Jun 23 09:34:40 <gena2x> Weiss: ok, thats what i expected after openmoko-kernel.
Jun 23 09:34:57 <gena2x> Weiss: i'm testing on .34 from latest git.
Jun 23 09:35:16 <JaMa> and 0001-accels.patch.patch seems to be doing much more then it should..
Jun 23 09:35:26 <mrmoku> JaMa: with oe3:
Jun 23 09:35:28 <mrmoku> root@om-gta02 ~ # find /sys -name power_on
Jun 23 09:35:28 <mrmoku> /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.1/gta02-pm-gsm.0/power_on
Jun 23 09:35:31 <mrmoku> /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-gpio/reg-fixed-voltage.2/gta02-pm-usbhost.0/power_on
Jun 23 09:35:34 <mrmoku> /sys/devices/platform/gta02-pm-gps.0/power_on
Jun 23 09:35:37 <mrmoku> /sys/devices/platform/gta02-pm-bt.0/power_on
Jun 23 09:35:47 <mrmoku> trying the oe4+gitr3 now
Jun 23 09:35:52 <gena2x> Weiss: no kms
Jun 23 09:35:59 <Weiss> gena2x: http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/om-gta02-2.6.34 ?
Jun 23 09:36:16 <gena2x> Weiss: yes
Jun 23 09:36:50 <Weiss> gena2x: appears that does NOT have the FIFO turned on..
Jun 23 09:37:00 <gena2x> Weiss: WOW.
Jun 23 09:37:17 <gena2x> Weiss: didn't thought about this.
Jun 23 09:37:26 <gena2x> Weiss: nice that i asked you!
Jun 23 09:37:59 <gena2x> Weiss: i were going to understand timings, lcm, jbt and so on...
Jun 23 09:38:08 <Weiss> gena2x: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=b90406de472c1aa5371ab593a2bb79136d5de658
Jun 23 09:38:09 <JaMa> mrmoku: seems like between oe3 and oe4 there was only "slow-resume" pcf fix and "lost-ts" fix
Jun 23 09:38:46 <Weiss> gena2x: appears it got lost between andy-tracking and 2.6.32 (though it should be in all KMS kernels)
Jun 23 09:38:53 <JaMa> mrmoku: ah only slow-resume, ts patch was already in oe3
Jun 23 09:39:04 <gena2x> Weiss: thanks.
Jun 23 09:39:09 <ThibG> JaMa, nothing striking in the OE patches
Jun 23 09:39:17 <mrmoku> JaMa: and oe4+git3 is missing the node too
Jun 23 09:39:28 <mrmoku> so that patch then...
Jun 23 09:39:44 <mrmoku> JaMa: where is that slow-resume patch from?
Jun 23 09:39:47 <ThibG> Weiss, oh, interesting!
Jun 23 09:40:25 <gena2x> ThibG: yeah :)
Jun 23 09:40:33 <JaMa> mrmoku: from larsc and it was applied a bit later to om git
Jun 23 09:40:37 <Weiss> gena2x: that's for andy-tracking, so might need some tweaking.. but you get the idea. changing the 4 to an 8 or even a C makes it go faster, but eventually you get LCD artifacts
Jun 23 09:40:41 <gena2x> i'll rebuild now and check all speeds.
Jun 23 09:40:45 <JaMa> mrmoku: see http://git.openembedded.org/cgit.cgi/openembedded/log/recipes/linux/linux-openmoko-2.6.34_git.bb
Jun 23 09:40:56 <Weiss> http://www.bitwiz.org.uk/s/2009/11/internal-memory-bottlenecks-and-their-removal.html
Jun 23 09:41:22 <gena2x> Weiss: i recall this famous patch from you.
Jun 23 09:41:39 <gena2x> Weiss: just didn't expect it is missing on .34.
Jun 23 09:42:12 <Weiss> me neither..
Jun 23 09:42:32 <Weiss> probably because I added it on andy-tracking but not 2.6.32, so it got missed for 2.6.34 as well
Jun 23 09:43:14 <ThibG> "the price of this was that the display became jittery and unstable" reminds me of my screen going berserk with SHR
Jun 23 09:43:41 <gena2x> ThibG: i were using .29 much
Jun 23 09:43:53 <gena2x> ThibG: in debian, qtmoko
Jun 23 09:43:58 <ThibG> yeah, with .29
Jun 23 09:44:04 <gena2x> ThibG: never saw any problems.
Jun 23 09:44:47 <ThibG> a few times, my screen went berserk, with apparently low refreshing rate, one line out of two, saturation... that sort of things
Jun 23 09:45:02 <Weiss> it's a different kind.. it sort of goes "wobbly", but with no other apparent corruption
Jun 23 09:45:12 <Weiss> give it a try and see... (but maybe backup your SD card first)
Jun 23 09:46:15 <gena2x> i have separate /var
Jun 23 09:46:33 <gena2x> so other partitions unlikely to corrupt on my sd...
Jun 23 09:47:21 <Weiss> yeah.. haven't seen any evidence that the jitteriness affects anything other than the LCD, but it's best to be aware
Jun 23 09:49:39 <gena2x> Weiss: may be it's possible to change this register to test values without kernel rebuilding?
Jun 23 09:50:03 <gena2x> Weiss: and why only 4, 8 and C? are other values possible?
Jun 23 09:50:59 <gena2x> something like write_mem (GLAMO_REG_LCD_A_BASE2, 0x4000) should be ok?
Jun 23 09:52:00 <Weiss> yes actually.. with the glamo regs sysfs.. from memory: echo "0x110e 0x4000" > /sys/bus/platform/devices/glamo3362.0/regs
Jun 23 09:52:40 <Weiss> the possible values are 0, 4, 8 and C meaning 1, 2, 4 or 8 FIFO stages respectively
Jun 23 09:53:19 <gena2x> Weiss: ok, thanks.
Jun 23 09:53:47 <mickey|cafe> ~seen GNUtoo
Jun 23 09:53:50 <apt> gnutoo <~gnutoo@host193-133-dynamic.16-79-r.retail.telecomitalia.it> was last seen on IRC in channel #oe, 11h 45m 35s ago, saying: 'I think that's all'.
Jun 23 09:54:24 <Weiss> fullscreen 16bpp VGA blits can be done at 100fps with the FIFO turned on :D
Jun 23 09:54:57 <gena2x> Weiss: in fact high fps will consume more power
Jun 23 09:55:15 <gena2x> Weiss: so, imo, it's better to reduce it.
Jun 23 09:55:38 <Weiss> but, you don't spend all your time doing flat-out blits anyway..
Jun 23 09:55:48 <gena2x> Weiss: oh, btw :)
Jun 23 09:55:55 <Weiss> :)
Jun 23 09:55:55 <gena2x> i finally run oprofile :)
Jun 23 09:56:16 <gena2x> and may be info about X may be interesting for you :)
Jun 23 09:56:31 <gena2x> i profiled mozilla run
Jun 23 09:56:51 <gena2x> total X cpu usage were 10%
Jun 23 09:57:34 <gena2x> better to say, 31 mozilla 5 xorg last run
Jun 23 09:57:40 <gena2x> so 1/6.
Jun 23 09:57:59 <gena2x> and in Xorg, i were a bit surprised
Jun 23 09:58:09 <gena2x>       898  5.1092 Xorg
Jun 23 09:58:09 <gena2x>                   TIMER:0|
Jun 23 09:58:09 <gena2x>           samples|      %|
Jun 23 09:58:09 <gena2x>         ------------------
Jun 23 09:58:09 <gena2x>               407 45.3229 libc-2.11.2.so
Jun 23 09:58:09 <gena2x>               134 14.9220 Xorg
Jun 23 09:58:11 <gena2x>               108 12.0267 vmlinux_tsbuild2.bin
Jun 23 09:58:13 <gena2x>               101 11.2472 libpixman-1.so.0.16.4
Jun 23 09:58:17 <gena2x>                75  8.3519 glamo_drv.so
Jun 23 09:58:38 <gena2x> that 50% is memcpy
Jun 23 09:58:54 <gena2x> samples  %        linenr info                 image name               symbol name
Jun 23 09:58:55 <gena2x> 373      41.5367  memcpy.S:60                 libc-2.11.2.so           memcpy
Jun 23 09:58:55 <gena2x> 134      14.9220  (no location information)   Xorg                     /usr/bin/Xorg
Jun 23 09:58:55 <gena2x> 101      11.2472  (no location information)   libpixman-1.so.0.16.4    /usr/lib/libpixman-1.so.0.16.4
Jun 23 09:58:55 <gena2x> 75        8.3519  (no location information)   glamo_drv.so             /usr/lib/xorg/modules/drivers/glamo_drv.so
Jun 23 09:58:57 <gena2x> 56        6.2361  (no location information)   libexa.so                /usr/lib/xorg/modules/libexa.so
Jun 23 09:59:00 <gena2x> 15        1.6704  malloc.c:4250               libc-2.11.2.so           _int_malloc
Jun 23 09:59:02 <gena2x> 10        1.1136  (no location information)   vmlinux_tsbuild2.bin     schedule
Jun 23 09:59:27 <Weiss> that sounds about right... lots and lots of tiny operations which can't be accelerated sensibly
Jun 23 10:00:21 <gena2x> hm. i thought lot of i tiny operations should be less memcpy, more in driver?
Jun 23 10:00:54 <gena2x> and here 50% of all time xorg is doing some memcpy.
Jun 23 10:04:14 <Weiss> Xorg asks the driver to get access to a pixmap in VRAM, but after that Xorg can do the writing/reading itself
Jun 23 10:04:24 <Weiss> (or in the DRM world, the client can do it)
Jun 23 10:06:26 <gena2x> oh, my glamo dead again after om screen power 0, and do not want to restore :(
Jun 23 10:06:34 <gena2x> so anyway need reboot...
Jun 23 10:14:00 <gena2x> Weiss: great
Jun 23 10:15:17 <gena2x> Weiss: now mmc card speed is 2.5/2.7 (om screen power 0/1)
Jun 23 10:15:52 <gena2x> PaulFerster: so all this 'internal wait states' is no true
Jun 23 10:16:39 <PaulFertser> gena2x: hm?
Jun 23 10:17:06 <gena2x> PaulFertser: few days ago we spoke about mmc card speed.
Jun 23 10:18:54 <gena2x> PaulFertser: i just wanted to grab a bit you your attention to show some interesting info about problem
Jun 23 10:22:10 <gena2x> larsc: is it possible to add Weiss patch to .34 somehow?
Jun 23 10:22:15 <gena2x> larsc: it seems very important.
Jun 23 10:22:30 <gena2x> larsc: doubles mmc access speed here...
Jun 23 10:32:48 <ThibG> gena2x, and how does it affect the worker?
Jun 23 10:33:08 <ThibG> (just curious)
Jun 23 10:34:10 <gena2x> ThibG: i din't tried. i have it disabled, i'll reeable it next rebuild and report...
Jun 23 10:34:32 <ThibG> ok, thanks! :)
Jun 23 10:35:05 <gena2x> but have you fixed problems alread reported? :)
Jun 23 10:35:24 <ThibG> like?
Jun 23 10:35:48 <gena2x> hang in 1st suspend with worker.
Jun 23 10:35:53 <ThibG> hm
Jun 23 10:35:58 <ThibG> I have an idea for that
Jun 23 11:24:31 <gena2x> Weiss: cat /sys/bus/platform/devices/glamo3362.0/regs: [  269.205000] Unable to handle kernel paging request at virtual address c893f100
Jun 23 11:24:32 <gena2x> [  269.210000] pgd = c6c44000
Jun 23 11:24:32 <gena2x> [  269.210000] [c893f100] *pgd=37c1e011, *pte=00000000, *ppte=00000000
Jun 23 11:24:32 <gena2x> [  269.215000] Internal error: Oops: 7 [#2]
Jun 23 11:24:32 <gena2x>  ... [  269.215000] [<c01b2370>] (regs_read+0x74/0x104) from [<c01a6034>] (dev_attr_show+0x28/0x54)
Jun 23 11:25:10 <ThibG> gena2x, that's fixed in Weiss's tree
Jun 23 11:25:26 <gena2x> ThibG: tree?
Jun 23 11:26:08 <gena2x> ThibG: where is it? and that is also fixed where?
Jun 23 11:26:29 <ThibG> http://git.bitwiz.org.uk/?p=kernel.git;a=commit;h=9cd5001fc2f4c817d5614b1ee5445d69af05d483
Jun 23 11:44:51 <gena2x> ThibG: added this to my build and enabled worker, thanks for info :)
Jun 23 11:45:06 <ThibG> np
Jun 23 11:53:18 <gena2x> ThibG: it's like a... rocket now :) 2.7/2.9 (vs 2.5/2.7)
Jun 23 11:53:22 <gena2x> so +10%
Jun 23 11:54:01 <gena2x> also i see mmc speed with worker is fewer affected by my X startup procedure.
Jun 23 11:54:23 <ThibG> ok, that's good to hear :)
Jun 23 11:58:19 <mrmoku> ret |= jbt_reg_write(jbt, JBT_REG_QUAD_RATE, 0x00);
Jun 23 11:58:26 <mrmoku> ret = jbt_reg_write(jbt, JBT_REG_DISPLAY_MODE, 0x80);
Jun 23 11:58:32 <mrmoku> looks wrong, no?
Jun 23 12:00:16 <ThibG> indeed
Jun 23 12:00:35 <mrmoku> JaMa: soo... without any patches I have gsm but it does not resume properly... with all patches it resumes but I have no gsm... WSoD they do show all... dunno if I want to switch today ;)
Jun 23 12:01:01 <Weiss> mrmoku: hmm.. where's that?
Jun 23 12:01:15 <mrmoku> jbt6k74.c
Jun 23 12:01:24 <ThibG> mrmoku, it can silence a few errors
Jun 23 12:01:30 <mrmoku> in set_resolution
Jun 23 12:01:45 <Weiss> mrmoku: which version?
Jun 23 12:02:30 <mrmoku> Weiss: current gdrm-2.6.34 in your tree
Jun 23 12:02:57 <mrmoku> the 'Enable 3D engine' one
Jun 23 12:04:45 <Weiss> eww, ok.. that probably won't help
Jun 23 12:05:28 <mrmoku> Weiss: just stumbled over it searching for places to set random delays :P
Jun 23 12:09:06 <Weiss> :)
Jun 23 12:16:36 <Weiss> not sure it explains any problems, but it should be fixed
Jun 23 12:23:29 <gena2x> Weiss: are you sure about ' echo "0x110e 0x4000" '?
Jun 23 12:26:23 <gena2x> Weiss: see no effect on sd speed
Jun 23 12:26:40 <gena2x> Weiss: or anything else
Jun 23 12:41:59 <ThibG> hm, almsot  ready to submit the glamo drivers (glamo-{core,gpio,mci,fb}) upstream...
Jun 23 12:45:16 <GNUtoo|laptop> hi mickeyl 
Jun 23 12:45:18 <GNUtoo|laptop> hi leviathan 
Jun 23 12:46:36 <GNUtoo|laptop> hi mickey|cafe 
Jun 23 12:47:27 <mickey|> hi
Jun 23 12:47:48 <GNUtoo|laptop> several things:
Jun 23 12:48:06 <GNUtoo|laptop> *we need to talk about htcdream/palm-pre
Jun 23 12:48:46 <GNUtoo|laptop> *I sent a response in State of htcdream and very short term roadmap
Jun 23 12:49:02 <GNUtoo|laptop> I really hesitate to buy a palm pre
Jun 23 12:49:26 <GNUtoo|laptop> nearly everything work in the htcdream but nearly nothing work well
Jun 23 12:50:13 <mickey|> yep
Jun 23 12:50:42 <GNUtoo|laptop> if there is not much to do for the palm pre,I would use it as a phone
Jun 23 12:50:54 <GNUtoo|laptop> and continue the work on the htcdream
Jun 23 12:51:08 <mickey|> hmm
Jun 23 12:51:21 <GNUtoo|laptop> what I need is a phone with the following capabilities:
Jun 23 12:51:24 <GNUtoo|laptop> *phone
Jun 23 12:51:27 <GNUtoo|laptop> *music
Jun 23 12:51:40 <GNUtoo|laptop> *16G
Jun 23 12:51:47 <GNUtoo|laptop> *correct battery life
Jun 23 12:51:52 <mickey|> hmm
Jun 23 12:51:59 <GNUtoo|laptop> I think palm pre will soon be ready
Jun 23 12:52:02 <mickey|> that means you need the pre plius
Jun 23 12:52:06 <GNUtoo|laptop> yes
Jun 23 12:52:14 <GNUtoo|laptop> that's what they sell in france I think
Jun 23 12:52:18 <GNUtoo|laptop> 429E
Jun 23 12:52:21 <GNUtoo|laptop> 16G
Jun 23 12:52:25 <mickey|> while it's a good phone, it's completely unclear to me whether this is the same has the pre
Jun 23 12:52:29 <GNUtoo|laptop> I must check the ram
Jun 23 12:52:39 <GNUtoo|laptop> ah ouch...
Jun 23 12:52:45 <mickey|> i don't know anyone who has it
Jun 23 12:52:57 <GNUtoo|laptop> maybe I should ask in webos internals
Jun 23 12:53:01 <mickey|> yes
Jun 23 12:53:17 <mickey|> the pre has some advantages
Jun 23 12:53:21 <GNUtoo|laptop> anyway I have to wait until I go in france
Jun 23 12:53:21 <mickey|> but also some disadvatages
Jun 23 12:53:26 <mickey|> and still some unclear areas
Jun 23 12:53:29 <GNUtoo|laptop> ok
Jun 23 12:53:29 <mickey|> which need looking at
Jun 23 12:53:38 <GNUtoo|laptop> I heard morphis
Jun 23 12:53:41 <mickey|> right
Jun 23 12:53:43 <GNUtoo|laptop> touchscreen now works
Jun 23 12:54:21 <GNUtoo|laptop> so what are the disavantages?
Jun 23 12:54:27 <GNUtoo|laptop> apart that it has no sdcard
Jun 23 12:54:30 <GNUtoo|laptop> and a bad keyboard
Jun 23 12:54:37 <GNUtoo|laptop> and that is maybe fragile
Jun 23 12:55:04 <Weiss> gena2x: not sure at all.. maybe it needs to not have the "0x"s
Jun 23 12:55:10 <GNUtoo|laptop> and what's unclear
Jun 23 12:55:11 <GNUtoo|laptop> ?
Jun 23 12:55:22 <mickey|> wifi 
Jun 23 12:55:23 <mickey|> bt
Jun 23 12:55:27 <mickey|> audio
Jun 23 12:55:33 <GNUtoo|laptop> audio?
Jun 23 12:55:34 <mickey|> while this is probably all easy and simple
Jun 23 12:55:38 <GNUtoo|laptop> ah ok
Jun 23 12:55:40 <mickey|> i have yet to confirm it
Jun 23 12:55:43 <GNUtoo|laptop> no one has looked yet
Jun 23 12:55:47 <mickey|> correct
Jun 23 12:55:53 <mickey|> chances are everything works
Jun 23 12:55:58 <mickey|> but i can't tell personally yet
Jun 23 12:56:01 <GNUtoo|laptop> ok
Jun 23 12:56:14 <GNUtoo|laptop> their wifi patches would be interesting
Jun 23 12:56:14 <mickey|> the good thing is the wifi can do ad-hoc ;)
Jun 23 12:56:21 <GNUtoo|laptop> but I bet they didn't post them
Jun 23 12:56:30 <GNUtoo|laptop> ah I heard that it can do ap
Jun 23 12:56:40 <GNUtoo|laptop> but maybe it was a marketting lie
Jun 23 12:56:44 <mickey|> AP i doubt
Jun 23 12:56:47 <mickey|> but ad-hoc is good enough
Jun 23 12:57:02 <mickey|> it works fine w/ my ipad :)
Jun 23 12:57:03 <GNUtoo|laptop> if it did AP buglabs would be interested in the patch
Jun 23 12:57:15 <GNUtoo|laptop> it's libertas_sdio right?
Jun 23 12:57:26 <mickey|> i think so, but i'm not sure
Jun 23 12:57:53 <GNUtoo|laptop> ah they say: mobile hotspot
Jun 23 12:57:57 <GNUtoo|laptop> maybe that doesn't mean ap
Jun 23 12:58:08 <mickey|> mobile hotspot is a marketing term
Jun 23 12:58:10 <mickey|> can mean both
Jun 23 12:58:12 <GNUtoo|laptop> ok
Jun 23 12:58:22 <mickey|> i'm still a bit waiting for morphis before diving deeper in the pre, also i was still hoping for the dream
Jun 23 12:58:36 <GNUtoo|laptop> mickeyl, the dream will be ok
Jun 23 12:58:51 <GNUtoo|laptop> mickeyl, but I'm impacient and I need a phone for the hollidays
Jun 23 12:59:31 <mickey|> i see
Jun 23 12:59:51 <mickey|> in that case, try to make sure that the pre plus has no bad surprises wrt. hackability
Jun 23 13:00:00 <GNUtoo|laptop> ok
Jun 23 13:00:02 <GNUtoo|laptop> I'll ask
Jun 23 13:00:13 <GNUtoo|laptop> because a non-hackable phone would be waisted money
Jun 23 13:00:20 <mickey|> correct
Jun 23 13:00:22 <mickey|> hmm
Jun 23 13:00:23 <mickey|> but wait
Jun 23 13:00:27 <mickey|> what about the nexus one?
Jun 23 13:00:40 <mickey|> or will we have the same problems as on the dream there?
Jun 23 13:00:43 <GNUtoo|laptop> another super-htcdream?
Jun 23 13:00:45 <mickey|> hmm
Jun 23 13:00:55 <mickey|> true
Jun 23 13:01:13 <GNUtoo|laptop> basically if I buy the palm pre it would be to do minimal knerel/system hacking
Jun 23 13:01:20 <GNUtoo|laptop> only oe hacking
Jun 23 13:01:23 <GNUtoo|laptop> and some basic help
Jun 23 13:01:32 <GNUtoo|laptop> like maybe writting a kenrel touchscreen driver
Jun 23 13:01:46 <leviathan> GNUtoo|laptop: I'm still waiting for my cable
Jun 23 13:01:55 <leviathan> they did not even work on it yet
Jun 23 13:01:57 <GNUtoo|laptop> buying a nexus-one would make me abandon the htcdream 
Jun 23 13:02:00 <GNUtoo|laptop> which is not good
Jun 23 13:02:03 <leviathan> yes
Jun 23 13:02:11 <leviathan> btw
Jun 23 13:02:16 <leviathan> did you correct my email?
Jun 23 13:02:25 <GNUtoo|laptop> leviathan, I got a phone call
Jun 23 13:02:29 <leviathan> k
Jun 23 13:02:31 <GNUtoo|laptop> and then went to sleep 
Jun 23 13:02:35 <GNUtoo|laptop> but I can do it now
Jun 23 13:02:43 <GNUtoo|laptop> is mickeyl aware of the mail?
Jun 23 13:02:56 <GNUtoo|laptop> what does he think?
Jun 23 13:03:19 <leviathan> I didn't show it to him, yet
Jun 23 13:03:41 <leviathan> btw: newest entry, now its functional: http://the-leviathan.ch
Jun 23 13:03:43 <leviathan> =)
Jun 23 13:03:48 <leviathan> they did a big mistake
Jun 23 13:03:51 <leviathan> anyway
Jun 23 13:03:58 <leviathan> please forward him the email
Jun 23 13:04:04 <GNUtoo|laptop> ok
Jun 23 13:04:06 <leviathan> as soon as you have corrected as you like
Jun 23 13:04:37 <Deubeuliou> GNUtoo|laptop: if you have questions regarding the nexus one, ask me, I have one and can run tests if you want
Jun 23 13:04:58 <GNUtoo|laptop> Deubeuliou, ok what doesn't work or doesn't work well?
Jun 23 13:05:46 <mickey|> we're especially interested in
Jun 23 13:05:55 <mickey|> audio, WiFi, GPS, BT, suspend/resume
Jun 23 13:06:00 <mickey|> (well... i'm, that is)
Jun 23 13:06:25 <GNUtoo|laptop> mickeyl, can I PM you?
Jun 23 13:06:29 <Deubeuliou> I managed quite easily, without having to patch anything, to get cornucopia running on it. I don't have any sound yet (did not try very hard), however. I will try more soon.
Jun 23 13:07:02 <GNUtoo|laptop> Deubeuliou, ok, about sound I fear that you will have to use the msm alsa driver...
Jun 23 13:07:05 <mickey|> GNUtoo|laptop: sure, i need to run soon though
Jun 23 13:07:06 * mickey| hungry
Jun 23 13:07:31 <Deubeuliou> wifi works ... but the kernel configuration for it to work is not trivial (with the one from android.kernel.org) ; I did not try with a vanillia kernel
Jun 23 13:07:50 <Deubeuliou> I didn't try bt nor gps
Jun 23 13:09:02 <Deubeuliou> I think suspend/resume works, but I'm not sure. I had troubles with lxde going idle and not coming back, but since I use it over nodm, it seems to work
Jun 23 13:09:33 <Deubeuliou> GNUtoo|laptop: ok
Jun 23 13:10:57 <gena2x> Weiss: still don't work for me, but ok. i tested with rebuilds. i'm on C value now.
Jun 23 13:11:15 <GNUtoo|laptop> Deubeuliou, what's the xorg driver, xf86-video-msmfb?
Jun 23 13:11:26 <gena2x> Weiss: ok so far. noticed 1 Xorg restart
Jun 23 13:11:48 <gena2x> Weiss: up 30 mins
Jun 23 13:12:07 <Deubeuliou> GNUtoo|laptop: I don't know
Jun 23 13:12:34 <GNUtoo|laptop> Deubeuliou, how do you have xorg running then?
Jun 23 13:12:55 <GNUtoo|laptop> btw if it's not comming back maybe I know why
Jun 23 13:12:58 <GNUtoo|laptop> look at the logs
Jun 23 13:13:16 <GNUtoo|laptop> I had the same thing when rotated
Jun 23 13:13:34 <Deubeuliou> GNUtoo|laptop: I don't remember which driver I'm using. is it ok if I look tomorrow ?
Jun 23 13:13:55 <gena2x> Weiss: mmc speed now is much better, thanks again for that fix.
Jun 23 13:14:14 <GNUtoo|laptop> Deubeuliou, ok
Jun 23 13:15:53 <Weiss> gena2x: cool :D
Jun 23 13:16:06 <Weiss> gena2x: "1 Xorg restart" meaning crash?
Jun 23 13:16:34 <ThibG> "1 Xorg restart" is *not* cool :o
Jun 23 13:18:40 <gena2x> yeah. not cool. but i'm not sure if it is related
Jun 23 13:18:51 <gena2x> because i have no screen artefacts.
Jun 23 13:19:51 <mickey|> bbl, lunch time
Jun 23 13:20:12 <Weiss> anything in the log?
Jun 23 13:22:01 <gena2x> Weiss: i now removed sd. (need to repartition it......) next time i see this i'll take a look to log.
Jun 23 13:22:05 <ThibG> gena2x, in fact, the sysfs nodes doesn't take hexa...
Jun 23 13:22:28 <gena2x> ThibG: so it should be in decimal?
Jun 23 13:22:35 <ThibG> yes
Jun 23 13:22:56 <gena2x> ThibG: nice, thanks. after repartition i'll test it.
Jun 23 13:23:02 <ThibG> but it segfaults when I try to set the GLAMO_REG_LCD_A_BASE2 register :)
Jun 23 13:23:55 <ThibG> (and so, I've written to random registers, yeah!)
Jun 23 13:24:25 <gena2x> btw, also my kernel can't see 8th partition on sd.
Jun 23 13:25:06 <gena2x> and i noticed this only because of lack of space :)
Jun 23 13:26:01 <gena2x> that were my planned /home, which goed to / instead, will all kernels :)
Jun 23 13:26:17 <gena2x> s/will/with/
Jun 23 13:26:18 <apt> gena2x meant: that were my planned /home, which goed to / instead, with all kernels :)
Jun 23 13:26:51 <gena2x> s/goed/gone/
Jun 23 13:26:51 <apt> gena2x meant: that were my planned /home, which gone to / instead, will all kernels :)
Jun 23 13:27:02 <gena2x> hm... damn <enter> key.
Jun 23 13:33:22 <GNUtoo|laptop> leviathan, sent
Jun 23 13:33:25 <GNUtoo|laptop> and corrected
Jun 23 13:33:29 <leviathan> ok
Jun 23 13:33:33 <leviathan> thx!
Jun 23 13:35:13 <GNUtoo|laptop> leviathan, I'll pm you because I forgott something
Jun 23 13:37:54 <leviathan> ok
Jun 23 15:10:04 <ThibG> larsc, ping
Jun 23 15:21:20 <larsc> ThibG: pong
Jun 23 15:22:27 <ThibG> I'm ready to submit the glamo drivers upstream (provided that you accept the latest patches :)), but I'm not too sure to who I should send/cc them
Jun 23 15:23:24 <larsc> there is scripts/get_maintainers.pl
Jun 23 15:23:55 <ThibG> yeah, but it pulls loads of people, and I don't think everyone there is interested in 150KB of patches :)
Jun 23 15:24:42 <ThibG> MFD maintainer is pretty obvious for glamo-core, as is the MMC maintainer for glamo-mci, etc.
Jun 23 15:25:09 <ThibG> but should the MFD maintainer be CCed for each subdriver? Things like that
Jun 23 15:25:56 <larsc> I would sent them all to samuel and Cc the maintainers for the subsystems of the subdrivers
Jun 23 15:26:11 <ThibG> ok, thanks
Jun 23 15:27:24 <larsc> that said i still think the glamo driver isn't ready yet
Jun 23 15:28:20 <ThibG> why?
Jun 23 15:31:42 <larsc> there are lots and lots of tiny issues. I just scrolled through the core driver and: "enum glamo_cells {" is unnecessary, the irq demuxer should not be a chained irq and reimplement handle_level_irq but instead use a normal irq handler, the regs file is should be a debugfs file instead of a sysfs file
Jun 23 15:32:06 <ThibG> ok
Jun 23 15:32:39 <larsc> and maybe glamo_engines_{suspend,enable,disable} should be hooked up to the mfd_cells enable,disable,suspend,resume callbacks
Jun 23 15:37:18 <larsc> glamofb_cmd_write has no users, as far as i can see
Jun 23 15:37:41 <ThibG> I'll have a look. That said, reviewers can point out things too, and having glamo upstream doesn't refrain us to post new changes
Jun 23 15:37:47 <ThibG> Anyway, thanks for your comments and help!
Jun 23 15:38:20 <gena2x> larsc: hi, how about LCD fifo patch?
Jun 23 15:38:41 <larsc> gena2x: is already applied
Jun 23 15:40:09 <gena2x> larsc: wow, nice.
Jun 23 16:23:16 <badcloud> how to change shr icon theme without using illume settings dialog? (it's segging)
Jun 23 16:26:33 <larsc> ThibG: pushed a few cleanups for glamofb
Jun 23 16:26:33 <GNUtoo|laptop> hi, does enlightenment segfault only for me on om-gta02 with shr
Jun 23 16:27:35 <ThibG> ok :)
Jun 23 16:34:49 <badcloud> anyway to find out why e-settings is segging?
Jun 23 16:35:07 <badcloud> as in me find out, not you
Jun 23 16:36:56 <Heinervdm> badcloud: connect with gdb and look at the backtrace, but i don't know if you will see sth usefull
Jun 23 16:37:28 <badcloud> Heinervdm: I see. what's the binary for e-settings?
Jun 23 16:37:46 <badcloud> maybe running it from terminal might help me understand
Jun 23 16:37:55 <badcloud> all I want it to change icon theme
Jun 23 16:38:05 <badcloud> isn't there a config file somewhere in /etc for that?
Jun 23 16:39:11 <Heinervdm> the configs are compiled edc files
Jun 23 16:39:54 <Heinervdm> best short term solution is to use enlightment_remote as someone else suggested already
Jun 23 16:41:44 <badcloud> Heinervdm: trying to... can't find the right option
Jun 23 16:42:24 <Heinervdm> hmm
Jun 23 16:43:29 <GNUtoo|laptop> mickey|, hi, welcome back
Jun 23 16:43:51 <badcloud> 'enlightenment_remote -module-list' doesn't seem to exist in the new version of e_remote
Jun 23 16:44:00 <mickey|> hi GNUtoo|laptop 
Jun 23 16:44:01 <badcloud> so I can't track down the option
Jun 23 16:44:25 <GNUtoo|laptop> mickey|, do you have time now to read my new mail about suspend? what should I do exactly?
Jun 23 16:45:04 <GNUtoo|laptop> I can also sum-up the mail in irc
Jun 23 16:45:13 <mickey|> hmm
Jun 23 16:45:22 <mickey|> i don't understand "the screen comes back but it doesn't resume"
Jun 23 16:45:24 <mickey|> because: 
Jun 23 16:45:40 <mickey|> the screen coming back is only when we push "on" to power/state
Jun 23 16:45:41 <GNUtoo|laptop> basically it's in the echo mem >/sys/power/state state
Jun 23 16:46:00 <GNUtoo|laptop> I know it because the touch part doesn't wrok
Jun 23 16:46:04 <GNUtoo|laptop> *work
Jun 23 16:46:15 <GNUtoo|laptop> but I see something on the screen,the backlight is on etc...
Jun 23 16:46:59 <mickey|> i don't understand how that can happen
Jun 23 16:47:07 <GNUtoo|laptop> I'll look
Jun 23 16:47:09 <mickey|> if the display is on, we did echo "on"
Jun 23 16:47:15 <GNUtoo|laptop> ah?
Jun 23 16:47:21 <GNUtoo|laptop> there is 2 things involved
Jun 23 16:47:22 <mickey|> we do not touch (sic!) the touchscreen at all
Jun 23 16:47:26 <GNUtoo|laptop> fsousaged
Jun 23 16:47:29 <GNUtoo|laptop> and fsodeviced
Jun 23 16:47:35 <GNUtoo|laptop> right?
Jun 23 16:48:06 <mickey|> yes, and no
Jun 23 16:48:10 <mickey|> strictly speaking
Jun 23 16:48:15 <mickey|> fsodeviced has nothing to do with suspend/resume
Jun 23 16:48:26 <mickey|> it's fsousaged alone
Jun 23 16:48:43 <GNUtoo|laptop> ok
Jun 23 16:49:01 <GNUtoo|laptop> what is responsible of getting the screen back when you're not suspended?
Jun 23 16:49:59 <mickey|> backlight handling and FBIOBLANK is a cooperation of fsodeviced and someone who listens to idle notification
Jun 23 16:50:53 <mickey|> what is happening when you do not run fsodeviced? do you still get display bakc?
Jun 23 16:51:13 <GNUtoo|laptop> I'll look
Jun 23 16:53:45 <GNUtoo|laptop> it doesn't come back
Jun 23 16:53:58 <GNUtoo|laptop> when I sleep 5s and apm -s
Jun 23 16:54:01 <GNUtoo|laptop> while disconnected
Jun 23 16:54:08 <GNUtoo|laptop> (USB disconnected)
Jun 23 16:54:19 <mickey|> oha
Jun 23 16:54:26 <mickey|> that's an important notice
Jun 23 16:54:34 <GNUtoo|laptop> I stopped fsodeviced with the init script and verified that fsousaged worked with pidof
Jun 23 16:54:43 <mickey|> that means we did _not_ echo "on" ...
Jun 23 16:54:51 <GNUtoo|laptop> indeed we did not
Jun 23 16:54:53 <mickey|> but display coming back was an artefact of FBIOUNBLAKN
Jun 23 16:55:00 <GNUtoo|laptop> 2010-06-23T16:52:24.625343Z [INFO]  UsageController <3 R>: >>>>>>> KERNEL SUSPEND
Jun 23 16:55:07 <GNUtoo|laptop> that's the last message of fsousaged
Jun 23 16:55:09 <mickey|> can you run it in foreground again?
Jun 23 16:55:17 <GNUtoo|laptop> ok
Jun 23 16:55:27 <mickey|> (temporary debug messages not going into the log)
Jun 23 16:56:59 <GNUtoo|laptop> ok let me try again
Jun 23 16:58:16 <GNUtoo|laptop> should I try with or without fsodeviced this time?
Jun 23 16:59:02 <mickey|> without
Jun 23 16:59:03 <CIA-58> freesmartphone.org: 03mickey 07vala-dbus-binding-tool * r03b5368d7a0b 10/src/vala-dbus-binding-tool.vala: 
Jun 23 16:59:03 <CIA-58> freesmartphone.org: refer to ObjectPath fully qualified as there are now two implementations
Jun 23 16:59:03 <CIA-58> freesmartphone.org: (one in gio-2.0 one in dbus-glib-1)
Jun 23 16:59:23 <mickey|> we need to find out why it never triggers the 'echo on'
Jun 23 16:59:43 <mickey|> just for reference
Jun 23 16:59:46 <mickey|> you don't have anyone else reading out
Jun 23 16:59:53 <mickey|>  proc/wakelocks_*
Jun 23 16:59:55 <mickey|> right?
Jun 23 17:00:01 <mickey|> (since those are cleared upon one read)
Jun 23 17:00:27 <GNUtoo|laptop> no
Jun 23 17:00:35 <GNUtoo|laptop> I don't read them for debugging this time
Jun 23 17:01:26 <GNUtoo|laptop> ah it say it did't felt asleep
Jun 23 17:01:30 <GNUtoo|laptop> I'll retry
Jun 23 17:02:08 <GNUtoo|laptop> let me see
Jun 23 17:02:12 <GNUtoo|laptop> maybe it felt before
Jun 23 17:02:55 <GNUtoo|laptop> it did twice
Jun 23 17:02:57 <GNUtoo|laptop> let me retry
Jun 23 17:03:31 <GNUtoo|laptop> because backlight was 0
Jun 23 17:06:25 <GNUtoo|laptop> ok it didn't come back
Jun 23 17:06:44 <GNUtoo|laptop> http://pastebin.com/DuTmwtZC
Jun 23 17:06:50 <GNUtoo|laptop> not even the screen
Jun 23 17:07:01 <GNUtoo|laptop> here what I got when I connected it back trough usb
Jun 23 17:07:14 <mickey|> hmm
Jun 23 17:07:16 <mickey|> that's all?
Jun 23 17:13:10 <GNUtoo|laptop> yes I've the normal log if you want
Jun 23 17:13:50 <mickey|> hmm, no, that won't help. it's unusable w/ those two logs. i need to bring all into one otherwise we can't see anything
Jun 23 17:14:00 <mickey|> you have run that in screen, right?
Jun 23 17:14:09 <GNUtoo|laptop> yes
Jun 23 17:14:12 <GNUtoo|laptop> also in tee
Jun 23 17:14:26 <GNUtoo|laptop> why not using syslog
Jun 23 17:14:31 <GNUtoo|laptop> we could do:
Jun 23 17:14:41 <GNUtoo|laptop> while true;logread -l;done | tee file
Jun 23 17:15:03 <GNUtoo|laptop> the other log:
Jun 23 17:15:04 <GNUtoo|laptop> 2010-06-23T17:04:00.522003Z [INFO]  UsageController <0 R>: >>>>>>> KERNEL SUSPEND
Jun 23 17:15:14 <GNUtoo|laptop> before that it loads the plugin
Jun 23 17:15:29 <ThibG> larsc, if I understand right, we should call request_irq and drop anything outside the demultiplexer's loop?
Jun 23 17:15:35 <GNUtoo|laptop> and before it's killed by me
Jun 23 17:16:49 <mickey||> <mickey|> hmm, no, that won't help. it's unusable w/ those two logs. i need to bring all into one otherwise we can't see anything
Jun 23 17:16:52 <mickey||> <mickey|> you have run that in screen, right?
Jun 23 17:16:54 <mickey||> <mickey|> (just to make sure you get updates after plugging usb)
Jun 23 17:16:56 <mickey||> <mickey|> my ssh connection seldomly survives when i don't run it in scree
Jun 23 17:17:18 <GNUtoo|laptop> ok
Jun 23 17:17:22 <GNUtoo|laptop> personally I said:
Jun 23 17:17:33 <GNUtoo|laptop> GNUtoo|laptop> why not using syslog
Jun 23 17:17:33 <GNUtoo|laptop> <GNUtoo|laptop> we could do:
Jun 23 17:17:33 <GNUtoo|laptop> <GNUtoo|laptop> while true;logread -l;done | tee file
Jun 23 17:17:33 <GNUtoo|laptop> <GNUtoo|laptop> the other log:
Jun 23 17:17:33 <GNUtoo|laptop> <GNUtoo|laptop> 2010-06-23T17:04:00.522003Z [INFO]  UsageController <0 R>: >>>>>>> KERNEL SUSPEND
Jun 23 17:17:34 <GNUtoo|laptop> <GNUtoo|laptop> before that it loads the plugin
Jun 23 17:18:45 <GNUtoo|laptop> so I wonder
Jun 23 17:19:03 <GNUtoo|laptop> ** (process:830): DEBUG: plugin.vala:149: --- we did! and now we're alive and kicking again!
Jun 23 17:19:15 <GNUtoo|laptop> why that didn't trigger a resume in the second log?
Jun 23 17:19:27 <GNUtoo|laptop> the one printing 2010-06-23T17:04:00.522003Z [INFO]  UsageController <0 R>: >>>>>>> KERNEL SUSPEND
Jun 23 17:23:14 <mickey||> that's the question
Jun 23 17:23:23 <mickey||> according to the code, it should
Jun 23 17:23:57 <mickey||> ok, let me add one thing
Jun 23 17:25:08 <larsc> ThibG: yes. I'm not sure if it's allowed to trigger a irq from a normal irq handler
Jun 23 17:25:47 <ThibG> ok, I'm looking at it :)
Jun 23 17:26:46 <CIA-58> freesmartphone.org: 03mickey 07cornucopia * r465f46bc8f67 10/fsousaged/src/plugins/lowlevel_android/plugin.vala: fsousaged: lowlevel_android: debug++
Jun 23 17:26:52 <mickey||> GNUtoo|laptop: can you try with this version, please?
Jun 23 17:28:31 <GNUtoo|laptop> ok
Jun 23 17:28:54 <ThibG> larsc, some mfd drivers use threaded IRQs and do the demultiplexing in the IRQ handler, using "handle_nested_irq"
Jun 23 17:29:16 <ThibG> (instead of generic_handle_irq)
Jun 23 17:29:26 <GNUtoo|laptop> btw sorry I was on the phone
Jun 23 17:29:38 <GNUtoo|laptop> (home phone as always,not the dream)
Jun 23 17:31:16 <larsc> ThibG: i know
Jun 23 17:31:31 <larsc> but handle_nested_irq only works for threaded irq handlers
Jun 23 17:31:55 <ThibG> hm ok
Jun 23 17:34:24 <GNUtoo|laptop> bitbaking the image now
Jun 23 17:37:09 <mickey||> oki
Jun 23 17:37:16 <mickey||> i moved everything to the same log now
Jun 23 17:37:24 <mickey||> so you don't need to run it in foreground
Jun 23 17:40:04 <GNUtoo|laptop> ok
Jun 23 17:50:20 <GNUtoo|laptop> ok doing rootfs
Jun 23 17:51:08 <mickeyl> good. i have 10 more minutes then i have to prepare for watching next game :)
Jun 23 17:51:15 <GNUtoo|laptop> ok 
Jun 23 17:51:41 <mickeyl> meanwhile lets update dbus to 1.3.1
Jun 23 17:52:02 <GNUtoo|laptop> I'm stupid...I'm doing the useless package-index
Jun 23 17:53:07 <GNUtoo|laptop> (it already did that: NOTE: package fso2-demo-image-1.0-r1: task do_package_update_index_ipk: Succeeded)
Jun 23 17:53:28 <GNUtoo|laptop> opkg-upgrading
Jun 23 17:53:30 <GNUtoo|laptop> 8 min left
Jun 23 17:54:50 <GNUtoo|laptop> booting
Jun 23 17:55:56 <GNUtoo|laptop> so I run it normally and everything will be in the logs?
Jun 23 17:56:19 <GNUtoo|laptop> killing fsodeviced
Jun 23 17:56:58 <mickeyl> yep
Jun 23 17:57:09 <GNUtoo|laptop> ok suspended
Jun 23 17:57:11 <mickeyl> (log_level = DEBUG, right?)
Jun 23 17:57:13 <GNUtoo|laptop> 4 min
Jun 23 17:57:17 <GNUtoo|laptop> by default yet
Jun 23 17:57:20 <GNUtoo|laptop> *yes
Jun 23 17:57:31 <GNUtoo|laptop> I had that before
Jun 23 17:57:37 <GNUtoo|laptop> I'll check at resume
Jun 23 17:58:01 <GNUtoo|laptop> no INFO
Jun 23 17:58:07 <GNUtoo|laptop> changing that
Jun 23 17:59:18 <GNUtoo|laptop> will you come back after the game?
Jun 23 17:59:22 <GNUtoo|laptop> when does the game finish?
Jun 23 18:00:04 <mickeyl> 2230 
Jun 23 18:00:27 <mickeyl> depends on the result whether i come back :)
Jun 23 18:00:28 <GNUtoo|laptop> http://pastebin.com/8qWjVEXx
Jun 23 18:00:32 <GNUtoo|laptop> ok
Jun 23 18:00:52 <GNUtoo|laptop> bad =>come back?
Jun 23 18:01:04 <mickeyl> yeah :
Jun 23 18:01:05 <mickeyl> )
Jun 23 18:01:08 <GNUtoo|laptop> ok
Jun 23 18:01:09 <mickeyl> otherwise some partying
Jun 23 18:01:11 <GNUtoo|laptop> look at the log
Jun 23 18:01:23 <GNUtoo|laptop> [DEBUG] LowLevelAndroid <>: Waiting for suspend returned with resume reason 'event3-531'
Jun 23 18:01:30 <GNUtoo|laptop> 2010-06-23T17:59:07.005004Z [DEBUG] LowLevelAndroid <>: Setting power state 'mem'
Jun 23 18:01:31 <mickeyl> oh!
Jun 23 18:01:35 <GNUtoo|laptop> indeed
Jun 23 18:01:37 <mickeyl> is that your power button?
Jun 23 18:01:42 <GNUtoo|laptop> yes
Jun 23 18:01:44 <mickeyl> d'oh
Jun 23 18:01:46 <GNUtoo|laptop> it's different than yours
Jun 23 18:01:48 <mickeyl> wtf
Jun 23 18:01:54 <GNUtoo|laptop> mine is 107 as keycode
Jun 23 18:01:57 <GNUtoo|laptop> yours is 103
Jun 23 18:02:01 <GNUtoo|laptop> or the coutrary
Jun 23 18:02:28 <GNUtoo|laptop> if it's not usb
Jun 23 18:02:31 <GNUtoo|laptop> it's the power button
Jun 23 18:02:36 <mickeyl> ok
Jun 23 18:02:39 <mickeyl> lets try a simple fix then
Jun 23 18:03:40 <CIA-58> freesmartphone.org: 03mickey 07cornucopia * r8361547901de 10/fsousaged/src/plugins/lowlevel_android/plugin.vala: fsousaged: lowlevel_android: trigger resume also on event3-531
Jun 23 18:03:51 <GNUtoo|laptop> ok bitbaking 
Jun 23 18:03:53 <GNUtoo|laptop> thanks a lot
Jun 23 18:03:55 <GNUtoo|laptop> see you soon
Jun 23 18:04:15 <mickeyl> np
Jun 23 18:04:16 <mickeyl> cu later
Jun 23 18:04:21 <GNUtoo|laptop> I'm not shure if I prefer your team to win or loose
Jun 23 18:04:23 <GNUtoo|laptop> lol
Jun 23 18:04:24 <GNUtoo|laptop> bye
Jun 23 18:04:25 <mickeyl> hehe
Jun 23 18:04:50 <GNUtoo|laptop> maybe see you during the adds
Jun 23 18:16:26 <leviathan|out> ls
Jun 23 18:16:31 <leviathan|out> GNUtoo|laptop: hi
Jun 23 18:16:40 <GNUtoo|laptop> hi
Jun 23 18:19:45 <GNUtoo|laptop> 2010-06-23T18:18:41.583923Z [DEBUG] LowLevelAndroid <>: Waiting for suspend returned with resume reason 'event3-523'
Jun 23 18:19:48 <GNUtoo|laptop> ???
Jun 23 18:32:27 <GNUtoo|laptop> 2010-06-23T18:31:23.218109Z [DEBUG] LowLevelAndroid <>: Waiting for suspend returned with resume reason 'event3-515'
Jun 23 18:34:58 <GNUtoo|laptop> ok mickeyl should listen for keypresses
Jun 23 18:37:04 <GNUtoo|laptop> hi leviathan|out 
Jun 23 18:37:15 <GNUtoo|laptop> any news
Jun 23 18:37:16 <GNUtoo|laptop> ?
Jun 23 18:38:31 <leviathan|out> hmm
Jun 23 18:38:46 <leviathan|out> I'm talking here right now, with some guys of my club
Jun 23 18:38:49 <leviathan|out> but...
Jun 23 18:38:52 <leviathan|out> hmm, lets see
Jun 23 18:39:03 <leviathan|out> did you forward the email to mickey?
Jun 23 18:39:08 <GNUtoo|laptop> yes
Jun 23 18:39:14 <GNUtoo|laptop> I did yesterday
Jun 23 18:39:18 <GNUtoo|laptop> but he's very busy
Jun 23 18:39:25 <leviathan|out> and the new version?
Jun 23 18:39:27 <GNUtoo|laptop> he didn't even read my mail on suspend
Jun 23 18:39:28 <GNUtoo|laptop> no
Jun 23 18:39:31 <GNUtoo|laptop> not the new version
Jun 23 18:39:40 <GNUtoo|laptop> but anyway he's watching the football now
Jun 23 18:40:10 <GNUtoo|laptop> I think hee needs to implement an /dev/input/event3 parser
Jun 23 18:41:24 <leviathan|out> hmm, ok
Jun 23 18:47:32 <GNUtoo|laptop> maybe I'll do it myself
Jun 23 18:47:35 <GNUtoo|laptop> it seem easy
Jun 23 18:47:40 <GNUtoo|laptop> it's already there
Jun 23 18:47:44 <GNUtoo|laptop> it's just commented
Jun 23 18:48:01 <GNUtoo|laptop> because he now uses the kenrel interfaces he added
Jun 23 18:48:05 <GNUtoo|laptop> but that doesn't work for input
Jun 23 18:51:22 <ThibG> larsc, I think calling generic_handle_irq inside a normal irq handler is allowed, however, I'm not sure it plays nicely with threaded "sub"-irqs
Jun 23 18:55:56 <GNUtoo|laptop> better wait for mickyel
Jun 23 18:56:04 <GNUtoo|laptop> I'll write a mail
Jun 23 19:03:07 <[Rui]> hi all
Jun 23 19:04:23 <GNUtoo|laptop> hi
Jun 23 19:07:27 <larsc> ThibG: that shouldn't be a problem, i think
Jun 23 19:07:58 <ThibG> well, let's try :)
Jun 23 19:35:18 <ThibG> glamo-fb does work, but glamo-mci seems to enter a deadlock
Jun 23 19:38:04 <ThibG> [  481.640000] INFO: task kmmcd:3093 blocked for more than 120 seconds.
Jun 23 19:38:05 <ThibG> indeed
Jun 23 19:46:30 <ThibG> larsc, my guess is that the previous implementation busy-loops while the IRQ haven't been handled
Jun 23 19:47:01 <GNUtoo|laptop> btw about freerunner Is xrandr -o 1 =>  thomas white's screen of death a known bug on 2.6.32
Jun 23 19:47:46 <ThibG> the current one returns after calling generic_handle_irq, but if the sub-driver's irq handling is threaded, then, generic_handle_irq will return straight away, and the demultiplexer will mark the IRQ as handled
Jun 23 19:47:57 <ThibG> although it's beeing handled by glamo-mci
Jun 23 19:49:39 <larsc> why will it mark it has handeled?
Jun 23 19:50:45 <ThibG> well, the demultiplexer returns
Jun 23 19:51:03 <ThibG> (it's just a guess)
Jun 23 19:53:05 <larsc> did you request the glamo irq with IRQF_DISABLED?
Jun 23 19:54:40 <ThibG> hm no, hm... nevermind... haven't had a look at the flags... copied... hm... gonna try :p
Jun 23 19:55:52 <larsc> it's gone in 2.6.35 so you'll have to remove it again before submitting
Jun 23 20:00:32 <leviathan|out> GNUtoo|laptop: I'll got home now
Jun 23 20:00:39 <leviathan|out> brb
Jun 23 20:00:42 <leviathan|out> :-)
Jun 23 20:00:49 <GNUtoo|laptop> ok
Jun 23 20:07:43 <ThibG> what is gone in 2.6.35?
Jun 23 20:10:16 <larsc> IRQF_DISABLED
Jun 23 20:10:48 <ThibG> sure? It's everywhere in rc3
Jun 23 20:11:08 <Q-Master> PaulFertser: here?
Jun 23 20:11:43 <larsc> it's a noop
Jun 23 20:12:26 <ThibG> hm ok
Jun 23 20:12:31 <larsc> all is scheduled for complete removal in 2.6.36
Jun 23 20:12:35 <larsc> aeh
Jun 23 20:12:40 <larsc> s/all/and
Jun 23 20:14:43 <Q-Master> mickey|WM: ping
Jun 23 20:14:55 <ThibG> thanks for the info
Jun 23 20:17:31 <Q-Master> PaulFertser: anyway. I've made a debug try with the problem we discovered. the funniest thing is that fsogsmd seems not responding to dbus calls
Jun 23 20:18:02 <Q-Master> mickey|WM: mdbused to fsogsmd. got this: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 23 20:18:46 <TAsn> OMG, just opkg upgraded and the phone is taking HOURS to boot :P 3 mins and counting.
Jun 23 20:19:00 <TAsn> And no but splash available
Jun 23 20:19:03 <TAsn> :(
Jun 23 20:19:05 <TAsn> boot*
Jun 23 20:19:13 <TAsn> Ok, finally.
Jun 23 20:19:21 <TAsn> Damn, that was slow.
Jun 23 20:22:27 <GNUtoo|laptop> Q-Master, he'll be back at 22:30 if their team loose
Jun 23 20:22:59 <Q-Master> GNUtoo|laptop: it's already 00:22 here. 8)
Jun 23 20:23:19 <GNUtoo|laptop> ah ok
Jun 23 20:23:28 <GNUtoo|laptop> here and where mickeyl is it's 22:23
Jun 23 20:23:50 <Q-Master> ah. 20 minutes is nothing then
Jun 23 20:24:53 <GNUtoo|laptop> he'll come back only if his team loose
Jun 23 20:24:57 <TAsn> GNUtoo|laptop, germany won
Jun 23 20:25:01 <GNUtoo|laptop> ok
Jun 23 20:25:11 <GNUtoo|laptop> so he won't come back
Jun 23 20:25:16 <TAsn> (it that's what you were talking about)
Jun 23 20:25:26 <GNUtoo|laptop> yes that's what I was talking about
Jun 23 20:25:30 <TAsn> :P
Jun 23 20:25:46 <GNUtoo|laptop> is it the world cup?
Jun 23 20:25:46 <TAsn> Next time it's Germany vs England :(
Jun 23 20:25:49 <GNUtoo|laptop> ok
Jun 23 20:25:52 <TAsn> GNUtoo|laptop, yes.
Jun 23 20:25:55 <GNUtoo|laptop> ok
Jun 23 20:26:03 <GNUtoo|laptop> maybe germany will win then?
Jun 23 20:26:11 <TAsn> In germany vs england?
Jun 23 20:26:20 <TAsn> Unfortunately they will win :(
Jun 23 20:26:23 <GNUtoo|laptop> no in germany vs world
Jun 23 20:26:30 <Q-Master> and with whom did they played today&
Jun 23 20:26:31 <Q-Master> ?
Jun 23 20:26:39 <TAsn> ghana
Jun 23 20:26:40 <GNUtoo|laptop> they seem good if they went until ther
Jun 23 20:26:46 <GNUtoo|laptop> *there
Jun 23 20:27:00 <GNUtoo|laptop> hi JaMa 
Jun 23 20:27:06 <GNUtoo|laptop> I'm doing the final git bisect
Jun 23 20:27:21 <TAsn> Anyhow, the world cup is too time consuming, I want it to end already! :P
Jun 23 20:27:31 <GNUtoo|laptop> lol
Jun 23 20:27:40 <GNUtoo|laptop> I do not watch the world cup
Jun 23 20:27:48 <TAsn> Or more correctly: I want it to end already and the next one to come! :P
Jun 23 20:27:57 <TAsn> GNUtoo|laptop, You are doing the right thing.
Jun 23 20:28:40 <GNUtoo|laptop> isn't there a world cup of FSO/SHR? where every new phone try to be fully working first
Jun 23 20:28:57 <TAsn> GNUtoo|laptop, nah.
Jun 23 20:28:58 <GNUtoo|laptop> like htcdream vs palm-pre vs nexusone vs htcleo vs...
Jun 23 20:29:12 <TAsn> well there is kinda
Jun 23 20:29:30 <TAsn> iPhone won the crowd's favorite to got in last in everything else :P
Jun 23 20:29:38 <TAsn> s/to/though/
Jun 23 20:29:39 <apt> TAsn meant: iPhone won the crowd's favorite though got in last in everything else :P
Jun 23 20:29:40 <GNUtoo|laptop> not shure
Jun 23 20:30:00 <TAsn> Motorola droid won: "The phone of the year"
Jun 23 20:30:02 <TAsn> I think.
Jun 23 20:30:05 <GNUtoo|laptop> there is more android phone sold than iSomething
Jun 23 20:30:17 <TAsn> GNUtoo|laptop, but people like the iPhone better.
Jun 23 20:30:21 <GNUtoo|laptop> ah
Jun 23 20:30:22 <GNUtoo|laptop> ok
Jun 23 20:30:25 <TAsn> for a reason I don't understand.
Jun 23 20:30:30 <TAsn> (btw)
Jun 23 20:30:32 <GNUtoo|laptop> ok 
Jun 23 20:30:38 <GNUtoo|laptop> maybe magick
Jun 23 20:30:41 <GNUtoo|laptop> I hate magick
Jun 23 20:30:48 <GNUtoo|laptop> I like to understand how things work
Jun 23 20:30:51 <TAsn> :P
Jun 23 20:30:57 <TAsn> Life is all about magic.
Jun 23 20:31:23 <GNUtoo|laptop> science vs magic
Jun 23 20:31:29 <GNUtoo|laptop> like in a free software game?
Jun 23 20:31:58 <TAsn> I don't know that free software game.
Jun 23 20:32:06 <GNUtoo|laptop> let me find the name
Jun 23 20:32:08 <TAsn> JaMa, 
Jun 23 20:32:11 <gena2x> all this stuff is popular because it is different.
Jun 23 20:32:15 <TAsn> ImportError: No module named dbus
Jun 23 20:32:22 <Deubeuliou> GNUtoo|laptop: Glest ?
Jun 23 20:32:35 <GNUtoo|laptop> yes
Jun 23 20:32:36 <TAsn> JaMa, :( Had to install it manually, it seems like it's missing in packages deps.
Jun 23 20:32:37 <GNUtoo|laptop> glest
Jun 23 20:32:48 <Deubeuliou> worst name ever, imho
Jun 23 20:32:53 <GNUtoo|laptop> lol
Jun 23 20:33:20 <GNUtoo|laptop> http://en.wikipedia.org/wiki/Glest
Jun 23 20:33:51 <GNUtoo|laptop> in another hand I always make the joke that free software embedded is like a RPG
Jun 23 20:33:58 <GNUtoo|laptop> with ELF,DWARF2
Jun 23 20:34:05 <GNUtoo|laptop> magic number in firmwares
Jun 23 20:34:08 <GNUtoo|laptop> etc...
Jun 23 20:34:30 <GNUtoo|laptop> there are cast to short
Jun 23 20:34:34 <GNUtoo|laptop> etc..
Jun 23 20:34:42 <GNUtoo|laptop> spell checker
Jun 23 20:34:59 <gena2x> yeah, like nethack. you can win only after 10 years of playing.
Jun 23 20:35:04 <GNUtoo|laptop> lol
Jun 23 20:35:18 <TAsn> Anyhow, I'm off to bed (actually to go study)
Jun 23 20:35:25 <GNUtoo|laptop> ok
Jun 23 20:35:28 <TAsn> Cya at the next world cup.
Jun 23 20:35:30 <TAsn> Ciao.
Jun 23 20:35:35 <GNUtoo|laptop> bye
Jun 23 20:35:38 <Wonka> hf, TAsn 
Jun 23 20:35:42 <TAsn> thanks.
Jun 23 20:40:52 <Q-Master> heh.
Jun 23 20:40:59 <Q-Master> fsogsmd is a bug
Jun 23 20:41:00 <Q-Master> 8)
Jun 23 20:41:11 <[Rui]> JaMa: found a bug with json-c :) uses plain ints rather than long long ints
Jun 23 20:46:46 <[Rui]> JaMa: since twitter statuses ID are in the many, many millions, and json-c detects them as integers, it uses the int type rather than long long int (which would be safer).
Jun 23 20:48:45 <[Rui]> I contacted the author, about that.
Jun 23 20:50:52 <mrmoku|wm> TAsn: so.... someday blody sunday ;)
Jun 23 20:51:35 <[Rui]> mrmoku|wm: well, they (UK) just admitted their bloody hands ;)
Jun 23 20:51:49 <mrmoku|wm> :P
Jun 23 20:52:12 <Q-Master> mrmoku|wm: I've tried to modify a contact today. It has a cyrillic letters. Tried to add 1 more field to it and failed. shr-contacts segfaulted
Jun 23 20:52:23 <Q-Master> mrmoku|wm: on saving
Jun 23 20:52:28 <mrmoku|wm> Q-Master: :/
Jun 23 20:52:41 <Q-Master> mrmoku|wm: it is very old bug
Jun 23 20:54:37 <Q-Master> mrmoku|wm: and I don't have any unread smses, but lock screen shows me one.
Jun 23 20:56:51 <Q-Master> mrmoku|wm: hm. and after xorg restart - no segfault on the same action...
Jun 23 21:03:57 <CIA-58> freesmartphone.org: 03mickey 07cornucopia * r29d0126ba770 10/fsousaged/src/plugins/lowlevel_android/plugin.vala: fsousaged: lowlevel_android: resurrecting input node grabbing for resume handling
Jun 23 21:04:26 <GNUtoo|laptop> hi mickey|WM 
Jun 23 21:04:30 <GNUtoo|laptop> I'll test
Jun 23 21:05:00 <mickey|WM> ok
Jun 23 21:05:04 <GNUtoo|laptop> thanks a lot
Jun 23 21:05:46 <mickey|WM> np, i hope this time we nailed it
Jun 23 21:05:50 <GNUtoo|laptop> ok
Jun 23 21:06:10 <mickey|WM> the input grabbing is a good idea anyways
Jun 23 21:06:18 <mickey|WM> since we don't want to the power key to be forwarded
Jun 23 21:06:25 <mickey|WM> when it's used to wake up
Jun 23 21:06:34 <GNUtoo|laptop> it will take the same time than before for bitbaking the image
Jun 23 21:06:45 <mickey|WM> why don't you only update fsousaged?
Jun 23 21:06:52 <GNUtoo|laptop> ok I'll do that
Jun 23 21:06:58 <GNUtoo|laptop> but I've to rebuild the cache anyway
Jun 23 21:07:32 <GNUtoo|laptop> (I was doing a git bisect for an opkg/oe issue for another machine)
Jun 23 21:07:36 <Q-Master> mickey|WM: fsogsmd refused to reply to dbus calls. killed it, then restarted by dbus and works for now
Jun 23 21:07:57 <Q-Master> mickey|WM: so, seems that it is a daemon bug, not hw
Jun 23 21:08:09 <GNUtoo|laptop> and playing pingus on the htcdream while waiting
Jun 23 21:09:43 <mickey|WM> Q-Master: any hint in the logs?
Jun 23 21:09:54 <GNUtoo|laptop> 34%
Jun 23 21:11:49 <GNUtoo|laptop> 58%
Jun 23 21:12:54 <GNUtoo|laptop> 75%
Jun 23 21:13:20 <GNUtoo|laptop> maybe I should have used bitbake -b
Jun 23 21:13:47 <Q-Master> mickey|WM: I think that there is something there. Do you have anything telling that DBusServiceResource resumed?
Jun 23 21:15:00 <GNUtoo|laptop> ok cross-compiling
Jun 23 21:16:46 <Q-Master> mickey|WM: everything seems the same as at other suspend/resume cycles, but just after the last resume it lost network, but telling that TiCalypsoModem <4C>: Modem Status changed to FSO_GSM_MODEM_STATUS_ALIVE_REGISTERED
Jun 23 21:17:06 <Q-Master> mickey|WM: seems that dbusservice not resumed
Jun 23 21:17:35 <GNUtoo|laptop> hmmm when playing with PaulFertser's emacs I got issue too with modem suspended
Jun 23 21:17:40 <Q-Master> mickey|WM: and on any incoming call I got this:
Jun 23 21:17:41 <Q-Master> 2010-06-23T20:15:37.285889Z [INFO]  libfsotransport <0710:2>: URC: [ "+CRING: VOICE" ]                                                                                                                                                       
Jun 23 21:17:42 <Q-Master> 2010-06-23T20:15:37.286541Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited '+CRING', 'VOICE'                                                                                                                       
Jun 23 21:17:42 <Q-Master> 2010-06-23T20:15:37.287445Z [DEBUG] FsoGsmGenericAtCallHandler <>: Synchronizing call status                         
Jun 23 21:18:32 <Q-Master> mickey|WM: last line repeated every 3-4 seconds till killing of fsogsmd
Jun 23 21:21:14 <GNUtoo|laptop> ok syncing
Jun 23 21:22:42 <GNUtoo|laptop> ok installed
Jun 23 21:25:07 <GNUtoo|laptop> wow
Jun 23 21:25:38 <ThibG> larsc, works with IRQF_DISABLED, at least it seems so
Jun 23 21:25:43 <GNUtoo|laptop> it resumed
Jun 23 21:25:57 <GNUtoo|laptop> not shure if it resumed at the first or at the second keypress tough
Jun 23 21:25:59 <GNUtoo|laptop> thanks a lot
Jun 23 21:26:04 <ThibG> without IRQF_DISABLED, we have to disable_irq_nosync & enable_irq?
Jun 23 21:26:40 <GNUtoo|laptop> it resume at the first keypress
Jun 23 21:28:02 <GNUtoo|laptop> I'll try with fsodeviced enabled now
Jun 23 21:29:54 <leviathan> GNUtoo|laptop: back
Jun 23 21:29:59 <leviathan> is mickey|WM back now?
Jun 23 21:31:41 <GNUtoo|laptop> yes
Jun 23 21:31:43 <GNUtoo|laptop> he is
Jun 23 21:33:15 <leviathan> excellent
Jun 23 21:33:18 <leviathan> mickey|WM: hi
Jun 23 21:33:38 <leviathan> did you recieve the corrected email from GNUtoo|laptop?
Jun 23 21:34:16 <GNUtoo|laptop> leviathan, I'm still testing but I think we've got some sort of userland suspend
Jun 23 21:35:10 <leviathan> GNUtoo|laptop: I ment the email concerning Samsung
Jun 23 21:35:11 <leviathan> :-)
Jun 23 21:35:38 <GNUtoo|laptop> yes I sent it to him
Jun 23 21:35:41 <GNUtoo|laptop> but not the new one
Jun 23 21:35:43 <leviathan> very well
Jun 23 21:35:45 <leviathan> oh
Jun 23 21:35:49 <leviathan> I'll do it then
Jun 23 21:36:14 <GNUtoo|laptop> ok
Jun 23 21:36:26 <GNUtoo|laptop> mickey|WM, If I let it suspend enough with fsodeviced it doesn't resume
Jun 23 21:36:49 <leviathan> mickey|WM: I've sent you an email
Jun 23 21:36:56 <leviathan> could you please review it?
Jun 23 21:37:35 <GNUtoo|laptop> ah it says key 114
Jun 23 21:38:07 <GNUtoo|laptop> http://pastebin.com/weGhGWnJ
Jun 23 21:38:12 <GNUtoo|laptop> I'll add the correct key
Jun 23 21:38:56 <GNUtoo|laptop> ouch...
Jun 23 21:39:00 <GNUtoo|laptop> evtest shows nothing
Jun 23 21:39:10 <GNUtoo|laptop> while fake-suspended
Jun 23 21:39:11 <GNUtoo|laptop> we have:
Jun 23 21:39:25 <Weiss> JaMa: could you point me at the xf86-video-glamo patch again?
Jun 23 21:39:26 <GNUtoo|laptop> evtest /dev/input/event3
Jun 23 21:39:33 <GNUtoo|laptop> which returns absolutely nothing
Jun 23 21:43:42 <leviathan> GNUtoo|oeee: ok
Jun 23 21:43:48 <leviathan> I guess, I'll sleep now
Jun 23 21:53:59 <[Rui]> Who can add a patch against json-c so it supports integers properly (aka use long long int rather than int)?
Jun 23 22:28:57 <ThibG> sveinung, ping
Jun 23 22:36:38 <sveinung> ThibG: recieved
Jun 23 22:44:35 <ThibG> larsc, it seems to work (even without IRQF_DISABLED), I'm sending it to the list. However, my testing is limited to one "client" (glamo-mci). Maybe we should test with Weiss's stuff first
Jun 23 22:52:43 <ThibG> 'night
Jun 23 23:12:10 <mickey|WM> GNUtoo|oeee: does it work with 114?
Jun 23 23:12:27 <GNUtoo|oeee> ah keycode 114
Jun 23 23:12:47 <GNUtoo|oeee> mickey|WM, I've tried a very long sleep
Jun 23 23:13:00 <GNUtoo|oeee> mickey|WM, I had to press the power button twice
Jun 23 23:13:10 <GNUtoo|oeee> basically the first time it resume
Jun 23 23:13:22 <GNUtoo|oeee> and then imediately after goo back to sleep
Jun 23 23:13:32 <GNUtoo|oeee> then I press a second time
Jun 23 23:13:37 <GNUtoo|oeee> and it's fully resumed
Jun 23 23:13:43 <mickey|WM> hmm, strange
Jun 23 23:13:58 <GNUtoo|oeee> mickey|WM, also we must be carefull, maybe input could go to sleep
Jun 23 23:14:06 <GNUtoo|oeee> that is to say
Jun 23 23:14:15 <GNUtoo|oeee> echo mem > /sys/power/state
Jun 23 23:14:22 <GNUtoo|oeee> evtest  /dev/input/event3
Jun 23 23:14:26 <GNUtoo|oeee> and nothing appeared
Jun 23 23:14:40 <GNUtoo|oeee> I've got that only 1 time
Jun 23 23:15:15 <mickey|WM> hmm, without fsousaged it should wake up a bit and let the event through
Jun 23 23:15:22 <mickey|WM> with fsousaged not, since we grab it
Jun 23 23:15:27 <mickey|WM> (if we suspend)
Jun 23 23:15:44 <GNUtoo|oeee> ok
Jun 23 23:15:49 <GNUtoo|oeee> not shure if it was with or without
Jun 23 23:16:07 <GNUtoo|oeee> anyway it was just to tell,for the record
Jun 23 23:16:07 <mickey|WM> ok, well so it almost works, that's an improvement
Jun 23 23:16:16 <GNUtoo|oeee> for future debuggings
Jun 23 23:16:23 <GNUtoo|oeee> a huge improvement
Jun 23 23:19:48 <GNUtoo|oeee> note that I've also fsodeviced now
Jun 23 23:20:49 <GNUtoo|oeee> how much time I should wait from a full resume to a full suspend on fso2-demo-image?
Jun 23 23:23:42 <GNUtoo|oeee> http://pastebin.com/Us8pY2yH
Jun 23 23:23:50 <GNUtoo|oeee> here's the log with the 2 keypress
Jun 23 23:28:36 <mickey|WM> hmm, interesting
Jun 23 23:28:49 <mickey|WM> i don't think it's a bug in fsousaged
Jun 23 23:29:12 <mickey|WM> could be autosuspend reaching a timeout or so
Jun 23 23:29:25 <GNUtoo|oeee> ?
Jun 23 23:29:31 <mickey|WM> will take a look when i have some time, i don't think it's hard to find
Jun 23 23:29:33 <GNUtoo|oeee> what's autosuspend
Jun 23 23:29:34 <GNUtoo|oeee> ok
Jun 23 23:29:52 <GNUtoo|oeee> btw
Jun 23 23:29:59 <GNUtoo|oeee> do you want more tests?
Jun 23 23:30:03 <GNUtoo|oeee> like with xorg?
Jun 23 23:30:17 <GNUtoo|oeee> when fso2-demo-image will work
Jun 23 23:30:52 <mickey|WM> yeah, lets see whether it still works with xorg then
Jun 23 23:31:10 <GNUtoo|oeee> ok
Jun 23 23:31:25 <mickey|WM> g'night
Jun 23 23:31:40 <GNUtoo|oeee> my phone will sleep
Jun 23 23:31:43 <GNUtoo|oeee> me too I think
**** ENDING LOGGING AT Thu Jun 24 02:59:58 2010