IRC log for #openezx on 20080212

02:37.46*** join/#openezx WM (i=wyrm@20158203002.user.veloxzone.com.br)
02:57.49*** join/#openezx ljp (n=lpotter@203.94.178.46)
04:34.01*** join/#openezx drWyrM (i=wyrm@201.78.17.80)
05:40.24*** join/#openezx agd5f (n=alex@c-69-143-24-183.hsd1.va.comcast.net)
06:53.15*** join/#openezx AndiM (n=andi@p50814286.dip.t-dialin.net)
07:01.49*** join/#openezx drath_ (i=vmaster@p5B07C17E.dip.t-dialin.net)
07:09.07*** join/#openezx WM (i=wyrm@20158208045.user.veloxzone.com.br)
08:06.43*** join/#openezx drWyrM (i=wyrm@20158203033.user.veloxzone.com.br)
08:07.58*** join/#openezx CIA-42 (n=CIA@208.69.182.149)
08:44.54Hopscotchgood morning
08:58.38flyhorse|linuxhi Hopscotch good afternoon
09:00.44*** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1)
09:01.10ao2hi
09:27.15*** join/#openezx z72ka (n=hermanj@r5af183.net.upc.cz)
09:32.55*** join/#openezx LuitvD (n=luitvd@beigetower/luitvd)
11:03.54*** join/#openezx ade|desk (n=adavey@194.200.143.249)
11:16.44*** join/#openezx florian (n=fuchs@217.146.132.69)
11:24.21floriangood morning
11:26.15*** join/#openezx Gottox (n=Gottox@s01.de)
13:05.22*** join/#openezx tombhadAC (n=tombhad@pD95DE64A.dip.t-dialin.net)
14:42.17*** join/#openezx goxboxlive (n=goxboxli@134.84-48-212.nextgentel.com)
15:17.41*** join/#openezx WM (i=wyrm@20158228223.user.veloxzone.com.br)
15:42.00*** join/#openezx CIA-42 (n=CIA@208.69.182.149)
15:42.41*** join/#openezx drWyrM (i=wyrm@201.78.25.5)
15:58.23*** join/#openezx TimRiker (n=timr@70-7-221-8.area7.spcsdns.net)
16:20.32*** join/#openezx LuitvD (n=luitvd@beigetower/luitvd)
16:26.59*** join/#openezx pH5 (n=ph5@e178210056.adsl.alicedsl.de)
16:47.17*** join/#openezx Hopscotch (n=cd@touchdown.maintech.de)
17:02.23*** join/#openezx ellisway (n=ellis@homealone.good1.com)
17:04.45*** part/#openezx ade|desk (n=adavey@194.200.143.249)
17:09.01*** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be)
18:04.26*** join/#openezx dion (n=dion@inhex.net)
18:36.12*** join/#openezx Sleep_Walker (n=Sleep@nat/suse/x-02e3ea041ed12107)
18:36.25Sleep_Walkerhi
18:55.24ao2hi Sleep_Walker
19:08.42AndiMhi
19:09.02AndiMextracting a dmesg from original moto environment ;)
19:12.09*** join/#openezx tombhadAC (n=tombhad@pD95DE015.dip.t-dialin.net)
19:37.57*** join/#openezx flo_lap (n=fuchs@f049168219.adsl.alicedsl.de)
19:45.36ao2hi AndiM any hint about i2c init?
19:46.10ao2I also have a static dmesg binary, that remember me to put on the wiki the A910 dmesg...
19:50.21AndiMo2: nope, dmesg isn't needed, just use /proc/kmsg
19:51.05AndiMao2: the camera interface is being pulled up _directly_ after i2c adapter init, thus it's somewhat conceivable that having a live camera is very important for i2c health.
19:52.00AndiMao2: what I need to do now is hack together the few bits and pieces to fumble some initialization for the camera interface (register CICR0, clock setup etc.)
19:52.06ao2maybe they put proper i2c inititlization inside camera specific code ?
19:52.31*** join/#openezx BadCluster (n=badclust@200.26.114.37)
19:52.46AndiMao2: nope, doesn't look like it. that stuff simply does i2c queries after bringing up pxa camera interface, there's no specific i2c _bus_ init I think.
19:53.39AndiMao2: the thing that makes me go "huh?" is that I see both i2c 0x60 (radio) and 0x7c (amp), but no camera on 0x53, that's why I think the camera is killing i2c comm.
19:54.03AndiMao2: oh, and /proc/interrupts...I2C did show activity there!
19:54.16AndiMas opposed to my 2.6.24 which doesn't.
19:55.08ao2I know that there are two i2c buses (or channels, I don't know how theu are called), is camera on the same one of radio and amp ?
19:55.08AndiMao2: I documented large parts of the pcap header to try to get a clearer picture of things, since searching for i2c mis-operation might prove difficult.
19:55.41AndiMao2: good question. I don't even know yet what exactly the "power i2c bus" (bus 0) is doing on a pxa. would have to read up on that soon.
19:56.16ao2well, maybe your work will turn useful also for camera addition eventually
19:56.46ao2see you later
19:57.17AndiMao2: bye!
20:34.52*** join/#openezx dion (n=dion@inhex.net)
20:54.32*** part/#openezx BadCluster (n=badclust@200.26.114.37)
20:57.56*** join/#openezx WM (i=wyrm@20158217087.user.veloxzone.com.br)
22:02.44AndiMargh, cannot get gpiotool to work :(
22:10.21ao2what's wrong?
22:10.57AndiMao2: my toolchain isn't sufficient
22:11.21ao2I can build gpiotool for you
22:11.32AndiMao2: is there a binary with ld-linux.so.2 dependency and GLIBC_2.0?
22:11.43AndiMerr, nope, GLIBC_2.5
22:11.44ao2don't know
22:11.58AndiMthe problem is that the openezx binary _is_ GLIBC_2.0
22:12.27AndiMmy toolchain doesn't provide mman.h
22:12.32ao2wait, gpiotool should be also in angstrom
22:13.01AndiMao2: I _am_ running angstrom. at least a binary GUI environment, the hopefully "fullest" one.
22:13.39ao2it should be called ezx-gpiotool
22:14.15AndiMnope, nothing there at least for me.
22:14.30AndiMoh wait, you mean in distribution directory? let's see...
22:17.14*** join/#openezx stefan_schmidt (n=stefan@sirius.lasnet.de)
22:17.46ao2hi stefan_schmidt
22:18.14stefan_schmidthi ao2
22:18.41AndiMstefan_schmidt: any idea where to get a gpiotool binary? codesourcery toolchain doesn't currently compile it for me...
22:19.10ao2AndiM, I'm trying building it with OE
22:19.41stefan_schmidtAndiM: I don't have one here.
22:20.47AndiMok. last desperate attempt...
22:27.59ao2OE wants to rebuild the whole toolchain... let's try crosscompiling manually with the current toolchain
22:28.27AndiMI wasn't successful here, so if you manage to get me a binary...
22:30.00AndiMuuuurks! I managed to download the wrong toolchain :-P
22:30.05ao2AndiM, do you need gpiotool for a 2.6 kernel?
22:30.41AndiMao2: yup. I want to figure out why I don't get i2c interrupts, either by twiddling pxa interrupt mask or by activating camera interface.
22:30.50ao2ok
22:31.58AndiMmanaged to download non-Linux-capable toolchain yet still managed to build a fully working kernel image ;)
22:33.07ao2AndiM, http://shell.studenti.unina.it/~ospite/tmp/gpiotool
22:33.12ao2let me know if it works
22:33.29ao2:)
22:36.13AndiMao2: thanks!!
22:36.20ao2you're welcome
22:36.28ao2ok, good night
22:36.52AndiMwait, I'm testing...
22:36.58AndiM;)
22:37.01ao2ah, ok
22:37.02ao2:)
22:37.28*** join/#openezx flo_lap (n=fuchs@f049168219.adsl.alicedsl.de)
22:37.29AndiManother 10 seconds
22:37.43AndiMok 20.
22:38.07AndiMok, 30 ;)
22:38.14AndiMno, wait, it ruuuuuns! :)
22:38.21ao2good
22:39.06AndiMso to summarize things: a) I have a working binary b) if for some reason I don't have it, then I now have a working toolchain c) profit!
22:39.57AndiMao2: have a nice sleep (if you decide to leave now)
22:40.10AndiMI'll have to go to sleep soon, too
22:40.22ao2ok, see you
22:44.41AndiMhmm, I2C interrupt is _not_ masked.
22:46.34*** join/#openezx Fry-kun (n=Fry-kun@63.82.6.66)
22:47.26WMHi.
22:47.33WMAndiM: progress?? :)
22:47.46AndiMWM: not really. only tool-wise.
22:47.57AndiMWM: and gathering more data and thoughts.
22:48.19*** part/#openezx stefan_schmidt (n=stefan@sirius.lasnet.de)
22:48.36AndiMI should probably now start activating the camera interface manually...
22:50.07WM"the thing that makes me go "huh?" is that I see both i2c 0x60 (radio) and 0x7c (amp), but no camera on 0x53, that's why I think the camera is killing i2c com"
22:50.17WMmaybe camera is just powered off?
22:50.33WMdo you have source code for the camera driver?? (on 2.4)
22:51.09AndiMWM: sure, I'd think that's the case, so I need to try switching it on to see whether it stops banging i2c bus.
22:51.31AndiMWM: yup, everything available, the whole sequence won't take too long I think.
22:55.49WMAndiM: i managed to get i2c communication with the camera on 2.6.16 some time ago..
22:57.44WMusing an "almost unmodified" version of the 2.4 motorola driver.
23:19.27*** join/#openezx pH5 (n=ph5@e178211235.adsl.alicedsl.de)
23:20.47AndiMok, need to leave now, bye!
23:46.27*** join/#openezx jannu (n=jannu@hoas-fe3cdd00-15.dhcp.inet.fi)

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