| 00:06.48 | WM | Sleep_Walker: no NOR for PXA on treo680 :( |
| 00:08.28 | Sleep_Walker | well, it doesn't matter much |
| 00:08.53 | Sleep_Walker | WM: so you expect one another GPIO for GSM as IN? |
| 00:09.13 | WM | yes. |
| 00:09.52 | WM | I think that the pxa on treo needs to sleep, otherwise battery life would be short. |
| 00:10.06 | Sleep_Walker | I think it's GPIO14 |
| 00:11.34 | Sleep_Walker | I can't remember how did I found that, but there is RE on that and WAKE_UP |
| 00:12.22 | WM | yeah, a good candidate. |
| 00:12.31 | WM | treo also has bluetooth right? |
| 00:12.36 | WM | its a bcm2035? |
| 00:12.41 | Sleep_Walker | nope |
| 00:13.13 | WM | nope = no bluetooth? or not bcm2035? |
| 00:13.41 | Sleep_Walker | BCM2045 and attached to USB |
| 00:13.56 | WM | hum.. |
| 00:14.09 | Sleep_Walker | http://hackndev.com/trac/wiki/Treo680Hardware |
| 00:14.16 | WM | so you probably have a RE wakeup from bcm2045 too. |
| 00:15.48 | Sleep_Walker | yes |
| 00:16.00 | Sleep_Walker | GPIO11 |
| 00:17.50 | Sleep_Walker | GPIO14 is changing RE on switching GSM on/off |
| 00:18.12 | WM | good. |
| 00:18.41 | Sleep_Walker | but I can't imagine how this GPIO can affect stop responding after 10 seconds |
| 00:19.13 | WM | try a BE interrupt on this pin. |
| 00:19.50 | WM | and rise some of the other 2 interrupts on gpio14 rise, and low it on gpio14 low. |
| 00:20.18 | WM | just mimic gpio14 on some of the other pins :) |
| 00:20.33 | Sleep_Walker | WM: I see |
| 00:20.45 | tmzt | prepareToReadData? |
| 00:22.07 | WM | if you see gpio14 going down at the same 10sec timeout, then rise some other pin, wait for gpio14 to come up, before sending data to uart. |
| 00:22.43 | tmzt | it loads imei into the radio? |
| 00:22.58 | Sleep_Walker | tmzt: I don't know |
| 00:23.16 | tmzt | but if you don't power off the radio it shouldn't matter |
| 00:23.47 | Sleep_Walker | btw. I found also in UsbRadioSerialBulverde.prc.prc "Clear Dtr during Modem poweroff" |
| 00:24.19 | Sleep_Walker | on USB is bluetooth |
| 00:24.32 | WM | the modem is on ffuart? |
| 00:24.38 | Sleep_Walker | yes |
| 00:24.56 | tmzt | it seems the radio can be power on/off by til |
| 00:26.43 | Sleep_Walker | wtf til? |
| 00:26.55 | tmzt | AT+CHLD |
| 00:26.57 | tmzt | AT+CHLD=2 |
| 00:27.01 | tmzt | AT+CHLD=3 |
| 00:27.37 | tmzt | sorry, that's for three way isn't it |
| 00:27.52 | tmzt | til is telephone interface layer |
| 00:29.00 | Sleep_Walker | If I only knew I need to create vocabulary :b |
| 00:58.43 | Sleep_Walker | WM: I haven't added BE to GPIO14, but I watched it's status through /sys/class/gpio/... interface |
| 00:58.50 | Sleep_Walker | no change |
| 00:58.54 | Sleep_Walker | always 0 |
| 00:59.17 | WM | so, it only changes when you change the power gpio? |
| 00:59.42 | Sleep_Walker | WM: I haven't seen it changing |
| 00:59.47 | WM | anybody knows how do I revert a git-revert? :) |
| 00:59.58 | WM | I did a git-revert -n <commit> |
| 01:00.09 | WM | and now I want the reverted changes back, how do I do it? |
| 01:00.26 | Sleep_Walker | git magic is black |
| 01:00.40 | Sleep_Walker | (and I don't have black chicken's blood) |
| 01:00.54 | WM | Sleep_Walker: (21:17:51) Sleep_Walker: GPIO14 is changing RE on switching GSM on/off |
| 01:01.02 | WM | so, its not the level that changes? |
| 01:01.08 | Sleep_Walker | WM: in PalmOS |
| 01:01.40 | Sleep_Walker | WM: in Linux (and without SIM) it doesn't react at all |
| 01:01.54 | WM | ahh, so palmos reconfigures it when you enable/disable gsm.. |
| 01:02.11 | WM | hum. |
| 01:02.37 | Sleep_Walker | yes |
| 01:02.37 | WM | you may have some kind of complex handshake, with the same pin acting as in/out depending on the step.. |
| 01:02.44 | WM | we have this on ezx too. :( |
| 01:02.58 | Sleep_Walker | oh no |
| 01:03.52 | Sleep_Walker | I have one really weird GPIO |
| 01:04.00 | Sleep_Walker | it's used for IrDA |
| 01:04.40 | Sleep_Walker | it switches between OUT-LOW-AFN1/IN-HIGH-AFN0 |
| 01:05.32 | Sleep_Walker | (and even more weirder is that other two GPIOs does changes in the same time) |
| 01:05.51 | WM | on irda? |
| 01:05.54 | WM | or gsm? |
| 01:06.01 | Sleep_Walker | IrDA |
| 01:06.10 | Sleep_Walker | but maybe it's multiplexed somehow :/ |
| 01:06.13 | WM | really weird! :) |
| 01:06.30 | WM | we have some weird stuff too... |
| 01:06.53 | Sleep_Walker | 9 - switches - IN LOW/HI, 47 as described above, 115 OUT LOW/HI |
| 01:07.09 | WM | SSP2, SSP3, Audio Codec, BCM2035 audio and BP audio are all connected together (network mode). |
| 01:07.14 | Sleep_Walker | and when emmiting, 47 is also OUT-HI sometimes :b |
| 01:07.22 | WM | so, if ssp2 pins are set wrong, the ssp3 will not work. |
| 01:07.36 | WM | on e680 the STUART pins are shared with leds. |
| 01:08.33 | WM | but we have the 2.4 kernel source released by moto... |
| 01:08.39 | WM | this makes everything easy ;) |
| 01:10.10 | WM | git-reset did the trick for git ;) |
| 01:10.58 | Sleep_Walker | I have to go sleeping |
| 01:11.08 | Sleep_Walker | it's 3 o'clock in the morning |
| 01:11.12 | WM | good night! |
| 01:11.21 | Sleep_Walker | good night |
| 01:11.32 | WM | I will tell you if I have more ideas about your gsm chip.. |
| 01:11.34 | Sleep_Walker | thanks for all your suggestions, help and time |
| 01:17.41 | Sleep_Walker | hm, I just found some another weird GPIO |
| 01:17.57 | Sleep_Walker | GPIO40 instead of FF UART DTR it's afn0 |
| 01:22.12 | Sleep_Walker | oh |
| 01:22.22 | Sleep_Walker | I'm too bad |
| 01:22.46 | Sleep_Walker | I mixed GPIO40 and GPIO87 into one /sys/ entry |
| 01:23.01 | Sleep_Walker | so - when I was speaking about power (later reset) |
| 01:23.11 | Sleep_Walker | it was always changing both |
| 01:23.22 | Sleep_Walker | some ancient part of code |
| 01:23.52 | WM | heh, so all we assumed about reset/wake is not valid ;) |
| 01:24.32 | Sleep_Walker | well, one of this two must be reset |
| 01:24.45 | WM | gpio87 probably. |
| 01:24.46 | Sleep_Walker | but I'm having too much GPIOs |
| 01:48.42 | *** join/#openezx flyhorse|linux (n=flyhorse@116.18.197.187) |
| 01:49.19 | Sleep_Walker | gpio40 0->1 allows me to talk with GSM |
| 01:50.20 | tmzt | no timeout? |
| 01:50.29 | Sleep_Walker | still timeout |
| 01:50.55 | tmzt | any gpios change when it stops responding? |
| 01:53.44 | Sleep_Walker | wow |
| 01:54.43 | Sleep_Walker | I just got to this menu: http://hhtinker.blogspot.com/2007/07/ring-ring.html |
| 01:55.05 | Sleep_Walker | but I haven't put some weird command |
| 01:55.17 | Sleep_Walker | I switched of GPIO57 |
| 01:55.29 | Sleep_Walker | and GPIO 40 ->0->1 |
| 01:57.15 | tmzt | armrd/armwr |
| 01:57.55 | Sleep_Walker | ? |
| 01:58.05 | Sleep_Walker | read/write |
| 01:58.23 | Sleep_Walker | but arm - bcm2133 and PXA270 - both ARM :b |
| 01:59.37 | WM | "Update: Ah. I've found references to something called cyclic sleep mode. So perhaps the baseband goes to sleep for some cycles and then wakes up and can receive commands again." |
| 01:59.55 | Sleep_Walker | I already read that |
| 02:00.27 | WM | I think this is the trick... Somehow the baseband is put to sleep, and you need to wake it up before talking to it again.. |
| 02:00.28 | Sleep_Walker | WM: http://hhtinker.blogspot.com/2007/07/wake-up.html |
| 02:00.31 | Sleep_Walker | one later |
| 02:01.30 | WM | and doesn't this work? |
| 02:03.09 | Sleep_Walker | I haven't figured which gpio is which |
| 02:03.20 | Sleep_Walker | but I've got interrupt on GPIO14 |
| 02:03.30 | WM | 11/rts is the "mimic" I told you, when 11 is high gsm is awake, so you can receive data.. |
| 02:03.52 | Sleep_Walker | yes |
| 02:04.03 | Sleep_Walker | that's exactly what I'm doing now |
| 02:04.08 | WM | as soon as 11 drops (because you lowered 57, or because it drops automagically), you drop rts too. |
| 02:04.13 | Sleep_Walker | I had to separate that "power" |
| 02:04.36 | WM | also, timing on these operations is critic... |
| 02:04.42 | Sleep_Walker | ls ../gpio[0-9]*/value |
| 02:04.43 | Sleep_Walker | ../gpio14/value ../gpio40/value ../gpio57/value ../gpio79/value ../gpio87/value |
| 02:04.51 | WM | I would go for kernel space code for this.. |
| 02:04.51 | Sleep_Walker | these GPIOs I'm working with |
| 02:05.33 | Sleep_Walker | cat ../gpio[0-9]*/value | tr '\n' ' ' |
| 02:05.34 | Sleep_Walker | 0 0 0 0 0 |
| 02:05.54 | Sleep_Walker | echo 1 > value |
| 02:05.57 | Sleep_Walker | (GPIO40) |
| 02:06.07 | Sleep_Walker | cat ../gpio[0-9]*/value | tr '\n' ' ' |
| 02:06.08 | Sleep_Walker | 1 1 0 0 0 |
| 02:06.20 | WM | im going to buy some cigarettes, bb in 20 minutes. |
| 02:07.43 | Sleep_Walker | echo 1 > ../gpio87/value |
| 02:07.53 | Sleep_Walker | cat ../gpio[0-9]*/value | tr '\n' ' ' |
| 02:07.53 | Sleep_Walker | 0 1 0 0 1 |
| 02:08.08 | Sleep_Walker | asserting GPIO87 clears interrupt on GPIO14 |
| 02:13.17 | Sleep_Walker | I have to really go sleeping :b |
| 02:33.11 | WM | Sleep_Walker: you are close to solve this! |
| 02:33.41 | WM | sleep and continue tomorrow, im sure you will have good news when I awake tomorrow. :) |
| 03:10.37 | *** join/#openezx arne (i=nobody@dslc-082-082-065-193.pools.arcor-ip.net) |
| 03:48.09 | *** join/#openezx purl (i=ibot@rikers.org) |
| 03:48.09 | *** topic/#openezx is OpenEZX Developer Lounge -- new gen-blob at http://people.openezx.org/wyrm/gen-blob/gen-blob -- http://openezx.org |
| 06:14.32 | *** join/#openezx WyrM (n=wyrm@20158136073.user.veloxzone.com.br) |
| 06:21.25 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 06:59.50 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 08:22.10 | *** join/#openezx florian_kc (n=fuchs@port-217-146-132-69.static.qsc.de) |
| 09:08.10 | *** join/#openezx WyrM (n=wyrm@20158137202.user.veloxzone.com.br) |
| 09:10.09 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 09:22.20 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 09:55.36 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 10:00.25 | *** join/#openezx Sleep_Walker (n=Sleep@1.57.broadband2.iol.cz) |
| 10:27.01 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 10:31.23 | ao2 | hi |
| 10:37.33 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 10:41.35 | *** join/#openezx WyrM (n=wyrm@20158152232.user.veloxzone.com.br) |
| 10:46.06 | *** join/#openezx gDD (i=io@125.116.32.29) |
| 10:55.13 | *** join/#openezx flo_lap (n=fuchs@port-217-146-132-69.static.qsc.de) |
| 11:37.30 | *** join/#openezx shpala (n=shpala@89-138-127-169.bb.netvision.net.il) |
| 11:43.05 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 11:48.44 | shpala | Hi, everyone! |
| 11:48.45 | shpala | Does anyone here work with motorola q? |
| 12:04.00 | *** join/#openezx univac (n=univac@148.81.191.193) |
| 12:05.27 | *** part/#openezx shpala (n=shpala@89-138-127-169.bb.netvision.net.il) |
| 12:19.49 | *** join/#openezx gmzhuo (n=gmzhuo@222.210.147.75) |
| 12:30.37 | gmzhuo | I can't boot the newst kernel compiled from git? |
| 12:31.02 | sabrod | gmzhuo, wyrm told me to use this one instead : a7bb3909b3293d503211d7f6af8ed62c1644b686 |
| 12:31.18 | sabrod | Hi, btw... :) |
| 12:33.12 | gmzhuo | Hi,sabrod |
| 12:33.21 | sabrod | You got a white screen soon after the boot? |
| 12:33.38 | sabrod | Here is what Wyrm said : "I think I found it. |
| 12:33.38 | sabrod | (06:52:40 PM) WM: changes on CS handling on the pxa2xx_spi.c driver. |
| 12:33.38 | sabrod | (06:53:01 PM) WM: commit a7bb3909b3293d503211d7f6af8ed62c1644b686 |
| 12:33.40 | sabrod | " |
| 12:34.17 | sabrod | WM: sabrod: if you want to fix your openezx.git tree, do a: |
| 12:34.17 | sabrod | (07:14:23 PM) WM: $ git revert -n a7bb3909b3293d503211d7f6af8ed62c1644b686 |
| 12:34.58 | sabrod | Sorry, it's not a git hash to checkout it's a git commit to revert... |
| 12:40.31 | *** join/#openezx gDD_mobilE (n=gDD@211.140.16.239) |
| 12:54.09 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 13:17.06 | *** join/#openezx johanbr (n=j@blk-7-131-230.eastlink.ca) |
| 14:28.32 | *** join/#openezx shpala (n=shpala@89-138-127-169.bb.netvision.net.il) |
| 14:29.20 | *** join/#openezx shpala (n=shpala@89-138-127-169.bb.netvision.net.il) |
| 14:30.51 | shpala | hi, i need help dumping the memory of my motorola q phone. i saw on the site that some people here work with motoq' |
| 14:31.52 | ao2 | shpala, you can ping tmzt |
| 14:39.54 | shpala | thanks |
| 15:00.54 | *** join/#openezx janneg (n=janne@tichy.grunau.be) |
| 15:01.30 | l403 | ao2, do you know if there is newer fso image where the on screen keyboard is fixed? |
| 15:02.24 | ao2 | l403, I am still at console images, I haven't tried any GUI image recently |
| 15:02.35 | l403 | I have some from this year and the OSK keys are too big to fit all on screen |
| 15:03.21 | l403 | well, only the most right keys like '=' are missing |
| 15:03.29 | ao2 | I see, it must have been coded for VGA resolution |
| 15:04.23 | l403 | the left keys like shifts have overflowing text label but are at least usable |
| 15:05.00 | yang | ao2: What is the current status of GPS (A780) do you have a program which enables you to see the map, or does it only get co-ordinates ? |
| 15:06.05 | ao2 | it just gives coordinate, it is not integrated with anything else yet |
| 15:07.06 | l403 | so loging with a bash script is possible? |
| 15:11.46 | *** join/#openezx johanbr (n=j@JBrannlund2.MathStat.Dal.Ca) |
| 15:28.07 | ao2 | l403, should be |
| 15:28.46 | l403 | does anything come to mind how to type + with the key being off screen? |
| 15:29.07 | l403 | ar maybe change the dpi so it fits, hmm |
| 15:31.36 | l403 | well, ssh :) |
| 16:28.00 | *** join/#openezx janneg (n=janne@tichy.grunau.be) |
| 16:48.47 | WyrM | hi |
| 16:49.50 | ao2 | hi WyrM |
| 17:50.14 | *** join/#openezx Fosforo (n=Fosforo@20151133039.user.veloxzone.com.br) |
| 18:13.26 | *** join/#openezx pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 18:26.08 | *** join/#openezx Sleep_Walker (n=Sleep@193.179.96.131) |
| 18:53.10 | *** join/#openezx stefan_schmidt (n=stefan@p5B036D20.dip.t-dialin.net) |
| 19:36.41 | *** join/#openezx stefan_schmidt_ (n=stefan@p5B035319.dip.t-dialin.net) |
| 20:00.16 | *** join/#openezx roh (n=roh@yamato.hyte.de) |
| 20:00.19 | roh | re |
| 20:01.25 | *** join/#openezx florian (n=fuchs@g227185239.adsl.alicedsl.de) |
| 20:03.07 | *** join/#openezx flo_lap (n=fuchs@82.113.121.120) |
| 20:15.52 | *** join/#openezx florian (n=fuchs@g227185239.adsl.alicedsl.de) |
| 20:30.47 | stefan_schmidt_ | ghane: What's the best place for some infos about flashing a kernel and other stuff on MAGX? I guess roh will be interested in some infos for the RAZR V8 |
| 20:49.33 | l403 | ao2, did you test vi in fso? |
| 20:50.18 | ao2 | l403, vim works as fas as I can tell. I used it via ssh tho |
| 20:50.30 | l403 | I thought I didnt know hoow to use it but then I was assured I was doing it rite and it must be broken |
| 20:50.45 | ao2 | s/fas/far/ |
| 20:51.03 | l403 | is there a versin file somewhere in the image? |
| 20:51.08 | ao2 | l403, maybe you have more recent, more broken image :) |
| 21:11.38 | *** join/#openezx stefan^_ (n=root@robolab.informatik.Uni-Osnabrueck.DE) |
| 22:14.34 | stefan_schmidt_ | ao2: Do you have a moment? |
| 22:14.49 | ao2 | stefan_schmidt_, tell me |
| 22:15.02 | stefan_schmidt_ | ao2: I have a device with two cameras here |
| 22:15.14 | stefan_schmidt_ | ao2: I have no idea how they are connected etc |
| 22:15.32 | stefan_schmidt_ | ao2: I would guess I2C for configuration and camera interface for data |
| 22:15.39 | stefan_schmidt_ | its an S3C2440 |
| 22:15.55 | stefan_schmidt_ | ao2: How could I poke I2C to see if it is there |
| 22:16.08 | stefan_schmidt_ | and especially _what_ sensor is connected there? |
| 22:16.41 | roh | stefan_schmidt_ i would simply latch the camera-if-es together controlled by some gpio.. or are the 2 cams used at the same time? |
| 22:17.01 | ao2 | stefan_schmidt_, before poking i2c with i2c-tools you need to power up the sensor, in our case this is done with a gpio pin. |
| 22:17.17 | stefan_schmidt_ | roh: under wimo I only saw them used either or |
| 22:17.41 | stefan_schmidt_ | ao2: ok, need to look if harald already found this with haret |
| 22:18.12 | stefan_schmidt_ | roh: I would think they did it the way you mentioned |
| 22:18.25 | stefan_schmidt_ | roh: AFAIK the s3c has only one camera if |
| 22:18.42 | ao2 | stefan_schmidt_, then you can get an address from i2c-tools which will see sone i2c device attached. Once you have the address you can verify what sensor it is, by either searching the address on datasheets, or trying to guess the registers sending data with i2c-tools |
| 22:18.57 | stefan_schmidt_ | roh: Connecting both and toogle with an gpio would be the only way. Also it would fit the .tw hardware development style. ;) |
| 22:19.21 | ao2 | stefan_schmidt_, is it a glofish device? |
| 22:19.32 | stefan_schmidt_ | ao2: thanks, will look for the power gpio later |
| 22:19.39 | stefan_schmidt_ | ao2: yup, glofiish m800 |
| 22:19.49 | ao2 | stefan_schmidt_, you're welcome |
| 22:20.16 | stefan_schmidt_ | hopes it is a sensor which already have a mainline driver |
| 22:20.29 | stefan_schmidt_ | There seem to got a lot of them in the last releases |
| 22:22.05 | ao2 | prowling in WINCE dlls you can also get some hints about camera driver |
| 22:22.18 | stefan_schmidt_ | hmm, no gpio for camera power listed. It either is handled by the CPLD or some other component or Harald just did not test it yet with haret. |
| 22:22.30 | stefan_schmidt_ | would go for the second bet :) |
| 22:22.44 | stefan_schmidt_ | ao2: good point |
| 22:22.59 | stefan_schmidt_ | ao2: Reading the IDA output is fun sometimes |
| 22:23.18 | stefan_schmidt_ | Even if I can't read ASM at all ;) |
| 22:28.45 | roh | well.. its not that hard |
| 22:28.54 | roh | even if the asm is unknown *ducks* |
| 22:31.00 | tmzt | shpala: still here? |
| 22:31.14 | tmzt | does anyone know if shpala has gsm or cdma? |
| 22:32.19 | WyrM | I guess that if both are pxa+doc+wm this shouldn't make a difference ;) |
| 22:44.42 | *** join/#openezx johanbr (n=j@blk-7-131-230.eastlink.ca) |
| 22:45.39 | *** join/#openezx l403 (n=l@85.132.159.239) |
| 22:59.22 | WyrM | tmzt: btw, any progress with eoc? |
| 23:05.02 | *** join/#openezx sabrod (n=sab@lns-bzn-53-82-65-49-164.adsl.proxad.net) |
| 23:05.39 | stefan^_ | WyrM: yes, we tried all that |
| 23:05.43 | stefan^_ | hi |
| 23:05.52 | stefan^_ | cancel the 2.last post |
| 23:05.58 | stefan^_ | one question |
| 23:06.09 | stefan^_ | i have the camera module loaded on a780 |
| 23:06.35 | stefan^_ | the cameraalso seems to be in use , at least i2c dump talks about the adress being busy |
| 23:07.03 | stefan^_ | but i dont have a /dev/video0 file. do i need to create that manually ? |
| 23:08.25 | tmzt | WyrM: haven't had time, probably not much untill weekend |
| 23:08.53 | tmzt | I think gsm is even more similar to ezx which is why I ask |
| 23:09.01 | tmzt | but we don't have any support for that phone yet |
| 23:10.16 | tmzt | how is upstream, should I pull? |
| 23:11.46 | WyrM | tmzt: openezx.git is broken. |
| 23:11.51 | WyrM | because of mainline. |
| 23:12.19 | WyrM | I already submitted the fix mainline, and I can point it to you if you want to pull. |
| 23:13.31 | WyrM | tmzt: also, I think that we should no longer have motoq on a different branch... |
| 23:14.30 | WyrM | its too similar to ezx, we could have ezx/current depending on it, so I remember to update motoq.c case anything changes on the drivers. :) |
| 23:16.46 | WyrM | and I think you should prepare a basic motoq.c and send it to LAK. :) |
| 23:19.06 | tmzt | ok, I definately have no reason to have a set of topic branches when everything is in one file |
| 23:19.25 | tmzt | but I'm wondering what the ezx topic branches are for and why ezx.c changes between them? |
| 23:19.52 | WyrM | tmzt: we can't send stuff upstream as a bit .diff file :) |
| 23:19.59 | WyrM | s/it/ig/ |
| 23:20.21 | tmzt | I know, but I mean different parts of the file are in different topics? |
| 23:20.34 | WyrM | yes, because it depends on different drivers. |
| 23:21.18 | tmzt | and the headers for those drivers are in the topic as well? |
| 23:21.27 | WyrM | or they are grouped to be sent mainline as a single patch (when there is no driver dependency), etc.. |
| 23:22.15 | tmzt | isp is gen1 only? |
| 23:22.15 | WyrM | tmzt: see http://people.openezx.org/wyrm/images/latest/topgit-layout.png |
| 23:22.27 | WyrM | isp is E2 and E6 only. |
| 23:22.42 | WyrM | tmzt: all ezx/mach/* patches are changes to ezx.c |
| 23:23.03 | WyrM | all ezx/* patches are drivers. |
| 23:23.21 | tmzt | is sparsemem fixed upstream? |
| 23:23.42 | WyrM | no, and I think it will never be. |
| 23:23.54 | WyrM | and its not supposed to go upstream :) |
| 23:24.04 | WyrM | ahh, motoq doesn't work with sparsemem, right? |
| 23:24.16 | tmzt | right |
| 23:24.30 | tmzt | but I would like to find out why if possible |
| 23:24.30 | WyrM | :( |
| 23:25.23 | WyrM | me too :) |
| 23:25.57 | tmzt | what is ezx/eoc and ezx/mach/eoc? it just says trivial merge |
| 23:26.23 | WyrM | eoc driver an eoc pdata. |
| 23:26.28 | WyrM | s/an/and |
| 23:27.04 | tmzt | so I need to look at tg patch to see what that is |
| 23:27.15 | tmzt | is eoc just a i2c chip driver now? |
| 23:27.23 | WyrM | yes |
| 23:27.30 | tmzt | and should it be a transceiver driver? |
| 23:27.44 | tmzt | like otg-transceiver is |
| 23:27.50 | WyrM | the emu driver is the one that will glue eoc, pcap, isp1583 on a common interface. |
| 23:31.08 | WyrM | can you point me where is otg-transceiver driver? |
| 23:31.11 | WyrM | what is it? |
| 23:31.16 | WyrM | generic otg driver? |
| 23:37.34 | WyrM | tmzt: are you talking about drivers/usb/otg/* ? |
| 23:55.36 | tmzt | http://kerneltrap.org/index.php?q=mailarchive/linux-usb/2008/12/2/4293494 |
| 23:55.40 | ao2 | stefan^_, you need to load pxa-camera by hand to have the video interface |
| 23:55.50 | tmzt | is part of it, or at least that helped with SEOS right? |
| 23:58.17 | WyrM | tmzt: I don't get it. |
| 23:58.44 | tmzt | that's not it, that just checks SEOS and disables something, sorry |
| 23:58.55 | tmzt | it's hard to search for this on google |
| 23:59.16 | WyrM | and I don't see a seos check in this page :) |
