IRC log for #htc-linux on 20090127

00:08.08maejrep[w]has anyone been able to connect via rndis with mac os x?
00:12.27*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
00:12.54*** join/#htc-linux chavonbravo (n=cb@fl-71-1-235-8.dhcp.embarqhsd.net)
00:14.12*** part/#htc-linux Zoolooc (n=lucian@nrbg-4dbfd70b.pool.einsundeins.de)
00:23.21*** join/#htc-linux bs2 (n=kra@87.72.13.87)
00:29.22*** join/#htc-linux lama (i=lama@netbsd.pl)
00:35.50*** join/#htc-linux ionstorm (n=ion@ip68-228-225-113.ph.ph.cox.net)
00:43.06*** part/#htc-linux exco (n=exco@e181088044.adsl.alicedsl.de)
00:58.01*** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda)
01:05.06dream_killanyone awake still?
01:06.46dream_killwhat gpio's missing in diamond?
01:22.59*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
01:47.35*** join/#htc-linux zycho (n=zycho@a89-182-202-65.net-htp.de)
03:19.09*** join/#htc-linux ALoGeNo (n=alogeno@unaffiliated/alogeno)
03:19.22ALoGeNohello all
03:27.59*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
03:30.15*** join/#htc-linux chavonbravo (n=cb@fl-71-1-235-8.dhcp.embarqhsd.net)
05:23.55*** join/#htc-linux apt (i=ibot@rikers.org)
05:23.55*** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup.
05:24.45*** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl)
05:25.13*** join/#htc-linux Funklord (n=cow@213.114.213.236)
05:25.50*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net)
05:26.12*** join/#htc-linux Marajin (n=marajin@87-194-102-189.bethere.co.uk)
05:27.08*** join/#htc-linux woodyPL_ (i=woody@gateway/shell/blinkenshell.org/x-a22f775afd68fe61)
05:29.49*** join/#htc-linux parmaster_ (i=par@69.60.134.179)
05:29.50*** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) [NETSPLIT VICTIM]
05:29.51*** join/#htc-linux cworth` (n=cworth@olra.theworths.org)
05:30.44*** join/#htc-linux mickey|zzZZzz (i=mickey@80.81.242.146)
05:30.44*** join/#htc-linux infernix (n=nix@82.192.92.187) [NETSPLIT VICTIM]
05:30.45*** join/#htc-linux methril|away (n=Methril@213.27.233.98)
05:34.44*** join/#htc-linux cworth` (n=cworth@olra.theworths.org) [NETSPLIT VICTIM]
05:34.44*** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) [NETSPLIT VICTIM]
05:34.44*** join/#htc-linux TeringTuby (n=maarten@195-241-125-243.ip.telfort.nl)
05:34.44*** join/#htc-linux ptl (n=patola@201.82.131.93) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux methril|away (n=Methril@213.27.233.98)
05:34.49*** join/#htc-linux infernix (n=nix@82.192.92.187) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux parmaster_ (i=par@69.60.134.179)
05:34.49*** join/#htc-linux Funklord (n=cow@213.114.213.236) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux defiant (n=add@p0pc0rn.eu) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux ecze (n=ecze@eczema.ecze.com) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) [NETSPLIT VICTIM]
05:34.49*** join/#htc-linux ALoGeNo (n=alogeno@unaffiliated/alogeno)
05:34.52*** join/#htc-linux Descention (n=munsco95@acm.pct.edu) [NETSPLIT VICTIM]
05:34.52*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl) [NETSPLIT VICTIM]
05:34.57*** join/#htc-linux Shinto (n=John@f049008146.adsl.alicedsl.de) [NETSPLIT VICTIM]
05:34.57*** join/#htc-linux maejrep (n=madCoder@smtp-n.myyearbook.com) [NETSPLIT VICTIM]
05:35.01*** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) [NETSPLIT VICTIM]
05:35.02*** join/#htc-linux Sti_0239 (n=Where_is@55.194-65-87.adsl-dyn.isp.belgacom.be) [NETSPLIT VICTIM]
05:35.02*** join/#htc-linux hlbot (n=adm@iclem.net) [NETSPLIT VICTIM]
05:35.02*** join/#htc-linux Dinde (i=kayser@sur-internet.net) [NETSPLIT VICTIM]
05:35.02*** join/#htc-linux XD (i=t3st1fy@ircop.com) [NETSPLIT VICTIM]
05:35.03*** join/#htc-linux BHSPitMonkey (n=stephen@pool-71-244-5-24.dllstx.fios.verizon.net) [NETSPLIT VICTIM]
05:35.18*** join/#htc-linux ChanServ (ChanServ@services.)
05:35.18*** mode/#htc-linux [+o ChanServ] by irc.freenode.net
05:35.19*** join/#htc-linux parmaster_ (i=par@dipole.idlepattern.com) [NETSPLIT VICTIM]
05:35.23*** join/#htc-linux Marajin (n=marajin@87-194-102-189.bethere.co.uk) [NETSPLIT VICTIM]
05:35.23*** join/#htc-linux seand (n=sean@adsl-69-232-201-43.dsl.pltn13.pacbell.net) [NETSPLIT VICTIM]
05:35.23*** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1)
05:35.23*** join/#htc-linux Kevin2 (n=Kevin2@207-237-194-161.c3-0.avec-ubr2.nyr-avec.ny.cable.rcn.com) [NETSPLIT VICTIM]
05:35.23*** join/#htc-linux swetland (n=swetland@nat/google/session)
05:35.23*** join/#htc-linux DJWillis (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
05:35.24*** join/#htc-linux ltxda (n=anon@c-98-201-10-242.hsd1.tx.comcast.net) [NETSPLIT VICTIM]
05:35.24*** join/#htc-linux zycho (n=zycho@a89-182-202-65.net-htp.de) [NETSPLIT VICTIM]
05:35.24*** join/#htc-linux RZK333 (n=rzk@daemonet.ru) [NETSPLIT VICTIM]
05:35.24*** join/#htc-linux Guest6474 (n=nospam@92.56.48.66)
05:35.24*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net) [NETSPLIT VICTIM]
05:35.28*** join/#htc-linux ALoGeNo (n=alogeno@79.150.192.25) [NETSPLIT VICTIM]
05:35.29*** join/#htc-linux ecze (n=ecze@217.145.35.90) [NETSPLIT VICTIM]
05:35.30*** join/#htc-linux defiant (n=add@p0pc0rn.eu) [NETSPLIT VICTIM]
05:35.31*** join/#htc-linux infernix (n=nix@unaffiliated/infernix) [NETSPLIT VICTIM]
05:35.32*** join/#htc-linux methril|away (n=Methril@213.27.233.98)
05:35.32*** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) [NETSPLIT VICTIM]
05:35.33*** join/#htc-linux lupine_85 (n=lupine@89-16-178-98.no-reverse-dns-set.bytemark.co.uk)
05:35.34*** join/#htc-linux Skitzo (n=DCLXVI@eth582.vic.adsl.internode.on.net) [NETSPLIT VICTIM]
05:35.34*** join/#htc-linux Sti_0239 (n=Where_is@55.194-65-87.adsl-dyn.isp.belgacom.be) [NETSPLIT VICTIM]
05:35.36*** join/#htc-linux lama (i=lama@netbsd.pl) [NETSPLIT VICTIM]
05:35.36*** join/#htc-linux NetRippah (n=netrippe@netripper.nl) [NETSPLIT VICTIM]
05:35.36*** join/#htc-linux wasabi (n=wasabi@akita.larvalstage.net) [NETSPLIT VICTIM]
05:35.38*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) [NETSPLIT VICTIM]
05:35.38*** join/#htc-linux madCoder- (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net)
05:35.38*** join/#htc-linux zule (n=zule@shadowmite.com) [NETSPLIT VICTIM]
05:35.39*** join/#htc-linux DracoDan (n=F@pool-71-163-138-224.washdc.east.verizon.net) [NETSPLIT VICTIM]
05:35.41*** join/#htc-linux chavonbravo (n=cb@fl-71-1-235-8.dhcp.embarqhsd.net) [NETSPLIT VICTIM]
05:35.42*** join/#htc-linux Abracadabra (n=aaabraca@62-244-191-249.cust.exponential-e.net) [NETSPLIT VICTIM]
05:36.21*** join/#htc-linux Funklord (n=cow@c-ecd572d5.014-46-73746f28.cust.bredbandsbolaget.se) [NETSPLIT VICTIM]
05:37.59*** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au)
05:38.19*** join/#htc-linux shoragan (n=shoragan@sicherheitsschwankung.de)
05:38.49*** join/#htc-linux [loy] (n=nobody@209.250.241.104) [NETSPLIT VICTIM]
05:39.07*** join/#htc-linux Balsat (n=kll@87.72.13.87)
05:39.10*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net) [NETSPLIT VICTIM]
05:39.54*** join/#htc-linux milfadoodle (n=milfadoo@78-69-144-82-no19.tbcn.telia.com) [NETSPLIT VICTIM]
05:40.23*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
05:40.33*** join/#htc-linux tmzt (n=tmzt@adsl-69-221-148-155.dsl.akrnoh.ameritech.net)
05:42.15*** join/#htc-linux dase (i=dase@p1atin.de) [NETSPLIT VICTIM]
05:42.15*** join/#htc-linux nizox (n=none@eros.ph0k.eu)
05:42.16*** join/#htc-linux thinko (n=jdoe6alp@smaug.rackdragon.com) [NETSPLIT VICTIM]
05:42.46*** join/#htc-linux toi (n=pleemans@d5153128F.access.telenet.be)
05:42.46*** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) [NETSPLIT VICTIM]
05:45.06*** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-227-232.customer.ch.netstream.com) [NETSPLIT VICTIM]
05:45.19*** join/#htc-linux mooky (n=suzannet@berger.projecthugo.co.uk)
05:45.54*** join/#htc-linux _Nono (n=arnaud@rps4056.ovh.net) [NETSPLIT VICTIM]
06:00.46*** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net)
06:05.32*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
06:10.02*** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no)
06:11.48*** join/#htc-linux woodyPL (i=woody@gateway/shell/blinkenshell.org/x-aef2dfd8a39ac4cc)
06:14.45*** join/#htc-linux PSPdemon (n=PSPdemon@c-66-177-151-78.hsd1.fl.comcast.net)
06:15.00*** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca)
06:15.04Venny:O
06:15.15PSPdemon?
06:15.17VennyHello everybody
06:15.28Vennylots of people'z here
06:15.34tmzthello
06:16.05HTCdemon:P
06:16.10Vennylol im gonna be a bastard here. And make my first full sentence about how i need help loool.
06:16.37Vennylol, k so i have a HTC touch pro CDMA.
06:16.49tmztsprint or verizon?
06:16.58tmztor t*
06:16.58VennyTelus ( im from canada)
06:17.08tmztthat's it
06:17.18Vennythats what?
06:17.22tmztwhat does it say under the battery?
06:17.35tmztthe name of the carrier, I saw your ip
06:18.07Vennyum m my ip is registerd with plantinum communications not telus lol
06:18.14tmztthe .ca part
06:18.18Vennyoh
06:18.29HTCdemonlol
06:18.33tmztas far as I know there is only one cdma carrier in canada
06:18.43Vennyum no theres a bunch
06:18.50Vennyas many as the GSM carriers
06:19.02Vennyhtc touch pro t7279
06:19.07tmztanyway, which model is it, raph500 raph800 or other?
06:19.31HTCdemonother :P
06:19.32Vennyraph800
06:19.34HTCdemonaww
06:19.40Vennyi knew it was raph 800
06:19.41tmztalright, what's your question?
06:19.48Vennythats why i downloaded the raph800 android port
06:19.58Vennyand when i go and launch the boot loader from haret
06:20.27VennyIt starts to mount the memory so it can mount the img files. But all mounts fail.
06:20.31tmztmaejrep: you here?
06:20.54tmztwhat is the last thing it says?
06:21.12HTCdemonwhat the....
06:21.21HTCdemonmaejrep has a interesting hostmask :P
06:22.32Vennytmzt, cannot find some file
06:22.36Vennyinstall.d or something
06:23.30Vennyhere i reset the boot of android again and tell you exactly if you want
06:23.32tmztcan you give me the message?
06:24.33Vennyinit: cannot find '/system/bin/installd', disable 'installd'
06:24.40Vennybut theres like 10 other lines on top of that
06:24.56VennyBut that is the last thing it says
06:25.16HTCdemonVenny, the other ones are normal
06:25.17tmztI don't know what installd is, I guess it's an android service
06:25.48Vennydemon the cannot mount things are normal?
06:25.58HTCdemonwell the time regarding ones
06:25.58tmztwhat are those lines?
06:26.24Venny<PROTECTED>
06:26.25HTCdemon( tmzt, me and Venny were discussing this in another chan.... and i havent been in this chan in ages xD )
06:26.27Vennythats the first line
06:26.43tmztyeah, ok
06:27.01tmztwhat sdcc_ option are you using, give me the whole CMDLINE from default.txt/startup.txt
06:27.15Venny.. how?
06:27.43Vennyuh oh
06:27.47Vennythe crash begins
06:28.58Vennymaybe not
06:29.53Vennytmzt, how do i do that?
06:30.02*** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1)
06:31.33VennySomeone? anyone?
06:31.49tmztpaste the line from the txt file
06:32.10VennyThe default text file for haret?
06:32.24tmztyes
06:32.42Vennyset cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 msmts_calib=0x6D.0x5D.0x340.0x375 msmvkeyb_toggle=hide"
06:32.42Vennyboot
06:33.59tmztchange msmsdcc_id to =3
06:34.01tmzttry it
06:34.47tmztwould you find out if the keyboard works (the hw keyboard) and if it does boot with msmvkeyb_toggle=off
06:34.50tmzt?
06:35.14*** join/#htc-linux maejrep (n=madCoder@smtp-n.myyearbook.com)
06:35.26tmztmaejrep: are you here?
06:35.49maejreponly for a moment ;o
06:35.51*** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com)
06:36.11tmztraph800 sdcc is 3 right?
06:36.16maejrepyes
06:36.37tmztdoes kb work and can you disable vkeyb for android (not X)?
06:36.52maejrepkeyboard does work in latest git, and I don't know about android
06:36.55maejrephaven't tried it
06:37.15maejrepthere's no reason you should need the vkeyb though since the keypad does work
06:37.21Vennyi do belive it does
06:37.33tmztI mean the command line msmvkeyb_toggle=off?? or does that not work?
06:37.40Venny"New build from Maejrep. The qwerty-keyboard is now working, but note that the keyboard mapping is for the raph800, meaning it will be slightly off with the Raph100/110. Maejrep also got the LED (navi-lights) working, however they are not fully implemented yet, so you are limited to a brief demo-flash at boot."
06:37.41tmztto disable it and the update thread
06:37.44maejreppossibly
06:38.18Vennylol oh, the porter is in the irc lol
06:38.26maejrep<--
06:38.28maejrephi thar
06:38.34Venny:) Hello
06:38.55Vennykeep working on it! Android and htc touch pro is a combination made in heaven!
06:38.56tmztdzo's here sometimes too
06:39.02maejrep;p
06:39.13Vennyso toggle hide or off?
06:39.22tmzttry off
06:39.32maejrepoff should work.. i think hide makes it just "minimized" or whatever
06:39.38maejrepwhich doesn't work right on raph800 anyway
06:39.38tmzthide keeps the update thread running which android doesn't need and might slow it down
06:40.17tmztand cupcake supports a real userspace vkeyb so it's not really needed for Diam either but it could still be useful there
06:41.22Vennymaejrep, ever need testing done on a raph800 im like always avalible
06:41.30Vennyw00t! android lives!!!!!!!!!!!!!
06:42.42Vennycrap
06:42.43maejrepVenny: stick around in here and you'll be able to test stuff from many of the other people who are working as hard or harder on writing drivers for our phones :)
06:42.54Vennythe touch is WAY off
06:43.12maejrepyour calibration command line is probably way off then
06:43.36Vennyhow do i calibrate it
06:44.07maejrepremove calib from your cmd line in default.txt, and next time it boots, follow the instructions for calibrating
06:44.52maejrepthen if you want you can take those new (properly) calibrated values and stick them into the cmd line and have an actually calibrated touchscreen instead of copying someone else's calibration :)
06:45.29Vennylol k
06:45.34Vennycolor is still off :(
06:46.15maejrepi don't know if git has the rgb444 hack builtin for raph800
06:46.23maejrepbut from what I understand, android doesn't honor it anyway
06:47.10maejrepthat's not likely to change until we either figure out how to properly initialize the lcd panel to be RGB565, or hack android to use 444 bit packing
06:47.17*** join/#htc-linux lpotter (n=ljp@58.173.176.153)
06:47.21maejrepanyway, gnite
06:47.35Venny>.>
06:47.36Vennynight
06:47.43*** join/#htc-linux bs2 (n=kra@87.72.13.87)
06:50.01*** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net)
06:52.20Vennyargg
06:52.27Vennycant get touch calibrated proper
06:52.58tmztdo you have the vkeyb off?
06:54.16Vennyyeah
06:54.52Vennyi deleted msmts_calib=0x6D.0x5D.0x340.0x375 and it did not work
06:58.01Vennylike big touch screen off calibration
06:58.26tmztdid you get a message about clicking to calibrate?
06:58.39Vennyh/o
07:00.45Vennyfroze durring boot
07:00.59Vennydo i delete everything in that line or just the part after the equals sign?
07:02.28*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
07:02.32Untouchab1eGood morning
07:02.41Vennymorning
07:02.46tmztall of msmts_calib=... not the whole line
07:02.59Untouchab1eany news on the wifi driver?
07:03.10Vennyso just after the = sign tmzt
07:04.28tmztyes
07:04.55tmztUntouchab1e: some but it's not working yet, you can read the logs from 24 or so hours ago if you want to know more
07:05.20Untouchab1ethanks
07:07.19Vennytmzt do you know if theirs any other projects on htc touch pro besides android?
07:07.51Untouchab1eVenny, what kind of projects?
07:07.58Untouchab1elike, Symbian? :P
07:08.16Vennysure?
07:08.28Untouchab1enot that I know of...
07:08.44Untouchab1eI dont think there is widespread interest in any other OS other than WinMo or Android
07:08.54Vennylol
07:09.01Vennywell i more ment linux
07:09.13Untouchab1eso, like openMoko and that lot?
07:09.28Vennyubuntu, debien
07:09.40tmztthe kernel should support about any linux distribution you want, OE/Angstrom, Debian, Ubuntu, Gentoo
07:09.42Untouchab1ei think someone has gotten somewhere with debian
07:10.01tmztfor X you need the vkeyb hide option
07:13.50Vennyhuh?
07:17.22Vennyarg
07:17.28Vennymy phone keeps freezeing on load
07:17.58Untouchab1eyou trying to get Android booting on the Touch Pro?
07:18.50Vennyyeah
07:19.22Untouchab1ewhich build are you using?
07:19.26tmztdo you get small green dots?
07:19.39Venny20090119
07:19.53Untouchab1eok.. describe the error then
07:20.01Vennyit just freezes
07:20.07Untouchab1ewhere?
07:20.08Vennyand i cant seem to calibrate my touch screen
07:20.10Untouchab1eor when
07:20.20Vennynow theirs a blue dot in android
07:20.22Untouchab1eand which touch pro you got? (Raph100/110, 500/800)?
07:20.28Vennyit was nothing Untouchab1e
07:20.33Vennyi have a raph 800
07:21.21Untouchab1ea blue/green dot as in the virtual keyboard marker?
07:21.38Vennyyeah lol
07:21.41Vennyi forgot to turn that off
07:21.50Untouchab1e^^ then you're good
07:22.07Vennycept i cant calibrate my touch screen
07:22.22*** join/#htc-linux kiozen (n=oeichler@p549222DE.dip0.t-ipconnect.de)
07:22.31Untouchab1eyeah, I read about another raph800 having the same problem
07:22.37Untouchab1ethink he figured it out over at xda
07:22.57Vennyhappen to have the link lol?
07:23.24Untouchab1ehttp://forum.xda-developers.com/showthread.php?t=402002&page=189
07:23.27Untouchab1eread a few pages back
07:24.24Vennythanks
07:24.32Untouchab1egood luck :)
07:25.44*** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be)
07:26.21Vennyim just gonna sit back, and observe untill i can get my hands on a raph800 version that the screens colors work poperlyon
07:26.40VennyWell not quite observe
07:27.15VennyIll talk to people in dis chatroom.
07:28.09Vennyhows everyone tonight?
07:28.25Untouchab1ehah, all good here.. class just started
07:29.06Vennyoh really
07:29.13Vennybut its midnight
07:29.34Untouchab1emaybe where you are ^^
07:29.42VennyCanada land for the win!
07:30.05Untouchab1ehah
07:30.49Vennyfriggen streaming video is slow
07:33.29VennyFor the amount of people in here it sure is dead
07:33.42Untouchab1ewell, its not a party channel tbh
07:33.54Vennylol
07:33.56Untouchab1emany are just here to follow the development..
07:34.12Vennywell why cant we do both?
07:34.20Untouchab1efeel free and go ahead :)
07:34.36Vennyturns on the rave music and takes out the drugs
07:35.00Venny:D ppaartttyyy
07:36.08Untouchab1eweewaaa
07:37.23Venny:)
07:37.33VennyI want ubuntu on my phone
07:38.21Vennywelcome back methril
07:38.31methrilthank you
07:38.35methrilG' morning
07:38.39VennyHow was your sleep?
07:38.49methrilwell, i didn't sleep a lot
07:39.03VennyOh well some sleeps better then none i supose.
07:39.30Untouchab1eheh
07:39.30methrilyes :)
07:39.32Untouchab1etell me about it
07:39.54Venny:)
07:40.23VennyWell i will brb
07:40.29Vennyi need to scavange the house for some coke
07:40.37Venny... i ment coca cola lol
07:40.53Vennybrb
07:42.29Vennyback
07:42.35VennyNo cola :( i got milk tho :)
07:44.14Untouchab1eMilk rocks
07:44.17VennySo anyone got something to talk about?
07:45.20Untouchab1eI wish.. heh
07:45.26Untouchab1eIn class atm
07:45.36Vennyah what fun
07:45.56Untouchab1ehah, yeah
07:45.59Untouchab1estatistics..
07:46.04Vennywooohooo
07:46.20*** join/#htc-linux barry (n=chatzill@host81-149-155-58.in-addr.btopenworld.com)
07:46.44Untouchab1eshoulndt you be going to bed soon? :P
07:46.47Vennywelcome ginge
07:47.01VennyShould yes. Will no.
07:47.10*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
07:47.21Vennywelcome rmoravcik
07:47.31gingemorning
07:47.58VennyWell good morning to you
07:48.04Vennyam i the only one here on mountain time?
07:48.35gingeshrugs
07:48.39gingeis GMT
07:48.45Untouchab1eis GMT+1
07:49.10Vennylol
07:49.36*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
07:49.55VennyYou know what sucks. Having paranoia and seeing shit in the middle of the night haha
07:50.00VennyWelcome BabelO
07:50.28gingechecks he isn't in #paranoia again
07:50.46gingeVenny: yeah that sucks
07:50.52Venny:P
07:51.05Vennynah your in the right channel im just trying to start some covo
07:51.09Vennyconvo^
07:51.20gingeVenny: truth is, i'm not really here
07:51.35Venny:O
07:51.57VennyWhere are you then?
07:52.24gingein your miiiiiiiiind
07:52.39Venny:O!!!!!
07:52.50Vennybashes head on wall
07:52.54VennyGET OUT OF MY HEAAADDDD
07:54.41Vennyanyways
07:54.50Untouchab1ehah
07:54.56Untouchab1ehow is canada these days?
07:55.12Untouchab1edont suppose you're a hockey fan? (Only way I can relate to Canada :P)
07:55.38VennyYou racist
07:55.40Vennylol
07:56.16Untouchab1eI guess not then
07:56.18Untouchab1e:P
07:56.28Vennylol somewhat
07:56.34Vennyi care if my team wins
07:56.37Vennybut i dont follow it
07:56.47Untouchab1eyour team being?
07:57.16VennyA team in the top 3 NHL
07:57.30Untouchab1eFlames?
07:57.31Vennyi think there still in top 3
07:57.37Vennylol shh yeah
07:57.40Untouchab1e;)
07:57.46Untouchab1eMy roomie is also a calgary fan
07:57.52VennyGood for him!
07:58.00Untouchab1eso when the Avs and flames meet, we stay up and watch it
07:58.12Untouchab1eor wake up really early.. depends.. :P
07:58.41Vennyhaha
07:59.02Vennysometimes its hard for me to catch the hockey game in my igloo
07:59.29Untouchab1edid you check out the Allstar game yesterday?
07:59.44Vennynope
08:00.12Untouchab1etoo bad.. Iginla got one in I think
08:00.50Vennykool
08:02.39Vennyid kill for a cola right now :(
08:03.06Untouchab1ewould love to help you out
08:03.08Untouchab1eheh
08:03.34Vennywell if your asking to get murdered i can help you out
08:04.26Untouchab1ehah, feel free to give it a go
08:04.57Vennymurderes Untouchab1e
08:05.40Untouchab1eis fortunately in the army, and fends off the weak attack, killing Venny in the process
08:05.45Untouchab1e^^
08:06.00Vennygoes to get some alcohol after the pitiful defeat
08:06.13Untouchab1ethought it was a cola you needed
08:06.28VennyGot none :( so alcohol will have to do
08:06.54Untouchab1ehaha
08:09.03Vennymmm bacardi
08:10.40Untouchab1emmm TĆørst
08:11.00Vennywhat?
08:11.39Untouchab1eflavoured water ^^
08:11.59Vennylol
08:12.11Vennythat stiff is nasty
08:13.24Vennystuff^
08:13.44Vennyeither im a huge lightweight or i need sleep
08:13.58Untouchab1eI would guess the latter
08:14.24Vennylatter?
08:15.27Untouchab1eyou need sleep!
08:16.17Vennywhat are you my mother?
08:16.56Untouchab1eyour mother ain't here, so you better listen to me!
08:16.58Untouchab1e:P
08:17.18VennyThen make me a bedtime snack and read me a story!
08:18.59VennyThis drinks kinda gross
08:19.00Vennylol
08:20.42Vennyalright
08:21.43Vennywhen this episode of house is over
08:21.46Vennyi go sleep
08:22.36*** join/#htc-linux danny123 (n=danny123@193.172.174.100)
08:22.45VennyWelcome danny
08:26.05Vennyokay
08:26.09Vennytill another day
08:26.11Vennygood night
08:27.39*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
08:38.01*** join/#htc-linux metter (n=metter@104-72.1-85.cust.bluewin.ch)
08:57.03lupine_85finds Android is growing on him
08:57.17Untouchab1eAgrees
08:57.37lupine_85applies lamisil
08:57.43lupine_85that'll teach it
08:57.46Untouchab1e:P
08:57.49Untouchab1ehaha
08:58.11lupine_85it *is* nice and smooth...
08:58.24Untouchab1eindeed
08:58.34lupine_85wonder if ATI/AMD will get around to open-sourcing their Imageon stuff
08:58.54Untouchab1ebut I like the Touch Pro more than the G1, so once the port is fully working, il be very happy
08:59.00Untouchab1eyeah!
08:59.09lupine_85mm, G1 is naff
09:00.23lupine_85knows someone who was orgasming over his jailbroken iphone yesterday
09:00.30Untouchab1elol
09:00.31lupine_85the poor little man :D
09:00.33Untouchab1ethe iPhone is boorng
09:00.35Untouchab1ebooring*
09:00.39lupine_85no hardware keyboard
09:00.45Untouchab1eand it makes me angry when they call it a smartphone
09:00.46lupine_85hence fail - at least for me
09:01.18Untouchab1eit is very good at what it does, but there is way too much it doesnt do
09:04.04lupine_85needs to duplicate the text-message-receiving in GPE or OPIE or something
09:04.27lupine_85what I do like about android is that they have a semi-sensible replacement for the X server
09:05.41Untouchab1e:)
09:06.02lupine_85now all it needs is X compatibility libs ;)
09:09.23*** join/#htc-linux Mullins (n=bw@mobileinternet4.o2.ie)
09:16.00lupine_85ho de hum, GPE image is sans phone
09:34.07*** join/#htc-linux timebomb (n=tb@e176098248.adsl.alicedsl.de)
09:51.24*** join/#htc-linux stefan_schmidt (n=stefan@c120.apm.etc.tu-bs.de)
10:01.14*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net)
10:20.59*** join/#htc-linux NeoS20078 (n=neos2007@82-136-223-208.ip.telfort.nl)
10:31.56*** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl)
10:36.55*** join/#htc-linux Mullins (n=bw@mobileinternet4.o2.ie)
11:07.44*** join/#htc-linux Mullins (n=bw@mobileinternet4.o2.ie)
11:16.06NetRippahanyone with some tslib experience about?
11:30.05MullinsAnyknow know hoe to get root in the terminal app, term.apk?
11:32.53DJWillisNetRipper: whats up?
11:56.40*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
12:07.36NetRipperDJWillis, im wondering how tslib works
12:08.04NetRipperDJWillis, tslib is userspace stuff to calibrate the touchscreen..
12:08.22NetRipperit uses an input like /dev/input0 or something... where does it output its data?
12:09.53DJWillisNetRipper: pointercal
12:09.57tmztMullins: #android
12:10.40DJWillisNetRipper: rather /etc/pointercal
12:12.17tmzttslib outputs it's data to whatever calls it, it's a library, it has functions like tslib_read or something
12:13.09DJWillistmzt: true, sorry, I read that as 'where can I stick calibration data' ;-)
12:14.17tmztlupine_85: not likely, it's qualcomm's now/soon it appears
12:17.42lupine_85booo
12:18.50tmzthuh, I just one of those strange ones that doesn't hate msm I guess
12:19.45NetRippertmzt, ah
12:20.04NetRippertmzt, do you know if android is tslib aware? or does it need to compiled with a specific flag for that? or something?
12:20.13NetRipper(note that i have no experience building android yet)
12:20.25tmztit doesn't use it, but you'll have to be more specific
12:20.50tmztactually I'm trying to figure out if it uses any calibration at all
12:22.27NetRippertmzt, but.. the touchscreen driver should return uncalibrated data.. and something in userspace should perform the calibration.. shouldnt it?
12:22.48NetRipperandroid itself doesn't seem to do that.. havent seen a calibration screen yet
12:22.58tmztright, but the g1 has a capacitative screen and doesn't need calibration from what I can see
12:23.03NetRipperah
12:23.13tmztthe emulator is qemu which is also absolute and screen-coordinates
12:23.19NetRipperyes
12:23.27tmztandroid is designed around it's hw/virtual hw it seems
12:23.31NetRipperi didnt know capacitive screens didnt need calibration
12:24.06tmzt<PROTECTED>
12:25.50NetRipperok
12:26.21NetRipperi should ask in #android about tslib i guess
12:26.55tmztI can tell you they don't use tslib and won't support it because of the licencse compatibility I would assume
12:27.02NetRipperoh
12:27.03tmztandroid is apache2 license
12:27.35NetRipperapache2 is a more lenient license than gpl afaik
12:27.44tmztit also seems X will have similar capabilities as tslib in the new evdev driver, still trying to track down when that's coming (not related to android of course)
12:27.59NetRipperok
12:28.06NetRipperbut, is tslib even used by X then?
12:29.41tmztit is now in kdrive at least with patches
12:29.51NetRipperkdive?
12:29.52NetRipperkdrive?
12:29.58tmztXfbdev
12:30.01NetRipperah ok
12:30.15NetRipperbut fb has nothing to do with ts
12:30.19NetRipperso that seems weird
12:30.33tmztno, but the patches are against the kdrive X server
12:30.43tmztthere might be ones for Xorg also
12:30.54NetRipperah, right
12:36.07*** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215)
12:54.59*** join/#htc-linux Mullins (n=bw@mobileinternet4.o2.ie)
13:30.23*** join/#htc-linux Mullins (n=bw@mobileinternet4.o2.ie)
13:42.33*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
13:49.24*** join/#htc-linux psykhon (n=chatzill@host5.190-225-50.telecom.net.ar)
13:53.23*** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl)
14:02.39*** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be)
14:05.10*** join/#htc-linux Moku (n=John@f049008146.adsl.alicedsl.de)
14:05.55Guest6474netripper
14:07.25*** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl)
14:14.03NetRipperdream_kill
14:15.41dream_killwhat GPIO's missing for raphael / diamond
14:15.46dream_killwhat is to be done
14:15.51dream_killput it this way
14:16.00dream_killmy santa gave me a HUGE gift :D
14:16.13dream_killand i can give u all u need :D
14:17.58psykhon?
14:19.53dream_killfor example :D
14:19.55dream_killunsigned char LED_TABLE[LED_TABLE_SIZE] =                //for Diamond/Raphael/ROSE
14:19.55dream_kill{
14:19.55dream_kill<PROTECTED>
14:19.55dream_kill<PROTECTED>
14:19.55dream_kill<PROTECTED>
14:19.56dream_kill<PROTECTED>
14:19.58dream_kill<PROTECTED>
14:20.00dream_kill<PROTECTED>
14:20.02dream_kill};
14:20.17dream_killunsigned char DC_TABLE[DC_TABLE_SIZE] =
14:20.17dream_kill{
14:20.17dream_kill<PROTECTED>
14:20.18dream_kill};
14:20.31dream_killunsigned char NAVI_TABLE[NAVI_TABLE_SIZE] =              //for Diamond/Raphael/ROSE
14:20.31dream_kill{
14:20.31dream_kill<PROTECTED>
14:20.31dream_kill};
14:20.42dream_killtypedef struct i2cmgr_parameter_tag {
14:20.42dream_killBYTE device_id;             // Device ID
14:20.42dream_killBYTE Address;             //Read/Write Address
14:20.42dream_killWORD wData;
14:20.42dream_killWORD wDataSize;                      // Write Data Size
14:20.42dream_killBYTE TxBuf[70];                      // Functions can put data here
14:20.44dream_kill} SET_I2C_PARAMS, *LPSET_I2C_PARAMS;
14:20.46dream_kill;)
14:20.50*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
14:22.53AstainHellbringmorning
14:23.04dream_kill#define GPIO1_REGS_PHYSICAL_BASE    0xA9000000      // physical address
14:23.04dream_kill#define GPIO1_REGS_VIRTUAL_BASE     0xB3100000      // non-cache virtual address
14:23.04dream_kill#define GPIO2_REGS_PHYSICAL_BASE    0xA9100000      // physical address
14:23.04dream_kill#define GPIO2_REGS_VIRTUAL_BASE     0xB3000000      // non-cache virtual address
14:23.19dream_kill#define GPIOSH1_REGS_PHYSICAL_BASE  0xA9200000      // physical address
14:23.19dream_kill#define GPIOSH1_REGS_VIRTUAL_BASE   0xB2F00000      // non-cache virtual address
14:23.19dream_kill#define GPIOSH2_REGS_PHYSICAL_BASE  0xA9300000      // physical address
14:23.19dream_kill#define GPIOSH2_REGS_VIRTUAL_BASE   0xB2E00000      // non-cache virtual address
14:24.05dream_kill#define NAND_REGS_PHYSICAL_BASE     0xA0A00000
14:24.05dream_kill#define NAND_REGS_VIRTUAL_BASE      0xB1100000
14:24.07*** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215)
14:24.23dream_kill#define UART1_REGS_PHYSICAL_BASE    0xA9A00000      // physical address
14:24.23dream_kill#define UART1_REGS_VIRTUAL_BASE     0xB2800000      // non-cache virtual address
14:24.49dream_kill#define UART2_REGS_PHYSICAL_BASE    0xA9B00000      // physical address
14:24.50dream_kill#define UART2_REGS_VIRTUAL_BASE     0xB2700000      // non-cache virtual address
14:24.58dream_kill#define UART3_REGS_PHYSICAL_BASE    0xA9C00000      // physical address
14:24.58dream_kill#define UART3_REGS_VIRTUAL_BASE     0xB2600000      // non-cache virtual address
14:25.07dream_kill#define UART1_DM_REGS_PHYSICAL_BASE    0xA0200000      // physical address
14:25.07dream_kill#define UART1_DM_REGS_VIRTUAL_BASE     0xB1800000      // non-cache virtual address
14:25.15dream_kill#define UART2_DM_REGS_PHYSICAL_BASE    0xA0300000      // physical address
14:25.15dream_kill#define UART2_DM_REGS_VIRTUAL_BASE     0xB1900000      // non-cache virtual address
14:25.25dream_kill#define USB_REGS_PHYSICAL_BASE      0xA9800000
14:25.25dream_kill#define USB_REGS_VIRTUAL_BASE       0xB2900000
14:25.44dream_kill#define CLK_CTL_REGS_PHYSICAL_BASE  0xA8600000
14:25.44dream_kill#define CLK_CTL_REGS_VIRTUAL_BASE   0xB3200000
14:25.53dream_kill#define EBI1_REGS_PHYSICAL_BASE     0xA8300000  // physical address
14:25.53dream_kill#define EBI1_REGS_VIRTUAL_BASE      0xB3500000  // non-cache virtual address
14:25.57*** join/#htc-linux stefan_schmidt (n=stefan@c120.apm.etc.tu-bs.de)
14:26.00dream_kill#define EBI2CR_REGS_PHYSICAL_BASE   0xA0D00000  // physical address
14:26.00dream_kill#define EBI2CR_REGS_VIRTUAL_BASE    0xB0F00000  // non-cache virtual address
14:26.13dream_kill#define ARM11S_VIC_REGS_PHYSICAL_BASE   0xC0000000  // physical address
14:26.13dream_kill#define ARM11S_VIC_REGS_VIRTUAL_BASE    0xB5300000  // non-cache virtual address
14:26.22dream_kill#define ARM11S_CSR_REGS_PHYSICAL_BASE   0xC0100000  // physical address
14:26.22dream_kill#define ARM11S_CSR_REGS_VIRTUAL_BASE    0xB5400000  // non-cache virtual address
14:26.29dream_kill#define CODECSSBI_REGS_PHYSICAL_BASE    0xA8100000  // physical address
14:26.29dream_kill#define CODECSSBI_REGS_VIRTUAL_BASE     0x91c00000  // non-cache virtual address
14:26.37dream_kill#define TSSC_REGS_PHYSICAL_BASE         0xAA300100  // physical address
14:26.37dream_kill#define TSSC_REGS_VIRTUAL_BASE          0x91b00100  // non-cache virtual address
14:26.42AstainHellbringuhm hi dream_kill
14:26.45dream_kill#define SHARE_MEMORY_PHYSICAL_BASE      0x01F00000
14:26.46dream_kill#define SHARE_MEMORY_VIRTUAL_BASE       0xAA000000
14:26.51dream_killhi :D
14:27.12AstainHellbringwhats all this stuff?
14:27.13dream_killso what u need let me know :D
14:27.22dream_killall the stuff for raphael / diamond :D
14:27.36dream_killso tell me what is missing for having full kernel working ;)
14:27.36AstainHellbringuhm?
14:27.48dream_killmy santa gave me something nice ;)
14:28.01dream_kill#define LCD_BPP                                     16
14:28.01dream_kill#define LCD_CRTC_TOTAL                              0x01450117
14:28.01dream_kill#define LCD_ACTIVE_H_DISP                           0x00F00000
14:28.01dream_kill#define LCD_ACTIVE_V_DISP                           0x01400000
14:28.11AstainHellbringwhat did you get?
14:28.21BalsatI love Santa
14:28.24dream_kill;)
14:28.33dream_killdon't put the wrong questions ;)
14:28.44dream_killask only the correct questions
14:28.49dream_killfor example what gpio...
14:28.55dream_killwhat mapping ... :P
14:31.21*** join/#htc-linux lupine_ (n=lupine@89-16-178-98.no-reverse-dns-set.bytemark.co.uk)
14:32.30*** part/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl)
14:32.51*** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl)
14:33.37NetRipperdream_kill, emmm ok, i'll let cr2 know, he'll have the proper questions
14:33.47NetRipperwhat is the ROSE?
14:34.18dream_killhtc rose :D
14:34.21dream_killsearch net :D
14:34.29NetRipperthis is from spl source code?
14:34.48dream_killdon't ask the wrong questions please ;)
14:35.24AstainHellbringdream_kill what kind of questions can we ask about the source of your information
14:36.16dream_killonly, what is at that gpio, where is keyboard ...
14:36.18dream_kill<PROTECTED>
14:36.18dream_kill---------------------------------------------------------------------------*/
14:36.18dream_kill#define CLKRGM_SRC_FREQ_TCXO_KHZ       19200   /* TCXO     = 19.2 MHz    */
14:36.18dream_kill#define CLKRGM_SRC_FREQ_TCXO4_KHZ       4800   /* TCXO/4   = 4.8 MHz     */
14:36.18dream_kill#define CLKRGM_SRC_FREQ_TCXO5_KHZ       3840   /* TCXO/5   = 3.84 MHz    */
14:36.19dream_kill#define CLKRGM_SRC_FREQ_PLL0_KHZ      196608   /* PLL0     = 196.608 MHz */
14:36.21dream_kill#define CLKRGM_SRC_FREQ_DCPLL0_KHZ    768000   /* DCPLL0   = 768 MHz     */
14:36.23dream_kill#define CLKRGM_SRC_FREQ_DCPLL1_KHZ         0   /* DCPLL1   = Not Used    */
14:36.25dream_kill#define CLKRGM_SRC_FREQ_DCPLL2_KHZ         0   /* DCPLL2   = Not Used    */
14:36.27dream_killclock setup ;)
14:36.28NetRipperdream_kill, can you find the clock formula?
14:36.35dream_kill#define CLKRGM_SRC_FREQ_USB_XTAL_KHZ   48000   /* USB_XTAL = 48 MHz      */
14:36.35dream_kill#define CLKRGM_SRC_FREQ_GSM_DIV_2_KHZ   6500   /* GSM/2    = 6.5 MHz     */
14:36.51dream_kill#define CLKRGM_SRC_FREQ_MPLL_KHZ      CLKRGM_SRC_FREQ_PLL0_KHZ
14:36.51dream_kill#define CLKRGM_SRC_FREQ_GPLL_KHZ      CLKRGM_SRC_FREQ_DCPLL0_KHZ
14:36.51dream_kill#define CLKRGM_SRC_FREQ_BPLL_0_KHZ    CLKRGM_SRC_FREQ_DCPLL1_KHZ
14:36.52dream_kill#define CLKRGM_SRC_FREQ_BPLL_1_KHZ    CLKRGM_SRC_FREQ_DCPLL2_KHZ
14:37.01dream_killtypedef enum
14:37.02dream_kill{
14:37.02dream_kill<PROTECTED>
14:37.02dream_kill<PROTECTED>
14:37.02dream_kill<PROTECTED>
14:37.02dream_kill<PROTECTED>
14:37.04dream_kill<PROTECTED>
14:37.06dream_kill<PROTECTED>
14:37.08dream_kill<PROTECTED>
14:37.10dream_kill<PROTECTED>
14:37.12dream_kill} clkrgm_apps_clk_type;
14:37.38dream_killthink will pastebin it ;)
14:37.40dream_killis huge ;)
14:37.46NetRipperok
14:38.32*** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com)
14:40.12NetRipperthe virtual addresses betray where the source is from ;)
14:40.31dream_kill;)
14:49.00*** join/#htc-linux MethoS- (n=lem@host-091-097-240-026.ewe-ip-backbone.de)
14:57.25*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
14:59.12tmztapt: hello
14:59.12aptsalut, tmzt
15:01.19tmztwe are looking for what Md and Ns are, aren't we?
15:06.18*** join/#htc-linux MethoS-- (n=lem@host-091-097-244-246.ewe-ip-backbone.de)
15:16.50dream_kill?
15:17.10tmztrelated to the clocks
15:18.17dream_killk
15:21.33dream_killvoid msWait3(UINT msDelay)
15:21.33dream_kill{
15:21.33dream_killUINT match_val;
15:21.33dream_kill
15:21.33dream_killmatch_val = msDelay * 356;
15:21.34dream_kill
15:21.36dream_killCSR_AGPT_ENABLE = 0;
15:21.38dream_killCSR_AGPT_MATCH_VAL = match_val;
15:21.40dream_killCSR_AGPT_ENABLE |= BIT0;
15:21.42dream_kill
15:21.44dream_killwhile(match_val--)
15:21.46dream_kill{
15:21.48dream_killif(CSR_AGPT_COUNT_VAL == match_val)
15:21.50dream_killbreak;
15:21.52dream_kill}
15:21.54dream_kill}
15:22.11NetRipperns, md
15:22.12NetRippernot ms
15:22.12NetRipper;)
15:23.09dream_killCLKRGM_MDC_CLK,             /* MDC (MDDI Client) clock */
15:23.11dream_killthis one?
15:23.46NetRipperi dont think so.. Md and Ns are part of the clock formula, afaik
15:23.57NetRippersome mathematical stuff
15:24.06dream_killseems i can't find anything regarding md and ns here
15:24.46NetRippermaybe tmzt knows more
15:25.44tmztI don't
15:26.16tmztmy process revolves around finding out what letters mean and drawing conclusions from there ;)
15:26.20dream_killwhay u rty to do ???
15:26.47tmztlooking for >> && |
15:27.04dream_killfor WHAT ?
15:27.07tmzt<PROTECTED>
15:27.10dream_killwhat driver u wana fix :P ?
15:27.17dream_killso i know where to look into :D
15:27.45NetRipperstill related to clocks ;)
15:28.05NetRipperthe clock formula will have a lot of bitshifting and other bit operations
15:33.21dream_killwhat u need this for?
15:33.45dream_killi2c?
15:34.20tmztclocks are needed for everything
15:34.25dream_kill#define I2C_HW_CTRL_SCL_FREQ 200 /* I2C clock control line frequency (KHz) */
15:34.25dream_kill#define I2C_HS_DIV(freq)  MAX( MIN( ((clk_i2c_freq_khz / (3 * (freq))) - 1), 7), 3)
15:34.25dream_kill#define I2C_FS_DIV(freq)  MAX( MIN( ((clk_i2c_freq_khz / (2 * (freq))) - 3), 255), 3)
15:34.45dream_kill#define I2C_SCL_FREQ_CAL(freq)   ((I2C_HS_DIV(freq) << 8) | I2C_FS_DIV(freq))
15:34.45tmztmost of them are already configured by wm and don't need changed in linux
15:35.26tmztNetRipper: could the table be needed then?
15:35.37dream_killso what u need exactly then
15:35.41dream_killwhat driver u wana fix
15:35.46dream_killtell me more details
15:35.50dream_killso i can trace it
15:36.44dream_killu need a good sd card driver ;) ?
15:36.46dream_killboolean sdhw_init( SLOT_ID slot_id)
15:36.46dream_kill{
15:36.46dream_killvolatile PCLK_CTL_REGS pClkCtlRegs = (PCLK_CTL_REGS) CLK_CTL_REGS_VIRTUAL_BASE;
15:36.46dream_kill<PROTECTED>
15:36.46dream_kill<PROTECTED>
15:36.47dream_kill<PROTECTED>
15:36.49dream_kill<PROTECTED>
15:36.51dream_kill<PROTECTED>
15:36.53dream_kill<PROTECTED>
15:36.55dream_killSetGpioDir(62, 1);
15:36.57dream_killSetGpioLevel(62, 0);
15:36.59dream_killSetGpioAlt(62, 0, 2, 0);
15:37.01dream_killSetGpioDir(63, 1);
15:37.03dream_killSetGpioLevel(63, 0);
15:37.05dream_killSetGpioAlt(63, 0, 2, 0);
15:37.07dream_killSetGpioDir(64, 1);
15:37.09dream_killSetGpioLevel(64, 0);
15:37.11dream_killSetGpioAlt(64, 0, 2, 0);
15:37.13dream_killSetGpioDir(65, 1);
15:37.15dream_killSetGpioLevel(65, 0);
15:37.17dream_killSetGpioAlt(65, 0, 2, 0);
15:37.19dream_killSetGpioDir(66, 1);
15:37.21dream_killSetGpioLevel(66, 0);
15:37.23dream_killSetGpioAlt(66, 0, 2, 0);
15:37.25dream_killSetGpioDir(67, 1);
15:37.27dream_killSetGpioLevel(67, 0);
15:37.29dream_killSetGpioAlt(67, 0, 2, 0);
15:37.31dream_kill<PROTECTED>
15:37.33dream_kill<PROTECTED>
15:37.35dream_kill<PROTECTED>
15:37.37dream_kill<PROTECTED>
15:37.39dream_killConfigCpuGpio(SIM_SDMC_CLK, PIN_OUT, DRV_2MA|FUNC_ALT1|PULL_NO,PIN_LOW);
15:37.41dream_killConfigCpuGpio(SIM_SDMC_CMD, PIN_OUT, DRV_2MA|FUNC_ALT1|PULL_NO,PIN_LOW);
15:37.43dream_killConfigCpuGpio(SIM_SDMC_D0,  PIN_OUT, DRV_2MA|FUNC_ALT1|PULL_NO,PIN_LOW);
15:37.45dream_kill<PROTECTED>
15:37.47dream_kill<PROTECTED>
15:37.49dream_kill*/
15:37.51dream_kill<PROTECTED>
15:37.53dream_killdriveno = sdhw_GetControllerNo(SLOT_WIFI);//return 0, for SDC1
15:37.55dream_kill<PROTECTED>
15:37.57dream_killSetGpioDir(51, 1);
15:37.59dream_killSetGpioLevel(51, 0);
15:38.01dream_killSetGpioAlt(51, 0, 1, 0);
15:38.03dream_killSetGpioDir(52, 1);
15:38.04tmztsd pins on the sim??
15:38.05dream_killSetGpioLevel(52, 0);
15:38.07dream_killSetGpioAlt(52, 0, 1, 0);
15:38.09dream_killSetGpioDir(53, 1);
15:38.11dream_killSetGpioLevel(53, 0);
15:38.13dream_killSetGpioAlt(53, 0, 1, 0);
15:38.15dream_killSetGpioDir(54, 1);
15:38.17dream_killSetGpioLevel(54, 0);
15:38.19dream_killSetGpioAlt(54, 0, 1, 0);
15:38.21dream_killSetGpioDir(55, 1);
15:38.23dream_killSetGpioLevel(55, 0);
15:38.25dream_killSetGpioAlt(55, 0, 1, 0);
15:38.27dream_killSetGpioDir(56, 1);
15:38.29dream_killSetGpioLevel(56, 0);
15:38.31dream_killSetGpioAlt(56, 0, 1, 0);
15:38.33dream_kill<PROTECTED>
15:38.35dream_kill<PROTECTED>
15:38.37dream_kill<PROTECTED>
15:38.39dream_kill<PROTECTED>
15:38.41dream_kill<PROTECTED>
15:38.43dream_kill<PROTECTED>
15:38.45dream_kill<PROTECTED>
15:38.47dream_kill<PROTECTED>
15:38.49dream_kill<PROTECTED>
15:38.51dream_killpClkCtlRegs->glbl_clk_ena.sdc1_h_clk_ena = 1;
15:38.52tmztPCLK_CTL_REGS there is something like that in android, isn't there? NetRipper ?
15:38.53dream_kill<PROTECTED>
15:38.55dream_kill<PROTECTED>
15:38.57dream_kill<PROTECTED>
15:38.59dream_kill<PROTECTED>
15:39.01dream_killpClkCtlRegs->glbl_clk_ena.sdc2_h_clk_ena = 1;
15:39.03dream_kill<PROTECTED>
15:39.05dream_kill<PROTECTED>
15:39.07dream_kill<PROTECTED>
15:39.09dream_kill<PROTECTED>
15:39.11dream_kill<PROTECTED>
15:39.13dream_kill<PROTECTED>
15:39.15dream_kill<PROTECTED>
15:39.16NetRippertmzt, think so, not sure
15:39.17dream_kill<PROTECTED>
15:39.19dream_kill<PROTECTED>
15:39.21dream_kill<PROTECTED>
15:39.23dream_kill<PROTECTED>
15:39.25tmzta struct?
15:39.26dream_kill<PROTECTED>
15:39.28dream_kill<PROTECTED>
15:39.30dream_kill<PROTECTED>
15:39.32dream_kill<PROTECTED>
15:39.34dream_kill}
15:39.36dream_killvoid SD_PowerHandler(BOOL bOn)
15:39.38dream_kill{
15:39.40dream_killif(bOn)
15:39.42dream_killPowerIC_Control(VREG_GP6_BT, 1, 0);
15:39.44dream_killelse
15:39.46dream_killPowerIC_Control(VREG_GP6_BT, 0, 0);
15:39.48dream_killmsWait(300);
15:39.50dream_kill}
15:39.52dream_killBOOL SD_Init(BOOL bMSIM)
15:39.54dream_kill{
15:39.56dream_killif(bMSIM)
15:39.58dream_killsdhw_init(SLOT_MEGASIM);
15:39.59tmztit would be in a .h file?
15:40.00dream_killelse
15:40.02dream_killsdhw_init(SLOT_SDMMC);
15:40.04dream_kill
15:40.06dream_killif (sdcc_open(SD_MEMORY_CARD_ON_SDCC))
15:40.06NetRipperyep
15:40.07tmzta struct PCLK_CLK_CTL
15:40.08dream_killreturn TRUE;
15:40.10dream_killelse
15:40.12dream_killreturn FALSE;
15:40.14dream_kill}
15:40.22dream_killint16 sdhw_GetControllerNo( SLOT_ID slot_id )
15:40.22dream_kill{
15:40.22dream_kill<PROTECTED>
15:40.22dream_kill<PROTECTED>
15:40.24dream_kill<PROTECTED>
15:40.26dream_kill<PROTECTED>
15:40.28dream_kill<PROTECTED>
15:40.30dream_kill<PROTECTED>
15:40.30NetRippertmzt, ah, no, it's probably a constant to a memory addres
15:40.32dream_killreturn 0;//SDC1
15:40.34dream_kill<PROTECTED>
15:40.34NetRipperctl = control
15:40.36dream_kill<PROTECTED>
15:40.38dream_kill<PROTECTED>
15:40.40dream_kill<PROTECTED>
15:40.42dream_kill}
15:40.53*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
15:42.07tmzt?
15:42.27dream_kill??
15:43.02NetRipperquite some spam ;)
15:43.12NetRipperbut the init might be useful
15:43.12dream_killu like spam :P ?
15:43.49dream_killwhat the atmega does inside the phone ;) ?
15:43.57NetRipperthe megasim?
15:44.05dream_killnot
15:44.10dream_killa atmel :P
15:44.32NetRipperdon't know
15:44.38NetRipperi gtg though..
15:44.46NetRipperi'll read back on some spam later tonight
15:44.47dream_killatmega88 :D
15:44.48NetRipper:)
15:44.58dream_killunsigned char ATMEGA88_nSLAVE_ADDRESS=0xCC;
15:45.10dream_killunsigned short int ATMEGA88_BOOT_PAGE_ADDRESS=0x1C00;
15:45.10dream_killunsigned short int ATMEGA88_ERASE_CHECKSUM=0x5102;
15:45.10dream_killunsigned short int ATMEGA88_BOOT_CODE_SIZE;//Important Note: The Length of AP code can not > 0x1C00=7168 bytes
15:45.36dream_killmmm
15:45.37tmztmegasim is a sim card which is also SD card
15:45.48dream_killthey use atmega for the LCD!?!?! controler?
15:45.59*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
15:46.10tmztbut it appears only one sd slot is supported, either megasim (not used) or sd (microsd)
15:46.15tmzton SDC2
15:46.33dream_killok what else u need :P ?
15:46.44dream_killbefore i go too :D
15:47.45dream_killvoid TurnOnWLAN(BOOL bOn)
15:47.45dream_kill{
15:47.45dream_killif(bOn)
15:47.45dream_kill{
15:47.46dream_kill<PROTECTED>
15:47.46dream_kill<PROTECTED>
15:47.47dream_killSetGpioLevel(102, 1);  // PM_EN
15:47.49dream_killSetGpioLevel(103, 1);// WW_OSC_1V8
15:47.53dream_kill<PROTECTED>
15:47.53dream_kill}
15:47.55dream_killelse
15:47.57dream_kill{
15:47.59dream_killSetGpioLevel(102, 0);  // PM_EN
15:48.01dream_killSetGpioLevel(103, 0);// WW_OSC_1V8
15:48.03dream_kill}
15:48.05dream_kill}
15:48.26*** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl)
15:49.03dream_killBOOL GetMACAddr(PBYTE pMACAddr)
15:49.03dream_kill{
15:49.04dream_killBYTETemp, MAC[16]={0};
15:49.04dream_killinti;
15:49.04dream_kill
15:49.04dream_killLoadMfgDataFromFlash((PBYTE)pMfg);
15:49.06dream_kill
15:49.08dream_killeMapiCheckWlanDataValidity((PWLAN_EEPROM_IN_FLASH) &pMfg->wlan);
15:49.10dream_killfor(i = 0; i < WLAN_MAC_ADDRESS_SIZE; i++)
15:49.12dream_kill{
15:49.14dream_killTemp = pMfg->wlan.MAC[WLAN_MAC_ADDRESS_SIZE-1-i];
15:49.16dream_killMAC[2*i]   = ((Temp >> 4)>9) ? ((Temp >> 4)+0x37):((Temp >> 4)+'0');
15:49.18dream_killMAC[2*i+1] = ((Temp & 0x0F)>9) ? ((Temp & 0x0F)+0x37):((Temp & 0x0F)+'0');
15:49.20dream_kill}
15:49.22dream_kill
15:49.24dream_killif(pMACAddr == 0)// For module
15:49.26dream_kill{
15:49.28dream_killOutputFormatString("MAC:%s\n",MAC);
15:49.30dream_killOutputFormatString("WCC:%x\n", pMfg->wlan.CountryCode);
15:49.32dream_kill}
15:49.34dream_killelse// For System
15:49.36dream_killstrcpy(pMACAddr, MAC);
15:49.38dream_kill
15:49.40dream_killreturn TRUE;
15:49.42dream_kill}
15:50.12*** join/#htc-linux hlbot (n=adm@iclem.net)
15:51.53dream_killBOOL GetMsmWlanIrqPin(void)
15:51.53dream_kill{
15:51.53dream_kill//ConfigCpuGpio(MSM_WL_IRQ, PIN_IN, FUNC_GPIO|PULL_NO, PIN_LOW);
15:51.53dream_kill
15:51.53dream_killreturn GetGpioLevel(29);
15:51.54dream_kill}
15:53.06timebombwhateve happened to booting linux from home made sd cards btw?
15:56.07dream_killanything else u need guys before i go ?
16:27.42*** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net)
16:34.46BHSPitMonkeyPeople can home-make SD cards?
16:45.49*** join/#htc-linux utter0182 (n=dk@92.9.69.220)
16:55.00*** join/#htc-linux Chiles (n=christop@32.133.24.11)
16:55.51Chileshelp, I am trying to mount system.img and zimage.bin.  Not a valid block device it says
16:56.31AstainHellbringChiles add -o loop
16:57.47Chilesthanks
16:58.14Chilesmust specify filesystem type? ext2?
16:58.28AstainHellbringshould autodetect that
17:00.02Chilesworks for system.img thanks
17:00.41Chileslol the lesson for today.  read the error message and type exactly what it says to do.... appreciate the help though
17:01.49*** join/#htc-linux psykhon (n=chatzill@host5.190-225-50.telecom.net.ar)
17:02.01AstainHellbringsure
17:04.56Chilesyeah the .bin files are giving the message that I need to specify the filesystem type, maybe the binaries cant be mounted?
17:05.15AstainHellbringzImage can't be mounted its a kernel
17:05.42Chileshmm..different type of .bin I'm thinking of can be mounted then
17:06.07Chileshow to edit vogue-ts.kcm.bin?
17:06.13Chilesif possible
17:07.55Chileslol I forgot, I'm not a compiler
17:07.56Chilesdoh
17:16.21*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
17:21.40*** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com)
17:21.40*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
17:22.22*** join/#htc-linux MethoS- (n=lem@host-091-096-212-216.ewe-ip-backbone.de)
17:29.16Chileshow do I get the compiler to compile this "/kernel/arch/arm/mach-msm/board-htc-kaiser-keypad.c"?
17:29.58Chilesand does linux already know which system I'm using to know which keyboard to use when it's compiled?
17:31.06imfloflowith your default.txt set MTYPE 1667
17:31.42Chilesthat is supposed to be vogue though right?
17:33.47imfloflo??
17:33.49Chilesshould I edit the vogue keyboard file instead?
17:33.56Chiles1667 is for vogue
17:34.24Chiles1553 is for kaiser. however apparently they added support for kaiser in the new vogue build
17:35.04Chileshow does the MTYPE know which keyboard to load?
17:35.09*** join/#htc-linux ginge (n=kvirc@78-105-175-81.zone3.bethere.co.uk)
17:36.03ChilesThe reason why I ask is I'm adding a new keyboard layout similar to kaiser but want to add a new keymap file
17:37.12ChilesI would settle for editing the kaiser one. (I'm using tilt) but I'm not sure if it is even looking there for the keyboard.
17:37.20imflofloin your function you must code  if mtyp=1234 ..... else if mtyp=.....
17:38.11Chilesso I can copy the board-htc-kaiser-keypad.c to something else then change the mtype inside to something else and then change it in default.txt?
17:45.15Chileswhere is this function?
17:45.43imfloflodunno ask rogro or look in the keyboard files
18:12.46*** join/#htc-linux Chiles (n=christop@32.133.219.166)
18:17.46*** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl)
18:28.36*** join/#htc-linux psykhon (n=chatzill@host5.190-225-50.telecom.net.ar)
18:36.37*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c608.pool.einsundeins.de)
18:37.12*** join/#htc-linux christopher (n=christop@32.130.227.142)
18:42.28*** join/#htc-linux Funkwheat (i=Funkwhea@pool-72-87-87-19.prvdri.fios.verizon.net)
18:43.04imfloflostill can't send SMS with polaris and lastest zImage and system.img :s
19:03.19*** join/#htc-linux MasterPrenium (n=MasterPr@ALille-257-1-133-69.w86-207.abo.wanadoo.fr)
19:06.44*** join/#htc-linux AstainZZZZZZ (n=AstainHe@unaffiliated/astainhellbring)
19:12.11*** join/#htc-linux christopher (n=christop@32.130.117.53)
19:13.05imflofloxda down ?
19:13.56AstainZZZZZZworks for me
19:20.27imflofloworks now :s
19:30.27*** join/#htc-linux christopher_ (n=christop@32.133.133.113)
19:30.44*** join/#htc-linux christopher_ (n=christop@32.133.133.113)
19:31.41*** join/#htc-linux christopher_ (n=christop@32.133.243.207)
19:32.20*** join/#htc-linux christopher_ (n=christop@32.133.116.94)
19:55.50*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c608.pool.einsundeins.de)
20:04.16*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c608.pool.einsundeins.de)
20:04.43*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
20:05.31*** join/#htc-linux sdt5551 (n=titus@147.145.40.44)
20:17.49*** join/#htc-linux cr2 (n=cr2@ip-90-186-237-11.web.vodafone.de)
20:19.24cr2maejrep[w]: i think i have found the right pull+alt+drvstr mixture :)
20:20.33AstainHellbringerr cr2 whats that mean?
20:20.39cr2through 3 orthogonal cases, and every other known combination fits into this schema
20:21.21cr2but i know the data only for rap100 and kais, so feel free to submit any new unknown data
20:22.06cr2AstainHellbring: googel obfuscated the gpio cfg access in the g1 kernel, so  it was necessary to decipher it
20:24.44cr2AstainHellbring: according to proc_comm.h there are 2 bits for pull, 4 bits for alt(func) and 4 bits for drvstr
20:25.16cr2they are shuffled in some way (2^3=8 combinations)
20:25.19*** join/#htc-linux Skitzo (n=DCLXVI@eth582.vic.adsl.internode.on.net)
20:25.35cr2and we know the result, but not the single components
20:26.16cr2"shuffled" was actually my assumption, because as we all know google is not evil ;)
20:27.52cr2so after writing down all know alt mixture settings, and their function, i was able to find the combination that explains where to find it's parts
20:28.30cr2the lower 2 bits are for pull, then come 4 bits for alt(func) and the remaining 4 bits are for drvstr
20:29.10cr2and least this schema can be applied to the all known raph100 and kais gpio alt settings
20:31.51imfloflohey is this files interressing ? http://nullwire.com/try_out_cupcake_yourself
20:33.02kiozencr2: GT has wms support and vector map overlay now
20:33.20cr2kiozen: wow, i need to check it.
20:33.41cr2kiozen: have you looked at the gpio 114,115,116 ?
20:33.55kiozenno, no time, sorry
20:33.59cr2ok
20:34.49cr2i fell 3 times from my bicycle today , while driving through the forest at night ;)
20:34.56kiozenlol
20:35.04cr2and still the nc10 is alive :)
20:35.11kiozenbuy a tricyle
20:35.22cr2but i broke some plastic parts ;)
20:35.50cr2yeah, i wish they will put sand on the ways in the forest instead ;)
20:36.36BabelOcr2: you don't have dynamo light ?
20:37.02cr2BabelO: i have, but it does not help when you drive on ice ...
20:37.13BabelOright
20:37.29cr2in the morning it was not a problem
20:37.51cr2but in the darkness it's more difficult to keep the balance
20:38.29cr2but somehow the ice is better than dirt ;O)
20:38.50cr2i don't want to drive there in spring
20:39.16kiozenwants to see cr2 driving there in spring
20:39.24kiozenand the squirils too
20:39.25cr2lol
20:39.52cr2i'll repar the car, or buy a new one before.
20:40.18kiozentake one with usb host adapter to connect gps
20:40.34cr2it's absolutely quiet the the forest.
20:40.36cr2LOL
20:41.00cr276Cx had some problems to get a fix
20:41.07*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
20:41.21cr2and i have removed the stored track because of the evil 10000 limit
20:41.43cr2and these forest ways are not (yet) in the osm ;-)
20:45.10cr2kiozen: http://openstreetmap.org/?lat=48.0685&lon=11.22466&zoom=16
20:46.04kiozenso you crossed the line where no man has before?
20:46.51cr2yeah, there are more paths and ways there
20:47.43cr2after i mostly broken my left arm, i was going by foot at some small path.
20:48.32cr2since there was no map anyway. i've only seen the train once
20:49.36cr2i'm curious what's available on the grmn topo map ;)
20:49.59kiozencr2: http://www.qlandkarte.org/shot3.png
20:50.08cr2google sucks anyway
20:50.59BabelOkiozen : is it the cpu monitor ? no multicore monitor at all ?
20:51.27BabelOkiozen: scshot with light / sun /sky and rock n roll !
20:51.46cr2wow, looks really nice
20:52.08cr2kiozen: what's the grmn bootcamp (?) software ?
20:52.14kiozenBabelO: yes no as good as before
20:52.18kiozencr2: wait
20:52.50kiozenhttp://www.qlandkarte.org/shot4.png
20:53.06kiozenhttp://www.qlandkarte.org/shot5.png
20:54.00kiozenno clue what's bootcamp
20:54.08kiozenmarketing mumbo jumbo?
20:55.02BabelOkiozen elevation lines look good too
20:55.10BabelOthe text i mean
20:56.15cr2these look better, but are still inaccurate
20:57.36cr2they show the second railway crossing, but there is nothing at this place.
20:57.45cr2it can be even seen on maps.google.com
20:58.28VennyWho wants to help me brick my brand new HTC touch pro???
21:01.27cr2kiozen: looking for the link
21:01.59VennySomeone? Brand new HTC TOUCH PRO CDMA, will do anything to brick it
21:02.00cr2BabelO: have you seen that http://lists.openstreetmap.org/pipermail/talk/2009-January/033289.html
21:03.31BabelOkiozen: looks better http://linuxbox2.free.fr/qlandkartegt.png
21:04.32kiozenhttp://pastebin.ca/1319912
21:05.09kiozenlol you show off with the "mountains"
21:05.09cr2hmm. can't find it anymore
21:05.21BabelOcr2:  wouah that strange from France, because Geoportail lock everything from its wms server, and all is IGN base
21:05.50cr2BabelO: they have all documents in wiki
21:06.11BabelOcr2: ok so it is a big change !
21:07.16BabelOkiozen: there is something new because map quality is still good in the 3d view
21:07.51cr2BabelO: http://wiki.openstreetmap.org/wiki/Cadastre_FranƃĀ§ais/Legal#La_rƃĀ©ponse_de_la_DGI
21:09.31kiozenBabelO: right looks like andrew is doing a bicubic interpolation
21:10.05BabelOkiozen: :)
21:10.21cr2kiozen: an arm version of >G
21:10.24cr2GT ?
21:10.25BabelOcr2: ok i read, but still look strange to me
21:11.40cr2BabelO: everybody is under pressure to open the data now, because of the EU INSPIRE programm
21:13.22*** join/#htc-linux konsta (n=asds@host81-157-60-163.range81-157.btcentralplus.com)
21:16.34BabelOcr2: maybe yes, but it is still incredible to me :)
21:17.37cr2kiozen: how can we get this magellan fw ? i was searching everywhere, but still didn't find anything
21:18.07cr2BabelO: the times change
21:21.13*** join/#htc-linux hollo_ (n=hollo@3e6b025d.rev.stofanet.dk)
21:21.17hollo_hh
21:23.26kiozencr2: think you have to login
21:23.59BabelOcr2: the time will change when HTC will publish datasheet of their phones  :)
21:25.04*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
21:27.48*** part/#htc-linux Balsat (n=kll@87.72.13.87)
21:30.34cr2kiozen: yes, but they also may ask for the device number too.
21:30.59kiozen:)))
21:31.04kiozenwe need to buy one
21:31.54cr2well, how much does it cost ?
21:32.14kiozenlet's see how much money is left after tax and if I can generate an acceptable WAF
21:32.25kiozen~250.- the 500
21:32.47AstainHellbringWAF?
21:32.55cr2i'll give you 50%
21:33.07kiozenAstainHellbring: Wife Acceptance Factor
21:33.15AstainHellbringlol
21:33.20AstainHellbringwhat you buying?
21:33.30kiozenmagellan triton 500
21:33.48kiozenthat wouldn't be a problem itself
21:33.56kiozenit's just I own 5 GPS already
21:35.12AstainHellbringdamn thats a few
21:36.28*** join/#htc-linux balsat (n=kll@87.72.13.87)
21:36.36cr2lol
21:36.54kiozenaccording to my wife one is enought to find out where you are
21:37.12*** join/#htc-linux Balsat (n=kll@87.72.13.87)
21:37.21cr2kiozen: but you don't have any water-tight devices
21:37.54cr2i have 5 phones, 2 bt gps, 1 cf
21:38.05cr2maybe more, don't remember now ;)
21:38.31cr2phones with gps
21:38.38kiozencr2: but you do not have to discuss it ;)
21:38.48cr2but only athena has acceptable gps quality.
21:39.01cr2the gps in raph100 is complete junk
21:39.06kiozenand the 60scx is as water tight as the 70
21:39.12cr2i see it when i compare it with 76Cx
21:39.18kiozenit just does not float
21:39.50cr2kiozen: but i have no other way to spend the money too :)
21:40.02kiozenbut I can save the 300.- bugs to rugg up the loox
21:40.04kiozen<PROTECTED>
21:40.37AstainHellbringyou can always save up for the tegra devices due towards the end of the year roughly
21:40.43lupine_85doesn't mind the raph100 gps
21:40.45cr2loox is such a pita on the software side, that i vote for triton ;)
21:40.53lupine_85it does it, just not through bricks, it would appear
21:41.09kiozencr2: :)))))
21:41.17NetRippercr2, did you look at dream_kill's spl source spam?
21:41.24NetRipperhi, btw :)
21:41.59cr2lupine_85: for showing on which street you are, maybe. but for recording tracks it's a complete junk
21:42.34cr2NetRipper: yes. i think he is really doing a bad service for us.
21:42.52NetRipperas in, we may not use code from that anyway?
21:43.00cr2NetRipper: because we already know 98% of that data anyway.
21:43.28lupine_85let's avoid tainting the code, eh? :)
21:43.44lupine_85dislikes code audits muchly
21:44.05NetRipperdoes it cause legal issues when he pastes stuff like that/
21:44.13NetRipperlupine_85, well they can audit the git all they want
21:44.22cr2NetRipper: if he will publish it at some $randomsite, we may have a look at it as any other person
21:44.37cr2but we should not rely on it as a single source.
21:44.47lupine_85NetRipper: if $company lawyers can demonstrate we used it, possibly
21:44.52lupine_85that'd be pretty hard to do though :p
21:45.10*** join/#htc-linux jsbach (n=jsbach@e178049142.adsl.alicedsl.de)
21:45.26NetRipperwell i can understand you can't use stuff that you wouldn't otherwise find out by reverse engineering
21:45.40lupine_85nah, you can use it, you just need to follow clean-room procedures
21:45.46cr2lupine_85: yeah, i'm happy that all my wiki editing is publicly available with the completehistory
21:45.55NetRippercr2, stuff like this is saved in the log and publically that way
21:46.10lupine_85(AIUI, that's why the tiacx driver isn't in the mainline kernel, for instance)
21:46.14jsbachhi, i wonder if i can communicate with my windows mobile over usb (os=linux)
21:46.26jsbachis there any linux application for that?
21:46.26cr2no. from how it looks, it's the original leaked source
21:46.37NetRipperjsbach, synce
21:46.42lupine_85jsbach: if you have 'advanced networking functionality' installed, you can use synce/etc
21:47.07jsbachadvanced networking functionality? what does that mean?
21:47.10lupine_85(plus you get a usb1 as 169.254.2.2 - the phone is 169.154.2.1)
21:47.11jsbachon htc is that?
21:47.16lupine_85it's in system -> connections on the phone
21:47.28NetRipperin fact, you'll get eth1 as 169.*
21:47.35jsbachi've tried for about 1,5 years ago with synce but it didn't work
21:47.37NetRipperor well, here i get eth instad of usb
21:47.37NetRipper:)
21:47.47lupine_85or eth1 ;)
21:47.51lupine_85is getting mixed up
21:47.52jsbachok i see, i'll have a look  on 'advanced...'
21:48.05NetRipperjsbach, synce probably improved over the last 1,5 years
21:48.12*** join/#htc-linux Xime (n=xime@bankize.net)
21:48.31jsbachNetRipper, probably. yes.
21:48.40NetRipperi've successfully used it a few days ago anyway..
21:48.44cr2NetRipper: we are missing some data only in 2 areas now
21:48.51*** part/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
21:48.53NetRipperatleast the cp/ls commands
21:49.00jsbachwas it an htc?
21:49.05NetRipperjsbach, the raphael
21:49.16imfloflo?etripper what are you working on ?
21:49.22cr2NetRipper: the remaining clocks in MSM_CLK, but they are not used by wince too. otherwise we would have seen them
21:49.49NetRippercr2, so that makes the remaining clocks less critical, as spl probably takes care of them
21:49.51cr2NetRipper: and the epson mddi panel chip.
21:50.00NetRipperah, yes
21:50.03jsbachthe raphael? all i know about what i have is, that you can slide the screen and you have the keyboard, and it has a huge display -only display at front
21:50.07cr2NetRipper: not the spl, but the oemsbl
21:50.19*** join/#htc-linux exco (n=exco@e181066083.adsl.alicedsl.de)
21:50.28jsbachmy old telco has put its own brand..
21:50.29cr2NetRipper: spl is the same kind of software like linux kernel
21:50.41NetRipperimfloflo, i've modified the msm_ts driver to be interrupt-based... but because of that i have to do some rework on msmfb and virtual keyboard as well
21:50.48cr2NetRipper: it does not setup teh  hardware
21:51.31NetRippercr2, ah, ok.. but, the virtual addressing such as the 0xb* addresses, they are mapped by spl, aren't they?
21:52.04*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
21:52.21NetRipperim not sure if what you say is correct
21:52.47NetRipperon #xda-devs someone explained the whole boot procedure to tmzt earlier today or yesterday
21:53.37NetRipperyesterday, 4am
21:53.37NetRipper;)
21:53.47NetRippercmonex
21:53.55NetRipperbut i might be remembering wrong
21:54.02cr2NetRipper: no, the spl has no place in the boot process
21:54.19NetRipperit does
21:54.26NetRipperit indicates to the oemsbl if it needs to load wince or not
21:54.31cr2NetRipper: the only device where is does, is the n560 of kiozen. and it's a _PITA_ because of that ;)
21:54.41NetRipperand it also indicates if it needs to load modem
21:55.20NetRipperthough you're correct that the oemsbl does the actual starting of the modem on arm9
21:55.30cr2NetRipper: i've disassembled the complete spl, so i can guess about the spl functions :)
21:56.02cr2oemsbl sets the clocks, and the MPU protection
21:56.10NetRipperok
21:56.22cr2so you don't see the protected nand areas.
21:56.27cr2on the hw level
21:56.29NetRipperso, that code dream_kill posted, would it be spl or oemsbl?
21:56.43NetRipperseemed to me to be spl
21:56.47cr2and you probably can't change these bits, without patching the oemsbl
21:57.11NetRipperhm, ok
21:57.12cr2i think it was spl, or the wince bsp (more likely)
21:57.36NetRipperbsp? boot sector program or something?
21:57.51cr2but the oemsbl is certainly RSA signed, so it's not easy to reflash the oemsbl
21:58.04cr2board support package
21:58.09NetRipperah, right
21:58.28cr2but i guess the people at #xda-dev know more than i about the device reflashing :)
21:58.48cr2and other dark corners
21:58.57NetRipperyea i hastly read what cmonex said about the boot process to tmzt and they really know a lot :)
21:59.06NetRipperpretty neat ;)
21:59.11lupine_85NetRipper: will msmfb tweaks result in X working without a Very Dirty Hack? :)
21:59.47*** join/#htc-linux MethoS (n=lem@host-091-096-212-216.ewe-ip-backbone.de)
22:00.11NetRipperlupine_85, no, the hack will be just as dirty... previously it worked as the msm_ts was polling every 5 ms, and in the process the vkeyb was redrawn every 5ms, which caused msm_fb to update every 5 ms
22:00.24NetRipperbut now, that the ts is on interrupt, the msmfb will need its own thread to keep redrawing
22:00.38NetRipperso it's the kaiser-solution ;) just as dirty
22:01.01cr2NetRipper: why not fix the g1 code instead ?
22:01.30NetRippercr2, there's nothing to fix, the 'very dirty hack' is needed as there is no proper X driver for msmfb
22:01.33cr2NetRipper: the raph100 init is not that complex. we just need some more patience to document it in all details
22:01.39NetRippereh
22:01.45NetRipperwhat do you mean?
22:01.52NetRipperwe're talking about different things i believe
22:01.53cr2it 's not an fb ??
22:02.00NetRipperyes it is, but normal fb's don't need a dma
22:02.07cr2can you write to /dev/fb0 ?
22:02.24cr2hmm
22:02.31NetRipperwhich is why fbdev doesnt work
22:02.40cr2and there is no hardware refresh at all ?
22:02.45NetRipperit updates the framebuffer memory correctly, but msmfb isn't signalled to do dma
22:02.53cr2ok, maybe we just don't know how to enable it.
22:02.56NetRipperandroid does it as it's specifically interoperating with msmfb ;)
22:03.09cr2that's evil
22:03.24NetRipperandroid has many evil things
22:03.36NetRipperi havent dived in the android code to see how exactly they do it
22:03.46AstainHellbringwhats evil about that?
22:03.48NetRipperbut point is, the "fbdev" X driver doesn't work
22:04.05NetRipperand the proper solution is an "msmfb" X driver (seperate from the kernel driver)
22:04.12cr2AstainHellbring: not supporting the classical unix way is evil.
22:04.34AstainHellbringlol
22:04.51*** join/#htc-linux ImCoKeMaN (n=imcokema@pool-98-111-118-30.hrbgpa.fios.verizon.net)
22:05.13NetRipperthe word 'conservatist' pops into mind
22:05.14cr2AstainHellbring: they could have written an accelerated fb driver first
22:05.27cr2and do their strange java stuff on top of that.
22:05.34cr2that's the unix way
22:08.07cr2NetRipper: "traditionalist" :)
22:08.21NetRippersure ;)
22:10.48NetRipperdoes blit mean anything?
22:11.07cr2for me linux is not just an option not to use the evil m$ software, but a proper way to do things right.
22:11.24NetRipperandroid probably issues an ioctl() which causes the display to update
22:11.29*** join/#htc-linux Sti_0239 (n=Where_is@55.194-65-87.adsl-dyn.isp.belgacom.be)
22:11.37cr2copying the bits block at once
22:11.51cr2like XCopyArea, i think
22:12.52NetRipperah
22:12.52NetRipperthere's a blit ioctl
22:12.52NetRipperMSMFB_BLIT
22:12.52NetRipperand an MSMFB_GRP_DISP
22:12.53NetRipperwhich sounds like a screendump
22:13.49NetRipperbut the ioctl issues a blit() to the mdp, not sure how that works internally and if it will get back to the msmfb_imageblit() finally, which does do an update() ;)
22:13.50cr2GRP is graphics
22:13.58NetRipperah
22:14.20*** join/#htc-linux Sti_0239 (n=Where_is@55.194-65-87.adsl-dyn.isp.belgacom.be)
22:14.24NetRippercalls set_grp_disp() on mdp
22:14.40cr2this whole hw3d part is missing inside my mind :)
22:15.16NetRipperi doubt that msm_fb is hardware accelerated
22:15.18NetRipperor is it?
22:15.18cr2we don't enable the imem and grp clocks too. and i don't see them anywhere inside wince
22:15.29cr2at least partly
22:15.41cr2there is no hw opengl
22:16.03cr2but there is some transformation support
22:16.27cr2i think there was some .pdf presentation available on the ATI openGL-ES implementation
22:17.43cr2the ati api on 7201A is pure software
22:18.19cr2compared to the ATI chipsets used on athena,hermes, ba/hima and such.
22:19.44NetRipperok
22:19.58NetRipperyea tomtom really performs poorly
22:20.12NetRipperit's worse than my hermes
22:20.25NetRipperhermes had a proper ati chip
22:20.48cr2the toshiba/epson has some embedded videoram
22:20.58cr2they even support PiP
22:21.10cr2in hardware
22:21.31*** join/#htc-linux Sti_0239 (n=Where_is@55.194-65-87.adsl-dyn.isp.belgacom.be)
22:21.46NetRippernice
22:21.59maejrep[w][15:21:21]  <cr2> but i know the data only for rap100 and kais, so feel free to submit any new unknown data <-- how do we submit that unknown data to know?
22:22.12cr2we can fix the hermes ATI driver, but it still will not be accelerated
22:22.24NetRipperi think noone is working on the hermes anymore
22:22.40cr2maejrep[w]: you can try to dump the values direcltly as we discussed
22:22.42NetRipperit's like a dead piece of hardware laying here
22:22.43NetRipper:P
22:22.55NetRipperthinking of letting my dad use it ;)
22:22.59cr2maejrep[w]: or i need to look at the 800 spl
22:23.09maejrep[w][15:28:30]  <cr2> the lower 2 bits are for pull, then come 4 bits for alt(func) and the remaining 4 bits are for drvstr <-- where are these set?  is it the same GPIOCFG address?
22:23.36maejrep[w]ok, where are the values found?
22:23.46cr2NetRipper: if the asic3_mmc will work in sdio infrastructure, we may fix the atiw_mmc. i have a lot of data
22:23.47*** join/#htc-linux adc (n=chatzill@80.175.184.123)
22:24.08NetRippercr2, for hermes you mean?
22:24.18NetRipperall i got hermes to do was boot to console and usb to it ;)
22:24.27cr2maejrep[w]: the value you write into CFG register is split into these pieces. so we can reimplement PCOM_GPIO_CFG now.
22:24.41NetRipperi have no clue about the hardware, it was a prebuilt package
22:24.41maejrep[w]that would be great if we could rewrite PCOM_GPIO_CFG properly :)
22:24.41NetRipper;)
22:24.41cr2maejrep[w]: for non-g1 wince devices.
22:24.51cr2NetRipper: yes, on hermes
22:24.57NetRipperok
22:24.58maejrep[w]cr2: that's great.  but how do we fit the 12 bits into it?
22:25.24cr2maejrep[w]: ?
22:25.43cr2maejrep[w]: it's only about the API
22:26.12cr2maejrep[w]: because we already know which value to write into CFG to get the required result
22:26.42maejrep[w]yes but the way we write CFG is gpio goes into byte 0, then cfg goes into byte 1
22:26.42cr2NetRipper: i'm more interested in athena, but it's the same ati chip.
22:26.52NetRipperah, ok
22:27.02maejrep[w]so if it takes 10 (sorry, 10 not 12) bits for config, where do the extra 2 bits go?
22:27.07NetRipperalso s3c244something cpu?
22:27.17cr2maejrep[w]: no. there are 2 separate 32bit registers
22:27.34maejrep[w]ohh
22:27.35maejrep[w]sorry
22:27.36maejrep[w]you're right
22:27.39cr2NetRipper: no, pxa270. but the same atiw228x video+sound+sd soc.
22:27.41maejrep[w]I was thinking they were 1 byte each
22:27.44NetRipperah ok
22:28.42cr2NetRipper: i think umts will be not a problem on hermes. it's only the ati SD that spoiled the whole game
22:28.43maejrep[w]so first register is gpio number (which only needs <1 byte, even though it gets 4 bytes?), then second register is 32 bits, of which we need 10 bits to do alt func, pull, and drvstr?
22:29.06cr212bit
22:29.08maejrep[w]which means we should change msm_gpio_set_function(), and instead maybe change msm_gpio_configure
22:29.10cr2!10
22:29.14maejrep[w]why 12?
22:29.16maejrep[w]4,4,2 ?
22:29.20maejrep[w]=10
22:29.30cr2hm, ok :)
22:29.34maejrep[w]lol
22:29.51cr2why. i think it was already done right ?
22:29.55maejrep[w]so change gpio_configure and add bitmasks
22:30.15maejrep[w]well, we did gpio_set_function() which takes gpio, func, out_en, op
22:30.22maejrep[w]but not pull or drvstr
22:30.42cr2maejrep[w]: PCOM_GPIO_CFG should call the old function by merging the appropriate bits
22:30.42maejrep[w]and we already have msm_gpio_configure, and can just insert the config into there for pull and drvstr ?
22:30.50maejrep[w]understood
22:31.13cr2func in this function is drvstr|alt|pull
22:31.45cr2or better ->
22:31.59maejrep[w]ok
22:32.11cr2CFG=drvstr<<6|alt<<2|pull
22:32.11maejrep[w]that makes sense
22:32.44maejrep[w]and then should we rename the function?  msm_gpio_set_function() is less meaningful now that we know how to use drvstr and pull with it
22:32.56maejrep[w]also, that means our alt settings were not working properly anyway :)
22:33.07maejrep[w]cause we were storing alt as alt<<0 not <<2
22:33.34*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
22:33.48cr2we used alt=drvstr<<6|func<<2|pull implicitly
22:34.25cr2it became a too academic discussion :)
22:34.29maejrep[w]lol
22:34.34cr2for most irqs you need CFG=3
22:34.48excoRogro82: your changes still aren't committed?
22:34.50cr2that means drvstr=0, alt=0, pull=3
22:34.53maejrep[w]got it
22:35.04*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
22:35.09maejrep[w]i thought alt was actual alt function, not cfg in general
22:35.12maejrep[w]makes sense now
22:35.16cr2so you only need to split the wiki values into driples
22:35.21maejrep[w]cool
22:35.22cr2s/dr/tr/
22:35.42cr2and let the PCOM_GPIO_CFG glue them back together
22:35.44maejrep[w]so, did we determine how to read those values from haret?
22:35.56cr2so you'll get the same result, but will also keep the g1 api
22:35.59maejrep[w]just pfw into reg1 the gpio number, then dump reg 2 ?
22:36.04maejrep[w]nice :D
22:36.45cr2disable interrupts, write the gpio number into reg1, and read CFG from rg2, enable interrupts
22:37.26cr2or somebody shall send me the blac100 wince nk.exe
22:37.42cr2so i can verify it.
22:37.58maejrep[w]ah, so would have to be done from linux then?
22:38.10maejrep[w]or is there a known way to do that ^ in haret? :p
22:38.26cr2you can do it in haret too
22:38.36cr2i'm mostly concerned about the interrupts
22:38.56cr2because you'll crash the device if you get interrupts in between
22:39.04cr2or may crash.
22:39.51cr2imho, setting the values need the cli/sti too
22:40.08cr2wince does it, and i think it's the right way :)
22:40.28*** join/#htc-linux psykhon (n=chatzill@host5.190-225-50.telecom.net.ar)
22:41.13maejrep[w]ok, I added spinlock to msm_gpio_set_function() in my checkout -- will get NetRipper a diff after adding in drvstr and pull
22:41.29maejrep[w]will also redefine PCOM_GPIO_CFG
22:41.45NetRippernot having spinlock caused the crashes?
22:42.13maejrep[w]that basically means that google's PCOM_GPIO_CFG uint64 numbers can be used in our regs too
22:42.15maejrep[w]just not via proc comm
22:42.29maejrep[w]which is super :)
22:42.30NetRippermaejrep[w], fyi, i rather have small patches than 'all at once' :) if possible of course
22:42.33NetRipper:)
22:42.48lupine_85do we have a signed-off-by: ? ;P)
22:42.51maejrep[w]NetRipper: lol sure ;p
22:42.58j0b0evening
22:43.00maejrep[w]you mean you didn't like my .27 patch that you asked for? :D
22:43.02NetRipperevening
22:43.31j0b0maejrep i have been hacking in your led driver a bit
22:43.33maejrep[w]NetRipper: I'll make it just the redefine of gpio_set_funtion
22:43.35maejrep[w]function*
22:43.35NetRippermaejrep[w], well, at least i lost some gray hairs because of it ;)
22:43.43*** join/#htc-linux TeringTu1y (n=maarten@195-241-125-243.ip.telfort.nl)
22:43.45maejrep[w]haha
22:43.51j0b0is the one in git recent?
22:43.56maejrep[w]j0b0: yes
22:44.23j0b0shall i put keyboard backlight and lis switch in the microp keypad driver?
22:44.32maejrep[w]i'd like to look at adding a led class driver soon as well
22:44.33cr2maejrep[w]: 64bit ?
22:44.41j0b0*lid
22:45.11cr2j0b0: backlight is a different driver class
22:45.14maejrep[w]cr2: PCOM_GPIO_CFG macro returns a uint64_t value, which is essentially the same structure (gpio number, drvstr, func, pull)
22:45.33imflofloyeahhh new rom from UDK R5 is coming :)
22:45.34maejrep[w]cr2: the keyboard backlight should be LED
22:45.36cr2maejrep[w]: redefine it to return int32
22:45.37maejrep[w]not LCD backlight
22:45.43j0b0the keyboard backlight is a led like home, send, ..
22:45.54j0b0its bit 0x4000
22:46.04maejrep[w]ok
22:46.04cr2maejrep[w]: why ? it may be the physical LED, but it's the backlight device.
22:46.17maejrep[w]but it's not a backlight device in the sense that you're thinking
22:46.28maejrep[w]the backlight class driver is for the backlight of the LCD panel
22:46.34cr2j0b0: ah, keybaord backlight
22:46.37maejrep[w]this is just lighting up the keyboard
22:46.38cr2yes.
22:46.43cr2ok
22:46.43j0b0yes, but i mean should the keyboard driver control the keyboard backlight
22:46.49cr2it's the same on universla
22:46.59j0b0or is that inappropriate and should we just expose it to the os
22:47.01maejrep[w]j0b0: did you verify that (0x4000)?
22:47.08j0b0yes. it works
22:47.10maejrep[w]I tried it and didn't get the result I was expecting
22:47.12maejrep[w]hmm
22:47.12cr2j0b0: imho it should not.
22:47.13maejrep[w]that's odd
22:47.27maejrep[w]for some people the gpio output worked, and i guess for you the 0x4000 bit works
22:47.30maejrep[w]but neither worked for me :/
22:47.37cr2maejrep[w]: there are some registers with bits.
22:47.55cr2the wince driver speaks about 'battery bit'
22:48.06maejrep[w]yeah, clearing the battery bit?
22:48.08maejrep[w]or something like that
22:48.11*** part/#htc-linux adc (n=chatzill@80.175.184.123)
22:48.38j0b0so i will have the keyboard driver report lid switch but not control backlight then
22:49.07maejrep[w]we should also let the stylus act as a switch
22:49.17maejrep[w]different SW_* but still via input
22:49.44j0b0i cant detect stylus
22:50.00maejrep[w]didn't mean in the same driver
22:50.02maejrep[w]just in general
22:50.04maejrep[w]as an input device
22:50.22*** join/#htc-linux MasteRTriX (i=ircap8@200.61.188.164)
22:50.25maejrep[w]can just pass it on to gpio_event_switch
22:50.44maejrep[w]it's a simple gpio + interrupt indicating whether stylus is in or out
22:50.46cr2j0b0: lid is a key event
22:50.56cr2of switch
22:51.10maejrep[w]cr2: yeah it reports EV_SW & SW_LID
22:51.18cr2ok
22:51.39maejrep[w]i wonder if there's a SW_PEN ;o
22:51.53lupine_85heh, would make life easier :p
22:51.58NetRipperim off for today, good night
22:51.59NetRipper:)
22:52.00cr2maejrep[w]: linux/input.h
22:52.09lupine_85night
22:52.30j0b0the navi driver might report the stylus, as it also does the volume up/down, and a REL_WHEEL
22:52.35cr2maejrep[w]: the last remaining big area is the lcd panel init ;) mostly epson
22:52.52maejrep[w]hmm
22:52.56maejrep[w]SW_TABLET_MODE ?
22:53.01cr2maejrep[w]: and a lot of minor driver software fixed.
22:53.18maejrep[w]cr2: i agree..  though I still can't get wifi to work either
22:53.27cr2like hardcoded 565 and 640x480 is many places. and hardcoded gpios and irqs
22:53.44cr2maejrep[w]: your spl does not have wifi control...
22:53.49maejrep[w]cr2: as I understand it, raph800 has a broken capabilities report
22:53.55maejrep[w]oh?
22:54.06cr2maejrep[w]: so you'd check the tiacx dll
22:54.12maejrep[w]what does that mean?  I need to turn off the WIFI_CONTROL option, and instead work with iwconfig ?
22:54.16maejrep[w]or am I confused
22:54.36cr2maejrep[w]: btw, the "oem" dlls on raph100 are not XIP
22:54.42maejrep[w]I didn't see a tiacx.dll..  Only TIWL1251 (or so)
22:54.51cr2yes,  this one
22:54.54maejrep[w]I don't know what XIP is either :p
22:55.06cr2eXecuteInPlace
22:55.14cr2rom module
22:55.14maejrep[w]hmm
22:55.20cr2can't be just copied
22:55.23cr2as a file
22:55.24maejrep[w]so what does that mean in my terms? :P
22:55.43cr2you can copy the .dll in a file manager
22:55.45maejrep[w]so they are not XIP, meaning they can be copied?
22:55.50maejrep[w]got it
22:55.51cr2yes
22:56.13maejrep[w]I wasn't able to copy smem.dll, which I was hoping would shed some light on smd
22:56.24cr2smem.dll is rom
22:56.38cr2and it does not have any device-dependent code
22:56.44cr2aka oem.
22:56.48maejrep[w]i see
22:57.03maejrep[w]ok helps explain some things :)
22:57.49cr2how many smd channels do we know ?
22:58.10cr2at=0,data=1,nmea=27 ?
22:58.20cr2what are the rest ?
22:58.26maejrep[w]everything gets auto-detected (about 5 channels on each device), EXCEPT channels 0 and 1 on 750x
22:58.32cr2there is one agps channel
22:58.50maejrep[w]we don't see the nmea channel on 750x either
22:59.01cr2check ril*
22:59.06cr2strange.
22:59.07maejrep[w]rilphone.dll ?
22:59.21cr2yes.
22:59.26maejrep[w]k
23:00.12maejrep[w]I can get channels 0 and 1 on 750x using vogue-smd-like code, but have not tackled that yet because it's going to need some ... "finesse" ;)  to be done right
23:00.14cr2is the ti1251.dll copyable ?
23:00.19maejrep[w]yes
23:01.11maejrep[w]I have it on my VM's desktop at home
23:01.27maejrep[w]dunno if I can mount a vbox disk image
23:01.29cr2maejrep[w]: do you mean that you have 24 vs 0x14 channel headers on CDMA ?
23:02.24maejrep[w]I have channel headers for data2, data5, data7, cs_m2a  (or something like that..  i don't have the exact names)
23:02.30cr2you can dump the 0x1f smem and pm it to me.
23:02.49*** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net)
23:02.52maejrep[w]can't connect to my phone from work (Mac OS X)
23:02.56cr2not the ascii names, but the pre-channel header
23:03.00cr2ok
23:03.02maejrep[w]but I have an old smem dump at home .. will copy them, sec
23:03.42lupine_85I have it here if you want it (the .dll)
23:04.06lupine_85runs it through iddadv
23:04.10lupine_85idaadv*
23:05.12maejrep[w]cr2: the names are part of the pre-channel headers
23:05.20maejrep[w]and that's how it auto-detects the channels
23:05.42maejrep[w]but channels 0 and 1 are not the same smd-style channel structure
23:05.57maejrep[w]there is no header, only a head and tail pointer, and the buffer itself
23:06.24imflofloon mac osx use missing sync to connect PDA
23:07.00maejrep[w]imfloflo: thanks.. does that work with RNDIS to allow TCP connections?
23:07.31imfloflodunno :p
23:07.34cr2maejrep[w]: it's still strange. g1 is CDMA after all
23:07.51MasteRTriXHello everybody
23:07.55maejrep[w]g1 is GSM
23:07.59maejrep[w]well
23:08.01maejrep[w]WCDMA
23:08.18MasteRTriXdoes anyone know if thereĀ“s a way to open a console on the booted android?
23:08.20maejrep[w]which is kind of in-between CDMA and GSM
23:08.51j0b0http://tibook.jb.b4m.com/j0b0/zImage-bklt-jobo <-- that kernel swithes the keyboard backlight when yuo open/close the slider
23:09.03MasteRTriXthe haret console closes when android boots
23:09.08j0b0on raph100, using LED 0x4000
23:09.52j0b0is it a gpio on raph800?
23:10.02cr20a1a1ac
23:10.15maejrep[w]j0b0: haven't figured that out yet
23:10.30cr2maejrep[w]: hm. right.
23:10.35maejrep[w]but I've tried i2cset with i2c-dev compiled in, and was not able to turn on the keyboard backlight via 0x4000
23:10.36excoMasteRTriX: http://code.google.com/intl/de/android/reference/adb.html
23:11.24MasteRTriXthanks.... I was looking in the wrong place with haret
23:11.26cr20x1e1d4
23:11.27MasteRTriX[exco]
23:11.46maejrep[w]imfloflo: I think that would only work for syncing
23:11.48cr20x1e1d4-0x1a1ac
23:11.56maejrep[w]and I really only want to connect for RNDIS
23:12.03maejrep[w]cr2: what are those?
23:12.25cr20x4028
23:12.32cr2<PROTECTED>
23:12.37cr2=0x2014
23:12.51cr2you have the 0x14 headers. like g1 and raph
23:13.08cr2so the vogue code should not work
23:13.19cr2raph100
23:14.45maejrep[w]no, the vogue code is correct based on my smem :x
23:14.47maejrep[w]http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/vogue-smd.c;h=0666ce5c067224d44e7baa372413969a20e86467;hb=refs/heads/htc-vogue#l736
23:14.49*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
23:15.28maejrep[w]g1 code does work on raph800 for *some* channels
23:15.35maejrep[w]but not for AT and SMD1
23:16.17maejrep[w]if you look at 0xf0000 and 0xf0200 in my smem dump, you can see the AT send and recv buffers
23:19.33cr2i see the sound data at 0xfd
23:20.33cr2yeah, and no header for at data
23:21.00cr2but the headers for other channels are there.
23:21.37cr2smd.dll should be different then
23:22.36maejrep[w]yes they are there
23:22.42maejrep[w]for other channels
23:22.50maejrep[w]just not for AT and data
23:22.54cr2the at rx has 0x400 size
23:23.03maejrep[w]no its 0x200 :o
23:23.03cr2but vogue also has a header
23:23.10cr2it's just different
23:24.19cr2ok, so it's the 512byte fifos
23:24.40maejrep[w]0xf0000 - 0xf01ff = AT RX, 0xf0200 - 0xf03ff = AT TX
23:24.44cr2ok, but then you need some irq  for the fifos
23:24.51cr22 irqs even
23:25.03maejrep[w]yeah, M2A_3 and 4 i think?
23:25.10cr2maybe
23:25.22maejrep[w]vogue uses channel_id + 3 (when id < 2)
23:25.26maejrep[w]so that means 3 and 4
23:25.40cr2blueangel used 2 512byte fifos for GPRS data
23:26.03cr2and athena has DPRAM with 2 512byte fifos.
23:26.09cr2so it's just different design
23:26.12cr2ok
23:26.23maejrep[w]http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/vogue-smd.c;h=0666ce5c067224d44e7baa372413969a20e86467;hb=refs/heads/htc-vogue#l63
23:26.43cr2but still you don't have the headers. afair kaiser has 24byte headers.
23:27.06maejrep[w]"head and tail at 0xf3fc8"
23:27.18maejrep[w]0xf3fc8, f3fcc, f3fd8, f3fdc
23:27.30maejrep[w]are head and tail of AT rx/tx and SMD rx/tx
23:28.02maejrep[w]and i've verified that it's the same on raph800
23:28.11cr2ok, but usually the header is just before the data
23:28.17cr2ok
23:28.19maejrep[w]right, but not here :P
23:29.08cr2but why NetRipper can't see the data channel ?
23:29.33maejrep[w]cause g1's smd_tty.c hard-codes the device node creation for only channels 0 and 27
23:30.00maejrep[w]tty_register_device(smd_tty_driver, 27, 0);
23:30.01maejrep[w]etc
23:30.11cr2and how does it handle the data channel ?
23:30.19maejrep[w]smd_tty
23:30.42maejrep[w]http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/smd_tty.c;h=020cb58dc27413c6431b6f72cc4035074696f553;hb=refs/heads/htc-vogue#l77
23:30.44cr2i mean channel 1
23:30.49maejrep[w]in the g1 code, that if block is not commented out
23:30.57maejrep[w]it doesn't, apparently .. :x
23:31.01maejrep[w]at least, not as smd_tty
23:31.12maejrep[w]smd_tty is only used for channels 0 and 27 in g1
23:31.34maejrep[w]maybe one of the other smd_*.c drivers
23:31.54cr2ok#define SMD_HEADER_SIZE 20.
23:32.08cr2the lcd is more important now
23:32.18maejrep[w]lol
23:32.50maejrep[w]looks like vogue has rpc working too
23:33.01maejrep[w]I'm sure a lot of that can be reused for us
23:33.10cr2yes
23:33.14maejrep[w]or rather, used as a guide to make rpc work in .27
23:33.15cr2and the sound too
23:33.36maejrep[w].27 uses a watchdog that (surprisingly) does manage to reboot my phone ;p
23:33.46maejrep[w]but it always reboots it so I had to disable it again
23:34.00maejrep[w]RPC is used for audio, right?
23:34.22cr2not only
23:34.35maejrep[w]right
23:34.37cr2audio needs some other things too. also proc_comm
23:34.45maejrep[w]ah
23:35.02maejrep[w]looks like smd_qmi is used for data connections
23:35.07maejrep[w]<PROTECTED>
23:35.27cr2isn't it in the newer amss only ?
23:35.53maejrep[w]I don't know
23:39.53*** join/#htc-linux cr2 (n=cr2@ip-90-186-237-11.web.vodafone.de) [NETSPLIT VICTIM]
23:39.57maejrep[w]cr2: looks like smd_qmi creates qmi0, qmi1, and qmi2 for data control
23:40.21*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
23:41.35*** join/#htc-linux hollo_ (n=hollo@3e6b025d.rev.stofanet.dk) [NETSPLIT VICTIM]
23:42.08maejrep[w]and looks like vogue's AudioPara.c just copies the tables from AudioPara*.csv files in wince
23:44.36*** join/#htc-linux hollo_ (n=hollo@3e6b025d.rev.stofanet.dk) [NETSPLIT VICTIM]
23:45.53cr2yes
23:46.35maejrep[w]ok, I'm heading home
23:47.16maejrep[w]will get a patch to NetRipper with the PCOM_GPIO_CFG fixes
23:50.27*** join/#htc-linux Shinto (n=John@g227195091.adsl.alicedsl.de)
23:54.37*** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net)

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