| 04:10.44 | *** join/#openezx LoneStar (n=xinzhen@218.81.37.194) |
| 05:10.32 | *** join/#openezx drWyrM (n=wyrm@201.2.68.83) |
| 05:28.42 | *** join/#openezx alexzhang (n=alexzhan@219.133.177.220) |
| 05:29.01 | alexzhang | hi, wyr! ;) |
| 05:29.02 | drWyrM | hi alexzhang. |
| 05:29.34 | alexzhang | what can i do for you? ;) |
| 05:30.00 | drWyrM | i am just finishing the ts commit. |
| 05:30.11 | drWyrM | Have you done anything else on EOC? |
| 05:30.12 | alexzhang | great! |
| 05:30.40 | alexzhang | LCD driver |
| 05:31.13 | alexzhang | I have posted the patch to ML, please take a look. |
| 05:31.42 | drWyrM | yes, i saw the email, i cant test it, it looks ok to me. |
| 05:32.00 | drWyrM | can you submit it to the fb-devel guys? :) |
| 05:32.42 | drWyrM | i mean, i will commit it to our svn too, but it is not ezx specific, so we could have it mainline earlier. |
| 05:33.38 | alexzhang | oh, where I can submit to fb-devel? give me some infor |
| 05:33.48 | drWyrM | also, i am planning a new binary release, do how much time do you need to finish EOC? |
| 05:34.27 | drWyrM | i think that googling fb-devel should point you, i dont know the exact url :) |
| 05:34.47 | alexzhang | hmmm... I think I need 2 days to clean up the codes of EOC |
| 05:35.13 | alexzhang | OK, I will contact fb-devel ... |
| 05:35.32 | drWyrM | hehehe, i am planing the release for about to 3 weeks, no need to hurry. :) |
| 05:35.47 | alexzhang | ;) |
| 05:36.11 | alexzhang | Now, I have some problem about EOC, need your advice! |
| 05:36.30 | drWyrM | i think it is good to do a binary release asap, i saw that a lot of guys are buggering you on motorolafans.com ;) |
| 05:36.46 | drWyrM | yes, whats your doubt? |
| 05:37.46 | alexzhang | hohoh, I saw too, but MMC driver is broke, so I don't think release binary will help to them. |
| 05:39.04 | alexzhang | yes, I cannot add EOC driver with i2c function to platform. |
| 05:40.20 | drWyrM | yes, most people there will not be able to setup NFS, but there are a few which can, and there is a potential for recruiting new developers ;) |
| 05:41.07 | drWyrM | why not? |
| 05:41.55 | alexzhang | phone will be crashed. I dont know why, maybe i2c buggy |
| 05:42.23 | drWyrM | humm.. |
| 05:42.47 | drWyrM | can you send me you current try? |
| 05:43.04 | alexzhang | so, I add i2c function to i2c/chips/eoc-i2c.c and move eoc initial codes to arch/arm/match-pxa/ezx-eoc.c |
| 05:43.39 | drWyrM | like ezx-pcap? |
| 05:44.10 | drWyrM | i mean, eoc-i2c init function is the one which calls a init function inside ezx-a1200.c |
| 05:44.52 | alexzhang | yes, like the relationship between ezx-ts.c and ezx-pcap.c |
| 05:46.04 | alexzhang | yes, after eoc-i2c probe, it will call a init function inside ezx-eoc.c i think |
| 05:46.39 | drWyrM | send me the code, let me take a look. |
| 05:47.18 | alexzhang | ok |
| 05:48.22 | drWyrM | please, send again. |
| 05:48.35 | alexzhang | why> |
| 05:50.11 | drWyrM | damn, i am behind nat, i think dcc will not work. |
| 05:50.35 | alexzhang | oh! ok, I send you email. |
| 05:50.55 | drWyrM | ok. |
| 05:51.30 | drWyrM | and.. you are behind nat too.. |
| 05:51.40 | drWyrM | 192.168.1.222 |
| 05:51.41 | drWyrM | ;) |
| 05:53.57 | alexzhang | 192.168.1.222, awesome!!!! you're a hacker!! |
| 05:54.14 | drWyrM | ? |
| 05:54.36 | alexzhang | I can see my lan ip... LOL!!! |
| 05:54.49 | drWyrM | the dcc send request you sent said the ip. |
| 05:55.02 | drWyrM | -:- DCC GET ("ezx-eoc.c") request from alexzhang[n=alexzhan@219.133.177.220 [192.168.1.222:39434] |
| 05:55.14 | alexzhang | ok, I have sent you the code via email |
| 05:55.33 | alexzhang | two files are same name now.. |
| 05:56.54 | alexzhang | have you received it? |
| 05:57.17 | drWyrM | yes, looking it now |
| 06:01.13 | alexzhang | I am cleaning up it. so it's not a final version, I think many things need to do. |
| 06:03.13 | drWyrM | you should be using platform_data to pass the init function, see how i pass pcap_data->init() from ezx-a1200.c to ezx-pcap.c |
| 06:03.46 | drWyrM | and i think you dont need to care about interrupts in the driver it. |
| 06:03.55 | drWyrM | s/it./yet./ |
| 06:04.32 | drWyrM | just a simple turn_on_usb() will do it for now :) |
| 06:05.24 | alexzhang | oh, but no interrupt? if usb hot plug? we dont support it? |
| 06:06.15 | drWyrM | i dont know if it is possible at all on a1200. |
| 06:06.19 | drWyrM | i mean.. |
| 06:06.34 | drWyrM | can the eoc chip interrupt pxa on the 2.4? |
| 06:07.56 | alexzhang | dont know yet... I just want to add a frame now. |
| 06:08.07 | drWyrM | ahh, this interrupt is not for usb. |
| 06:08.20 | alexzhang | oh, really? |
| 06:09.02 | drWyrM | it is for changing port mode, if you configure it to usb and leave, the udc driver still receives interrupts of cable connect/disconnect. |
| 06:09.30 | alexzhang | seems we need to scan the eoc to find if usb is plug in/out. right? |
| 06:10.16 | drWyrM | it is used so the EOC chip can recognize the type of device connected(audio, charger, usb, ...). |
| 06:10.29 | drWyrM | it is motorola specific. |
| 06:10.58 | drWyrM | i think that the udc is aware of it by itself. |
| 06:10.58 | alexzhang | oh, so we dont need to support it, now? |
| 06:11.07 | drWyrM | i think no. |
| 06:11.26 | drWyrM | and as a nfs only setup, you dont really want to disconnect your cable ;) |
| 06:12.17 | alexzhang | so, I want to do a good frame, it's not just for nfs workaround |
| 06:13.57 | drWyrM | i know. its good. but you dont need to do everything at once. you decide. |
| 06:16.02 | alexzhang | OK, I'll re-design a work-frame after MMC works |
| 06:16.20 | alexzhang | now, I just provide a nfs workaround, is it ok? |
| 06:16.38 | drWyrM | no. |
| 06:16.46 | alexzhang | =-O |
| 06:16.53 | alexzhang | what's opinion? |
| 06:17.20 | drWyrM | you should provide a driver skeleton, which supports at least changing the port mode to USB. |
| 06:17.38 | drWyrM | and will allow easy extending in the future. |
| 06:18.45 | alexzhang | hmmm... ok, I try to do so. |
| 06:20.46 | alexzhang | I think eoc-i2c is almost ok now, and I will modify ezx-eoc to provide a skeleton just like ezx-emu, right? |
| 06:21.10 | drWyrM | no. forget ezx-emu. :) |
| 06:21.58 | drWyrM | just do a basic driver, with a write() function, and a set_usb() which calls write() and does the magic. |
| 06:22.34 | drWyrM | on a platform_driver, and calls init() provided by a platform_data structure. |
| 06:23.00 | drWyrM | err. i am not good at explaining things :( |
| 06:25.56 | alexzhang | heheh me too, because I am not english native speaker, but it's ok, I got your mean... |
| 06:29.41 | alexzhang | ok, as you mentioned, there are 2 drivers like mine too, one is eoc-i2c (which provides i2c function to write and read EOC), another is ezx-eoc(which provides a skeleton to control & initialize usb modes) right? |
| 06:30.57 | drWyrM | no, just one driver. the driver is called because there is a matching platform_device struct in ezx-a1200.c |
| 06:31.15 | drWyrM | and we use a separate patch for that, but not a new file. |
| 06:32.21 | alexzhang | hmmm... I have tried as what you said, but phone will be crashed... |
| 06:33.10 | alexzhang | because you know, i2c-core is called after platform_device init? |
| 06:37.12 | drWyrM | have you tried setting i2c as parent device? |
| 06:37.53 | drWyrM | there is a pxa2xx-i2c platform_device in generic.c |
| 06:38.19 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 06:38.28 | alexzhang | I have tried. but seems it's same |
| 06:38.31 | drWyrM | hi ao2 |
| 06:38.41 | ao2 | hi |
| 06:39.17 | alexzhang | I know how to set parent device.... anyway, I try again... |
| 06:40.41 | alexzhang | OK, Wyr, since I gotta go, could you please give me a email for the driver skeleton? |
| 06:41.55 | drWyrM | ok. |
| 06:42.46 | alexzhang | thank you. bye |
| 06:42.52 | *** part/#openezx alexzhang (n=alexzhan@219.133.177.220) |
| 06:45.03 | *** join/#openezx leoncamel (n=leoncame@p1239-ipbfp1105fukuokachu.fukuoka.ocn.ne.jp) |
| 07:01.10 | ao2 | drWyrM, I saw that Guy Martin replyed you on opensource.motorola.com |
| 07:01.55 | drWyrM | anything useful? i will take a look :) thanks. |
| 07:44.58 | *** join/#openezx dion (n=dion@inhex.net) |
| 08:13.45 | ao2 | bye |
| 09:17.03 | *** join/#openezx alexzhang (n=alexzhan@219.133.177.220) |
| 09:17.56 | alexzhang | :)hi, all |
| 09:34.47 | drWyrM | wb alex. |
| 09:41.21 | alexzhang | wb? |
| 09:45.52 | drWyrM | welcome back :) |
| 09:47.36 | alexzhang | oh! ;) |
| 09:49.59 | alexzhang | OK, I think I'll try again to re-implement eoc codes |
| 10:00.10 | *** join/#openezx stefan_schmidt_ (n=stefan@62.226.242.63) |
| 10:08.18 | *** join/#openezx stefan_schmidt (n=stefan@62.226.242.63) |
| 10:16.18 | drWyrM | https://opensource.motorola.com/sf/discussion/do/listPosts/projects.sitewide/discussion.opensource_feedback.topc1550?_message=1187518110252 |
| 10:16.47 | drWyrM | i think that things are changing slowly at Motorola... But at least they are trying ;) |
| 10:20.23 | stefan_schmidt | drWyrM: I really doubt this, but let us see. |
| 10:26.40 | drWyrM | stefan_schmidt: the code on the z6 kernel release is cleaner and better documented. I think that there is already a group inside Moto which is commited to better relationship with the community, but probably they are experiencing resistance from other groups. |
| 10:28.20 | stefan_schmidt | drWyrM: I also see that there are people working on better relations, but I doubt they will give us what we want. |
| 10:28.56 | drWyrM | i would be happy with some hardware samples atm ;) |
| 10:30.13 | *** join/#openezx flo_lap (n=fuchs@f049185242.adsl.alicedsl.de) |
| 10:31.12 | stefan_schmidt | drWyrM: hmm, that's not what I'm looking for. This stuff we can buy ourself. But without data sheets or contact to engineers we will always have problems to support all features of the phones and spent tons of time on support new phones. |
| 10:31.38 | stefan_schmidt | hi flo_lap |
| 10:32.27 | stefan_schmidt | drWyrM: My tip is that we will not even get a real answer on this besides something like: "We work on this" and 1 year silence |
| 10:32.40 | flo_lap | good morning |
| 10:33.08 | stefan_schmidt | But perhaps I'm just pessimistic. |
| 10:33.20 | stefan_schmidt | Would be nice to get proven wrong |
| 10:35.45 | *** join/#openezx Shoragan (n=shoragan@datenfreihafen.org) |
| 10:36.13 | *** join/#openezx alphaone (n=daniel@datenfreihafen.org) |
| 10:36.28 | *** join/#openezx _stefan_schmidt (n=stefan@datenfreihafen.org) |
| 10:55.51 | *** join/#openezx Shoragan (n=shoragan@datenfreihafen.org) |
| 10:56.19 | *** join/#openezx _alphaone (n=daniel@datenfreihafen.org) |
| 10:56.34 | *** join/#openezx _stefan_schmidt (n=stefan@datenfreihafen.org) |
| 11:09.16 | *** join/#openezx drath_ (i=vmaster@p5B07C8DC.dip.t-dialin.net) |
| 11:26.37 | *** part/#openezx alexzhang (n=alexzhan@219.133.177.220) |
| 11:49.54 | *** join/#openezx alphaone- (n=alphaone@2001:638:602:af01:0:0:0:1) |
| 11:51.28 | *** part/#openezx alphaone (n=daniel@datenfreihafen.org) |
| 11:55.58 | *** join/#openezx alphaone_ (n=alphaone@2001:638:602:af01:0:0:0:1) |
| 14:36.00 | *** join/#openezx leoncamel (n=leoncame@p6009-ipbfp903fukuokachu.fukuoka.ocn.ne.jp) |
| 15:09.46 | *** part/#openezx stefan_schmidt (n=stefan@62.226.242.63) |
| 15:43.05 | *** join/#openezx LoneStar (n=xinzhen@218.81.37.194) |
| 17:09.05 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 17:11.56 | *** join/#openezx flo_lap (n=fuchs@f049185242.adsl.alicedsl.de) |
| 19:43.46 | *** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 20:53.16 | *** join/#openezx Shoragan (n=shoragan@datenfreihafen.org) |
| 20:53.59 | *** join/#openezx stefan_schmidt (n=stefan@datenfreihafen.org) |
| 23:28.10 | *** join/#openezx agd5f (n=alex@c-69-143-255-50.hsd1.va.comcast.net) |