| 00:30.39 | *** join/#openezx WyrM1 (n=wyrm@20158150073.user.veloxzone.com.br) |
| 01:37.50 | *** join/#openezx johanbr (n=j@DF007.VPN.Dal.Ca) |
| 02:44.50 | *** join/#openezx SuN (i=unices@82-170-225-106.ip.telfort.nl) |
| 03:10.18 | *** join/#openezx arne_ (i=nobody@dslc-082-082-082-145.pools.arcor-ip.net) |
| 03:26.41 | *** join/#openezx james__ (n=james@gimel.esc.cam.ac.uk) |
| 04:30.28 | *** join/#openezx WyrM (n=wyrm@20158141107.user.veloxzone.com.br) |
| 05:26.53 | *** join/#openezx WyrM (n=wyrm@20158144002.user.veloxzone.com.br) |
| 05:30.26 | *** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 06:31.23 | *** join/#openezx stefan_schmidt (n=stefan@w1686.wlan.rz.tu-bs.de) |
| 06:33.52 | *** join/#openezx methril|work (n=Methril@213.27.233.98) |
| 07:04.46 | *** join/#openezx pleemans (n=toi@d51A49C45.access.telenet.be) |
| 07:18.05 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 07:29.26 | *** join/#openezx alain2210 (n=alain@AMontsouris-151-1-66-165.w82-123.abo.wanadoo.fr) |
| 07:38.06 | Hopscotch | good morning |
| 07:40.11 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 07:40.33 | ao2 | hi |
| 08:37.31 | *** join/#openezx Sleep_Walker (n=Sleep@nat/suse/x-e726bed4f762f6f3) |
| 09:17.37 | *** join/#openezx gDD (n=gDD@unaffiliated/gdd) |
| 09:59.00 | *** join/#openezx florian_kc (n=fuchs@port-217-146-132-69.static.qsc.de) |
| 10:31.21 | *** join/#openezx gDD (n=gDD@unaffiliated/gdd) |
| 10:36.35 | ao2 | WyrM, in Atlas documentation I read that it is possible to start ADC conversion even periodically on an ADTRIG interrupt, if this is possible on PCAP as well we could base the ts driver on this concept, I mean letting the hardware handle the timer, but I don't know yet. |
| 10:36.53 | WyrM | ao2: yes, it is. |
| 10:37.35 | WyrM | but I think we don't have adtrig on pcap2. |
| 10:37.55 | WyrM | adtrig is a gpio that pxa interrupts the PMCI to start the conversion.. |
| 10:38.09 | ao2 | WyrM, and should I add some queuing mechanism to adc driver? To handle conversion request by different sources? |
| 10:38.18 | WyrM | ao2: yes. |
| 10:38.56 | WyrM | previous code I removed from ezx-pcap.c did no queueing. It was doing only blocking when the adc was in use. |
| 10:39.07 | ao2 | ok, right now, I am just studying and rebuilding a prototype based on old code, then I will break it an redesign. |
| 10:40.25 | WyrM | and we need to provide some sync conversion too. to block until the conversion result is ready. |
| 10:40.50 | WyrM | the spi subsystem provides both queueing for spi message as sync. |
| 10:40.55 | ao2 | I spent yesterday reading something about what an ADC _is_ :) and how it works. I am starting to put pieces together. Yes, the documentation also have some notes about conflicting conversion requests. |
| 10:41.01 | WyrM | it may be a good source of ideas. |
| 10:41.35 | WyrM | yeah, but the conflict may not apply to pcap. :) |
| 10:42.41 | WyrM | anyway, don't care about the possible conflict yet. just assume that adc is not shared with BP. |
| 10:43.23 | ao2 | ok, let's see what comes out |
| 10:46.22 | WyrM | ilya is doing great progress on mux stuff. |
| 10:46.38 | WyrM | but we will need some more changes on userspace. |
| 10:46.41 | WyrM | 2 ioctls. |
| 10:46.50 | WyrM | one to start the handshake. |
| 10:47.03 | WyrM | and another to setup the line discipline. |
| 10:48.15 | WyrM | this way we will not have timing problems anymore, the handshake ioctl will start the bp only when everything is ready on userspace, and will cause the enumeration at the right time. |
| 10:48.47 | WyrM | and using a line discipline for mux (and providing a raw tty with muxed data) will allow an userspace implementation of ts0710. |
| 10:50.31 | WyrM | things are moving on a nice rhythm now. Sometimes its good to break stuff and do a restart. ;) |
| 10:57.05 | mickey|zzZZzz | :) |
| 10:57.09 | mickey|zzZZzz | great to hear |
| 10:57.49 | mickeyl | btw., are you sure we receive the +KPEVENT (or however it's called) on all models on holding POWER key for a while (how long is that while?). I can't seem to remember that I've seen it on my 780 |
| 11:07.45 | WyrM | mickeyl: only on a780/e680 |
| 11:07.54 | WyrM | and its +EKEV |
| 11:08.53 | mickeyl | ok, so this is for gen1 only |
| 11:48.55 | *** join/#openezx marex (i=marex@eduroam81.ms.mff.cuni.cz) |
| 12:00.17 | *** join/#openezx gDD (n=gDD@unaffiliated/gdd) |
| 12:13.55 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 12:20.27 | *** join/#openezx gmzhuo-- (n=gmzhuo@118.113.165.89) |
| 13:19.35 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 13:36.34 | *** join/#openezx sabrod (n=sab@lns-bzn-31-82-252-253-76.adsl.proxad.net) |
| 13:41.08 | gmzhuo | Hi mickeyl |
| 13:43.04 | mickeyl | hey gmzhuo |
| 13:51.34 | yang | hello mickeyl |
| 13:51.47 | mickeyl | hi yang |
| 13:52.09 | yang | mickeyl: last year, when you were purchasing a new phone off Ebay, which one did you buy? |
| 13:52.47 | mickeyl | i grabbed a 910 |
| 13:53.00 | yang | No, you said it was around 300 EUR |
| 13:53.50 | yang | seems a bit much for the a910 |
| 13:54.12 | mickeyl | well, it was a new one |
| 13:54.20 | yang | ok |
| 13:54.37 | yang | I guess I got a real bargain for mine then |
| 13:55.18 | mickeyl | how much did you pay?` |
| 13:55.30 | yang | i think 50 with shipping for a refurbished model |
| 13:56.04 | mickeyl | wow |
| 13:56.07 | mickeyl | that's a steal |
| 13:56.09 | mickeyl | good job |
| 13:56.57 | yang | www.ebay.co.uk |
| 13:57.12 | yang | Some Britain provider of refurbished phones |
| 13:57.17 | yang | Brittish |
| 13:57.44 | yang | mickeyl: how close is the OM port for the A910's ? |
| 13:58.01 | mickeyl | well |
| 13:58.07 | mickeyl | there's no such things as an OM port |
| 13:58.11 | mickeyl | lets break it down to |
| 13:58.16 | mickeyl | kernel, middleware, UI |
| 13:58.31 | mickeyl | kernel i have no idea |
| 13:58.41 | mickeyl | middleware i think it should be more or less on par with the other models |
| 13:58.51 | mickeyl | although i never tried to install anything custom on mine |
| 13:59.05 | mickeyl | didn't touch it since buying :/ |
| 13:59.15 | mickeyl | UI will be challenging due to the softkey interface |
| 13:59.27 | mickeyl | we have a conference with the SHR-project.org guys end of this week |
| 13:59.37 | mickeyl | i will raise the issue of supporting different UI metaphors to them |
| 13:59.55 | mickeyl | i expect them to deliver the UIs we can use for openezx |
| 14:00.38 | yang | mickeyl: but OM was working on previous builds, later "something" changed and now the GUI doesn't work |
| 14:00.55 | mickeyl | well |
| 14:01.07 | mickeyl | the thing you refer to as OM was a set of Gtk apps which are unmaintained |
| 14:01.22 | mickeyl | these days OM works on phone UIs based on EFL |
| 14:01.43 | mickeyl | (the remaining parts of OM Inc., that is... 2 people ) |
| 14:01.52 | mickeyl | (for software) |
| 14:02.14 | yang | ok, thanks for the explanation |
| 14:03.26 | mickeyl | I haven't worked on UI since years |
| 14:03.28 | mickeyl | i'm really missing that |
| 14:03.37 | mickeyl | so if noone else will do anything good, i'll do it |
| 14:04.52 | yang | i guess it will take some more time, untill finished product with GUI, at least byy the end of year (my guess) |
| 14:05.08 | mickeyl | yeah |
| 14:05.40 | yang | From these device seems that only Neo and G1 have some full support |
| 14:07.40 | yang | From the amount of coders on the OpenEZX project, I think the guys do a good work |
| 14:08.02 | yang | It would probably be much easier with a motorola support |
| 14:28.13 | *** join/#openezx darion76 (n=darion76@94-248-85-78.dynamic.peoplenet.ua) |
| 14:55.39 | *** join/#openezx pH5 (n=ph5@e178193101.adsl.alicedsl.de) |
| 15:04.15 | *** join/#openezx darion76 (n=darion76@94-248-85-78.dynamic.peoplenet.ua) [NETSPLIT VICTIM] |
| 15:04.15 | *** join/#openezx WyrM (n=wyrm@20158144002.user.veloxzone.com.br) [NETSPLIT VICTIM] |
| 15:07.14 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * rde908f1a37 10openezx/include/linux/mfd/ezx-pcap.h: these are no longer used |
| 15:10.03 | *** join/#openezx gDD_mobilE (n=gDD@unaffiliated/gdd) |
| 15:19.34 | WyrM | I will break bp code on openezx.git |
| 15:19.52 | WyrM | and commit the current muromec cleanup code. |
| 15:20.19 | gmzhuo | let's go:) |
| 15:20.32 | WyrM | it looks better than the original ;) |
| 15:21.48 | WyrM | http://pastebin.com/m4d40a9d |
| 15:21.59 | WyrM | heh, almost a full rewrite. :) |
| 15:23.26 | gmzhuo | when will you commit it? |
| 15:23.34 | WyrM | now. |
| 15:23.43 | WyrM | but I got some rejects that I will need to solve. :( |
| 15:24.05 | gmzhuo | rejects? |
| 15:24.14 | ao2 | 2000 lines removed? |
| 15:24.33 | WyrM | gmzhuo: yeah, conflicts. |
| 15:24.44 | WyrM | ao2: 3000 |
| 15:24.58 | WyrM | oh, 3000 - 1000, yeah ;) |
| 15:25.09 | gmzhuo | :) |
| 15:25.27 | ao2 | wow, that is a cleanup |
| 15:25.44 | WyrM | well, it has some new features too. ;) |
| 15:28.22 | gmzhuo | include discipline? |
| 15:28.32 | WyrM | yes |
| 15:28.43 | ao2 | WyrM, any clue about why I can't get to the probe function with a pcap subdriver with this structure http://pastebin.ca/1426465? |
| 15:29.45 | WyrM | ao2: probably something wrong on pcap-core. |
| 15:29.52 | WyrM | I haven't tested this ;) |
| 15:30.10 | ao2 | ok, that's a starting point at least, thanks |
| 15:30.10 | WyrM | altough it's almost a cutnpaste from da903x driver. |
| 15:34.02 | mickeyl | alain2210: +EKEV is not handled in FSO |
| 15:34.21 | mickeyl | alain2210: as promised it triggers org.freesmartphone.GSM.Device.KeypadEvent( s, b ) |
| 15:34.29 | mickeyl | err |
| 15:34.31 | mickeyl | s/not/now/ |
| 15:34.32 | mickeyl | :) |
| 15:51.08 | alain2210 | mickeyl : thanks |
| 15:51.27 | mickeyl | we can now catch this signal how we like |
| 15:51.36 | mickeyl | either with a Trigger,Action pair in oeventsd |
| 15:51.41 | mickeyl | or from any UI |
| 15:52.21 | alain2210 | I have to read how work oeventsd. |
| 15:56.37 | alain2210 | By the way, IIRC, there is another signal that is generated but not used : when a sms is received in not |
| 15:56.41 | alain2210 | buffered mode. |
| 15:58.26 | mickeyl | other than +CMT? |
| 15:59.37 | alain2210 | yes recieved with +CMT. |
| 15:59.48 | alain2210 | and fso send a signal. |
| 15:59.58 | alain2210 | but nothing after that. |
| 16:00.13 | mickeyl | what would you expect? |
| 16:00.24 | mickeyl | in direct mode the signal contains the SMS |
| 16:00.45 | mickeyl | if the UI doesn't pick it up, it's gone |
| 16:00.48 | alain2210 | that the sms will be decoded anywhere. |
| 16:00.57 | mickeyl | the sms should already be decoded |
| 16:01.02 | mickeyl | should come out via cleartext |
| 16:01.05 | mickeyl | in the signal |
| 16:01.10 | mickeyl | is it not for you? |
| 16:01.38 | alain2210 | I see the signal in frameworkd.log saying only that a sms arrived. |
| 16:02.17 | alain2210 | where should I see the clear text ? |
| 16:02.23 | mickeyl | in the signal |
| 16:02.29 | mickeyl | did you check with mdbus -s -l ? |
| 16:02.41 | alain2210 | no I never used this. |
| 16:02.45 | mickeyl | ah |
| 16:02.52 | mickeyl | this shows dbus signals |
| 16:03.07 | mickeyl | in realtime |
| 16:03.58 | alain2210 | I will build the most recent fso. And try to see it and the power key. |
| 16:04.07 | mickeyl | ok, cool |
| 16:04.25 | alain2210 | but the shutdown should be in osuaged ? as for standby ? |
| 16:04.50 | mickeyl | yes |
| 16:04.57 | mickeyl | the actual shutdown happens in ousaged |
| 16:05.07 | mickeyl | [SIGNAL] org.freesmartphone.GSM.Device.KeypadEvent from :1.26 /org/freesmartphone/GSM/Device |
| 16:05.07 | mickeyl | ('power', True) |
| 16:05.07 | mickeyl | <PROTECTED> |
| 16:05.07 | mickeyl | ('power', False) |
| 16:05.14 | mickeyl | that's what i see here now |
| 16:05.19 | mickeyl | (from mdbus -s -l) |
| 16:05.42 | mickeyl | so the missing bits is to link the source (ogsmd's keypad event signal) to the destination |
| 16:05.46 | mickeyl | (ousaged shutdown) |
| 16:05.52 | mickeyl | and this can be done via oeventsd as rule |
| 16:05.53 | mickeyl | or via any UI |
| 16:06.02 | mickeyl | (if you want to open a dialog or so) |
| 16:07.06 | alain2210 | I found it in ousaged. |
| 16:08.40 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 16:49.50 | *** join/#openezx marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 17:15.08 | *** join/#openezx sabrod (n=sab@lns-bzn-52-82-65-79-80.adsl.proxad.net) |
| 17:25.06 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r0f7b4ea5c9 10openezx/ (6 files in 2 dirs): import Muromec's work on ts0710 and ipc |
| 17:25.50 | WyrM | I had to solve a lot of stuff manually, seems that the diff was not complete (previous changes) |
| 17:26.09 | WyrM | im testing build now :) |
| 17:29.15 | WyrM | it builds. :) |
| 18:09.56 | tmzt | why is power button over AT? |
| 18:10.58 | WyrM | because its connected to pcap. |
| 18:11.16 | WyrM | and bp takes the interesting interrupt. |
| 18:11.56 | WyrM | but this is only on gen1, where bp is the pcap master (connected to the primary spi port). |
| 18:12.23 | WyrM | on gen2, ap is connected to the primary spi port, and we can get the power button irq. |
| 18:12.55 | tmzt | ah ok |
| 18:27.43 | *** join/#openezx WyrM1 (n=wyrm@20158145047.user.veloxzone.com.br) |
| 18:36.31 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 18:47.56 | *** join/#openezx florian (n=fuchs@f054213071.adsl.alicedsl.de) |
| 18:56.57 | *** join/#openezx pH5 (n=ph5@e178193101.adsl.alicedsl.de) |
| 19:03.32 | *** part/#openezx darion76 (n=darion76@94-248-85-78.dynamic.peoplenet.ua) |
| 19:04.22 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r1a44d4534c 10openezx/drivers/char/ts0710_mux_usb.c: get rid of warnings, remove debug code |
| 19:04.23 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r5c7f789c7c 10openezx/drivers/input/keyboard/pcap_keys.c: for PCAP_IRQ_* |
| 19:04.23 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * rd99dbba3e7 10openezx/drivers/input/keyboard/pcap_keys.c: change name |
| 19:04.25 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r18704d746f 10openezx/arch/arm/mach-pxa/include/mach/irqs.h: change A1/HS name, add some comments |
| 19:04.27 | CIA-33 | OpenEZX: 03Daniel Ribeiro <drwyrm@gmail.com> 07ezx/current * r1bf30d0f3f 10openezx/drivers/input/keyboard/pcap_keys.c: not needed |
| 19:06.18 | WyrM1 | ao2: subdev code is working ok. |
| 19:06.52 | WyrM1 | it is mounting the rootfs, so regulator was registered. |
| 19:11.21 | WyrM1 | pcap_keys is working too. |
| 19:32.22 | *** join/#openezx Gottox (n=Gottox@s01.de) |
| 19:33.17 | *** part/#openezx Gottox (n=Gottox@s01.de) |
| 19:33.33 | tmzt | WyrM: so based on the new information, is moto a gen2 ezx phone? |
| 19:33.46 | tmzt | motoq |
| 19:35.24 | tmzt | I haven't found a wdi that I know of but one of the bp->ap gpio/irqs could be it |
| 19:36.12 | WyrM | tmzt: it has a EOC chip. |
| 19:36.18 | WyrM | so its probably gen2. |
| 19:36.29 | WyrM | the best way to test is to dump the pcap registers. |
| 19:37.07 | WyrM | if reg 4 has a value (not all 0xff), then it is connected to the primary spi port on pcap. |
| 19:37.39 | tmzt | I'm guessing the mux is already up in ce so I either need to make ao2's code work in that case |
| 19:37.51 | WyrM | see ezx-pcap.h it lists the registers that are only acessible by port1. |
| 19:37.54 | tmzt | I think we did that |
| 19:38.08 | WyrM | I don't get. |
| 19:38.12 | WyrM | what about mux? |
| 19:38.22 | tmzt | if you mean AP |
| 19:38.33 | WyrM | I think your mux is different than ours. |
| 19:38.42 | WyrM | not the same software on BP. |
| 19:38.54 | tmzt | ce driver is called usbipc |
| 19:39.32 | WyrM | hum, then its probably similar to our ipc. |
| 19:39.41 | tmzt | the channels are called ts0710 and they have dlci's |
| 19:40.26 | tmzt | but usbserial works somewhat so I think handshake is through usb |
| 19:40.42 | tmzt | qualcomm's amss is very modular |
| 19:41.04 | tmzt | I think they added gsm muxing to it |
| 19:41.10 | WyrM | I think that the ipc is probably another endpoint. |
| 19:41.21 | tmzt | for compatibility with ezx |
| 19:41.40 | WyrM | and your serial is just the interface exported to the pc when you use the phone in modem mode. |
| 19:42.43 | tmzt | there was no real reason not to expose multiple serial ports to ap over usb |
| 19:42.47 | tmzt | yeah |
| 19:43.13 | tmzt | the AT is for dun, at voice commands don't work |
| 19:45.18 | tmzt | same is true of dun port on cdma lg phones and rzrs |
| 19:45.41 | tmzt | atdXXXX; fails |
| 19:46.40 | tmzt | lsusb -v -v showed AT port, MUX port, DIAG port |
| 19:46.53 | tmzt | from pxa host |
| 19:47.38 | tmzt | all of those enumeratedwith usbserial though |
| 19:52.45 | WyrM | so you can access muxed data with usbserial? |
| 19:55.39 | tmzt | yes, but I don't know the protocol or if there is seperate handshaking |
| 19:56.25 | tmzt | when I send data I usually get it back with some bytes incremented |
| 20:30.04 | ao2 | WyrM, about subdevs, well, then it must be something on my side |
| 21:16.31 | tmzt | ao2: what kind of handshaking does ipc use? |
| 21:16.53 | tmzt | is it similar to uart? |
| 21:17.17 | WyrM | no |
| 21:17.37 | WyrM | see ezx-bp.c |
| 21:18.03 | tmzt | gitweb? |
| 21:18.21 | WyrM | drivers/char/ezx-bp.c |
| 21:27.57 | tmzt | is wake called before reading/writing? |
| 21:31.22 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 22:22.38 | WyrM | tmzt: before writing. |
| 22:22.44 | WyrM | but its not really needed. |
| 22:23.24 | WyrM | because bp only sleeps if the usb device is suspended by the hub driver. |
| 22:23.59 | WyrM | motorola code does a layer violation, and suspends the usb device 2.5 seconds after any activity. |
| 22:24.30 | WyrM | we use the mainline hub driver, which only suspends the device on AP suspend. |
| 22:30.10 | tmzt | we can suspend one port though, can't we? |
| 22:30.29 | WyrM | not sure. |
| 22:30.39 | WyrM | you mean while ap still run? |
| 22:31.33 | tmzt | I guess, but there's no reason? |
| 22:34.06 | WyrM | I think we can. |
| 22:34.16 | WyrM | but I don't know how to do it :) |
| 22:34.30 | WyrM | and the usb resume will not wake bp. |
| 22:34.42 | WyrM | that really needs to be done with gpio. |
| 22:35.40 | tmzt | composite usb device? |
| 22:35.56 | WyrM | composite? |
| 22:36.15 | tmzt | or wait, you mean root hub |
| 22:36.27 | WyrM | yeah, root hub |
| 22:37.59 | tmzt | might still work though |
| 22:38.25 | WyrM | well, we need to test/do this from scratch. |
| 22:39.04 | WyrM | first thing we removed from mux on clean-up was the suspend part, as it was conflicting with the hub driver :) |
| 22:57.11 | tmzt | so what is the ezx-bp driver for? |
| 23:21.26 | *** join/#openezx agd5f (n=alex@c-69-143-4-28.hsd1.va.comcast.net) |
| 23:23.25 | WyrM | just for the handshake. |
| 23:23.39 | WyrM | the gpio part of the ipc. |
| 23:23.47 | WyrM | moto code does this on the board file. |
| 23:24.23 | WyrM | we will move the code on ezx-bp to the ipc driver. |
| 23:44.42 | tmzt | ah ok |
| 23:45.16 | tmzt | but if ours doesn't sleep, what's the handshake for? |
| 23:45.55 | WyrM | well, without the handshake the chip doesn't work at all :) |
| 23:46.02 | WyrM | s/chip/bp/ |
| 23:46.35 | tmzt | the first time? |
| 23:46.46 | WyrM | yeah. |
| 23:46.54 | WyrM | the handshake is done only at start. |
| 23:46.54 | tmzt | ok |
| 23:47.01 | WyrM | its not done at resume. |
| 23:49.27 | *** join/#openezx dth1 (n=dth@p4FDEDDDA.dip.t-dialin.net) |