IRC log for #openezx on 20070626

01:59.57*** join/#openezx Fry-kun (n=kostya@h-67-100-89-239.snfccasy.covad.net)
02:55.01*** join/#openezx AlexZhang (n=alex@58.60.77.216)
04:13.25*** part/#openezx Fry-kun (n=kostya@h-67-100-89-239.snfccasy.covad.net)
04:45.46*** part/#openezx AlexZhang (n=alex@58.60.77.216)
06:07.37*** join/#openezx Fry-kun (n=kostya@h-66-166-233-66.snvacaid.covad.net)
06:16.10*** join/#openezx goxboxlive (n=goxboxli@141.80-202-161.nextgentel.com)
06:17.07Hopscotchgood morning
06:17.19Fry-kungood night :)
06:22.28Fry-kunwhich time zone are you in?
06:22.41Fry-kunGMT?
06:23.10*** join/#openezx koen (n=koen@dominion.kabel.utwente.nl)
06:37.57*** join/#openezx |dion| (n=dion@inhex.net)
06:52.28*** join/#openezx pleemans (n=peter@leemanpe.ugent.be)
06:59.18*** join/#openezx AlexZhang (n=alex@58.60.77.216)
07:16.42Fry-kunwow everyone gathers around midnight
07:16.49Fry-kunwell, not everyone...
07:18.47*** join/#openezx AlexZhan1 (n=alex@58.60.77.216)
07:34.05*** join/#openezx z72ka-ntb (n=hermanj@tux2.software602.cz)
08:40.28*** join/#openezx z72ka-ntb_ (n=hermanj@tux2.software602.cz)
08:48.44*** join/#openezx florian (n=fuchs@217.146.132.69)
08:50.34*** join/#openezx z72ka-ntb (n=hermanj@tux2.software602.cz)
09:08.29*** join/#openezx ade|desk (n=adavey@194.200.143.249)
09:14.29*** join/#openezx jannu (n=jannu@hoas-fe29dd00-231.dhcp.inet.fi)
09:19.48*** part/#openezx ade|desk (n=adavey@194.200.143.249)
09:33.48*** join/#openezx AlexZhang (n=alex@58.60.77.216)
10:56.06*** join/#openezx james__ (n=james@gimel.esc.cam.ac.uk)
11:17.22stefan_schmidtdrath: ok, first question starts already with the build. I'm trying to build it against the amontec provided ftd2xx but this one only offer the *.so file and no header file
11:17.51stefan_schmidtdrath: results in a build error of course: ft2232.c:45:20: error: ftd2xx.h: No such file or directory
11:25.19*** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1)
11:27.54stefan_schmidtdrath: with libftdi it builds at least. Will use that for my first tests then.
11:31.43drathstefan_schmidt: the problem only occurs when trying to read/write a large amount of data, like when flashing the board
11:32.44stefan_schmidtdrath: ok, I prepare a config now and let you take a look
11:32.49*** join/#openezx |dion| (n=dion@inhex.net)
11:36.52drathstefan_schmidt: http://ftdichip.com/Drivers/D2XX/Linux/libftd2xx0.4.13.tar.gz
11:37.24stefan_schmidtdrath: And the special PID/VID for the amontec dongle?
11:37.49drathstefan_schmidt: on linux they can be set during runtime
11:38.11drathstefan_schmidt: just specify them in the .cfg: ft2232_vid_pid 0x0403 0xcff8
11:38.18stefan_schmidtdrath: Ah, so the note in the wiki is only about cygwin
11:38.44stefan_schmidtdrath: FIne, first libftdi now and ftd2xx later
11:43.02*** join/#openezx drWyrM (i=c88e3026@gateway/web/cgi-irc/ircatwork.com/x-9657c98bd6433f12)
11:43.19drWyrMgood morning
11:44.30stefan_schmidtdrath: http://pastebin.com/936662
11:44.35stefan_schmidthi drWyrM
11:45.09drWyrMhi stefan.
11:47.18drathhttp://pastebin.com/936667
11:47.44drathi made two small changes - the "reset_config ... separate" has been deprecated for quite some time
11:48.19drathand using "reset halt" is safer on a pxa, as it guarantees code running on the target wont interfere with jtag
11:49.02stefan_schmidtdrath: OK, then we should update the PXA example from cbrake: http://openfacts.berlios.de/index-en.phtml?title=OpenOCD_scripts
11:51.06stefan_schmidtdrath: I'll put together all the pieces now. Will take some time.
11:59.26*** join/#openezx pleemans (n=peter@leemanpe.ugent.be)
12:04.35stefan_schmidtdrath: It's some time since our last test so perhaps some other problems: Error:   target.c:1104 handle_working_area_command(): target number '0' not defined
12:07.05stefan_schmidtdrath: Left LED form JTAGKey is getting green so vcc should be fine, right?
12:07.54*** join/#openezx james__ (n=james@gimel.esc.cam.ac.uk)
12:08.56drathah, you have to put the working_area command after the target command
12:16.15stefan_schmidtdrath: Ah, makes sense. After moving run_and_halt_time also he can't find the dongle:
12:16.25stefan_schmidtError:   ft2232.c:1432 ft2232_init_libftdi(): unable to open ftdi device: device not found
12:17.11stefan_schmidtlsusb finds it: Bus 002 Device 003: ID 0403:cff8 Future Technology Devices International, Ltd
12:19.19drathtry removing the " A" from "Amontec JTAGkey A"
12:19.43drathftd2xx uses this to determine which interface of the FT2232 to connect to
12:20.00drathbut it's only necessary on windows iirc
12:21.03drathwith libftdi i'm using an extra call to secify the right interface
12:21.46stefan_schmidtdrath: Yay, now I get way more infos. :)
12:21.59stefan_schmidtdrath: I need to digg through it.
12:22.07drathtry telnetting to localhost 4444
12:22.29drathunless the daemon exited already, which would be bad
12:22.50stefan_schmidtexit: Error:   xscale.c:762 xscale_write_dcsr(): JTAG error while writing DCSR
12:23.29drathcan you mail me a complete log (-d -l <logfile>)? Dominic dot Rath at gmx dot de
12:23.34stefan_schmidtdrath: with -d3 http://pastebin.com/936698
12:24.07drathah, thx
12:24.07stefan_schmidtpastbin should be faster for the small logs
12:24.19drathyeah
12:25.03stefan_schmidtcurrent config http://pastebin.com/936699
12:27.53drathcould you try with increased "jtag_n[st]rst_delay" settings? like 1000 or 1500?
12:30.12stefan_schmidtSame with both values :(
12:32.06drathdo you still have the tiny? i haven't used the prototype i sent you in months, maybe some changes to the code broke the prototype config (there are only two in use)
12:34.06stefan_schmidtdrath: Sure, I'll test vthe tiny
12:36.30stefan_schmidtdrath: Just change to ft2232_layout "jtagkey", or something else?
12:38.13stefan_schmidtdrath: Same with the tiny. :/
12:38.47stefan_schmidtdrath: I can also offer the wiggler, but not sure if all parport stuff is ready on my pc for it...
12:43.58*** join/#openezx z72ka-ntb (n=hermanj@tux2.software602.cz)
12:48.45CIA-24OpenEZX: wyrm * r2042 /trunk/src/kernel-2.6/patches/defconfig-a1200: disable pxa27x-udc on a1200.
12:50.52drathhum, wiggler shouldn't change anything...
12:51.11draththe problem occurs earlier this time than when we worked on this a few months ago
12:52.33stefan_schmidtdrath: exactly, perhaps I should try the version we used that time? bisecting it...
12:53.09drathcould you try with drastically increased jtag_n[st]rst_delays? like 10,000
12:53.54stefan_schmidtdrath: Sure. With the prototype or tiny?
12:54.00drathshouldn't matter
12:54.14stefan_schmidtok, will try
12:54.20drathdid you have to do anythign special when you tried with the bdi2k?
12:54.33drathor did it work out of the box?
12:57.40stefan_schmidthttp://pastebin.com/936725
12:57.52stefan_schmidtOne line double but same problem.
12:58.27stefan_schmidt(bdi2k)PXA firmware and setting the bus width, nothing more.
13:00.56drathhum, guess the additional line is the tiny's fault
13:01.12drathit failed setting the JTAG instruction register - this is so low-level it's got nothing to do with jtag
13:01.16stefan_schmidtcould be
13:01.16draths/jtag/xscale/
13:01.55stefan_schmidthmm, perhaps really try the older version
13:02.26drathjust one more test with the current version, the increased delays and the prototype would be nice
13:02.48stefan_schmidtsure
13:05.35stefan_schmidtdrath: Same as with the tiny. Doubled line as with tiny, too.
13:08.02drathhow long does it take until the openocd exits?
13:08.23stefan_schmidtdrath: I fetch some food now. Back in 30 minutes.
13:08.32drathok
13:39.15*** join/#openezx ade|desk (n=adavey@194.200.143.249)
13:46.05*** join/#openezx drath_ (i=vmaster@p5B07F9DA.dip.t-dialin.net)
14:04.25*** join/#openezx drWyrM (i=c88e3026@gateway/web/cgi-irc/ircatwork.com/x-a178eb86bdca6eb3)
14:04.45stefan_schmidtdrath: Longer as expected, but I'm back.
14:04.55stefan_schmidtdrath: Any new idea I should test?
14:05.27stefan_schmidtdrath: If not I would search for the svn version we used last time and try this one.
14:06.01stefan_schmidtdrath: Of course no working xscale support, but perhaps we would see what does worked and what not.
14:11.29drathstefan_schmidt: i guess you used branches/xscale/ last time - there were no changes after your tests to this branch
14:11.46drathstefan_schmidt: but i don't think that's going to change anything
14:11.53stefan_schmidtdrath: ah, great. That makes it easier.
14:12.06stefan_schmidtdrath: I also found some of the old logfiles.
14:12.21stefan_schmidtdrath: You mean we have a borked hw setup now?
14:14.08drathstefan_schmidt: hmm, no, but the changes i made to make it work on the pxa270 board at pengutronix can't affect the behaviour we're seeing now
14:14.45drathstefan_schmidt: what's worse is that increasing the reset delays causes the jtag ir scan to fail
14:15.30stefan_schmidtdrath: So why don't go down to 260 as cbrake have in his config?
14:15.33drathstefan_schmidt: the hardware seems to be fine, the IDCODE is good
14:15.44drathstefan_schmidt: you could try that again
14:16.08drathstefan_schmidt: only delay nsrst by 260ms, and no ntrst delay
14:16.19stefan_schmidtdrath: OK, firt 260ms and xscale branch afterwards. Running out of ideas anyway.
14:16.20drathstefan_schmidt: is the phone powered when you're trying to connect?
14:16.47stefan_schmidtdrath: It must. If it is off connections already fails earlier.
14:19.03stefan_schmidtdrath: With other timings I get the same result, just faster, of course.
14:19.55stefan_schmidtdrath: Error with powered off device: http://pastebin.com/936789
14:20.50drathstefan_schmidt: i'll see if i can talk to robert. in theory i should have remote access to their pxa270 board, just have to ask him for permission
14:21.33stefan_schmidtdrath: Tell him I owe him a beer if we get it running. :)
14:21.35drathstefan_schmidt: i /think/ cbrake used the current svn version, but maybe he had some older changes in his tree
14:22.28stefan_schmidtdrath: OK, the plan: You talking to robert, I test the old xscale branch and ask cbrake if I can catch him in #oe
14:22.48stefan_schmidtdrath: I also could try libftd2xx later
14:22.50drathstefan_schmidt: he's cbrake_away...
14:23.02stefan_schmidtdrath: hmm, ok
14:23.03drathstefan_schmidt: do you have a multimeter to measure the reset signals?
14:23.12stefan_schmidtdrath: yes
14:23.49stefan_schmidtdrath: What do you like to get?
14:24.29drathstefan_schmidt: both lines should be high at the beginning, then trst low for a short time before going high again
14:24.48drathstefan_schmidt: the openocd currently exits before srst goes low
14:26.08*** join/#openezx z72ka-ntb (n=hermanj@tux2.software602.cz)
14:26.43stefan_schmidtdrath: OK, I prepare the measure.
14:38.46stefan_schmidtdrath: trst: Power on phone 2.7V, start openocd trst goes down short and back short after.
14:39.22stefan_schmidtdrath: srst is high all time
14:40.21drathstefan_schmidt: you could try disabling the calls to jtag_add_reset in xscale_init_target (xscale.c)
14:43.39stefan_schmidtdrath: All five?
14:45.24stefan_schmidtdrath: It stays alive
14:45.34drathdrath: only in xscale_init_target()
14:45.34stefan_schmidtdrath: ah, no :(
14:45.46draths/drath/stefan_schmidt/
14:45.59stefan_schmidtdrath: ah, oh
14:47.03stefan_schmidtdrath: But both 1,0 and 0,0, right?
14:47.13drathstefan_schmidt: yeah
14:47.26drathstefan_schmidt: that disables the nTRST toggling, which wasn't included before
14:47.49drathstefan_schmidt: it's the only thing that happens before the dcsr is written
14:48.24stefan_schmidtdrath: yay, stays alive and I can telnet into it
14:49.04drathstefan_schmidt: what does "poll" say?
14:49.21stefan_schmidtdrath: target state: running
14:49.28drathstefan_schmidt: ok, that's not good
14:49.43drathstefan_schmidt: but as expected
14:49.49stefan_schmidtdrath: indeed, even manual halt does not work
14:50.07drathstefan_schmidt: yeah, the debug handler was never executed, otherwise it would have been halted from the beginning
14:50.58drathstefan_schmidt: could you reenable the jtag_add_resets, and put a "jtag_add_spee(100000);" in between the two?
14:51.08draths/spee/sleep/
14:51.13drathnot sure what's wrong with my typing today...
14:51.43drathyou could also place a "jtag_execute_queue();" after the rests
14:51.55draththat allows us to verify the state after we pulsed ntrst
14:55.32stefan_schmidt~lart pastebin.com
14:55.32purltakes a big bite out of pastebin.com's jugular vein
14:56.24stefan_schmidtdrath: these two changes brings us back to the beginning.
14:56.38stefan_schmidtError:   xscale.c:762 xscale_write_dcsr(): JTAG error while writing DCSR
14:58.51stefan_schmidthttp://pastebin.com/936821
15:02.09drathhum, i don't think it makes sense to move on with this - i'll wait for robert to reply so i can run some tests on their board
15:03.27drathah, was there one failed check or two failed checks?
15:03.44drath(i.e. the "doubled" line you mentioned earlier)
15:04.55stefan_schmidtdrath: one failed check
15:05.28stefan_schmidtdrath: You mailed robert?
15:05.51drathstefan_schmidt: i messaged him via IRC
15:06.12stefan_schmidtdrath: Ah, what I like to suggest :)
15:12.13*** join/#openezx drWyrM (i=c88e3027@gateway/web/cgi-irc/ircatwork.com/x-b83a9e578be8afb0)
15:14.48*** join/#openezx drWyrM (i=c88e3027@gateway/web/cgi-irc/ircatwork.com/x-4c9695b8fa5a410e)
15:22.37*** join/#openezx agd5f (n=deuchera@65.242.105.130)
15:41.22*** join/#openezx |dion| (n=dion@inhex.net)
15:44.58*** join/#openezx LoneStar (n=xinzhen@218.81.28.68)
15:59.00*** join/#openezx |dion| (n=dion@inhex.net)
15:59.55*** join/#openezx LuitvD (n=luitvd@beigetower/luitvd)
16:18.47*** join/#openezx pH5 (n=ph5@p5485FFA4.dip.t-dialin.net)
16:19.40*** join/#openezx Fry-kun (n=kostya@h-66-166-233-66.snvacaid.covad.net)
16:21.41pH5hej, is there a version of the 2.6 pxa-camera driver patch against vanilla linux? I tried to copy the driver files from the R57_G_10.06.47R-r1 kernel and apply daniel's patches on top of that but didn't succeed.
16:22.19koendid slapin finish his patch?
16:23.30pH5I don't know, I just read about the a780 ov9640 driver on openezx-devel and I have the same chip (or ov9650, not sure).
16:26.10stefan_schmidtpH5: Last time I heard about it slapin was interested to start the work on the video driver. Not sure if he started and what the actual status is.
16:28.03*** join/#openezx drWyrM (i=c88e3026@gateway/web/cgi-irc/ircatwork.com/x-50d1bcd3c2dd7ea0)
16:29.21drWyrMhi.
16:29.34stefan_schmidthi drWyrM
16:29.47drWyrManyone has information on how to develop for the archos gmini500? :)
16:29.49stefan_schmidtdrWyrM: ph5 has some questions about the camera driver
16:30.09drWyrMhi ph5.
16:30.23stefan_schmidtdrWyrM: (archos) no idea
16:30.37Fry-kunhi drWyrM
16:30.57*** join/#openezx z72ka-ntb (n=hermanj@r5af183.net.upc.cz)
16:32.15Fry-kunthe latest patch seems to have worked - no more stack trace for kernel panic
16:32.34drWyrMFry-kun: good! And the TF? :)
16:32.36*** join/#openezx z72ka (n=hermanj@r5af183.net.upc.cz)
16:32.51Fry-kunstill trying to figure stuff out
16:34.09pH5hi drWyrM, I was wondering if there is a pxa-camera driver patch against vanilla kernels floating around or against which kernel sources the patches at http://people.openezx.org/wyrm/ should be applied?
16:34.25pH5I have a ov96x0 on the pxa camera interface, too.
16:34.39pH5koen, stefan_schmidt: thanks
16:35.23drWyrMpH5: They were applied against ezx9 patchset, on 2.6.16.
16:35.38drWyrMpH5: Have you talked to slapin already?
16:35.57drWyrMi think that he was testing some pxa camera stuff today.
16:37.19pH5drWyrM: no, I didn't know that he is working on this until just now.
16:38.27drWyrMi think that he has something working on .21, just invited him.
16:38.28*** join/#openezx slapin (n=slapin@iap-pxy-mow1.siemens.ru)
16:38.48drWyrMhi slapin.
16:38.52pH5ow, that would be great.
16:38.57pH5hi slapin
16:39.05drWyrMhow is the pxa camera driver going? :)
16:41.23slapinpH5, or we discuss it here... :)
16:42.38drWyrMhere is a nice place ;) i want to participate too!
16:42.44slapinpH5, I just started from part I understand more or less
16:43.11slapinpH5, and found a lot of interesting nuances
16:43.19koen[18:38] pH5: slapin: hi, I just heard on #openezx that you are working on the pxa-camera driver - are there any patches against the current mainline kernel?
16:43.20koen[18:38] slapin: pH5, it is quite separate
16:43.21koen[18:38] slapin: pH5, hi
16:43.21koen[18:39] slapin: pH5, I think you can take from hnd svn and add to Kconfig
16:43.22koen[18:39] slapin: pH5, I work on i2c sensor now
16:43.22koen[18:39] slapin: pH5, pxa CI is not ready yet.
16:43.23koen[18:40] slapin: pH5, driver requires rewriting to make something good aout of it.
16:43.25koen[18:40] slapin: pH5, since it is glued to specific hardware too much, and redundant.
16:43.32koenfor a bit of context :)
16:43.36slapinif we could get spec, that'd be easier.
16:45.36pH5heh, ok. so if I'm keen to get an ov9640/ov9650 chip on the pxa's quick capture interface to work, what would you advise to look at first?
16:46.10slapinpH5, I'd better rewrite this part, it could be a lot simpler.
16:46.24slapinsensor has 2 interfaces - CI and I2C
16:46.54slapinand has 2 potential other signals - to poweroff and to reset.
16:47.09slapinas for CI interface - it is well-described in PXA spec.
16:48.12pH5slapin: so you are going to rewrite the CI driver from scratch?
16:48.20slapinCI implementation is quite ok, but it needs to be separated from hardware stuff, so to put out device-specific code, and get rod of #ifdefs.
16:48.24pH5I'm not quite sure how everything fits together API wise.
16:48.31slapinpH5, not from scratch
16:48.33pH5ok
16:48.48slapinpH5, I want to redesign it.
16:49.02slapinthe wqy it is it will never get to mainline
16:49.05slapin*way
16:49.42slapinit is really hard to understand, and some developers really didn't - if you look at i2c part you'll understand why.
16:50.12slapinso as I get device on bus, it will be easy to hook it into CI part.
16:50.47slapinpH5, so if you get familiar with CI part of this driver I'd like to reuse your improvements :)
16:51.16*** part/#openezx ade|desk (n=adavey@194.200.143.249)
16:51.21pH5what part will hook into the v4l2 api? will it be the pxa-ci part or the individual sensor drivers?
16:51.42slapinpH5, actually driver design is bad - there's no proper separation of interfaces regardless of file names
16:52.09slapinpH5, it should consist of these parts - i2c, CI, v4l
16:52.15slapinpH5, both of them
16:52.32slapinpH5, it controls sensor via i2c
16:52.50slapinpH5, and only data stream is acquired via CI.
16:53.14pH5so it will be a bit like asoc where a small machine driver will select the correct interfaces and sensor drivers?
16:53.26slapinpH5, really, read PXA spec about CI interface to know what it does, because this part is important to understand.
16:53.27pH5I assume the ov9640 driver shouldn't depend on the pxa CI interfase.
16:53.34slapinpH5, yes
16:53.40slapinpH5, yes
16:53.42pH5ok, I'll start with that
16:54.31slapinpH5, feel free to ask me anytime
16:55.02slapinpH5, I really like there's someone whocould help with this stuff.
16:55.25slapinpH5, most problem will be to find these device specific GPIOs.
16:56.12pH5slapin: sure! good to know whom I can bother with this stuff :)
17:04.23drWyrMslapin: are you still using the motorola drivers as reference?
17:27.44*** join/#openezx goxboxlive (n=goxboxli@141.80-202-161.nextgentel.com)
17:40.54*** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be)
17:53.23*** part/#openezx Fry-kun (n=kostya@h-66-166-233-66.snvacaid.covad.net)
18:07.43*** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be)
18:49.03*** join/#openezx slapin_nb (n=slapin@143.166.249.ozerki.net)
18:49.09slapin_nbrehi, all!
18:49.14slapin_nbdid I miss something?
18:58.20*** join/#openezx drWyrM (n=wyrm@201.2.68.83)
19:00.29*** join/#openezx Fry-kun (n=kostya@h-67-100-89-239.snfccasy.covad.net)
19:01.16drWyrMhi Konstantin.
19:01.39Fry-kunhi
19:01.44Fry-kunDaniel, right?
19:02.01drWyrMyes.
19:02.06drWyrMany progress? :)
19:02.20Fry-kunnope, totally lost so far :(
19:04.44Fry-kuni have no idea what i'm looking for
19:04.52Fry-kunrather, what it should look like
19:05.19drWyrMyou have to work ok a1200_mci_init()
19:05.57drWyrMfirst, look at the pxa_gpio_mode() calls, see if they match the gpio numbers on ezx.h from kernel2.4
19:06.14pH5slapin: nothing I guess. I've most probably found my reset/power cam gpios, but that's all I've done.
19:07.43Fry-kunthere are hundreds of GPIO #defines in 2.4 that are missing in 2.6 - will it be one of those?
19:07.52drWyrMthen, look at the request_irq() call, i am sure 0x49 is wrong here. it should be IRQ_GPIO(????) on the MMC_DETECT gpio defined on ezx.h from 2.4
19:08.50pH5I think, it should be gpio_to_irq for newer kernels (include arch/gpio.h).
19:09.05drWyrMFry-kun: motorola defines a lot of gpio numbers on ezx.h, we prefer to use pxa-regs.h
19:09.34Fry-kunah okay
19:10.02drWyrMpH5: you are right, thank you for pointing this. :)
19:11.01pH5very good :D
19:11.28koenwasn't the old gpio api removed in .21?
19:13.11pH5koen: I think the IRQ_GPIO macro still exists
19:18.03drWyrM#define gpio_to_irq(gpio)       IRQ_GPIO(gpio)
19:18.36drWyrMwill IRQ_GPIO be removed in future?
19:19.11stefan_schmidtdrWyrM: Take a look at schedule for removal text file in the kernel tree.
19:22.36drWyrMstefan_schmidt: not in there.
19:23.32stefan_schmidtdrWyrM: So I think it will stay. But we will see it at least when it breaks. ;)
19:23.41*** join/#openezx florian (n=fuchs@f049170238.adsl.alicedsl.de)
19:23.50drWyrManyway, i will start changing things to use arch/gpio.h. arch independent gpio functions are nice :)
19:24.04stefan_schmidtack
19:24.13florianre
19:24.32stefan_schmidtwb florian
19:24.51stefan_schmidtflorian: How are you?
19:25.32stefan_schmidtflorian: You really should get an assistent to to the lame work and doing R&D only. :)
19:26.24florianstefan_schmidt: hi... incredibly busy, but pretty fine apart from this.
19:28.00florianstefan_schmidt: yeah, that would rock - but currently reality is different: i have to keep things running at kc while others are travelling
19:28.39stefan_schmidtflorian: So you are the assistent and nils have fun. ;)
19:30.01florianstefan_schmidt: not exactly, but currently he has the advantage that he is far away... in fact i would't want his current job.
19:30.18stefan_schmidtflorian: heh
19:30.32florianstefan_schmidt: since Linuxtag he was at home for about five days...
19:30.47stefan_schmidtflorian: ouch
19:31.06pH5wow, busy
19:31.31florianyeah
19:32.16drWyrMu cant have a family if you want to work on embedded linux atm. ;)
19:32.46stefan_schmidtdrWyrM: Psst. Don't tell this our wifes and GFs. ;)
19:33.30florianI made things more complicated... I'll have to move in near future.
19:33.54stefan_schmidtflorian: .cn? ;)
19:34.27florian*cough*
19:35.39florianstefan_schmidt: well that's the positive side - about 600m which makes things easier
19:36.13stefan_schmidtflorian: Jup
19:36.41stefan_schmidtflorian: btw, you as gtk dude can tell me for sure what's about sane tap and hold
19:37.20stefan_schmidtflorian: tslib, gtk, external patches for gtk, in own ui lib or in every application?
19:37.35stefan_schmidtBesides the first two everything would get me nuts. :)
19:37.38florianI don't prefer it - but i'll have more room for an office, garden and better internet connectivity
19:38.13stefan_schmidtflorian: ah, garden is nice. We should need notebooks with better displays.
19:40.49florianstefan_schmidt: I think Phil's solution as a loadable gtk module is a quite good way to solve this. libgtkstylus is not perfect but quite simple and easy to understand.
19:41.53florianstefan_schmidt: true, but there are only a very few. i was told there is a FSC one with a reflective display, but i have never seen this...
19:42.02stefan_schmidtflorian: These are one or two solutions?
19:42.29stefan_schmidtflorian: With Phil you mean Philippe from FOSDEM embedded room?
19:42.52stefan_schmidtflorian: I'm new in such stuff, but I don't get why it isn't in tslib.
19:43.09florianstefan_schmidt: one
19:43.31stefan_schmidtflorian: (displays) yeah, but available in thinkpads is a must for me. :)
19:43.52florianstefan_schmidt: ah no, there are several... Philip Blundell wrote that module.
19:44.14stefan_schmidtflorian: ah, to much phil's :)
19:44.40stefan_schmidtflorian: thanks
19:44.57stefan_schmidtI'm off for some time now. See you guys later.
19:45.01koenthe only downside is that libgtkstylus doesn't give feedback
19:45.14stefan_schmidtah, no feedback is a bummer
19:45.16koenthe downside off the maemo approach is that it is too intrusive
19:45.40koenboth need a good tslib dejitter and variance filter, btw
19:45.51florianindeed
19:46.51stefan_schmidt*sigh*
19:46.58florianHmm... anyone familiar with the GTK input API?
19:47.29stefan_schmidtflorian: input methods? no.
19:48.35stefan_schmidtAnyway, later
19:49.09florianstefan_schmidt: right... i always tried to keep away from it, but it is useful for advanced key input so it might offer us an advanced interface to button behaviour as well - but that's only a theory.
19:49.14florianstefan_schmidt: later
19:49.27koenflorian: can't xkbd do that?
19:50.16floriankoen: that's xlib
19:53.44*** join/#openezx Fry-kun (n=kostya@63.82.6.66)
19:53.51Fry-kunlooks like i got disconnected...
19:54.20drWyrMFry-kun: wb. It happens ;)
19:54.37Fry-kundidn't see any replies from you on my question
19:55.22drWyrMlast msg from you: <Fry-kun> ah okay
19:55.33drWyrMwhat question?
19:55.55Fry-kunoh wow, this isp *REALLY* sucks...
19:56.08Fry-kun(12:41:27) Fry-kun: drWyrM: 2nd pxa_gpio_mode call, "pxa_gpio_mode(GPIO112_MMCCMD_MD);"
19:56.08Fry-kun(12:41:50) Fry-kun: defined as "(112 | GPIO_ALT_FN_1_OUT)"
19:56.15Fry-kun(12:42:06) Fry-kun: vs. ezx.h "#define GPIO_MMC_CMD_MD         (GPIO_MMC_CMD | GPIO_ALT_FN_1_IN | GPIO_ALT_FN_1_OUT)"
19:56.15Fry-kun(12:42:36) Fry-kun: so.. GPIO_ALT_FN_1_IN is missing
19:56.15Fry-kun(12:42:52) Fry-kun: i don't know what it means, so i don't know if it's supposed to be missing -_-
19:56.52drWyrMlet me take a look.
19:58.57koen~logs
19:58.58purlextra, extra, read all about it, logs is apt/ibot/infobot/jbot/purl all log daily to http://ibot.rikers.org/<channelname>/ where channelname is html encoded ie: %23debian | lines that start with a space are not shown | some channels have stats at http://ibot.rikers.org/stats/<channelname>.html.gz
20:02.02Fry-kunadding these doesn't seem to have any effect, though (MMC still not detected)
20:02.56Fry-kunooh, nice with the logs =)
20:09.26pH5GPIO_ALT_FN_1_IN | GPIO_ALT_FN_1_OUT doesn't make any sense. either it's in, or it's out.
20:09.30pH5Fry-kun: but in this case it doesn't actually matter because both ALT_1_OUT and ALT_1_IN are the same functionality (just look at the pxa developer's manual).
20:10.05drWyrMmotorola code. doesnt make sense at all.
20:10.26Fry-kunit was probably written by schmucks like me :D
20:10.41Fry-kunwithout peer review
20:12.15koenI doubt they could find a bad coder just like me, so there can't be any peer review for my C code :)
21:13.55*** part/#openezx drWyrM (n=wyrm@201.2.68.83)
22:10.39*** part/#openezx agd5f (n=deuchera@65.242.105.130)
22:55.23*** join/#openezx drWyrM (n=wyrm@201.2.68.83)
23:01.06*** join/#openezx agd5f (n=alex@c-69-143-17-173.hsd1.va.comcast.net)
23:50.22*** join/#openezx AlexZhang (n=alex@218.17.82.125)

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