IRC log for #openezx on 20090524

02:25.11*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
02:26.16*** join/#openezx bjk (n=bjk@223.sub-75-200-234.myvzw.com)
03:09.21*** join/#openezx arne__ (i=nobody@dslc-082-082-067-081.pools.arcor-ip.net)
03:30.57*** join/#openezx WyrM1 (n=wyrm@20158157059.user.veloxzone.com.br)
03:31.47*** join/#openezx gmzhuo (n=gmzhuo@221.237.69.29)
04:49.30*** join/#openezx WyrM (n=wyrm@20158175126.user.veloxzone.com.br)
07:01.41Hopscotchgood morning
07:50.10*** join/#openezx sabrod (n=sab@mic92-8-82-234-143-184.fbx.proxad.net)
08:03.58*** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1)
08:06.36*** join/#openezx pH5 (n=ph5@p5485FD50.dip.t-dialin.net)
08:32.45*** join/#openezx gDD (n=gDD@unaffiliated/gdd)
09:11.47CIA-33OpenEZX: 03Antonio Ospite <ospite@studenti.unina.it> 07ezx/current * ra6dfc4a95d 10openezx/drivers/input/touchscreen/pcap_ts.c: Bring touchscreen driver back to a working state.
09:16.34*** join/#openezx gmzhuo-- (n=gmzhuo@125.70.86.27)
09:24.04*** join/#openezx WyrM1 (n=wyrm@20158145058.user.veloxzone.com.br)
09:30.43ao2hi WyrM I tried to remove the workqueue from the TS driver and use just the timer but I get "BUG: scheduling while atomic: python/905/0x00000103"
09:31.35ao2http://pastebin.com/d79f65038
11:37.36*** join/#openezx l403 (n=l@85.132.159.239)
12:59.39gmzhuo--Oh,Prison Break has finished
13:14.16tmzt?
13:22.21*** join/#openezx johanbr (n=j@blk-7-129-240.eastlink.ca)
13:47.50WyrMgood morning.
13:48.56WyrMao2: python?
14:12.00ao2eh WyrM I don't know where that python come from, let me try again
14:12.49WyrMthe irq handlers are executed from the pcapd thread.
14:13.47WyrMpython is really weird, something on mux maybe?
14:15.59*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
14:19.36ao2mux driver disabled
14:45.18WyrMnew driver on rc7?
14:45.30WyrMdrivers/scsi/fnic/
14:55.55*** join/#openezx Sleep_Walker (n=Sleep@193.179.96.131)
15:20.42WyrMhttp://developer.motorola.com/platforms/android/
15:35.33CIA-33OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r9c862f2ade 10openezx/drivers/char/ (ts0710_mux.c ts0710_mux_usb.c):
15:35.34CIA-33OpenEZX: From: Ilya Muromec <ilya.muromec@gmail.com>
15:35.34CIA-33OpenEZX: fix warnings, remove some useless code, fix ipc initialisation
15:37.38tmztkernel source?
15:37.40tmztfor android
15:37.54WyrMnope
15:38.03WyrMfor now just marketing I think.
15:38.04WyrM:)
15:38.20WyrMlater probably an sdk.
15:38.45WyrMkernel source only some months after they release android powered phones.
15:38.48WyrMas usual. :)
15:40.52tmztgoogle was nice enough to release kernel source a year before the phones
15:41.19tmztfor the dev boards, but very similar to the released device
15:45.03WyrMheh, moto is not google ;)
15:45.28WyrMa728, a760 are linux and they never released the kernel source.
15:46.08WyrMe680 (the first phone they released kernel source), first release came with "confidential proprietary" everywhere.
15:47.36WyrMeven today, a1600 kernel source is just s joke.
15:48.10WyrMas it doesn't contain the motorola bits (pmic driver, board file, etc..)
15:49.22WyrMin fact, only thing that was useful on a1600 release is the changes on the sd driver to support sdhc, but this was useful only for the modding community.
16:20.10*** join/#openezx alain2210 (n=alain@AMontsouris-151-1-18-245.w82-123.abo.wanadoo.fr)
16:28.11WyrMalain2210: I think you will not get ppp data with gprs on mux12
16:28.31alain2210wyrm: hello
16:28.42WyrMthe ppp you see on ttyACM on your host is not from BP.
16:28.51WyrMits from AP. :)
16:28.54WyrMhi! :)
16:29.03alain2210wyrm : from ap ?
16:29.51tmztopenmagx is going to need to use mxc tree from upstream you think? minor help from moto?
16:30.13alain2210wyrm : I think I have to understand how gprs works....
16:31.20WyrMalain2210: gprs on the original fw is a line discipline.
16:31.49WyrMalain2210: its not ppp data, the kernel handles it, with the gprs driver
16:32.30WyrMtmzt: magx is easier I think.
16:32.41WyrMtmzt: except for the security bits ;)
16:32.49alain2210thanks. I will have to read the gprs driver in 2.4 kernel.
16:38.49alain2210wyrm : yes in include/asm-arm/termios.h, there is #define N_GPRS      16  /* virtual GPRS data line discipline  */
16:40.05WyrMalain2210: basically what you have to do is to to port the gprsv.c driver from 2.4
16:40.13WyrMstart the gprs connection on mux6
16:40.32WyrMand then open mux12 and ioctl it to start the ldisc
16:40.58WyrMthis should give you a network interface and gprs should work.
16:41.16WyrMsend me the patch when you are done ;)
16:41.43alain2210wyrm : ;-) but I have not found the gprsv.c...
16:41.57WyrMits on opensource.motorola.
16:42.35alain2210I have a kernel 2.4 for e680 found on opensource.motorola....
16:42.46WyrMjust a min.
16:42.53WyrMI will give you the link.
16:44.35*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:45.56WyrMmy net is so slow today :/
16:46.13WyrMhttps://opensource.motorola.com/sf/frs/do/downloadFile/projects.a780e680/frs.a780_e680_source.gprsv_source/frs1016?dl=1
16:46.28alain2210wyrm: I have not have the time to test strace, but I will. ;-)
16:46.42WyrMnp :)
16:48.01WyrMyou are working on stuf that will still need some time to go upstream :)
16:49.26alain2210wyrm: I would like to use the phone for making my mail where I have no network....
16:50.30alain2210I have read the gprsv.c, and I have no idea of the amount of work. I will see...
16:50.31WyrMwe are still far from an usable firmware alain2210.
16:50.49alain2210wyrm : I don't think so...
16:51.19WyrMalain2210: are you using the python implementation of fso?
16:51.22alain2210wyrm: yesterday, I succeed in sending/receiving sms.
16:51.35alain2210yes with fso and zhone.
16:51.54WyrMalain2210: well, we can get everything working, its not the hard part.
16:52.03WyrMthe hard part is to get everything stable. ;)
16:52.11WyrMand preferably with mainline grade code.
16:52.29WyrMalso, the python fso implementation can't work nice on ezx.
16:52.37WyrMwe don't have enough RAM.
16:52.38alain2210but it is not so unstable... (since your a catching the official kernel)
16:52.50alain2210it works.
16:53.04alain2210I need some time a little swap.
16:53.21alain2210of course, I wait for the vala version of fso.
16:53.58alain2210but I think where are near of something unstable but working.
16:54.10WyrMI don't even dare to try to have something usable at this point ;)
16:54.30WyrMwe will need to break a lot of stuff to make it mainline grade.
16:54.39alain2210I'm probably optimist since I do not know....
16:54.51WyrMeg, mux is being rewritten now.
16:55.08alain2210I see. But I have not test a recent kernel.
16:55.19alain2210s/test/tested/
16:55.42WyrMyeah, the point is that some apis will change.
16:55.53WyrMand userspace will need to be updated too.
16:56.31alain2210fso is very adaptable. we will see.
16:57.08WyrMbut anyway, we are still far from mainlining IPC/MUX
16:57.11WyrM:)
16:57.44alain2210I'm very ignorant about this.
16:57.48tmztao2 is working on this right?
16:58.45WyrMtmzt: Ilya Muromec is working on mux
16:59.15WyrMao2 is working on ADC/TS.
16:59.39tmztoh,
16:59.40tmztok
17:02.22WyrMtmzt: btw, have you looked at the current ezx/mach/motoq patch?
17:02.30WyrMI want to submit it upstream asap.
17:02.37tmztlooked at or tested?
17:02.52tmztI have 50 terminals right now
17:02.57WyrMbecause then I can submit the pcap support together with openezx.
17:02.59tmztmaybe 20 but still alot
17:03.09WyrMtmzt: looked, I don't expect it to work.
17:03.22WyrMbut it will be sent upstream, so, it needs to be clean ;)
17:03.49WyrMI mean... the support is minimum, but it needs to be correct.
17:05.13WyrMeg, the key comments, a lot of '?' :)
17:05.29tmztwhere can I see on the gitweb?
17:05.34tmztoh, the keys
17:05.35WyrMpin_config seems to be incomplete.
17:05.40tmztyeah
17:06.00tmztif you can give me the address range to dump in haret I can do that
17:06.15tmztthe I can make a python parser or something
17:06.55tmztis it a topgit patch you want me to look at?
17:07.03WyrMyes
17:07.09WyrMezx/mach/motoq
17:07.13tmztcan you paste it?
17:07.18WyrMsure
17:07.18tmztI don't have a tree right now
17:08.04WyrMhttp://people.openezx.org/wyrm/motoq.patch
17:09.36WyrMmostly I need a complete pin_config
17:09.44WyrMto avoid having to ammend it later.
17:09.58tmztright, and then I should be able to verify all the keys
17:10.18tmztdo you know the range to dump on pxa to get all the alt settings?
17:10.39WyrMnot from memory.
17:10.43WyrMbut its on the manual.
17:11.42WyrMwe need Low Power config too.
17:11.52tmztwhat I should tell you is the keys are basically right, but with different degrees of confidence
17:12.03WyrMPEDR, PRER, PGSR.
17:12.05tmztand I have some mapped for conveinience
17:12.17tmztlike right softkey is tab
17:12.30tmztthe names in comments are what they should be
17:13.17tmztthe ones I've duplicated are the ones I'm not sure of
17:14.17tmztI need to add keycode printks back to the kernel
17:14.23tmztraw matrix scanscodes
17:22.40tmztWyrM: alright, what can I do for this alt settings and lpm?
17:23.04WyrMdump correct values from haret :)
17:23.07WyrMand translate them,
18:09.15*** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be)
19:23.39*** join/#openezx WyrM1 (n=wyrm@20158164020.user.veloxzone.com.br)
19:35.38*** join/#openezx bjk (n=bjk@223.sub-75-200-234.myvzw.com)
19:38.22*** join/#openezx johanbr (n=j@JBrannlund2.MathStat.Dal.Ca)
20:50.01*** join/#openezx flo_lap (n=fuchs@f048244174.adsl.alicedsl.de)
21:59.45*** join/#openezx pH5 (n=ph5@e178213068.adsl.alicedsl.de)
22:14.37*** join/#openezx muromec (n=muromec@79.140.14.132)
22:14.43muromechi
22:15.01WyrMhi
22:15.02WyrM:)
22:18.51*** join/#openezx WyrM1 (n=wyrm@20158178152.user.veloxzone.com.br)
22:30.10WyrM~seen stefan_schmidt
22:30.13purlstefan_schmidt <n=stefan@p5B036695.dip.t-dialin.net> was last seen on IRC in channel #openezx, 15d 23h 58m 52s ago, saying: 'night folks'.

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