IRC log for #openezx on 20090628

00:31.13*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
03:08.45*** join/#openezx arne__ (i=nobody@dslc-082-082-077-119.pools.arcor-ip.net)
03:14.02*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
05:11.21*** join/#openezx bartv (n=bart@thisnet.xs4all.nl) [NETSPLIT VICTIM]
05:23.04*** join/#openezx ecloud_work (n=srutledg@gw.autoxray.com) [NETSPLIT VICTIM]
05:35.25*** join/#openezx agd5f (n=alex@c-69-143-4-28.hsd1.va.comcast.net)
07:41.59Hopscotchgood morning
08:14.23*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
09:10.36*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
09:12.28*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
09:13.24*** join/#openezx pH5 (n=ph5@e178205188.adsl.alicedsl.de)
09:30.43*** join/#openezx darion76 (n=darion76@94-248-108-66.dynamic.peoplenet.ua)
10:55.36*** part/#openezx majia321 (n=gDD@unaffiliated/gdd)
10:58.47*** join/#openezx FeLLa (n=46241@mnhm-590d80cf.pool.einsundeins.de)
11:19.43*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
12:06.38*** join/#openezx FeLLa (n=46241@mnhm-590d80cf.pool.einsundeins.de)
12:36.18*** join/#openezx medhu (n=medhamsh@124.125.110.212)
12:36.59medhui am a newbie to openezx, i am unable to find the boot_usb program to download.
12:37.04medhuplease help
12:37.34medhuplease point me to some exact how tos of porting openezx on my motorola a780.
12:41.42gmzhuoHi medhu,maybe this will help you,http://people.openezx.org/wyrm/boot_usb
12:46.00medhuthanks gmzhuo
12:46.08medhui have downloaded.
12:46.27medhuany luck for me regarding the "how to" documentation
12:50.08*** join/#openezx FeLLa (n=46241@mnhm-590d80cf.pool.einsundeins.de)
12:54.35*** join/#openezx medhu (n=medhamsh@124.125.110.212)
13:37.22*** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1)
14:16.49*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
14:24.03*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
14:32.24*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
14:42.40*** join/#openezx gmzhuo_ (n=gmzhuo@118.112.103.3)
14:44.24*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
14:50.09*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
14:51.31*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
14:58.27*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
16:01.22*** join/#openezx gmzhuo (n=gmzhuo@118.112.103.3)
16:08.12*** join/#openezx darion76 (n=darion76@94-248-108-66.dynamic.peoplenet.ua)
17:05.16*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
17:09.25WyrMhi.
17:09.31ao2hi WyrM
17:10.06ao2the jack insertion api will send an input event I've checked that, now I am trying to use it...
17:10.34ao2if it will prove useful we could remove that part from the misc input driver
17:10.34WyrMao2: good, so we can drop the jack insertion event from the pcap_keys.c driver :)
17:10.40WyrMthanks for looking at this.
17:11.04ao2well, thanks to you for looking at everything else :)
17:11.28WyrMI did some tests with cpufreq last night.
17:12.10ao2mmh, interesting matter
17:12.21WyrMwith the "ondemand" governor I have some weird white lines on the FB whenever it switches the frequency
17:12.35WyrMand something is wrong with touchscreen.
17:13.00WyrMif I try to use the touchscreen when running at a lower speed (104mhz), the kernel deadlocks.
17:13.36WyrMbut the regulator part seems to be working.
17:13.40WyrMlet me push it.
17:14.08CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r01934e9471 10openezx/drivers/regulator/pcap-regulator.c: register the driver at subsys_initcall so it can be used by cpufreq
17:14.09CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * rcf232f4802 10openezx/drivers/mfd/ezx-pcap.c: register early so the regulator may be used by cpufreq
17:14.09CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r959a549406 10openezx/ (.topdeps .topmsg drivers/spi/pxa2xx_spi.c): create, register pxa2xx_spi early
17:14.16CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * rf6a9663dfa 10openezx/arch/arm/mach-pxa/ezx.c: register SW1 regulator for cpufreq
17:14.17CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * rec0e001108 10openezx/.topdeps: add dependency on spi/pxa2xx_spi-register-early
17:16.46yanghi ao2 , WyrM
17:16.55WyrMhi yang
17:17.00ao2hi yang
17:22.06mickeylhi
17:22.10ao2WyrM, I am trying to dump the RAM from gen-blob in order to see a backtrace message, how much time I have to reinsert the battery before memory gets erased?
17:22.42ao2I am using this command "./boot_usb read 0xa0000000 31457280 memdump" but I can't see the backtrace in the resulting file
17:22.44ao2hi mickeyl
17:29.10WyrMao2: I have no idea.
17:29.32ao2ok, I'll try again
17:29.44WyrMao2: on my a780 I had results of the RAM being preserved for more than 10 minutes without battery.
17:34.26WyrMao2: its usually at the end of the file... I have a dump here, and the kernel messages are around 0x3aa000.
17:34.26WyrMI just use "strings" ;)
17:37.04*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
17:39.01WyrMhttp://www.clicrbs.com.br/blog/jsp/default.jsp?uf=1&pg=1&coldir=1&section=Blogs&topo=4236.dwt&uf=1&local=1&template=3948.dwt&source=DYNAMIC,blog.BlogDataServer,getBlog&blog=153&tipo=1&post=197129
18:12.28ao2WyrM, I have those symptoms: If I enter gen-blob usb mode with POwer button and Vol+ (that is after the 2.4 has been loaded) I can dump what I want. If I enter gen-blob simply with Vol+ pressed when inserting the battery (skiipng the 2.4 alltogether I guess) the phone turns off after a while I am reading the ram.
18:12.39ao2*these
18:13.45ao2is this expected? I am charging the battery anyway just to be sure it is not only a power issue
18:14.06WyrMweird.
18:14.06WyrMI only tested this on gen2.
18:14.07WyrMwhere 2.4 is not loaded on battery insertion.
18:14.32WyrMtry to read a smaller block on RAM.
18:14.54WyrMI guess that gen1 has a watchdog even if we don't complete the handshake.
18:15.15ao2that is is with a780, I will retest both large and small blocks with a fully charged battery later
18:23.33WyrMao2: do you know about this new dev_pm_ops thing.
18:24.13WyrMIm getting a lot of kernel messages saying that basically _all_ of our and pxa drivers need to be updated.
18:24.30ao2WyrM, no
18:24.44CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r16bf36663d 10openezx/drivers/input/touchscreen/pcap_ts.c: Antonio Ospite comments
18:24.46CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r046724ccf4 10openezx/drivers/input/touchscreen/pcap_ts.c: Trilok Soni comments
18:24.47CIA-27OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r3660b3d3e0 10openezx/drivers/input/keyboard/pcap_keys.c: Trilok Soni comments
18:26.30WyrM[   47.756553] Platform driver 'pcap-ts' needs updating - please use dev_pm_ops
18:28.59WyrMno more platform_driver->suspend/resume.
18:34.30*** join/#openezx FeLLa (n=46241@mnhm-590d80cf.pool.einsundeins.de)
18:42.59*** join/#openezx flyhorse|linux (n=flyhorse@116.18.188.58)
19:22.08*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
19:26.26*** join/#openezx _Andrew (n=andrew@unaffiliated/andrew/x-643872)
20:03.08*** join/#openezx tombhadAC (n=tombhad@pD95DFC19.dip.t-dialin.net)
20:28.05*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
20:55.40*** join/#openezx purl (i=ibot@rikers.org)
20:55.40*** topic/#openezx is OpenEZX Developer Lounge -- http://www.openezx.org
21:57.16*** join/#openezx florian (n=fuchs@g228202028.adsl.alicedsl.de)
22:19.44ao2WyrM, I verified that when gen-blob is loaded right on battery insertion (without letting 2.4 to be loaded) then gen1 phones shut off after exactly 1 minute. No matter if you read something from ram or not. So it is the watchdog.
22:21.45WyrMao2: I don't remember if SECSPI (the port where AP is connected to PCAP on gen1) has access to disable the watchdog.
22:21.57WyrMand I don't know if the PCAP watchdog is used at all.
22:22.11WyrMor if BP software is running and asks the poweroff.
22:25.58WyrMao2: there is a way to workaround the issue.
22:26.11WyrMao2: do what you are doing.
22:26.25WyrMbut instead of trying to read the RAM after inserting the battery.
22:26.33WyrMuse "boot_usb off"
22:26.42WyrMand then power on again to read the RAM dump.
22:26.56WyrMshould work, the 2.4 kernel will not overwrite everything.
22:27.20ao2even if it is booted?
22:27.29WyrMit will not be booted.
22:27.44WyrMinsert the battery with vol+ pressed.
22:27.49tmztWyrM: almost have mfp configs
22:27.58WyrMbut instead or "boot_usb read", use "boot_usb off"
22:28.09WyrMthe phone will power off, without loading the 2.4 kernel.
22:28.11tmztpython code: http://pastebin.com/m247433eb
22:28.26ao2ok, but maybe I misunderstood the second "power on" part
22:28.31WyrMthen you power on again, with vol+, so there is no watchdog :)
22:28.46ao2ok, now it is clear
22:29.04WyrMtmzt: good. :)
22:34.25ao2WyrM, worked perfectly, thanks!
22:53.19*** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz)
23:55.13WyrMao2: have you got the trace?
23:55.16WyrMwhat was wrong?
23:56.52ao2WyrM, something about pxa_camera but I will look at that tomorrow, I wanted to try that jack api stuff first, no good news yet

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.