| 00:08.40 | *** join/#htc-linux gh0ul (n=asds@host81-157-60-163.range81-157.btcentralplus.com) |
| 00:42.38 | *** join/#htc-linux scatterp (i=acka@82-35-152-46.cable.ubr05.enfi.blueyonder.co.uk) |
| 00:43.06 | scatterp | hi whats the best htc for linux/android/windows use preferably with a keyboard and lots of power ? |
| 00:43.43 | tmzt | probably touch pro |
| 00:44.59 | scatterp | hmm first page i open on it "power meets beauty work meets play" |
| 00:45.06 | scatterp | not a bad start im going to read more :D |
| 00:45.50 | tmzt | that's their way of saying it has sliding panels and animated clouds |
| 00:45.58 | scatterp | tv out |
| 00:46.04 | scatterp | omg i always wanted that!! |
| 00:47.32 | scatterp | whats the max gbs of flash i can put in it ? |
| 00:47.56 | tmzt | currently, 32gb I think |
| 00:48.45 | scatterp | nice |
| 00:48.53 | scatterp | i see a few diffrent "varients" |
| 00:48.59 | scatterp | whats the most powerfull? |
| 00:49.44 | tmzt | whichever network you need it for |
| 00:50.19 | scatterp | i mean the specs are diffrent for each varient right ? |
| 00:50.32 | tmzt | not the gsm ones, those are the same I think |
| 00:51.25 | scatterp | oh |
| 00:51.39 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
| 00:52.46 | scatterp | look diffrent on the page im seeing |
| 00:52.50 | scatterp | some have 3g some dont |
| 00:52.53 | scatterp | some weigh more... |
| 00:56.08 | tmzt | I didn't know there were touch pro's without 3g |
| 01:01.38 | exco | imfloflo: around? |
| 01:01.48 | imfloflo | exco what is the version of system.img you are using to can make call ? cause with the lastest DZO files + change mtype + rogro's override rogro zimage i can't make call |
| 01:01.53 | imfloflo | yes here |
| 01:02.45 | exco | imfloflo: 1st try the default.txt from the wiki |
| 01:03.42 | exco | I'm still using that image in the all-in-one on my site (trying to find out what version that was again) |
| 01:03.56 | imfloflo | this http://wiki.xda-developers.com/uploads/default.txt ? |
| 01:04.14 | exco | yes |
| 01:04.49 | exco | ok found it - I'm still using the system.img from 21-01 I guess (probably data.gz and initrd from some days ago) |
| 01:05.22 | exco | I started a Files section on the wiki where we can link to single files as they get updated |
| 01:05.35 | imfloflo | good point |
| 01:06.13 | exco | but I have no idea what changed with recent system.img's - but there seems to be a problem with calls and other stuff - at least that's what the messages on the Kaiser thread indicate |
| 01:06.42 | exco | did you already PM that guy about pics - or should I? |
| 01:06.51 | imfloflo | so i retry lastest dzo package, rogro's zimage ,wiki default , on a fresh SD format FAT ,lets go |
| 01:06.54 | imfloflo | not pm |
| 01:07.28 | exco | for me once google login and wifi works - Android will be my main OS |
| 01:08.03 | exco | thought about getting a G1 even before I bought my Polaris - but where'd be the fun in that ;-) |
| 01:08.25 | imfloflo | me too want to use it every day |
| 01:08.56 | imfloflo | result : not working |
| 01:09.25 | exco | so use the system.img from 21 (sms enabled one) |
| 01:09.53 | exco | btw what changed with the new one apart from the important stuff being broken? |
| 01:10.48 | imfloflo | need t ofind this system img from 21 |
| 01:10.56 | imfloflo | kaiser thread ? |
| 01:11.07 | exco | yeah |
| 01:12.09 | *** join/#htc-linux scaterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 01:12.26 | exco | imfloflo: http://forum.xda-developers.com/showthread.php?p=3194496#post3194496 |
| 01:12.51 | exco | I don't know if he replaced that system.img since then |
| 01:13.01 | imfloflo | thanks |
| 01:13.10 | exco | you can always just load it from the wiki again |
| 01:13.20 | imfloflo | i though he remplace it cause different size in the new release |
| 01:13.30 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 01:13.41 | imfloflo | just ask him :p |
| 01:15.28 | imfloflo | 31604ko lastest package, 31476ko 21package |
| 01:19.00 | exco | so whats new in the new one? bootlogo, what else? |
| 01:19.25 | imfloflo | not working :s |
| 01:20.01 | exco | what isn't working? |
| 01:20.06 | imfloflo | call |
| 01:20.52 | exco | well I haven't tried calling to be honest (but data works fine) |
| 01:21.12 | imfloflo | don't have data plan so i test call instead data :p |
| 01:21.52 | exco | calling doesn't work altogether or just some audio? |
| 01:22.58 | imfloflo | altogether i can't pass a call, a popup appears and says not registered on the network |
| 01:23.34 | exco | and signal strength shows bars? |
| 01:25.37 | imfloflo | x appears so doesn't work |
| 01:26.07 | exco | well it does work on mine |
| 01:26.30 | exco | umts or gsm coverage? |
| 01:28.27 | imfloflo | 3G Hspda under winmo , toulouse is big city in france |
| 01:31.06 | imfloflo | i se under winmo there is 2 authetification possible under GPRS , PAP and CHAP does't it matter? mine is PAP |
| 01:33.27 | exco | don't know - I don't need to activate data in Win anymore |
| 01:33.43 | exco | I'm also on a 3G network so that shouldn't be it then |
| 01:34.14 | exco | xda is down - and so am I for the night ;-) |
| 01:34.34 | exco | c ya |
| 01:35.09 | *** part/#htc-linux exco (n=exco@e181065103.adsl.alicedsl.de) |
| 01:35.29 | imfloflo | gn |
| 01:37.32 | *** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) |
| 01:59.52 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 02:07.32 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 02:09.57 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 02:12.10 | *** join/#htc-linux br1ck_ (n=br1ck@xdslcf074.osnanet.de) |
| 02:25.00 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 02:51.41 | *** join/#htc-linux Shinto (n=John@f048226167.adsl.alicedsl.de) |
| 03:05.03 | imfloflo | dzo your website seems to be down :s |
| 03:12.44 | *** join/#htc-linux Zack84a (n=zack84a@r74-192-0-176.bcstcmta01.clsttx.tl.dh.suddenlink.net) |
| 04:09.11 | *** join/#htc-linux scatterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 04:14.13 | *** join/#htc-linux scaterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 04:16.56 | *** join/#htc-linux scatterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 04:20.22 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 04:31.56 | *** join/#htc-linux pigeon_ (n=pigeon@60-241-137-179.static.tpgi.com.au) |
| 04:33.07 | *** join/#htc-linux PoohbaLT (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net) |
| 04:50.33 | *** join/#htc-linux techie (n=blarg@ip24-250-212-67.ga.at.cox.net) |
| 04:51.03 | *** join/#htc-linux scaterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 04:54.34 | *** join/#htc-linux Zack84a (n=zack84a@r74-192-0-176.bcstcmta01.clsttx.tl.dh.suddenlink.net) |
| 04:58.53 | *** join/#htc-linux scatterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 05:09.23 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) [NETSPLIT VICTIM] |
| 05:12.49 | maejrep | tmzt: I haven't made any changes to smd yet |
| 05:13.43 | maejrep | I could hack it the way it is in vogue, but because it needs to work on raph100 as well, it's better to plan the changes properly, with minimal changes to smd.c |
| 05:15.09 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
| 05:23.19 | *** join/#htc-linux Zack84a (n=zack84a@r74-192-0-176.bcstcmta01.clsttx.tl.dh.suddenlink.net) [NETSPLIT VICTIM] |
| 05:23.19 | *** join/#htc-linux gh0ul (n=asds@host81-157-60-163.range81-157.btcentralplus.com) [NETSPLIT VICTIM] |
| 05:23.19 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) [NETSPLIT VICTIM] |
| 05:23.19 | *** join/#htc-linux tmzt (n=tmzt@adsl-69-221-148-155.dsl.akrnoh.ameritech.net) [NETSPLIT VICTIM] |
| 05:23.19 | *** join/#htc-linux hairyraven (n=nobody@209.250.241.104) [NETSPLIT VICTIM] |
| 05:23.42 | maejrep | what's a good way to implement the navi LED hardware blinking? |
| 05:23.55 | maejrep | the led class dev supports blink_set(int delay_on, int delay_off) |
| 05:24.17 | maejrep | and triggers |
| 05:57.07 | AstainHellbring | maejrep let the other processes access it and tell it to turn on off blink? |
| 06:38.25 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfeb2e.pool.einsundeins.de) |
| 06:54.07 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 07:06.27 | *** join/#htc-linux kiozen (n=oeichler@p54922353.dip0.t-ipconnect.de) |
| 07:12.36 | *** join/#htc-linux kiozen (n=oeichler@p54922353.dip0.t-ipconnect.de) |
| 07:13.31 | *** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
| 07:15.13 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 07:15.19 | Untouchab1e | Good morning! |
| 07:28.33 | *** join/#htc-linux [1]Untouchab1e (n=Untoucha@82.147.51.146) |
| 07:36.45 | *** join/#htc-linux timebomb (n=tb@e176123041.adsl.alicedsl.de) |
| 07:43.58 | *** join/#htc-linux opennandra (n=opennand@80.122.179.98) |
| 07:50.39 | opennandra | morning |
| 08:10.50 | *** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-207-193.customer.ch.netstream.com) |
| 08:17.00 | *** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 08:28.56 | *** join/#htc-linux Kensan_ (n=ken@gw.ptr-80-238-228-249.customer.ch.netstream.com) |
| 08:32.14 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 08:48.09 | *** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-186-165.customer.ch.netstream.com) |
| 08:59.01 | j0b0 | maejrep, re the navi driver, for development i kept everything in 1 file, but tried to write it so that it is easily split into a header, the bit that goes into the board-bla.c, and the navi driver itself |
| 08:59.35 | j0b0 | it no longer reports lid switch. moved that into your keyboard driver, and it should probably also not control LEDs directly |
| 09:00.37 | j0b0 | altho that is a very easy way to test confirm that both the touch pad and the leds are working for now |
| 09:05.21 | *** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl) |
| 09:09.33 | *** join/#htc-linux scaterp (n=acka@82-35-198-69.cable.ubr05.enfi.blueyonder.co.uk) |
| 09:12.44 | *** join/#htc-linux ykut_johny (n=ykut_joh@mitsa.org.my) |
| 09:16.18 | *** join/#htc-linux timebomb (n=tb@p5B3E7B0E.dip.t-dialin.net) |
| 10:00.25 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 10:00.43 | *** join/#htc-linux marked (n=marklive@host86-140-53-74.range86-140.btcentralplus.com) |
| 10:19.16 | *** join/#htc-linux rl2000 (n=rl2000@0x573b88ac.hhnqu1.dynamic.dsl.tele.dk) |
| 10:33.29 | *** join/#htc-linux timebomb (n=tb@p5B3E7B0E.dip.t-dialin.net) |
| 10:58.59 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 11:48.21 | *** join/#htc-linux scatterp (n=acka@82-35-152-46.cable.ubr05.enfi.blueyonder.co.uk) |
| 11:55.37 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 12:08.47 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 12:09.34 | *** join/#htc-linux exco (n=exco@e181065103.adsl.alicedsl.de) |
| 12:09.37 | *** part/#htc-linux exco (n=exco@e181065103.adsl.alicedsl.de) |
| 12:09.39 | *** join/#htc-linux exco (n=exco@e181065103.adsl.alicedsl.de) |
| 12:13.45 | exco | dzo: vogue-hw.c -> backlight -> machine_is_htckaiser -> is_msm7200 |
| 12:23.14 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 12:27.28 | *** join/#htc-linux scaterp (i=acka@82-35-152-46.cable.ubr05.enfi.blueyonder.co.uk) |
| 12:32.11 | *** join/#htc-linux xutywx (n=pawel@195.205.38.95) |
| 12:44.56 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 13:01.30 | *** join/#htc-linux _defcon (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 13:12.36 | xutywx | hi! do you have any new ideas about ts in g900? yestarday's work wasnt bad ;P it isnt working but screen is shaking when i touch the screen |
| 13:17.31 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
| 13:46.24 | *** part/#htc-linux Abracadabra (n=aaabraca@unaffiliated/abracadabra) |
| 13:48.01 | tmzt | 18:58 < cr2_> ptr,0x220800,...,8,7 |
| 13:48.01 | tmzt | 18:58 < cr2_> 0x48 should be the i2c id |
| 13:48.01 | tmzt | 18:58 < cr2_> or 0x48>>1 |
| 13:48.01 | tmzt | 18:58 < cr2_> which touchscreen is that ? |
| 13:48.03 | tmzt | 18:59 < cr2_> i think it'd be easy to mmutrace the 1688 i2c data reg, and touch the screen. |
| 13:48.27 | tmzt | xutywx: what did you do yesterday to make it shake? |
| 13:48.51 | xutywx | when im touching the screen it shakes but pointer doesnt move |
| 13:49.09 | tmzt | yes, what did you change yesterday to make it do that? |
| 13:49.32 | xutywx | compiled and booted |
| 13:49.49 | xutywx | http://opensource.wolfsonmicro.com/node/7 look here 0 here are drivers for more ts |
| 13:49.51 | tmzt | I guess we are supposed to trace the i2c data, I don't know how that will tell us if it's tscXXXX or something else |
| 13:50.04 | xutywx | in my kernel are only for 9713 |
| 13:50.06 | tmzt | but it doesn't appear to be the wm97xx since that doesn't use i2c |
| 13:50.36 | tmzt | that might be used for the audio though |
| 13:52.54 | xutywx | so what should i do now? |
| 13:57.23 | *** join/#htc-linux rewpparo (n=rewpparo@lns-bzn-45-82-65-149-197.adsl.proxad.net) |
| 13:59.58 | tmzt | #define IDBR (0x08) |
| 14:00.36 | tmzt | <PROTECTED> |
| 14:00.39 | tmzt | that's what he means |
| 14:01.19 | tmzt | can you start haret? |
| 14:02.16 | xutywx | yes |
| 14:03.04 | xutywx | ok |
| 14:03.09 | xutywx | what next? |
| 14:03.23 | xutywx | but moment - haret console will be needed? |
| 14:03.29 | tmzt | add mmutrace 0x40301680 0x4 |
| 14:03.39 | tmzt | no, telnet will work |
| 14:03.49 | tmzt | although haretconsole will make it easier to save logs |
| 14:04.03 | tmzt | and we will need logs, so use haretconsole if you can |
| 14:04.25 | xutywx | im after format so where i can find it |
| 14:04.35 | tmzt | what? |
| 14:04.47 | tmzt | handhelds.org/~koconnor/haret/ |
| 14:04.50 | xutywx | thx |
| 14:05.48 | xutywx | wait a mopment im going to update haret on pda |
| 14:06.51 | tmzt | add mmutrace 0x40301688 0x4 |
| 14:07.36 | tmzt | #define IRQ_I2C PXA_IRQ(18) /* I2C Service Request */ |
| 14:08.02 | tmzt | #define IRQ_GPIO0 PXA_IRQ(8) /* GPIO0 Edge Detect */ |
| 14:08.02 | tmzt | #define IRQ_GPIO1 PXA_IRQ(9) /* GPIO1 Edge Detect */ |
| 14:08.03 | tmzt | #define IRQ_GPIO_2_x PXA_IRQ(10) /* GPIO[2-x] Edge Detect */ |
| 14:08.29 | tmzt | addlist irqs 18 |
| 14:08.33 | tmzt | wirq 3 |
| 14:08.36 | tmzt | touch the screen |
| 14:10.40 | xutywx | im ready but moment |
| 14:11.00 | xutywx | how to do it? what exactly i should type? |
| 14:11.16 | tmzt | add mmutrace 0x40301688 0x4 |
| 14:11.17 | *** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) |
| 14:11.29 | tmzt | addlist irqs 18 |
| 14:11.32 | tmzt | wirq 3 |
| 14:11.34 | tmzt | touch the screen |
| 14:11.47 | xutywx | Unknown keyword: `add' |
| 14:11.55 | tmzt | addlist |
| 14:12.20 | xutywx | line 2: Address 00000012 is not aligned for 32-bit accesses |
| 14:13.11 | tmzt | add mmutrace 0x40301688 0x2 |
| 14:13.19 | xutywx | HaRET(1)# addlist mmutrace 0x40301688 0x4 |
| 14:13.19 | xutywx | HaRET(2)# addlist irqs 18 |
| 14:13.19 | xutywx | line 2: Address 00000012 is not aligned for 32-bit accesses |
| 14:13.19 | xutywx | HaRET(3)# wirq 3 |
| 14:13.19 | xutywx | irq:80405cd0@A07043F8=80fb90ec abort:8043fc4c@A07043F0=80fb9110 prefetch:80405840@A07043EC=80fb913c data=80f78000 sizes=c:000014e4,t:000454e4 |
| 14:13.21 | xutywx | Beginning memory tracing. |
| 14:13.25 | xutywx | Watching IRQS(00): Addr a9200000(@40d00000) |
| 14:13.27 | xutywx | Watching IRQS(01): Addr a920009c(@40d0009c) |
| 14:13.29 | xutywx | Watching IRQS(02): Addr a9300048(@40e00048) |
| 14:13.31 | tmzt | touch the screen |
| 14:13.31 | xutywx | Watching IRQS(03): Addr a930004c(@40e0004c) |
| 14:13.33 | xutywx | Watching IRQS(04): Addr a9300050(@40e00050) |
| 14:13.34 | tmzt | don't paste all that |
| 14:13.35 | xutywx | Watching IRQS(05): Addr a9300148(@40e00148) |
| 14:13.37 | xutywx | Warning! Tracing non-section mapping (40300000) not well supported |
| 14:13.39 | xutywx | If you really want to do this, run 'set permissivemmutrace 1' and retry |
| 14:13.47 | tmzt | no |
| 14:13.56 | tmzt | add mmutrace p2v(0x40301688) 0x2 |
| 14:13.58 | rewpparo | what device are you guys working on ? |
| 14:14.05 | xutywx | g900 |
| 14:14.05 | tmzt | dump mmu 2 0x40301688 |
| 14:14.49 | rewpparo | :) |
| 14:15.32 | xutywx | http://wklej.org/id/51434/ |
| 14:16.51 | tmzt | add mmutrace 88801688 0x2 |
| 14:16.53 | tmzt | add mmutrace a8801688 0x2 |
| 14:16.55 | tmzt | wirq 5 |
| 14:16.58 | tmzt | touch the screen |
| 14:17.17 | tmzt | restart haret first |
| 14:19.43 | xutywx | line 2: Unknown variable 'a8801688' in expression |
| 14:19.44 | xutywx | line 2: Expected <start> |
| 14:27.31 | xutywx | http://wklej.org/id/51441/ |
| 14:27.32 | xutywx | ? |
| 14:32.43 | tmzt | add mmutrace 0xa8801688 0x2 |
| 14:33.17 | tmzt | did you restart haret? |
| 14:33.20 | xutywx | yes |
| 14:34.08 | tmzt | show mmutrace |
| 14:34.32 | xutywx | 000: 0x054b0198 2 'rw' 00000000 none |
| 14:34.32 | xutywx | 001: 0xa8801688 2 'rw' 00000000 none |
| 14:35.09 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 14:35.10 | tmzt | where are you getting 054... from? |
| 14:35.14 | tmzt | restart haret |
| 14:35.18 | tmzt | add mmutrace 0xa8801688 0x2 |
| 14:35.21 | tmzt | add mmutrace 0x88801688 0x2 |
| 14:35.26 | tmzt | wirq 5 |
| 14:37.16 | xutywx | nearly all http://wklej.org/id/51446/ |
| 14:39.03 | tmzt | ibit irqs 11 |
| 14:39.05 | tmzt | ibit irqs 26 |
| 14:39.22 | tmzt | try again, don't touch anything this time |
| 14:39.31 | tmzt | wirq 5 |
| 14:39.35 | tmzt | don't restart haret |
| 14:40.11 | xutywx | http://wklej.org/id/51447/ |
| 14:51.03 | *** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-1e18e3ddb65c90fb) |
| 14:55.48 | xutywx | so - what does it mean? |
| 14:59.35 | tmzt | try again, this time press the screen |
| 14:59.39 | tmzt | also, use wirq 10 |
| 15:00.27 | xutywx | http://wklej.org/id/51456/ |
| 15:00.34 | xutywx | pressed, break, pressed, end |
| 15:02.43 | tmzt | we're not getting any data on the I2C register though |
| 15:02.50 | tmzt | just I2C interrupts |
| 15:03.17 | xutywx | 98 line? |
| 15:03.21 | xutywx | what's that? |
| 15:05.14 | tmzt | direction register |
| 15:05.21 | xutywx | oh i see |
| 15:05.34 | xutywx | so... what should i do? |
| 15:08.33 | tmzt | not exactly sure |
| 15:08.41 | tmzt | maejrep: how do you do mmutrace? |
| 15:13.19 | *** join/#htc-linux TL|Jermu (n=no@a91-156-151-141.elisa-laajakaista.fi) |
| 15:37.20 | xutywx | sth new? |
| 15:38.48 | *** join/#htc-linux rewpparo (n=rewpparo@lns-bzn-38-82-253-109-3.adsl.proxad.net) |
| 15:39.23 | *** join/#htc-linux metter (n=metter@254-134.62-81.cust.bluewin.ch) |
| 15:40.39 | *** join/#htc-linux rewpparo (n=rewpparo@lns-bzn-38-82-253-109-3.adsl.proxad.net) |
| 15:45.55 | *** join/#htc-linux MethoS (n=lem@host-091-097-243-250.ewe-ip-backbone.de) |
| 15:50.49 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-163-089.ewe-ip-backbone.de) |
| 15:56.52 | *** join/#htc-linux MethoS-- (n=lem@host-091-097-244-111.ewe-ip-backbone.de) |
| 16:00.07 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
| 16:01.11 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 16:08.46 | *** join/#htc-linux MethoS (n=lem@host-091-097-243-102.ewe-ip-backbone.de) |
| 16:08.48 | *** part/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 16:09.25 | xutywx | http://wklej.org/id/51482/ |
| 16:09.35 | xutywx | this is when i touch the screen |
| 16:10.13 | xutywx | those are i2 lines ;) |
| 16:10.19 | xutywx | 117 and 118 |
| 16:10.44 | xutywx | 76 00001000 I 1 0 FE TS irq |
| 16:11.27 | xutywx | but i dont know how to read this |
| 16:11.36 | xutywx | one is probably clock |
| 16:11.39 | xutywx | but the second? |
| 16:16.01 | xutywx | does anybody know how to read i2c in pxa270 ;) |
| 16:16.43 | xutywx | http://www.eggheadcafe.com/software/aspnet/32259112/pxa270-i2c-register-mappi.aspx |
| 16:16.45 | xutywx | some help |
| 16:18.42 | *** join/#htc-linux ykut_johny (n=ykut_joh@www.mitsa.org.my) |
| 16:22.04 | tmzt | xutywx: can you look through Drivers/BuiltIn in your registry and see if what touchscreen driver it uses? |
| 16:22.15 | xutywx | yes moment |
| 16:22.58 | xutywx | how it will be named? |
| 16:23.52 | tmzt | sorry, that won't work, ce doesn't really use the device names |
| 16:25.06 | xutywx | i can send you touch.dll |
| 16:25.16 | xutywx | only that information is in registry |
| 16:25.27 | tmzt | run strings on it |
| 16:25.38 | tmzt | but you will have to extract it from the imgfs |
| 16:28.14 | xutywx | i know ;) |
| 16:28.26 | xutywx | wait a moment - globalbus have extracted ingfs |
| 16:28.29 | xutywx | *imgfs |
| 16:30.59 | *** join/#htc-linux balsat (n=balsat@87.72.13.87) |
| 16:40.34 | xutywx | nothing special ;/ |
| 16:41.51 | xutywx | no information about model or sth... how can i read it more confortably than in mc editor? ;) |
| 16:43.41 | tmzt | what? |
| 16:43.44 | tmzt | mc editor? |
| 16:43.57 | tmzt | strings touch.dll |
| 16:44.06 | tmzt | look for TSC or WM or similiar |
| 16:45.24 | xutywx | http://wklej.org/id/51498/ |
| 16:51.24 | tmzt | strings -e l |
| 16:51.44 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
| 16:52.20 | xutywx | http://wklej.org/id/51503/ |
| 16:54.45 | tmzt | check the registry, Drivers\BuiltIn\Touch and HARDWARE\DEVICEMAP\TOUCH |
| 16:55.25 | xutywx | i havent got dirversbuiltin\touch |
| 16:56.09 | tmzt | look at Drivers\Active |
| 16:56.34 | xutywx | second: drivername: touch.dll, maxcalerror: 50, systemps: on, calibration data is too long ;P |
| 16:56.47 | tmzt | where? |
| 16:57.20 | xutywx | HARDWARE\DEVICEMAP\TOUCH |
| 16:58.06 | xutywx | in active it doesnt exists |
| 16:59.08 | xutywx | drivers/display/active/builtinlcd/tap mode =1 |
| 16:59.16 | xutywx | dll- ddi.ddl |
| 16:59.19 | xutywx | *dll |
| 16:59.51 | tmzt | what else is in builtinlcd? |
| 17:00.09 | xutywx | buffermode=1 |
| 17:00.15 | xutywx | nothing more |
| 17:01.34 | xutywx | that's probably all |
| 17:03.31 | tmzt | this shouldn't be drivers/display though |
| 17:04.38 | xutywx | so? |
| 17:05.26 | *** join/#htc-linux MethoS- (n=lem@host-091-097-243-135.ewe-ip-backbone.de) |
| 17:05.43 | tmzt | we know it's on I2C1, which I guess is the built-in I2C port in pxa |
| 17:05.59 | tmzt | but we don't know what type of touchscreen controller it is |
| 17:06.21 | xutywx | yeah... |
| 17:08.05 | tmzt | is this the toshiba g900? |
| 17:08.14 | xutywx | yes |
| 17:10.41 | *** part/#htc-linux Dunedan (n=dunedan@phoenitydawn.de) |
| 17:10.46 | *** join/#htc-linux Dunedan (n=dunedan@phoenitydawn.de) |
| 17:14.54 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-117-208.web.vodafone.de) |
| 17:15.36 | tmzt | cr2: how do we find out what touchscreen controller is in g900, or trace i2c, mmutrace returned a number of interrupts but no writes/reads to data register |
| 17:16.01 | cr2 | on 1688 ? |
| 17:16.21 | cr2 | you may try the pxa hw tracer |
| 17:16.29 | cr2 | set trace ... |
| 17:16.44 | cr2 | i think it was 1688 |
| 17:17.13 | cr2 | set trace p2v(0x40301688) 4 |
| 17:17.18 | cr2 | wi 10 |
| 17:18.14 | tmzt | yeah |
| 17:18.44 | cr2 | tmzt: i think only by opening the device. or by tracing the i2c, and comparing to the known i2c touchscreen chips |
| 17:18.48 | cr2 | which id has tsc2003 ? |
| 17:18.56 | tmzt | should we maybe try tsc2003/2007? |
| 17:19.05 | cr2 | check the id first |
| 17:19.19 | xutywx | how to hide some irqs? |
| 17:19.21 | cr2 | or use the i2ctool |
| 17:19.26 | cr2 | ibit irqs |
| 17:19.35 | xutywx | thx |
| 17:19.40 | cr2 | but i'd try 'set trace' first |
| 17:19.55 | tmzt | we can do that, we need to setup telnet over usbnet |
| 17:20.23 | xutywx | http://wklej.org/id/51515/ |
| 17:20.48 | xutywx | when touching the screen |
| 17:21.26 | cr2 | with 'set trace' ? |
| 17:21.34 | xutywx | no |
| 17:21.36 | cr2 | and 'clear mmutrace' |
| 17:21.45 | xutywx | after haret reset |
| 17:21.52 | cr2 | ok |
| 17:22.03 | xutywx | so? |
| 17:22.21 | cr2 | since you have the irqs, you should see the data |
| 17:22.26 | xutywx | sorry with set trace |
| 17:22.53 | cr2 | 1680 bus monitor ? |
| 17:23.00 | xutywx | haret |
| 17:23.01 | cr2 | try 1680 too |
| 17:23.12 | xutywx | what's that? |
| 17:23.17 | tmzt | 0x48? |
| 17:23.20 | cr2 | the register |
| 17:23.29 | cr2 | 0x40301680 |
| 17:23.33 | tmzt | yes |
| 17:23.40 | xutywx | oh i see ;) |
| 17:23.40 | tmzt | http://www.nabble.com/tsc2003-userspace-driver-td18834088.html |
| 17:23.46 | *** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl) |
| 17:23.53 | cr2 | it's some time ago that i've traced i2c on pxa ;) |
| 17:24.43 | xutywx | http://wklej.org/id/51518/ |
| 17:24.44 | xutywx | now |
| 17:24.48 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 17:24.50 | Untouchab1e | Good evening |
| 17:25.15 | tmzt | cr2: where did you get that dump you pasted earlier? if it's 0x48 it's probably tsc2003, checking to see if it could be tsc2007 |
| 17:25.44 | cr2 | tmzt: why 0x2 in mmutrace ? it's a full reg |
| 17:25.55 | tmzt | it complained when we did 0x4 |
| 17:26.07 | tmzt | but that could be because we had the phys instead of virt |
| 17:26.12 | cr2 | 0x48 is from touch.dll |
| 17:26.25 | cr2 | trace works on virt only |
| 17:26.44 | cr2 | which is not user-friendly, but this is how it is. |
| 17:27.44 | cr2 | pmmutrace extension will be nice. |
| 17:28.09 | cr2 | is there a ts irq line ? |
| 17:28.29 | xutywx | yes |
| 17:28.39 | tmzt | you found one? |
| 17:28.56 | cr2 | tsc2003 is 0x48 ? |
| 17:28.58 | xutywx | http://www.handhelds.org/moin/moin.cgi/ToshibaG900 |
| 17:29.08 | xutywx | 76 00001000 I 1 0 FE TS irq |
| 17:29.22 | xutywx | and my logs also can tell you that it is it ;) |
| 17:29.27 | tmzt | ah, 76 |
| 17:29.55 | tmzt | why can't I find an example tsc2003 platform_data? |
| 17:30.01 | cr2 | ac97 is probably for the sound |
| 17:30.26 | cr2 | htc used only spi ts, and i2c on some recent devices |
| 17:31.00 | cr2 | the chhances are very good that its tsc2003 |
| 17:31.25 | cr2 | g900 has usb host ? |
| 17:31.38 | xutywx | yes |
| 17:32.00 | cr2 | ok |
| 17:32.06 | cr2 | hmm. ssp2 is used too |
| 17:32.32 | tmzt | we need a dump gpio ? |
| 17:32.47 | cr2 | dump pxa27x will be better |
| 17:32.57 | tmzt | the alt functions are there though |
| 17:33.02 | cr2 | yes |
| 17:33.23 | cr2 | but the ssp2 timing is interesting to know. |
| 17:33.35 | cr2 | and it can be mmutraced too |
| 17:33.40 | *** join/#htc-linux MethoS-- (n=lem@host-091-097-247-069.ewe-ip-backbone.de) |
| 17:34.34 | cr2 | never seen ssp3 used by htc. |
| 17:35.50 | cr2 | techfaith wireless |
| 17:36.24 | cr2 | cdma modem ? |
| 17:36.26 | tmzt | this is toshiba though? |
| 17:36.49 | cr2 | http://www.techfaithwireless.com |
| 17:37.04 | cr2 | yes |
| 17:37.12 | *** join/#htc-linux MethoS (n=lem@host-091-097-247-069.ewe-ip-backbone.de) |
| 17:37.36 | cr2 | xutywx: you have gsm ? |
| 17:37.42 | xutywx | yes |
| 17:37.46 | cr2 | ok |
| 17:38.24 | cr2 | ssp2 and ssp3 need more research. |
| 17:38.59 | cr2 | the ts is more or less clear |
| 17:40.53 | *** join/#htc-linux zycho (n=zycho@a89-182-208-118.net-htp.de) |
| 17:41.05 | *** join/#htc-linux MethoS (n=lem@host-091-097-247-069.ewe-ip-backbone.de) |
| 17:42.55 | Untouchab1e | Slighty off topic: I have a ADP1 here, and I want to change the keyboard layout.. |
| 17:42.58 | Untouchab1e | any idea on how? |
| 17:44.35 | xutywx | http://git.openmoko.org/git/openmoko.git/packages/linux/linux-2.6.21/tsc2003.c |
| 17:44.44 | xutywx | is it ok? |
| 17:44.48 | xutywx | how to use it ;) |
| 17:44.58 | balsat | The keylayout files are in /system/usr/kaylayout on Android |
| 17:47.27 | tmzt | xutywx: you have to add a struct platform_data and the other struct we added yesterday for wm97xx-ts but change that to tsc2003 and add the .dev = {} to point to the platform_data |
| 17:47.45 | tmzt | I'm trying to find a good example, I think the handhelds.org cvs would have one |
| 17:48.06 | tmzt | also, we need to patch the kernel for tsc2003.c, yes the openmoko should work |
| 17:48.12 | cr2 | Untouchab1e: what about dumping from /dev/mem instead ? :) |
| 17:48.14 | xutywx | ok - i have sth to do so... if you got sth tell what to do ;) |
| 17:48.14 | tmzt | but you need to add it to Makefile and Kconfig also |
| 17:48.43 | cr2 | tmzt: i'll look for ssp* later in the evening |
| 18:00.28 | *** join/#htc-linux balsat (n=balsat@87.72.13.87) |
| 18:02.11 | xutywx | im ready ;) so what should i do? |
| 18:10.44 | xutywx | http://gullfoss2.fcc.gov/prod/oet/forms/blobs/retrieve.cgi?attachment_id=782239&native_or_pdf=pdf |
| 18:10.51 | xutywx | photos of g900 inside |
| 18:11.39 | tmzt | xutywx: look in the gta01/02 file in arch/arm/mach-s3c2440 copy the tsc2003 structs to g900.c |
| 18:14.12 | xutywx | but... i dont have that file |
| 18:14.36 | xutywx | what sources shuld i use? |
| 18:14.39 | tmzt | no, on the openmoko page where you got tsc2003.c |
| 18:14.48 | xutywx | ok |
| 18:18.14 | xutywx | i cant find it - could you post a link? |
| 18:18.36 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d874cdd.pool.einsundeins.de) |
| 18:18.56 | tmzt | http://git.openmoko.org/git/openmoko.git/packages/linux/linux-2.6.21/tsc2003.c |
| 18:18.59 | tmzt | what is that? |
| 18:19.15 | xutywx | link that i ve posted ;) |
| 18:19.30 | xutywx | but what exactly i dont know ;) google said that ;P |
| 18:20.00 | *** join/#htc-linux timebomb (n=tb@p548F9FA5.dip0.t-ipconnect.de) |
| 18:25.58 | *** join/#htc-linux DasFx (n=John@5354790B.cable.casema.nl) |
| 18:26.04 | *** join/#htc-linux ClashTheBunny (i=c72ec6e7@gateway/web/ajax/mibbit.com/x-8714d700b1c3eaf8) |
| 18:28.10 | xutywx | http://www.handhelds.org/moin/moin.cgi/HandheldHardwareXref |
| 18:28.18 | xutywx | ans touchscreen section |
| 18:28.21 | xutywx | last point |
| 18:31.35 | xutywx | ill be back in a moment ;) |
| 18:52.49 | *** join/#htc-linux tao (n=tao@69.63.74.26) |
| 18:53.06 | xutywx | im back |
| 18:53.09 | xutywx | sth new? |
| 18:53.48 | tmzt | no |
| 18:53.57 | tmzt | can't find it |
| 18:54.02 | xutywx | ;/ |
| 18:54.16 | tmzt | wait, it's an i2c chip isn't it |
| 18:54.42 | xutywx | it's built in |
| 18:54.49 | tmzt | i2c_board_info |
| 18:55.36 | *** join/#htc-linux hollo (n=hollo@3e6b025d.rev.stofanet.dk) |
| 18:56.32 | xutywx | ? |
| 19:00.38 | tmzt | alright |
| 19:01.00 | xutywx | yup? |
| 19:01.00 | tmzt | static struct i2c_board_info __initdata g900_i2c_board_info[] = { |
| 19:01.49 | tmzt | <tab> I2C_BOARD_INFO("tsc2003-ts", 0x48), |
| 19:01.50 | xutywx | in g900.c? |
| 19:01.58 | tmzt | <PROTECTED> |
| 19:02.19 | tmzt | <PROTECTED> |
| 19:02.22 | tmzt | }, |
| 19:02.27 | tmzt | yes |
| 19:02.35 | tmzt | }; |
| 19:03.06 | tmzt | then enable TSC2003 in your .config |
| 19:03.17 | tmzt | take out the wm97xx stuff from yesterday |
| 19:04.29 | xutywx | static struct platform_device g900_touchscreen = { |
| 19:04.29 | xutywx | <PROTECTED> |
| 19:04.29 | xutywx | }; |
| 19:04.29 | xutywx | static struct i2c_board_info __initdata g900_i2c_board_info[] = { |
| 19:04.29 | xutywx | <PROTECTED> |
| 19:04.30 | xutywx | <PROTECTED> |
| 19:04.32 | xutywx | <PROTECTED> |
| 19:04.34 | xutywx | }, |
| 19:05.01 | tmzt | get rid of the first one |
| 19:05.13 | tmzt | static struct platform_device ... |
| 19:05.15 | xutywx | ts2003.c to /drivers/i2c/chips |
| 19:05.20 | xutywx | delete? |
| 19:05.20 | tmzt | yes |
| 19:05.29 | tmzt | delete that struct |
| 19:05.31 | xutywx | ok |
| 19:05.43 | tmzt | add to _init |
| 19:06.18 | tmzt | i2c_register_board_info(0, g900_i2c_board_info, ARRAY_SIZE(g900_i2c_board_info)) |
| 19:06.35 | xutywx | to static struct platform_device *g900_devices[] __initdata = {? |
| 19:06.47 | xutywx | no |
| 19:06.51 | tmzt | no, to your init function |
| 19:06.53 | xutywx | static void __init g900_init(void) |
| 19:06.57 | tmzt | yes |
| 19:07.10 | xutywx | what next? |
| 19:07.42 | tmzt | you need to add tsc2003.o to drivers/i2c/chips/Kconfig and Makefile |
| 19:07.59 | tmzt | read those files you should be able to figure it out |
| 19:09.53 | xutywx | config TOUCHSCREEN |
| 19:09.53 | xutywx | <PROTECTED> |
| 19:09.53 | xutywx | <PROTECTED> |
| 19:09.54 | xutywx | <PROTECTED> |
| 19:09.54 | xutywx | <PROTECTED> |
| 19:09.54 | xutywx | <PROTECTED> |
| 19:09.57 | xutywx | kconfig? |
| 19:10.25 | xutywx | config TOUCHSCREEN_TS2003 |
| 19:10.50 | tmzt | yes, ok |
| 19:10.57 | tmzt | then just enable those in .config |
| 19:11.14 | xutywx | obj-$(CONFIG_TOUCHSCREEN_TS2003)+= tsc2003.o |
| 19:11.19 | xutywx | in makefile? |
| 19:11.27 | tmzt | yes |
| 19:11.48 | tmzt | you don't need experimental though, did you write that section or was it already there? |
| 19:12.05 | xutywx | ? |
| 19:12.12 | xutywx | ive added this |
| 19:12.39 | tmzt | then you have to enable experimental in menuconfig to see it |
| 19:13.06 | xutywx | in what section it should be? |
| 19:13.54 | tmzt | the main menu, like the first option |
| 19:14.07 | tmzt | same as hacking |
| 19:14.41 | xutywx | i cant see that |
| 19:15.25 | tmzt | what does the first option in menuconfig main menu say? |
| 19:15.46 | xutywx | first option? general setup |
| 19:15.53 | tmzt | ok, try in there |
| 19:16.28 | xutywx | nothing |
| 19:16.53 | tmzt | the just add CONFIG_EXPERIMENTAL=y to .config and try again |
| 19:17.17 | xutywx | its set |
| 19:17.50 | tmzt | then just enable TSC2003 in drivers->input->touchscreen I think |
| 19:18.16 | xutywx | it isnt here |
| 19:18.44 | tmzt | drivers->i2c->chips then |
| 19:18.45 | xutywx | i2c |
| 19:18.52 | xutywx | its here ;) |
| 19:19.16 | xutywx | errors ;/ |
| 19:19.20 | xutywx | in g900.c |
| 19:20.04 | tmzt | pate |
| 19:20.05 | tmzt | paste |
| 19:20.38 | xutywx | http://wklej.org/id/51578/ |
| 19:21.47 | xutywx | GPIO_NR_G900_TOUCHSCREEN_GPIO |
| 19:21.59 | tmzt | well first, TSPGPIOFROMWIKI is the one from the wiki page, you were supposed to look it up |
| 19:22.19 | tmzt | your not using ac97 right now comment /* */ all of that out |
| 19:22.37 | tmzt | yes |
| 19:22.51 | tmzt | add a #define for GPIO_NR_G900_TOUCHSCREEN_GPIO |
| 19:23.02 | tmzt | replace NR with the number though |
| 19:23.04 | xutywx | it is already |
| 19:23.21 | tmzt | 76 |
| 19:23.25 | xutywx | #include <asm/arch/g900-gpio.h> |
| 19:23.30 | tmzt | ok |
| 19:23.42 | tmzt | just use that then |
| 19:23.47 | xutywx | ok |
| 19:23.49 | xutywx | what next? |
| 19:24.38 | xutywx | probably include sth like i2c? |
| 19:25.06 | tmzt | yes |
| 19:25.16 | tmzt | /linux/i2c.h |
| 19:25.18 | xutywx | but what? |
| 19:25.19 | tmzt | linux/i2c.h |
| 19:29.06 | xutywx | pid.pl/g900.c |
| 19:29.30 | xutywx | http://wklej.org/id/51582/ |
| 19:32.20 | tmzt | I think you need to remove the * from g900_devices |
| 19:32.34 | xutywx | line 94 change , to ; |
| 19:32.46 | xutywx | that makes it ok ;) |
| 19:33.03 | xutywx | but g900_i2c_board... struct and its init is but |
| 19:33.05 | xutywx | *bad |
| 19:33.18 | tmzt | yes |
| 19:33.38 | tmzt | you have to have { { } } |
| 19:34.00 | xutywx | ? |
| 19:34.12 | tmzt | it's an array of structs |
| 19:34.20 | tmzt | look at ac97 |
| 19:34.24 | tmzt | it's the same way |
| 19:35.11 | xutywx | ok |
| 19:35.22 | xutywx | updated on server |
| 19:35.24 | xutywx | compiles |
| 19:35.32 | tmzt | don't comment out ac97, it looks ok |
| 19:35.41 | tmzt | good, try booting |
| 19:35.44 | xutywx | drivers/i2c/chips/tsc2003.c: In function 'tsc2003_driver_register': |
| 19:35.44 | xutywx | drivers/i2c/chips/tsc2003.c:392: error: implicit declaration of function 'LONG' |
| 19:35.44 | xutywx | make[3]: *** [drivers/i2c/chips/tsc2003.o] BÅÄ
d 1 |
| 19:36.26 | tmzt | get the version from git.linuxtogo.org kernel.git summary htc-msm-2.6.25 |
| 19:36.32 | tmzt | it's newer |
| 19:36.44 | xutywx | what version? |
| 19:36.48 | tmzt | wait, don't |
| 19:36.52 | xutywx | tsc2003.c? |
| 19:37.32 | xutywx | <PROTECTED> |
| 19:37.32 | xutywx | <PROTECTED> |
| 19:37.32 | xutywx | <PROTECTED> |
| 19:37.32 | xutywx | <PROTECTED> |
| 19:37.32 | xutywx | <PROTECTED> |
| 19:37.43 | xutywx | only this |
| 19:37.52 | xutywx | no more times this func is used |
| 19:39.02 | tmzt | I think you can change LONG to LONGBIT |
| 19:39.31 | xutywx | there is no func like that |
| 19:40.30 | tmzt | http://focus.ti.com/lit/ml/slyt292/slyt292.pdf |
| 19:40.34 | tmzt | don't read that |
| 19:40.56 | tmzt | PENIRQ, we might need it for msm though |
| 19:41.24 | xutywx | nice article ;) |
| 19:41.37 | tmzt | yeah |
| 19:42.06 | xutywx | but... what to use instead of LONG? |
| 19:42.16 | xutywx | maybe nothing? |
| 19:43.09 | tmzt | you need those |
| 19:43.14 | xutywx | so? |
| 19:44.26 | tmzt | why is msm_ts.c still in the kernel? |
| 19:44.31 | *** join/#htc-linux exco_ (n=exco@e181065103.adsl.alicedsl.de) |
| 19:44.43 | xutywx | ? |
| 19:45.38 | tmzt | not asking you |
| 19:45.52 | xutywx | should i tick off old touchscreen drivers? |
| 19:46.38 | tmzt | no, don't worry about those |
| 19:46.47 | tmzt | well you can |
| 19:46.49 | xutywx | ive ticked off |
| 19:47.01 | *** join/#htc-linux metter (n=metter@254-134.62-81.cust.bluewin.ch) |
| 19:52.09 | xutywx | how can i check if that all includes are ok in that file? |
| 19:52.30 | tmzt | the includes are ok, the problem is that missing macro |
| 19:52.49 | xutywx | oh macro? |
| 19:53.10 | xutywx | maybe it is sth like (long int)? |
| 19:53.28 | tmzt | no, it finds which byte of the long the bit is in |
| 19:53.55 | xutywx | ... ;) |
| 19:54.14 | tmzt | do you have bitops.h included? |
| 19:54.35 | xutywx | in tsc2003.c? |
| 19:54.37 | xutywx | no |
| 19:54.44 | tmzt | add linux/bitops.h |
| 19:55.01 | xutywx | ok try? |
| 19:55.15 | xutywx | same |
| 19:58.34 | tmzt | comment those out |
| 19:58.43 | tmzt | add |
| 19:58.59 | tmzt | input_set_abs_param(input_dev, ABS_X, 0, MAX_12BIT, 0, 0); |
| 19:58.59 | xutywx | those 3 lines? |
| 19:59.06 | tmzt | input_set_abs_param(input_dev, ABS_Y, 0, MAX_12BIT, 0, 0); |
| 19:59.16 | tmzt | input_set_abs_param(input_dev, ABS_PRESSURE, 0, MAX_12BIT, 0, 0); |
| 19:59.17 | tmzt | yes |
| 19:59.20 | *** join/#htc-linux m4D (n=m4D@ppp91-76-194-68.pppoe.mtu-net.ru) |
| 20:00.19 | xutywx | drivers/i2c/chips/tsc2003.c: In function 'tsc2003_driver_register': |
| 20:00.19 | xutywx | drivers/i2c/chips/tsc2003.c:400: error: implicit declaration of function 'input_set_abs_param' |
| 20:00.19 | xutywx | drivers/i2c/chips/tsc2003.c:400: error: 'input_dev' undeclared (first use in this function) |
| 20:00.19 | xutywx | drivers/i2c/chips/tsc2003.c:400: error: (Each undeclared identifier is reported only once |
| 20:00.19 | xutywx | drivers/i2c/chips/tsc2003.c:400: error: for each function it appears in.) |
| 20:00.20 | xutywx | drivers/i2c/chips/tsc2003.c:400: error: 'MAX_12BIT' undeclared (first use in this function) |
| 20:00.20 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-164-114.ewe-ip-backbone.de) |
| 20:00.48 | xutywx | params not param? |
| 20:01.12 | tmzt | #define MAX_12BIT ((1 << 12) - 1) |
| 20:01.15 | tmzt | add that to the top |
| 20:01.38 | tmzt | do you have #include <linux/input.h> ? |
| 20:01.52 | xutywx | not yet ;) |
| 20:02.06 | tmzt | this driver is probably too old |
| 20:02.26 | xutywx | drivers/i2c/chips/tsc2003.c: In function 'tsc2003_driver_register': |
| 20:02.26 | xutywx | drivers/i2c/chips/tsc2003.c:403: error: 'input_dev' undeclared (first use in this function) |
| 20:02.59 | tmzt | paste your driver |
| 20:03.22 | xutywx | pid.pl/tsc2003.c |
| 20:04.09 | tmzt | change input_dev to data->idev |
| 20:04.13 | xutywx | ok |
| 20:04.37 | tmzt | and you don't need the first two I gave you, you already have them |
| 20:04.46 | xutywx | ok |
| 20:04.49 | xutywx | it compiles |
| 20:04.50 | tmzt | ok, it should be ok now |
| 20:05.20 | xutywx | compiles |
| 20:05.22 | xutywx | im trying |
| 20:05.22 | tmzt | dzo: where did you get the first version of tsc2003 you used? |
| 20:08.09 | xutywx | doesnt work ;/ |
| 20:08.42 | tmzt | everything works except the touchscreen? |
| 20:08.49 | tmzt | can you start the angstrom verion? |
| 20:08.50 | xutywx | yes |
| 20:08.56 | xutywx | yes |
| 20:09.01 | xutywx | dmesg shows: |
| 20:09.12 | xutywx | i2c /dev entries driver |
| 20:09.18 | xutywx | : enabling slave mode |
| 20:09.49 | xutywx | i2c: i2c-i : pxa i2c adapter, slave addresss 1 |
| 20:09.54 | xutywx | that's all |
| 20:10.05 | tmzt | ls /sys/class/input/ |
| 20:10.25 | tmzt | sorry, we need to get a usbnet connection working first |
| 20:10.42 | xutywx | why? |
| 20:10.50 | exco_ | I'd also be interested in how to do that on Polaris ;-) |
| 20:11.01 | tmzt | how else are you typing in commands? |
| 20:11.08 | tmzt | exco_: it won't work on polaris yet |
| 20:11.25 | xutywx | i have terminal in angstorm |
| 20:11.27 | xutywx | it boots |
| 20:11.41 | xutywx | i have a keypad so everything is ok ;) |
| 20:11.54 | tmzt | you have a keypad? |
| 20:12.00 | xutywx | event0, input0, mice |
| 20:12.03 | xutywx | yes ;) |
| 20:12.09 | xutywx | qwerty ;P |
| 20:12.11 | tmzt | it's not registering it then |
| 20:12.36 | xutywx | so? |
| 20:13.17 | tmzt | there's no BTN_TOUCH enabled either in that driver |
| 20:13.25 | tmzt | so it won't work |
| 20:13.30 | *** join/#htc-linux MethoS-- (n=lem@host-091-096-212-089.ewe-ip-backbone.de) |
| 20:13.57 | xutywx | so... |
| 20:14.16 | *** join/#htc-linux exco_1 (n=exco@e181088187.adsl.alicedsl.de) |
| 20:14.19 | *** join/#htc-linux cr2 (n=cr2@ip-77-25-99-36.web.vodafone.de) |
| 20:15.15 | xutywx | http://forum.xda-developers.com/archive/index.php/t-382265.html |
| 20:15.27 | tmzt | can you paste the current g900.c to .pl |
| 20:15.42 | exco_1 | tmzt: I know |
| 20:15.49 | xutywx | uploaded |
| 20:16.15 | cr2 | xutywx: do you have usb and usbh working ? |
| 20:16.28 | xutywx | as i remember no |
| 20:16.29 | cr2 | usb=udc |
| 20:16.52 | cr2 | do you have wifi ? |
| 20:16.59 | xutywx | yes |
| 20:17.07 | xutywx | but not working |
| 20:17.12 | cr2 | can you connect to haret over wifi ? |
| 20:17.17 | xutywx | only sd, keypad, lcd are working |
| 20:17.21 | xutywx | yes |
| 20:17.28 | xutywx | or by usb |
| 20:17.38 | tmzt | cr2: what's the current tsc2003.c driver? |
| 20:17.45 | xutywx | i thought tah you was talking about linux ;P |
| 20:18.02 | xutywx | pid.pl/tsc2003.c |
| 20:18.04 | xutywx | ;) |
| 20:18.48 | cr2 | tmzt: vogue has one |
| 20:18.52 | xutywx | http://git.openmoko.org/git/openmoko.git/packages/linux/gumstix-kernel-2.6.21/tsc2003.c |
| 20:18.56 | tmzt | daemonize? is this even used anymore? |
| 20:18.57 | xutywx | what about this? |
| 20:19.03 | cr2 | vogue/kaiser |
| 20:19.15 | tmzt | cr2: I know, but it's modified |
| 20:19.15 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B035179.dip.t-dialin.net) |
| 20:19.15 | cr2 | ok |
| 20:19.42 | tmzt | xutywx: the "tsc2003-ts" should have been "tsc2003" in i2c_board_info |
| 20:20.15 | xutywx | type too? |
| 20:20.26 | tmzt | yes |
| 20:20.32 | tmzt | I don't know if .type is used though |
| 20:20.57 | xutywx | compiled testing |
| 20:23.03 | xutywx | what angstrom rootfs should have enlightment? |
| 20:23.21 | tmzt | only openmoko shr that I know of |
| 20:23.40 | xutywx | is it ok on mobile? |
| 20:24.28 | tmzt | it's meant for mobile |
| 20:24.39 | tmzt | illume |
| 20:25.08 | xutywx | nothing new - the same ;/ |
| 20:25.26 | tmzt | huh? |
| 20:25.38 | tmzt | the driver might just be too old |
| 20:25.42 | xutywx | nothing new in sys class input |
| 20:25.48 | xutywx | http://git.openmoko.org/git/openmoko.git/packages/linux/gumstix-kernel-2.6.21/tsc2003.c |
| 20:25.53 | xutywx | maybe this? |
| 20:26.02 | tmzt | look at the version, 2.6.21 |
| 20:26.27 | cr2 | tmzt: what' s wrong with the kais driver ? |
| 20:26.43 | tmzt | it has the scaling in it for android doesn't it? |
| 20:26.43 | xutywx | i have 2.6.25 |
| 20:27.00 | tmzt | yes, but you linked to a 2.6.21 version of that driver |
| 20:27.35 | xutywx | ohh i havent noticed |
| 20:28.01 | cr2 | tmzt: the affine transformation does not matter for ts |
| 20:28.02 | tmzt | let's try the kaiser driver then, you are using android anyway |
| 20:28.14 | xutywx | where it is? |
| 20:28.22 | tmzt | copy that file somewhere |
| 20:28.52 | tmzt | git.linuxtogo.org kernel.git summary htc-vogue-2.6.25 |
| 20:29.41 | xutywx | could you post a hyperlink? im a bit tired after whole day... ;) |
| 20:31.30 | xutywx | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=tree;f=drivers/input/touchscreen;h=68dc14fcceecc54a0c8892b3189b63cf94ab6bc2;hb=b7279469d66b55119784b8b9529c99c1955fe747 |
| 20:31.36 | xutywx | sth from there? |
| 20:31.50 | tmzt | it's not in there |
| 20:32.06 | tmzt | either in arch/arm/mach-msm |
| 20:34.10 | tmzt | s/ei/nei/ |
| 20:34.26 | tmzt | vogue-ts |
| 20:34.30 | tmzt | but not tsc2003.c |
| 20:35.00 | m4D | hi. does anyone knows if alsa-lib links with uclibc and works fine w/o segfaults or artifacts? |
| 20:35.06 | tmzt | set_bit(EV_ABS, data->idev->evbit); |
| 20:35.11 | tmzt | that's what we were missing |
| 20:35.40 | xutywx | about 398 line? |
| 20:35.56 | tmzt | ah, tsc2003.c is in arch/arm/mach-msm also |
| 20:36.31 | xutywx | in my kernel not |
| 20:36.38 | tmzt | yeah, at that link |
| 20:37.21 | xutywx | is it diffrent/ better or sth? |
| 20:40.50 | xutywx | nothing new |
| 20:43.43 | *** join/#htc-linux MethoS (n=lem@host-091-096-214-022.ewe-ip-backbone.de) |
| 20:44.14 | *** join/#htc-linux ClashTheBunny (i=c72ec6e6@gateway/web/ajax/mibbit.com/x-9f145ee42b0434fc) |
| 20:48.41 | cr2 | NetRipper: the 0x17200000 is special |
| 20:56.42 | xutywx | sb told me that he has sources for g900 touch drivers... |
| 20:56.52 | xutywx | and ac97 is a controller ^^ |
| 20:57.55 | *** join/#htc-linux balsat (n=balsat@87.72.13.87) |
| 21:00.03 | xutywx | Philips UCB1400 Touchscreen/ADC/power management palmtc, intelmainstone2 [WWW]html |
| 21:00.10 | xutywx | it would be this... |
| 21:00.17 | xutywx | but im too tired for today |
| 21:00.24 | xutywx | thx and bye ;) |
| 21:00.52 | *** join/#htc-linux ClashTheBunny (i=c72ec6e8@gateway/web/ajax/mibbit.com/x-ef5bd76a0760b26f) |
| 21:01.20 | *** join/#htc-linux opennandra (n=opennand@afrodita.advanet.sk) |
| 21:01.43 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 21:02.54 | *** join/#htc-linux Timbo_ (n=Timbo@cpe-67-9-132-146.austin.res.rr.com) |
| 21:11.30 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfeb2e.pool.einsundeins.de) |
| 21:14.34 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 21:15.52 | *** join/#htc-linux cmonexaway (n=xy6091@i8p6w63khs.adsl.datanet.hu) |
| 21:20.10 | *** join/#htc-linux cmonexaway (n=xy6091@i8p6w63khs.adsl.datanet.hu) |
| 21:23.09 | cr2 | hm. smi and ebi seem to be mixed ;) |
| 21:23.41 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
| 21:25.08 | cr2 | 172 + 0xe |
| 21:27.47 | *** join/#htc-linux Pure4Real (n=pure4rea@89-97-140-219.ip17.fastwebnet.it) |
| 21:33.45 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-160-122.ewe-ip-backbone.de) |
| 21:34.50 | *** join/#htc-linux Xime (n=xime@bankize.net) |
| 21:40.35 | *** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl) |
| 21:45.34 | *** join/#htc-linux rewpparo (n=rewpparo@lns-bzn-38-82-253-109-3.adsl.proxad.net) |
| 21:50.10 | *** join/#htc-linux MethoS-- (n=lem@dyndsl-085-016-160-115.ewe-ip-backbone.de) |
| 21:54.57 | *** join/#htc-linux p3t3r__ (n=peter@gate1.net-you.de) |
| 21:56.19 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 21:57.42 | *** join/#htc-linux Tinyboom (n=nahh@112.80-202-155.nextgentel.com) |
| 21:59.23 | *** part/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl) |
| 22:02.14 | *** join/#htc-linux exco (n=exco@e181088187.adsl.alicedsl.de) |
| 22:02.35 | radem205 | hey |
| 22:02.37 | radem205 | exco |
| 22:02.58 | radem205 | do you think it is difficult to let the charger work? |
| 22:03.59 | exco | radem205: I don't think it's a huge deal, but I lack the skills |
| 22:04.24 | Timbo_ | question: when linux is ran to start andriod, is winmo closed? or is it running in the background? |
| 22:04.27 | radem205 | ok, it isn't a gpio issue right? |
| 22:04.35 | radem205 | winmo is disabled |
| 22:04.46 | Timbo_ | k |
| 22:05.33 | exco | radem205: don't think so - either we just have to put the kaiser stuff in polaris files and call it - or slightly modify it (irq?) |
| 22:05.38 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
| 22:14.25 | *** join/#htc-linux Tinyboom (n=nahh@112.80-202-155.nextgentel.com) |
| 22:16.24 | *** join/#htc-linux Temujin2887 (n=nathanh@rrcs-71-40-222-116.sw.biz.rr.com) |
| 22:19.01 | *** join/#htc-linux nathanh (n=nathanh@rrcs-71-40-222-116.sw.biz.rr.com) |
| 22:19.08 | *** join/#htc-linux Marajin (n=marajin@87-194-102-189.bethere.co.uk) |
| 22:26.18 | *** join/#htc-linux p3t3r__1 (n=peter@gate1.net-you.de) |
| 22:27.31 | *** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 22:34.51 | *** join/#htc-linux Tinyboom (n=nahh@112.80-202-155.nextgentel.com) |
| 22:34.57 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) |
| 22:45.26 | exco | does battery status in Android already show the correct values for Kaiser? |
| 22:51.17 | Pure4Real | yep, more or less |
| 22:51.51 | Pure4Real | differs maybe a few percent between android and winmo |
| 22:52.39 | NetRipper | cr2, committed the memory map and ether as usb0 stuff to git |
| 22:53.14 | cr2 | hi NetRipper |
| 22:53.15 | exco | Pure4Real: regardless of the performance of your battery? (1100, 1350, ... mAh) |
| 22:53.20 | NetRipper | hi cr2 |
| 22:53.37 | Pure4Real | exco: that i dont know |
| 22:53.49 | cr2 | NetRipper: i've looked at oemsbl |
| 22:53.50 | NetRipper | cr2, did you check out the mpu setup in oemsbl yet? |
| 22:53.57 | NetRipper | nice |
| 22:53.57 | NetRipper | :) |
| 22:54.17 | cr2 | yes, it does some obvious and some nonobvious things |
| 22:54.34 | cr2 | the smd layout is setup by oemsbl |
| 22:55.34 | cr2 | the gpio usage is very strange |
| 22:57.17 | NetRipper | cr2, did you find other locked memory places? |
| 22:57.25 | NetRipper | and, define strange ;) |
| 22:58.22 | cr2 | the 0x17200000+ is hijacked by oemsbl too |
| 22:58.47 | cr2 | together with smi, mDSP and aDSP ram |
| 22:59.01 | marex | cr2, hi, long time no .... :) |
| 22:59.14 | cr2 | so it's something very lowlevel |
| 22:59.28 | marex | cr2, http://hackndev.com/ check the last two articles ;-) |
| 23:01.04 | cr2 | marex: i'm a gpl guy |
| 23:02.03 | marex | cr2, I'm a bi ... GPL and BSD |
| 23:02.06 | NetRipper | cr2, does that mean we have to change memory map again? |
| 23:02.51 | cr2 | NetRipper: i'll check your patches |
| 23:05.29 | NetRipper | winmo 6.5 looks funny |
| 23:12.07 | cr2 | -#define VMALLOC_END (PAGE_OFFSET + 0x10000000) |
| 23:12.09 | cr2 | +#define VMALLOC_END (PAGE_OFFSET + 0x20000000) |
| 23:12.23 | cr2 | so it's the g1 setting |
| 23:12.28 | NetRipper | is it? |
| 23:12.36 | NetRipper | i think g1 just has 0x1 |
| 23:12.41 | NetRipper | it's a global file |
| 23:12.50 | cr2 | i mean not something generic |
| 23:13.57 | *** join/#htc-linux p3t3r__ (n=peter@wlan.net-you.de) |
| 23:14.25 | cr2 | we should always keep in mind the patches that we can immediately submit to the mainline |
| 23:16.52 | cr2 | NetRipper: the patches look good |
| 23:17.37 | cr2 | phy_reset_gpio is missing |
| 23:18.36 | cr2 | NetRipper: do we know the raph100 cam i2cids ? |
| 23:19.31 | cr2 | static void __init halibut_init(void) |
| 23:20.00 | cr2 | static void __init halibut_map_io(void) |
| 23:20.20 | NetRipper | i take it you're referring to "halibut"? |
| 23:20.30 | cr2 | yes. confusng |
| 23:20.42 | cr2 | <PROTECTED> |
| 23:20.48 | cr2 | maybe a Kconfig option ? |
| 23:21.00 | NetRipper | yes, that's a possibility |
| 23:21.08 | NetRipper | i'd rather have a runtime check though |
| 23:21.17 | cr2 | ok |
| 23:21.33 | NetRipper | like, writing to 0x2*, and check whether we get an exception from the cpu or not |
| 23:21.36 | cr2 | we may also consider naming the msm gpios in board-*.h |
| 23:21.37 | NetRipper | ;) |
| 23:22.15 | cr2 | s/halibut/htcraphael/ |
| 23:23.25 | NetRipper | the gpios are different per device... i.e. raph, diam, cdma, gsm |
| 23:24.55 | *** join/#htc-linux baard (i=baard@starsky.rehn.no) |
| 23:28.41 | NetRipper | im off to bed |
| 23:28.48 | NetRipper | good night |
| 23:29.15 | cr2 | good night |
| 23:41.23 | *** join/#htc-linux p3t3r__ (n=peter@wlan.net-you.de) |