IRC log for #htc-linux on 20090131

00:04.08*** join/#htc-linux myxor (n=myxor@pdbn-4d089c45.pool.mediaWays.net)
00:04.19*** part/#htc-linux Jon_ (n=Jon@93-97-203-170.zone5.bethere.co.uk)
00:08.33*** join/#htc-linux gh0ul (n=asds@host81-157-60-163.range81-157.btcentralplus.com)
00:08.35*** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net)
00:18.48*** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com)
00:21.01*** part/#htc-linux nashpa (n=dliviu@dliviu.plus.com)
00:29.43*** join/#htc-linux ppman (n=mkern@pool-70-111-252-30.nwrk.east.verizon.net)
00:29.53ppmanhiya
00:30.16ppmanon kaiser, how do I tell the difference between winmo and the hardware calling I2C?
00:36.19ppmanhttp://omploader.org/vMTZ3dw
00:36.27ppmanlook at all the I2C stuff,
00:36.31ppmanabout every 10 seconds
00:38.17*** join/#htc-linux sdt555 (n=titus@70.114.152.91)
00:40.41cr2ppman: you need 0 and c
00:47.30cr2good night
01:51.34ppmancr2: what was that?
01:51.52ppmanI got all the bytes related to I2c in that command, right?
01:51.59ppmanoh wait
01:52.03ppmanhe disconnected :(
02:11.22dream_killppman u seen what i posted about battery?
02:11.31ppmannope
02:11.33dream_killhttp://pastebin.com/d51a868fa
02:12.05ppmanwhat is that?
02:12.43ppmanwhat language is that?
02:12.50dream_killbattery stuff from diamond/raphael :P
02:12.52dream_killc:P ?
02:13.02ppmanit *almost* looks like c...
02:13.07dream_killvisual c :P
02:13.11ppmanewwww
02:13.18ppmanbut raph/diamond doesn't help me
02:13.33dream_killshould be similar in kaiser!
02:13.43ppmanmsm7x00A uses proc_comm/ read from memory
02:13.57ppmanmsm7x00, the arm9 doesn't read battery status
02:14.59ppmankaiser's battery driver reads the ds2746 directly in wince
02:15.00dream_killSmem batterry id
02:15.00dream_killyes?
02:15.00ppmanthere's no battery stuff in shared mem on kaiser
02:21.16*** join/#htc-linux ALoGeNoff (n=alogeno@137.pool85-60-2.dynamic.orange.es)
02:23.01dream_killppman did u check priv?
02:23.06ppmanpriv?
02:23.33dream_killon irc
02:23.39dream_killi sent u a query
02:23.50ppmanpriv is a user?
02:24.29dream_killwhat do u use for irc conenction?
02:24.41ppman(I really should use IRC more often, but I don't - I don't know the lingo/anything else)
02:24.44ppmanusing irssi
03:07.25*** join/#htc-linux ALoGeNo (n=alogeno@137.pool85-60-2.dynamic.orange.es)
03:25.07ppmanon kaiser, how do I know whether the USB or the AC is plugged in?
03:29.35ppmanwait... do I need to know that?
03:29.48ppmanthe hardware handles fast vs. slow, correct?
03:43.58tmztppman: mmutrace to see what ce does
03:46.30ppmantmzt: I can only find the difference between chrging and not
03:46.52ppmanI'm running android w/o a battery driver with the USB plugged in atm
03:46.56tmztsorry I meant to paste that earlier
03:47.07tmztwhat are you trying to do?
03:47.09tmztwith i2c
03:47.19ppmantalk to the ds2746
03:47.23ppmanthe battery chip
03:48.47tmztyeah that's going to you about the battery not the charging I think
03:49.32ppmanI see a bunch of traffic on  0xa9900000 and friends every ten seconds
03:49.58ppmanthat and a comment I saw in battdrvr.dll suggests the os is reading the chip directly.
03:56.12ppmanschweet - I don't have to tell it which type of chrge it's doing.
04:24.18*** join/#htc-linux ppman_ (n=mkern@pool-70-111-215-98.nwrk.east.verizon.net)
04:39.24*** join/#htc-linux ALoGeNoff (n=alogeno@137.pool85-60-2.dynamic.orange.es)
05:00.56*** part/#htc-linux sdt555 (n=titus@70.114.152.91)
05:06.17*** join/#htc-linux Dan__ (n=chatzill@cpe-74-69-91-35.rochester.res.rr.com)
06:02.11*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net)
06:03.23*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
06:55.40*** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com)
07:26.10ALoGeNomorning
07:26.37ALoGeNonice news for mp900c and 2.6.28 kernel :)
07:26.57ALoGeNowe have basic support for the MobilePro 900/c mini-laptop
07:26.58tmztwhat news?
07:27.11tmztvideo/keyboard?
07:27.16ALoGeNohttp://kernelnewbies.org/Linux_2_6_28#head-44ac0f9cb64e8495d6cd5a3fc4dafc744fb93f5a
07:27.18*** join/#htc-linux Zoolooc (n=lucian@nrbg-4dbfd174.pool.einsundeins.de)
07:27.22ALoGeNoi dunno :P
07:28.40ALoGeNoand hello tmzt :)
07:28.53*** join/#htc-linux tcccp (i=hey@ballbreaker.hey-ix.net)
07:29.57ALoGeNoi go try now to compile the 2.6.28 with mp900default_config or so..
07:31.05ALoGeNohey you seen goboxlive in this days over here tmzt ?
07:31.27ALoGeNothe uni still stoped :/
07:32.19tmzt~seen goxboxlive
07:32.44aptgoxboxlive is currently on #htc-linux (37m 4s) #handhelds (37m 4s) #openmoko (37m 4s) #opie (37m 4s), last said: 'hi cr2 . What device are you working on these days'.
07:32.45goxboxlivehi tmzt
07:32.50tmztslow
07:32.51ALoGeNoheyyy
07:32.52ALoGeNoxD
07:32.56ALoGeNois here !
07:32.56ALoGeNoxD
07:33.12tmztthere's still an opie?
07:33.36ALoGeNowhat do you mean?
07:33.52goxboxlivehttp://opie.handhelds.org - Opie 1.2.4 is out!
07:34.04ALoGeNowow!
07:34.07tmztwhat qtopia or qt/e is that?
07:34.25ALoGeNobut is a new uni kernel with that??
07:34.26tmztopie logo was the nicest thing to possibly see after switching from sharp rom
07:34.29ALoGeNoO_O
07:35.13goxboxliveafar qt-2.3.10
08:05.35*** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca)
08:22.22*** join/#htc-linux Sti_0239 (n=Where_is@127.185-65-87.adsl-dyn.isp.belgacom.be)
08:40.21*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
08:50.42*** join/#htc-linux kiozen (n=oeichler@BAH49d7.bah.pppool.de)
08:55.31*** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net)
09:13.07*** join/#htc-linux cr2 (n=cr2@ip-90-186-23-128.web.vodafone.de)
09:21.42*** join/#htc-linux Jon__ (n=Jon@93-97-203-170.zone5.bethere.co.uk)
09:31.58*** join/#htc-linux Jon___ (n=Jon@93-97-203-170.zone5.bethere.co.uk)
09:57.33*** join/#htc-linux Moonlit (i=mooonlit@mario.dreamhost.com)
10:00.09*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-0d229978fbfd257c)
10:05.36*** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net)
10:13.02cr2hi
10:13.16cr2looking for some non-A people
10:16.21*** join/#htc-linux Xime (n=xime@bankize.net)
10:19.42*** join/#htc-linux metter (n=metter@137-171.62-81.cust.bluewin.ch)
10:22.38Moonlitnon-A?
10:22.42Moonlit(hi, btw)
10:23.11BabelOmsm7200 not ùsù7200A
10:23.38BabelOhi
10:23.38BabelOhi cr2
10:23.38Moonlitoh, gotcha, I'm actually just idling to try and learn something
10:23.49Moonlitunfortunately I know nothing about any of this stuff but it does interest me, and you guys are awesome :P
10:25.30cr2hi BabelO
10:25.37cr2Moonlit: which cpu do you have ?
10:26.51Moonlituh... you know, I couldn't tell you, what I can tell you is that I have a GSM Kaiser (kais130)
10:27.15cr2ok, it's a non-A cpu :)
10:27.35Moonlittakes notes
10:27.46cr2do you know to to telnet to haret ?
10:28.20MoonlitI'd probably have a rough idea, but sadly my USB socket's borked and I haven't fixed it yet
10:28.34cr2wifi ?
10:28.38Moonlitdoh
10:29.03Moonlitwas thinking of connecting via a serial terminal emulator
10:29.19Moonlityou'll have to give me a while to catch up here :P
10:29.26Moonlitbut yeah
10:29.28MoonlitI can do that
10:30.24*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
10:31.01cr2kais does not have a serial port.
10:31.30Moonlitnah, I'm new to HTC phones, I'm used to phones having serial via usb cables
10:31.44Moonlitso it's taking a little adjustment :P
10:34.57cr2there is serial over usb here too
10:35.14*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
10:35.38MoonlitI can't imagine needing it all that much though
10:35.54Moonlitconsidering these phones have connectivity out the wazoo
10:36.56Moonlithrm, so this is what telnetting to haret's like
10:37.15Moonlitguess I wouldn't have expected anything different, I just didn't realise you could telnet to it
10:42.56MoonlitI'd admit that I'm sitting here turning the LCD on and off via telnet, but I'd feel like a 5 year old in here lol
10:45.34cr2type
10:45.54cr2pd 0xa8600000 0x100
10:46.26cr2like at the bottom here :
10:46.30cr2http://wiki.xda-developers.com/index.php?pagename=MSM_CLK
10:46.30Moonlithang on, resetting, got the LCD stuck off >_>
10:47.44MoonlitSDC2 Md?
10:49.00Moonlitok, that gave me some garbage that I can only imagine means something more to you than it does to me
10:50.04Moonlityou want the result pastebinned?
10:54.59cr2yes
10:57.53Moonlithttp://slexy.org/view/s21UAWjva5
11:00.54cr2thanks, it looks good.
11:01.26Moonlitwell, I wouldn't put it up on my wall, but I'll take your word for that ;)
11:02.12Moonlitbut uh... I gather that's a dump of something specific, what's that address range for?
11:02.20*** join/#htc-linux Skitzo (n=DCLXVI@eth582.vic.adsl.internode.on.net)
11:02.46cr2MSM_CLK
11:02.59cr2the internal clock setup.
11:03.17Moonlitoh, heh, I guess that makes sense when you look at it
11:03.22cr2it is documented here http://wiki.xda-developers.com/index.php?pagename=MSM_CLK
11:03.23Moonlitwhat with the CLK in the name and all
11:04.17Moonlityeah, I did look at that page but it didn't make a huge amount of sense to me, though I'd gathered it had something to do with timing, given that it's SDC2 Md (where M is multiplier and d is PWM duarion)
11:04.31Moonlitwhen I say I'm new to this, I mean I'm *really* new to this
11:05.19Moonlitmy experience with Linux is minimal, my coding experience is pure Visual Basic (and the predecessors thereof) and I only just got this Kaiser
11:05.26Moonlitso all in all, I'm pretty clueless lol
11:06.23Moonlitbut hey, if there are moments where I can learn and/or contribute then I'm pretty happy to hang around
11:11.49cr2ok, then it will take too long to explain :)
11:12.25Moonlityeah, no biggy, I just pick up things as I go along, it'll probably make sense soon enough :)
11:25.15*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
11:25.58*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
11:32.27*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-15d7521ba7bc0446)
11:37.06*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-e2bfa3fd6929b0bd)
11:38.50*** join/#htc-linux Untouchab1e (n=Untoucha@cm-84.209.89.86.getinternet.no)
11:38.54Untouchab1eGood afternoon! :)
11:38.58Moonlitaf'noon
11:39.03Untouchab1ehow's it going?
11:39.08Moonlitit's good, you?
11:39.16Untouchab1enot too bad :)
11:39.23Moonlitgood good :)
11:39.54Untouchab1eUp to anything special?
11:39.59Untouchab1eor just hanging out? :)
11:40.07Moonlitnah, not really, just hanging out :)
11:40.39Moonlitjust kinda watching this channel, thought maybe I'd learn something lol
11:40.49Untouchab1e:)
11:40.57Untouchab1eits a good place to learn, thats for sure ^^
11:41.32Moonlityeah, well I kinda mentioned earlier that I'm totally new to pretty much all this stuff, since I can't really code and my Linux experience is limited
11:41.54Moonlitbut I've already figured out Git and how to compile a kernel, which is good progress I think :)
11:42.01Untouchab1eAbsolutely ;)
11:43.36MoonlitI have to say, embedded Linux is much easier to deal with as a user than "desktop" Linux
11:44.05Untouchab1eheh, I see what you mean
11:44.16MoonlitI mean I guess it has to be in order to be usable, but it's definitely a positive thing
11:45.09Untouchab1eyeah
11:45.57Untouchab1eIm still more comfortable in a Windows environment. Mostly because I'm a Windows developer (.NET), but I still love Linux
11:46.16Moonlityeah, I'm a Windows guy, I've done some VB.net stuff
11:46.36MoonlitI do like Linux and I want to be able to use it, it just isn't there for me yet (on the desktop at least)
11:47.24Untouchab1eheh.. to be honest, most of my problems with Linux has almost always been Compiz's fault
11:48.10MoonlitI just get the little niggly stuff, stuff not always working how I want or occasionally malfunctioning for no reason
11:48.43Moonlitand tbh another reason I prefer the idea of embedded Linux is the UIs in a lot of the desktop Linux world leave a lot to be desired
11:49.10cr2Moonlit: do you have a bt headset ?
11:49.18Moonlitnope, not yet anyway
11:49.29Untouchab1eI have one.. but I dont have it on me atm
11:49.38Moonlita lot of use we are, eh? lol
11:49.42Untouchab1ehaha
11:49.51Moonlit"not yet" and "not with me" :P
11:50.19cr2ok
11:52.55Untouchab1ehaha
11:53.10Untouchab1eMy point being, I will have access to mine on sunday
11:54.47Untouchab1eI need some brainstorming help here btw..
11:54.56Untouchab1eIm working on my HTC Android Config tool..
11:55.25*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
11:55.34Moonlitnice idea
11:55.42Untouchab1eyeah, the first version is already released.. but
11:56.11Untouchab1eand someone over at XDA suggested implementing a check for newest Android builds for the Raph and Diam (which I host).. Now, I am stuck with the dilemma of either implementing a direct download feature. kinda like (download the latest version now). or just a simple check that reports which version is the newest one
11:57.13Untouchab1eon one hand, its handy to just being able to download the latest build from the app, but on the other hand, by saying "Hey, its a new build out, wanna go and get it?" will send them to the download page on my site where they can also read up on the changelog and usage instructions
11:59.07Moonlityou could give both options
11:59.18Moonlita "download now" and a "read more"
11:59.36Untouchab1eHmm, yea
11:59.38Untouchab1eyeah*
12:04.39Untouchab1eFor some reason, I didnt think of that ^^
12:08.01Moonlitsometimes it's the simple things :)
12:11.16Untouchab1eyeah, very true
12:11.16cr2a dumb question here
12:11.20Untouchab1eshoot
12:11.45cr2are there any miniUSB stick available ?
12:11.55Moonlitnot that I'm aware of
12:12.01cr2me too
12:12.28Moonlityou could use an adapter I guess if a device was capable of being a USB host
12:12.33Untouchab1ehmm, you mean like miniUSB sticks that would be able to act as a memory card for mobile devices or something?
12:12.44cr2yes
12:12.54cr2i have not seen them too
12:12.57Moonlitit'd be a little inconvenient though
12:13.11cr2why ?
12:13.31Moonlitwell, compared to a microSD it'd be awkward
12:13.32Untouchab1ewhy not use a regular microSD card?
12:13.34Untouchab1ehehe
12:13.52Moonlithaving things hanging off your device is never particularly fun
12:13.59cr2i have a microSD-USB-B adapter
12:15.02cr2it seems that raph100 supports miniUSB stick, but the details should be sorted out
12:15.29cr2hanging ? it'll be just a mini instead of a normal USB
12:16.22MoonlitI dunno if we're thinking the same thing, I'm imagining a USB stick with a miniUSB plug on it instead of a normal USB plug
12:16.30cr2i must have a miniUSB-A cable somewhere
12:16.32Moonlitwhich you'd plug into the USB port on a phone or whatever
12:16.51cr2Moonlit: exactly.
12:16.59cr2but i've never seen it
12:17.18Moonlitwell I can see how it could be useful but I've never seen or heard of them existing
12:17.32cr2probably because there are no miniUSB hosts ?
12:17.38Moonlitwould make sense
12:17.57MoonlitI think microSD would make them kinda redundant though
12:18.20cr2diamond does not have microSD
12:18.26Moonlitfair point
12:18.36cr2but may have usb otg
12:18.58cr2at least it seems that raph100 has it
12:19.05Moonlithrm, I see where you're going now, I hadn't considered the lack of a microSD slot
12:22.44cr2http://forum.xda-developers.com/showthread.php?t=411905
12:23.58Moonlitthat's an idea I had a while back, jagnet mentions a device that allows you to access USB sticks via bluetooth
12:24.08Moonlitthat could be another option for phones without microSD
12:24.44Moonlitthe host thing sounds interesting though
12:31.36cr2http://www.willcom-fan.com/wzero3/entries/mobachiki/000380/03.jpg
12:33.52cr2but i think we don't have an msm-ohci driver ?
12:39.52cr218bit lcd
12:40.53swetlandehci
12:44.57Untouchab1eOk, updated the app now :) 0.4.. added a "latest build" checker
13:00.39cr2swetland: ehci driver is in the tree ?
13:01.15cr2this h2w port seems to be misused in all possible ways.
13:01.37cr2audio,video,rs232...
13:02.24cr2at least we know the gpio alt setting for ehci now.
13:10.40*** join/#htc-linux ALoGeNoff (n=alogeno@137.pool85-60-2.dynamic.orange.es)
13:19.45*** join/#htc-linux exco (n=exco@e181118017.adsl.alicedsl.de)
13:41.34dcordesaye
13:42.39excodo you have a parrot on your shoulder?
13:47.13cr2dcordes: i have cleaned up the MSM_CLK
13:47.13Moonlityarr?
13:47.25cr2do you have a bt headset ?
13:48.07cr2polaris_cpld page does not exist ?
13:52.06excocr2: no
13:52.39excobut if you tell me how to get the affected data - I can create it
13:53.00*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-fbd362c453364822)
13:54.07excoYou can access my Polaris through haret if you want
13:57.05cr2exco: copy the kaiser_cpl page, but remove all the descriptions
13:57.19cr2exco: do you have a bt headset ?
13:58.01excocr2: unfortunately just sold mine
13:58.19Moonlitlol, you'd think someone would have a headset, right?
13:58.37excoany reason for "_" instead of "space" in wiki pagenames?
13:59.53excoI have the E100 headset (don't think that helps)
14:03.39cr2exco: %20 is ugly
14:04.11cr2my bt headset is too far away
14:04.33cr2because i never use it ;)
14:04.58excothere are 2 pages for titan cpld http://wiki.xda-developers.com/index.php?pagename=Titan_CPLD http://wiki.xda-developers.com/index.php?pagename=TitanCPLD (also the second one says vogue cpld)
14:05.04exco*although
14:14.21cr2hehe
14:14.25cr2401         /* 0x32 normal, 0x50 for Toshiba display */
14:14.26cr2402         mddi_writel(0x0050, DRIVE_LO);
14:14.53cr2raph100 and blac100 have 0xd0, raph800 has 0xa0
14:16.29cr2409         /* disable periodic rev encap */
14:16.29cr2410         mddi_writel(MDDI_CMD_PERIODIC_REV_ENCAP, CMD);
14:16.29cr2not on wince
14:16.48*** join/#htc-linux pH5 (n=ph5@e178237090.adsl.alicedsl.de)
14:17.27cr2420         /* Recommendation from PAD hw team */
14:17.27cr2421         mddi_writel(0xa850f, PAD_CTL);
14:17.34cr2only on raph800
14:17.46cr2raph100 and blac100 have 0xa8505
14:18.05excocr2: http://wiki.xda-developers.com/index.php?pagename=Polaris_CPLD
14:23.18tmztcr2: got some data from lama for i780, the framebuffer is 320x320x16 and is the pxafb address, writing to it in haret works
14:24.13tmztharet/haretconsole don't support pxa3xx, I was able to trace the matrix keyboard registers and got some activity there on keypress, but nothing on i2c (optical mouse maybe)
14:25.02cr2tmzt: there are no pxa3xx docs ? only the linux kernel source ?
14:25.25tmztI used kernel source, marvell might have them somewhere, I didn't look
14:25.26cr2tmzt: where is the fb located ?
14:26.15cr2exco_: does the current code use cpld on polaris ?
14:26.37tmzt00:21 <tmzt> HaRET(1)# print "%08x" VRAM
14:26.38tmzt00:21 <tmzt> bc8c0000
14:27.10cr2tmzt: i'm not familiar with the pxa3xx memory map
14:27.17cr2is it sram ?
14:27.32tmztI didn't try the sd card gpio because the gpios var was empty, I addlisted the linux headers values once but forgot to the last time
14:27.42cr2the sdram is at 0xc afair, like on the sa1100 ?
14:27.50tmztI'm not sure how haretconsole detects the device
14:28.05tmztfrom the haret session
14:28.18cr2through the list
14:28.41cr2do you have the earlyharetlog ?
14:28.48tmzt01:27 <tmzt> 8b200000  | 44000000 |   1MB section | CB AP=1
14:28.49exco_cr2: you'd need to ask Rogro82 about that (or dcordes) - because his changes aren't committed yet
14:28.49tmzt01:27 <tmzt> ab200000  | 44000000 |   1MB section |    AP=1
14:28.49tmzt01:28 <tmzt> HaRET(14)# pd 0x44000000 0x14
14:28.49tmzt01:28 <tmzt> 44000000 | 03b008f9 17173d3f 0301053f 04f0000c | ....?=..?.......
14:28.52tmzt01:28 <tmzt> 44000010 | 8400fe92                            | ....
14:28.54tmzt01:28 <tmzt> that should be it
14:28.57tmztno
14:28.58cr2exco_: ok
14:29.07tmztask lama for that I only have some haretconsole logs
14:30.49cr2ok
14:30.50tmzt00:27 <tmzt> ========  Connecting to haret  ========
14:30.50tmzt00:27 <tmzt> Minimal virtual address: 00010000, maximal virtual address:  7FFFFFFF
14:30.54tmzt00:27 <tmzt> Detected machine Default/generic (Plat='PocketPC' OEM='SGH-i780')
14:30.57tmzt00:27 <tmzt> CPU is Intel ARM arch 5TE revision 2 product 9 stepping 1 running  in system mode
14:31.17cr2that's enough
14:31.41tmzthow?
14:31.56cr2but you need to modify the mach-pxa.cpp
14:32.23cr2enough to assign a pxa3xx cpu to it
14:33.03cr2this virtual address range message is really useless
14:33.57tmztso the sram is important because it needs noncontig patches?
14:34.15cr2not really
14:34.22cr2just it's faster than sdram
14:34.38cr2pxafb will be happy using sdram for fb
14:35.06tmztok, a virtual write to that framebuffer drew on the screen and we have the timings (lccr's) posted above (the pd)
14:35.19cr2tmzt: maybe if we will setup pmdh as in wince, the hw refresh will work again ;)
14:35.28cr2linux != android os.
14:35.33tmztah
14:35.46dcordesexco_: no the parrot.. he left me
14:35.58tmzthave you been able to dump pmdh regs?
14:36.02tmztdcordes !!!
14:36.38dcordesme?
14:36.49cr2tmzt: if the subsystem addresses are the same as on pxa27x, you can try to run my old px27x parser
14:37.16cr2aka haret-w.exe
14:37.28dcordescr2: got no bt headset
14:37.33tmztI have a dumper somewhere
14:37.39dcordesbut I can lend one
14:38.40cr2dcordes: i'm interested in the MSM_CLK area 0x100 dump with BT headset playing  sound, or phone talking
14:38.55tmzthsuart?
14:39.27cr2tmzt: that's the question
14:39.43tmztnot i2s with the bt chip?
14:39.45cr2tmzt: there is some other bt audio related gpio alt config.
14:39.53cr2afaik no.
14:39.56dcordesI thought kaiser bt is no uart
14:40.23cr2bt audio should use some other pcm port
14:40.31cr2not uart.
14:40.43tmztok, but if it's pcm why does it need hs-uart?
14:40.59cr2control line
14:41.08cr2to send bts commands
14:41.36cr2i've lost my raph headset somewhere, can't test fm too ;)
14:41.37tmztI see this as the problem android had, they want to implement a2dp with audioflinger
14:41.57tmztso this clk would be for the uart2dm also, even if not in high speed mode?
14:42.03cr2no
14:42.12cr2the uart2dm clocks are known.
14:42.17*** join/#htc-linux ALoGeNo (n=alogeno@137.pool85-60-2.dynamic.orange.es)
14:42.48tmztyou figure out the clk grp?
14:43.19dcordescr2: when I got the bt and audio is active on it, what command must I run?
14:43.20cr2yes, but it is also doing some scary stuff at +0x2xx
14:43.35cr2dcordes: pd 0xa8600000 0x100
14:43.39dcordesok will do
14:44.03*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
14:44.07cr2tmzt: check the MSM_CLK wiki page
14:44.58Moonlityou must get sick of typing that lol
14:46.12tmztdo you know where to dump the h3wd area?
14:48.01cr2Moonlit: it's a bit cryptic page, i know :)
14:48.29cr2tmzt: i'm not concerned about the hw3d now.
14:49.44cr2tmzt: it's a separate project, that includes disassembling g1 binaries
14:50.26cr2tmzt: i want to get the working and suspending/resuming framebuffer device. and autorefreshing too ;)
14:50.28tmztyeah, I'm just wondering about the register space and grp clk
14:51.30*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-7c25bed5b989d0fb)
14:51.38cr2tmzt: mdp ?
14:52.03tmztno, whatever the linux hw3d exposes
14:52.32cr2#define MDP_TV_OUT_CTL                   ( 0xc0000)
14:52.50cr2need a tvout cable for it though ;)
14:52.54cr2ok
14:53.02tmztshouldn't that be on a seperate chip?
14:53.14cr2msm has tvout
14:53.28imfloflohey guys do you try to search on google anything and click on the first link
14:53.31cr2don't now where is the encoder
14:53.37*** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net)
14:53.47tmztit doesn't use the epson/toshiba for that? I thought the pdf pretty much confirmed it
14:54.06tmztthe two page one from epson I mean
14:54.10cr2hm. g1 does not have tvout
14:54.23*** join/#htc-linux exco (n=exco@e181118017.adsl.alicedsl.de)
14:54.26cr2yeah, a full datasheet will be nice
14:54.35cr2epson also has PiP
14:56.04tmztnot sure it matters but I enabled the pxa overlay on my q kernel and it caused some corruption. this could apply because they are working on simplyfing support for overlays and other multiple framebuffer devices if we ever wanted picture-in-picture or something else to work
14:56.32cr2it's hardware pip
14:59.32tmzt#define HW3D_REGS_LEN 0x100000
14:59.56tmztyeah, that's hardware too but they decide to use multiple framebuffer memory devices in this version of the driver
15:00.17tmztit even has yuv support on one of the overlays apparently
15:01.14tmzthah, static struct clk *grp_clk/*imem_clk are both in mach-msm/hw3d.c
15:02.05excocr2: I didn't notice - Rogro's changes have been committed 16h ago.
15:02.15cr2raph manual says that the lcd is 666, but wince supports only 565
15:02.27tmzt18-bit?
15:03.11cr2yes
15:03.35cr2but you probably need to send some spi commands to configure it.
15:03.54cr2but not on raph100 it seems
15:05.04tmztit has pmem_pdata for bot pmem_gpu0 and pmem_gpu1
15:05.28tmzts/bot/both/
15:05.51cr2what is gpu0 ?
15:05.52tmzt0x00000000 0x00700000 what??
15:06.04*** join/#htc-linux foobarman (n=foobarma@81.193.82.81)
15:06.12cr2raph manual says 32MB sram
15:06.24cr2that's tricky
15:06.25tmztgpu1: MSM_RAM_CONSOLE_BASE-MSM_PMEM_GPU1_SIZE
15:06.38*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
15:06.41tmzthow can gpu0 base be at 0x0?
15:06.44cr2i need to find a portable way to detect the sram size.
15:06.53miknixwhat the heck
15:06.55cr2why not
15:07.04tmzthttp://android.git.kernel.org/?p=kernel%2Fmsm.git&a=search&h=android-msm-2.6.27&st=grep&s=MSM_PMEM
15:07.07miknix"This site may harm your computer."
15:07.11tmztnot sure how to do that
15:07.12cr2spl is preserved only on wince
15:07.24tmztmiknix: lama said something similar
15:07.26miknixis it only me or Google searches are filtering every single result?
15:07.55cr2miknix: works for me
15:08.07miknixstrange
15:08.12tmztlama: hi
15:08.25cr2miknix: but i've seen such things on other computer
15:08.35cr2and thought, wtf ?
15:09.26cr2miknix: you have an msm device now ?
15:09.39miknixnot really, why?
15:09.43*** join/#htc-linux patoche (n=patoche@lns-bzn-58-82-251-208-84.adsl.proxad.net)
15:09.52miknixfunny: http://pastebin.com/d2b871015
15:10.05cr2you search fr msm-related things :)
15:10.15lamawell
15:10.19lamawhole google is borked
15:10.26lamano matter what you search
15:10.29*** join/#htc-linux MethoS- (n=lem@host-091-097-242-061.ewe-ip-backbone.de)
15:10.33lamaeven their own sites are badware :P
15:10.34excohttp://www.google.com/interstitial?url=http://www.microsoft.com/windows/windows-7/beta-download.aspx
15:10.34excoWarning - visiting this web site may harm your computer! - *harrharr*
15:10.41cr2lol
15:10.48Moonlithehe, was just talking about that in another channel
15:11.10cr2Or you can continue to http://www.microsoft.com/windows/windows-7/beta-download.aspx at your own risk. For detailed information about the problems we found, visit Google's Safe Browsing diagnostic page for this site.
15:11.19tmztso framebuffer has same address as GPU1?
15:12.04cr2tmzt: on g1 ?
15:12.05lamatmzt: are you going to compile test kernel for i780?
15:12.05tmztanyway this is about grp clk, if you have that working I guess we don't need this
15:12.06miknixcr2, heh! Just checking out Google was not tagging "linux" only searches
15:12.12tmztin android kernel (for g1)
15:12.17lamaI don't have tools, and... skills :P
15:12.43cr2tmzt: NetRipper uses a different memory layout.
15:13.07tmztwould the trout one work?
15:13.32cr2need to ask NetRipper
15:13.44tmztI'm hoping to see if someone can try a JesusFreke image extracted from yaffs2, for testing maejrep's wifi support
15:13.51cr2but you must be sure that you have 64MB smem first
15:14.05tmztah, so it won't work on raphael?
15:14.35cr2tmzt: the raph800 spl does something to detect 32 vs 64
15:15.58tmztI assume maps of pmem devices use the physical addresses so that will break on raph with NetRipper map
15:16.20tmztdo you know what clk_imem is?
15:16.31cr2no
15:16.44cr2i get exception reading from 0x02000000
15:16.59tmztit's disabled when gpu is in android kernel
15:17.00cr2but it may be MPU, who knows
15:17.08cr2in wince
15:17.20lamahttp://www.smh.com.au/news/technology/biztech/relief-for-those-caught-by-street-views-dunny-deal/2009/01/29/1232818599129.html
15:18.05cr2because i can't read the amss area too
15:18.18cr2it was possible on titan, btw ;)
15:18.55tmztwhat are you trying to read?
15:21.00cr2tmzt: ram
15:21.09cr2lama: lol. image of a man in Spain who flipped his middle finger at a passing Google car.
15:21.14tmztI mean why that address
15:21.27miknixInternet is fixed now
15:23.26excomiknix: was it broken?
15:23.37Moonlityeah, google went boom
15:23.39tmztcr2: INT_GRAPHICS?
15:23.53miknixGoogle IS the Internets :P
15:23.55excoso google == internet?
15:23.59cr2http://images.smh.com.au/ftsmh/ffximage/2008/11/18/gmaps_bird_spain_gallery__554x400.jpg
15:24.00tmzthttp://android.git.kernel.org/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/hw3d.c;h=b013b57077af9c60f1728f0f65e0494be6c5ff7
15:25.39*** join/#htc-linux Mullins (n=bw@89.204.239.174)
15:27.08cr2tmzt: it_graphics is known
15:27.39excogotta try Win 7 ... bbl (hopefully)
15:28.21tmztmissed one, pdata in the h3wd.c driver itself
15:28.53tmzth3wd 0xA0000000 0x1000000 .cached = 0 (something in the memory controller)
15:28.54cr2179 static struct android_pmem_platform_data pmem_data = {
15:28.55cr2180         .name = "hw3d",
15:28.57cr2181         .start = 0xA0000000,
15:28.58cr2182         .size = 0x100000,
15:28.59tmztyes
15:29.07cr2is it virtual of physical address ?
15:29.13*** part/#htc-linux exco (n=exco@e181118017.adsl.alicedsl.de)
15:29.14cr2s/of/or/
15:29.26tmztthis is all phys that I know of (pmem)
15:29.35tmztpmem is physical version of /dev/mem
15:30.00*** join/#htc-linux pH5 (n=ph5@e178237090.adsl.alicedsl.de)
15:31.32cr25c000000 | a0000000 | Extended (4K) |    AP=3
15:31.34cr2<PROTECTED>
15:31.35cr291b00000  | a0000000 |   1MB section |    AP=1
15:31.37cr2b1b00000  | a0000000 |   1MB section |    AP=1
15:31.38cr2H
15:33.01tmztonly 1mb?
15:33.05cr2ok, it's not in the raphaelmemorymap
15:34.19cr2no, it's included
15:34.23cr2b1b00000  a0000000  1
15:38.07*** join/#htc-linux ALoGeNoff (n=alogeno@137.pool85-60-2.dynamic.orange.es)
15:49.04tmztcr2: does the cpld driver support the i2c mode?
15:49.29tmzt(this is for wizard actually but I'm wondering if there is a generic cpld driver)
15:50.26cr2htc-egpio ? no.
15:50.26miknixtmzt, not really. each cpld behave differently
15:50.35cr2miknix has written one
15:50.37cr2ok
15:51.04miknixit works with htc herald and htc wizard so far
15:51.08*** join/#htc-linux stefan_schmidt (n=stefan@p5B034270.dip.t-dialin.net)
15:51.16cr2tmzt: the generic gpio+irq cpld driver is htc-egpio
15:51.37cr2miknix: artemis is the only omap850 exception
15:51.48cr2which does not use i2c-cpld
15:53.13*** join/#htc-linux ALoGeNo (n=alogeno@137.pool85-60-2.dynamic.orange.es)
15:53.52miknixcr2,  so, there are other omap850 devices using it?
15:54.38cr2i'm looking at the MSM_CLK list and at the clock-7x01a.h
15:54.45cr2miknix: the only one i know
15:54.54*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
15:55.26tmztmaybe excalibur, not sure if we confirmed if it does/does not use it
15:55.28cr2usb is after uart ...
15:55.48cr2tmzt spl will tell you
15:56.19tmztI don't have it, penguinz was working on it some time ago
15:56.32cr2hmm, +0xe0 is usb clock then
15:56.55tmztwhy do you say usb is after uart?
15:57.06tmztand how does this tell you the memory order
15:57.09cr2in the list
15:57.31cr2they don't match 100%, but the order is very similar
15:58.04cr2goolge is probably not evil, they have taken the spec and didn't mix it :)
15:58.33cr2the g1 vreg order 100% fits the dex masks
15:59.27miknixthe google thing was slashdoted
16:00.25*** join/#htc-linux ppman (n=mkern@pool-70-111-235-140.nwrk.east.verizon.net)
16:03.16cr2if my therory is right, then "Stereo DAC clock " is between the pmdh and SD
16:04.05cr2hm. there is an unknown clock there in between
16:04.57cr2the i2c is at the wrong place, though
16:05.52tmztah, I see
16:06.02tmztwhat's missing then?
16:06.14tmztI assume the grp and imem are together
16:06.18cr2emdh is cam ?
16:06.28tmztprobably, it's mddi isn't it?
16:06.36cr2external mddi host
16:06.49tmztyeah, I mean cam is mddi isn' it?
16:06.56cr2should be the camera, accordig to the qcom patents ;)
16:07.15cr2i don't know, but there are mddi cams
16:07.26tmzthah, you have two grp_clk's?
16:07.31cr2but then the cam is a host, and msm is the client
16:07.38cr21
16:07.44tmztin wiki
16:07.51cr2but the 0x80 register is related to grp_clk
16:07.57tmzt+0x80 and +0x84
16:08.23cr2i have evin more sdc_clk
16:08.33cr2s/evin/even/
16:08.49tmztI know, but I assume those are sdc1,2,3,4 and Md/Ns?
16:09.01tmztor, pclk and clk
16:09.02tmztsorry
16:09.28cr2clock-7x01a.c
16:09.51tmztI'm saying the hw3d.c suggests one of those is imem if you grp-related means they change together
16:09.57cr2yes, we need to think about clk_api
16:10.14cr2how to implement it in a non-evil way
16:10.42*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
16:10.58cr2icdec_rx and tx are after i2 ?
16:11.16cr2looks like that in the list
16:11.17tmzticdec?
16:11.23cr2icodec
16:11.49tmztwhich is? Stereo DAC?
16:11.54cr2no
16:11.59cr2sdac is later
16:12.18tmztthen what? do you know?
16:12.35cr26c-78 may be icodec_rx and tx
16:12.40cr2are they used somewhere ?
16:13.22cr2sdac is between mddi and sd
16:13.43cr2maybe 98-9c
16:13.45tmztno
16:13.52tmztnot used in git-grep of android
16:14.53cr2ok
16:14.56cr2sdac ?
16:15.13cr2the regs in the table are those referenced by oemsbl
16:15.19tmztno, odd
16:15.31cr2ok
16:15.47cr2they may use rpc et al.
16:15.47tmztthey are in clock-7x01a.c also but nowhere else
16:15.55tmztnot clock api?
16:16.07cr2g1 code has many hacks
16:16.37tmztit enables codecs by name, that could activate different clocks on the arm9 side?
16:17.15cr2yes
16:17.39cr2wince also implements the proc_comm clk api. but does not use it ;)
16:17.51cr2so there are 2 clock groups
16:18.01cr2one is accessng the regs directly
16:18.06cr2they are all documented
16:18.24cr2and there are some sec_clk calls
16:18.29tmztwhat address?
16:18.31cr2that go into nowhere
16:18.39cr2at least i can't track them
16:18.50cr2address ?
16:19.16tmztsorry, I was thinking we could search for a writel to it but it would be macro
16:20.33cr2there are 3 0xe0 groups:
16:21.05cr210,20; 400,800; 1000,2000
16:21.16cr2if they are for usb
16:21.33cr2then clocks-7x01a.h has 3 usb clocks
16:22.05cr2hs clk, hs pclk and otg
16:22.18cr2makes sense
16:22.29cr2but needs to be traced somehow.
16:23.10tmztover bluetooth/wifi?
16:24.19tmzthttp://android.git.kernel.org/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/clock-7x01a.c#l47
16:24.34tmztUSB_OTG_CLK 38 /* Full speed USB clock */
16:24.35cr2the idx 0,a,c are one group
16:24.47tmztassuming then otg host only supports 1.1 speeds
16:25.03tmzt(although otg is really 2.0)
16:25.07cr2swetland said ehci, when i've said ohci :)
16:25.35cr2so it is 2.0
16:26.08cr20 enables bit 0x200, a is mddi and c is grp
16:26.21*** join/#htc-linux |patoche| (n=patoche@lns-bzn-58-82-251-208-84.adsl.proxad.net)
16:26.23cr2so this bit 0x200 is mddi/grp related
16:27.10cr2then 1,5,3,6,7,b
16:27.16cr2b is some generic
16:27.43*** join/#htc-linux Andrew3 (n=Andy@71-211-46-165.clsp.qwest.net)
16:27.44cr26,7 sdc1 and 2
16:27.56*** part/#htc-linux Andrew3 (n=Andy@71-211-46-165.clsp.qwest.net)
16:28.01cr23 is uart2dm
16:28.15cr2sorry
16:28.20cr25 is uart2dm
16:28.35*** join/#htc-linux AndyCR (n=Andy@71-211-46-165.clsp.qwest.net)
16:28.41tmzt20:15 < swetland> yeah, the hsusb controller is otg capable, has a ehci host controller
16:28.46cr21 and 3 are usb something
16:29.02cr2tmzt: but there is no driver for it.
16:29.16tmztfor what, the otg part?
16:29.18cr2but we can find the ehci location
16:29.29cr2for ehci host
16:29.43tmztI think the biggest differences are ulpi registers
16:29.59tmztlike that was the block that had to be changed between non-A and A
16:30.54tmzt#define USB_HS_PCLK 37 /* High speed USB pbus clock *?
16:30.59tmztwhat is pbus?
16:31.25tmztand what is pbus_clk (searched for pbus in clock-7x)
16:31.29*** join/#htc-linux _patoche_ (n=patoche@lns-bzn-58-82-251-208-84.adsl.proxad.net)
16:31.39cr2remote_apis_clnt.dll where is it ?
16:31.54cr2peripheral bus
16:31.56tmztwhat?
16:32.08cr2pbus=peripheral bus
16:32.12tmztI've only ever seen rapiclnt
16:32.25tmztmaybe in the .NET dlls
16:32.29cr2no
16:32.34cr2in the phone
16:32.41cr2i don't see such dll
16:32.50tmztyeah, there is .net in wm
16:33.10*** join/#htc-linux dream_kill (n=nospam@92.56.48.66)
16:33.11cr2but clkregim.dll says some clocks are exported by remote_apis_clnt.dll
16:33.32tmztwhat is clkregim.dll?
16:34.24tmztare all the pclks's related to pbus_clk?
16:34.32cr2no idea
16:34.39cr2maybe
16:35.12tmztIMEM Internal graphics memory clock
16:35.55cr2found remore_apis_
16:36.00cr2it's a xip dll
16:36.41cr2and it's some rpc stuff
16:36.55cr2not surprising for the xip
16:38.09cr2time for the rpc wiki page ;)
16:39.56*** join/#htc-linux _patoch3 (n=patoche@lns-bzn-58-82-251-208-84.adsl.proxad.net)
16:40.00cr2hehe. vbatt_read
16:40.02tmztVFE_CLK 40 /* Camera / Video Front End clock */
16:40.28tmztVFE_MDC_CLK 41 /* VFE MDDI client clock */
16:40.56tmztInternal CODEX RX clock
16:41.04tmztInternal CODEX TX clock
16:41.16tmztthis is onboard audio adc/dac?
16:42.22cr2probably
16:42.40tmztnot used then if external codec is used
16:43.03tmztPCM_CLK 15
16:50.15*** join/#htc-linux |patoche| (n=patoche@lns-bzn-58-82-251-208-84.adsl.proxad.net)
16:55.37*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87ed28.pool.einsundeins.de)
17:00.03*** join/#htc-linux ALoGeNoff (n=alogeno@137.pool85-60-2.dynamic.orange.es)
17:01.32*** join/#htc-linux balsa1 (n=kll@87.72.13.87)
17:03.19*** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk)
17:04.21*** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net)
17:07.43*** join/#htc-linux Mullins (n=bw@89.204.239.174)
17:17.54*** join/#htc-linux timebomb (n=tb@e176127158.adsl.alicedsl.de)
17:35.06*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
17:45.49*** join/#htc-linux ALoGeNo (n=alogeno@137.pool85-60-2.dynamic.orange.es)
17:46.55*** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my)
17:54.44*** join/#htc-linux shoragan_ (n=shoragan@sicherheitsschwankung.de)
17:55.54*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) [NETSPLIT VICTIM]
17:56.16*** join/#htc-linux konsta (n=asds@host81-157-60-163.range81-157.btcentralplus.com)
17:56.33*** join/#htc-linux _Nono (n=arnaud@rps4056.ovh.net) [NETSPLIT VICTIM]
17:57.33*** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com)
18:00.00*** join/#htc-linux Mullins (n=bw@89.204.239.174) [NETSPLIT VICTIM]
18:05.06*** join/#htc-linux stefan_schmidt (n=stefan@p5B0376FD.dip.t-dialin.net)
18:08.02*** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk) [NETSPLIT VICTIM]
18:09.15*** join/#htc-linux LemHxC (n=nimp@cnv94-1-82-232-227-160.fbx.proxad.net)
18:13.22LemHxCis away: vadrouille
18:21.04*** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com)
18:44.36*** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk)
18:58.41*** join/#htc-linux patoche (n=patoche@lns-bzn-54-82-251-114-125.adsl.proxad.net)
19:15.33*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
19:16.12*** join/#htc-linux Jon__ (n=Jon@94-194-181-77.zone8.bethere.co.uk)
19:23.11*** join/#htc-linux jack_ (n=ASUS@f048251105.adsl.alicedsl.de)
19:23.16jack_hi
19:25.37*** join/#htc-linux AstainHellbring (n=arto@unaffiliated/astainhellbring)
19:26.50jack_where are the htc-msm-2.6.27 autobuilds?
19:27.54jack_I need the kernel
19:31.28jack_I have new 7201a board
19:43.10cr2jack_: there is no such thing as 7201a board
19:53.57*** join/#htc-linux kill_me2 (n=km2@99-7-110-97.lightspeed.lsanca.sbcglobal.net)
19:56.37*** join/#htc-linux MethoS-- (n=lem@dyndsl-085-016-165-155.ewe-ip-backbone.de)
20:00.06*** join/#htc-linux patoche (n=patoche@lns-bzn-54-82-251-114-125.adsl.proxad.net)
20:02.34*** part/#htc-linux balsa1 (n=kll@87.72.13.87)
20:10.57*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
20:31.56*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
20:33.49*** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net)
20:41.53*** join/#htc-linux Jon__ (n=Jon@94-194-181-77.zone8.bethere.co.uk)
20:55.53*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
21:07.10*** join/#htc-linux Pure4Real (n=pure4rea@89-97-140-219.ip17.fastwebnet.it)
21:09.13cr2it's quiet today
21:09.42Pure4Realso i notice
21:10.34Pure4Realwas just reading up a bit on irc logs
21:10.44Pure4Realwho's working on the wifi driver atm?
21:11.36cr2maejrep compiled and run it, but the driver needs some fixes
21:12.36Pure4Realand that's based on the acx100 driver?
21:12.51*** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde)
21:17.49*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
21:19.33cr2no
21:19.50cr2it's the tiacx driver written by ti+android people
21:20.20Pure4Realah
21:23.48*** part/#htc-linux Jon__ (n=Jon@94-194-181-77.zone8.bethere.co.uk)
21:26.35*** join/#htc-linux reformatt (n=chatzill@97-121-30-66.bois.qwest.net)
21:28.59*** join/#htc-linux MethoS- (n=lem@host-091-097-241-018.ewe-ip-backbone.de)
21:48.23*** join/#htc-linux Venny (i=Travis@h216-45-127-2.dynamic.platinum.ca)
22:14.55nashpacr2, where can the tiacx driver be found?
22:17.20cr2it's better to wait for maejrep
22:17.51maejrepthe code is in android's git
22:18.11maejrepbut does take some tweaks to be usable
22:18.36Pure4Realdo you have a description of the tweaks somewhere?
22:18.47maejrepnot yet
22:25.43*** join/#htc-linux Jon__ (n=Jon@94-194-181-77.zone8.bethere.co.uk)
22:28.28*** join/#htc-linux vmpu (n=pui@89-33-138-94.u-nite.ro)
22:31.50cr2maejrep: i've detected most clocks. the rest is accessed over rpc (if at all)
22:32.05maejrepcool
22:32.18maejrepyeah rpc is another beast we haven't started on yet :p
22:32.49nashpawhat device are you guys working on?
22:33.03cr2i've also documented all mddi init differences between g1,raph100,raph800 and blac100
22:33.28cr2maejrep: imvho g1 disables the autorefresh
22:33.39*** join/#htc-linux Jon__ (n=Jon@94-194-181-77.zone8.bethere.co.uk)
22:34.12cr2nashpa: mainly raph?00
22:34.29maejrepah nice
22:34.38nashpa7201A? or 7200A?
22:34.39maejrepautorefresh of what?
22:34.45maejrep7x01a
22:34.55maejrepraph100 is 7201a, raph800 is 7501a
22:34.58cr2maejrep: mddi
22:35.32maejrepcr2: which means what? :x  it doesn't refresh the screen? :x  or handles it all in software
22:35.34nashpaah, the difference is only in the companion chips, one is GSM, other is CDMA
22:35.45*** join/#htc-linux timebomb (n=tb@e176099053.adsl.alicedsl.de)
22:35.54cr2maejrep: i think it handles it in software
22:36.03maejrepnashpa: right, but i think raph500 is actually 7500a (?)
22:36.14maejrepwell that's lame
22:36.24cr27501a _is_ 7500a :)
22:36.29maejreporl
22:36.31maejrep+y
22:37.09cr2maejrep: it may save some mA. and we don't know the special 3D requirements
22:37.27maejreptrue
22:37.32cr2maejrep: i've also added the HW3D area to memory map.
22:37.58cr2and the per-device vreg table
22:38.24cr2and the usb host alt gpios
22:38.38cr2but there is no ehci-msm driver afaik
22:39.16maejrephmm, wifi vreg level is set to 0 ?
22:39.17cr2and the raph manual says 32MB stacked ram
22:39.37cr20 means don't touch
22:39.39cr2in enable
22:39.46cr2idx,1,0
22:39.48maejrepso just leave it as is?
22:39.51cr2yes
22:39.56maejrephmm
22:40.22maejrepwhat happens if it wasn't initialized properly by windows yet?
22:40.22cr2enable without changing the level
22:40.33cr2by oemsbl
22:40.39maejrepah
22:40.48cr2g1 does not init a _lot_ of things too
22:40.59maejrepi see
22:41.18cr2and i've documented all your alt gpios
22:41.26cr2your = raph800
22:41.59maejrepwhat is "a/m" in the gpio page?
22:42.55cr2application/modem = arm11/arm9 owner
22:43.00maejrepah
22:43.22cr2but this column is unfinished
22:43.37cr2and some gpios may change the owner and runtime :)
22:43.41maejrepyou saw my gpio dump at the bottom?
22:43.49cr2oemsbl has some variations too.
22:43.56cr2where ?
22:44.06maejreplink at the bottom of that page: http://wiki.xda-developers.com/index.php?pagename=Raph800GPIODump
22:45.07cr2yes. but it's more interesting for haret
22:46.00maejrepany idea why I don't see it enabling/disabling vregs when turning wifi on and off? :o
22:46.19cr225    0x19        0    9    O    soft reset=0
22:46.30cr2GPIO25: Owner=Arm9, Dir=O, Level=H
22:47.02cr2this is the gpio that changes the owner btw.
22:47.06maejrepi've tried gpio_set_value(25,0) and it doesn't work :x
22:47.18cr2you need to change the owner first
22:47.25maejrepoh?
22:47.32maejrepi guess that makes sense
22:47.44cr2in your table arm9 is the owner
22:48.08cr2btw you can try to modify the arm9 gpio directly :)
22:48.15cr2but then it may crash
22:48.54cr2i doubt that the MPU can have control on per-register basis
22:48.57maejrepso you change that at a9100504 ?
22:49.14cr2since we have access to the arm9 gpio area, we can control it completely.
22:49.36cr2change the owner bit for this gpio
22:49.49maejrepk i'll try that
22:49.50cr2at least it's how wince does it
22:50.04maejrepwill also work on putting patches together for the small tweaks i've done
22:50.14cr2writing directly to the arm9 address seems risky
22:50.38cr2ok
22:51.07cr2do you have write access to linuxtogo git ?
22:51.54maejrepno
22:51.59cr2hmm
22:52.05maejrepi have an account, but haven't asked to be added to the project yet
22:52.07cr2NetRipper: are you alive ?
22:54.22cr2maejrep: do you have a bt headset ?
22:54.49maejrepsomewhere :p
22:55.35cr2i'm interested in the MSM_CLK dump, while the bt audio is active
22:56.11maejrepas in, while on a call?  or just while paired?
22:56.16maejrepor while listening to music
22:57.28maejrepcr2: owner bit is..  0=arm9,1=arm11?  or the other way
22:57.41maejrepi guess I could dump the regs to find out :p
22:58.10cr2i forgot it :)
22:58.40cr2call or listening musi
22:58.50cr2i think call is better
22:59.14cr2because for music they can use sco over 4mbit serial
22:59.56maejrep0=arm9
23:00.17maejrepHaRET(1)# pdump 0xa9100504 0x4
23:00.17maejrepa9100504 | 07fffcbe                            | ....
23:00.36maejrepat least, if my gpio dump is close to accurate (I assume windows doesn't change everything ;)
23:00.54maejrepall the arm9 bits are 0 in that value ^
23:03.07maejrephmm, msm_gpio_configure() doesn't have any kind of lock
23:03.55cr2wince disables interrupts there
23:04.06cr2which makes sense
23:05.26maejrepright
23:05.31maejrepbut msm_gpio doesn't :x
23:05.38maejrepunless its handled further u
23:05.40maejrepup*
23:05.51maejrepwhich could make sense..  gpio support is handled at a higher level
23:05.55maejrep<PROTECTED>
23:05.55maejrep<PROTECTED>
23:06.12maejrep(i left the 25 there just for you :D )
23:06.44maejrepso, if you pass it either GPIOF_OWNER_ARM9 or GPIOF_OWNER_ARM11, it'll either ORR or BIC the respective bit
23:09.15NetRippercr2, i am, but im a bit busy
23:09.17NetRipperwhats up
23:10.15NetRippermaejrep, if you got patches to commit, just pm me the link :) to get access to git yourself, you can go to the mobile linux project on projects.linuxtogo.org and "apply" somewhere on the right-side of the main 'linux mobile' project page
23:10.31NetRipperpH5 or Kevin2 will then receive an e-mail to allow you access
23:10.41maejrepah
23:10.48maejrepI'm working on creating diffs right now
23:11.02maejrepnot in any hurry to get access myself ;p
23:11.05NetRipper;)
23:11.27NetRipperonly thing i want to keep nice in the git is support for multiple devices.. i.e. proper #ifdefs and machine_is_* stuff
23:11.30maejrepand i figure it's better that patches go through one person, to review code, etc
23:11.41maejrepnods
23:12.30NetRipperwell im not the most experienced guy.. i also like the idea if people check up on my commits when i put something on linuxtogo ;)
23:12.51cr2NetRipper: ok
23:13.44NetRippercr2, btw, i havent been using the trout memory layout yet.. i first wanted to sort the ts/vkeyb/msmfb out.. im hitting performance issues
23:13.53cr2maejrep: i'll put the mddi init into wiki. the code there needs some changes
23:14.05NetRipperi have added a 'callback' mechanism in the msmfb to allow vkeyb and ts calibration to draw on the framebuffer just before the dma starts
23:14.21cr2NetRipper: the manual says raph has 32MB. and i can't read from smem for some reason.
23:14.36NetRipperbut its causing a major impact on graphics, too much to be true ;)
23:14.51NetRippercr2, read from within wince?
23:14.59cr2yes, in haret
23:15.13NetRipperis it protected memory? locked by oemsbl?
23:15.14cr2it may be protected on several levels
23:15.40cr2maybe locked, maybe has the evil page table bits set
23:15.46NetRippercr2, you could ask cmonex in #xda-devs, he knows pretty much about what they locked.. and if it's unlockable...
23:15.52cr2locked = locked by MPU
23:16.12NetRipperthere's also an sdcard based unlock
23:16.33cr2the evil bits can be changed, but the MPU will probably need an oemsbl reflash. if it 's possible ;)
23:16.35NetRipperdon't we disable the MPU in haret when linux boots?
23:16.51NetRipperor is MPU != MMU?
23:16.57cr2no.
23:17.07cr2MemoryProtectionUnit
23:17.28NetRipperok
23:17.33cr2it's some DMA/MA restriction
23:17.49cr2NetRipper: everything that SPL does, linux can do too.
23:18.06*** join/#htc-linux Dvyjones (n=dvyjones@unaffiliated/dvyjones)
23:18.06cr2because the SPL has the same level of permissions as linux.
23:18.27DvyjonesHi everybody!
23:18.42Dvyjoneswill start porting Linux to HTC Pharos again :P
23:18.57NetRippercr2, ok, but SPL has nothing to do with smem, so it could be normal that we cant access it
23:19.04cr2NetRipper: we need to fix more urgent problems first, before reflashng oemsbl :)
23:19.12NetRipperyes
23:19.17NetRipperof course ;)
23:19.45NetRipperbut i wont reflash oemsbl on my device... if it would be possible at all..
23:19.54cr2i'll add detecting the smem size to my wiki todo list
23:20.02NetRipperwe'd need jtag and the gold card in case the flash fails
23:20.13Kevin2evin
23:20.29Kevin2Heh, wrong window.  :-)]
23:20.32NetRipper;)
23:20.33cr2no gold card will help you on oemsbl failure
23:21.00NetRippercr2, gold card is needed to do jtag, isnt it? and with jtag it should be possible to recover from oemsbl error
23:21.11*** join/#htc-linux ale_____ (n=alessand@host248-205-dynamic.19-79-r.retail.telecomitalia.it)
23:21.18NetRipperit's a low-level msm7k trick afaik
23:22.39cr2ok
23:23.10cr2it's beyond my knowlegde level :)
23:24.26NetRipperhehe same here i guess ;)
23:26.03maejrepcr2: to be sure I'm reading this right..  LDR     R2, =0xBC0FC120  <-- means R2 = the value at address bc0fc120?  not the number bc0fc120
23:26.30*** join/#htc-linux ali1234 (n=al@robotfuzz.co.uk)
23:27.51cr2maejrep: number
23:27.53maejrepactually, no I guess that's the other way around...  cause then it uses [R2] in ldr and str calls
23:28.27cr2maejrep: do you think that proc_comm_dex is a good idea ?
23:28.32maejrepso what's the difference between LDR R2, =0xDEADBEEF;  and MOV R2, #0xDEADBEEF; ?
23:28.45maejrepyou mean instead of _wince ?
23:28.59cr2not instead, but an additional api
23:29.15maejrepwhy would it need to be additional?
23:29.27cr2mov r2, #deadbeef does not work as a single machine op. afair
23:29.31maejrepshouldn't proc_comm cover everything that data exchanger does?
23:29.55cr2it's easier to compare with wince drivers
23:30.08cr2while you use the g1 api for proc_comm
23:30.22cr2which looks a bit artificial to me :)
23:30.40cr2with things like 0x18a instead of 0x8a
23:30.51maejrepI don't pass 0x18a
23:31.02maejrepthe driver adds the 0x100 when data exists
23:31.40maejrepwhich is how wince does it :x
23:31.58maejrepactually i'm reading through it again now, to make sure I fix any remaining bugs in the _wince implementation
23:32.11maejrepif you want, I can rename it to msm_data_exchanger in the process ;)
23:34.46cr2nothing against proc_comm, but it's easier to track the wince api.
23:36.34maejrepi don't care either way
23:37.10maejrepif it's easier to name things DEX and track the wince dex function, then that makes sense
23:42.51*** join/#htc-linux ginge (n=kvirc@78-105-175-81.zone3.bethere.co.uk)
23:44.05maejrepcr2: what's the point of this?
23:44.06maejrepSTRB    R3, [R4]
23:44.06maejrepLDR     R3, [R4]
23:44.25maejrepis it just to truncate R3 to a 0xff mask?
23:46.15cr2strange code, but yes
23:48.00maejrepso, it looks like the wince dex code actually does send 0x100 with the command, to tell the driver when there's data to be read...  is that better than what we're doing, which is check if data1 != 0?
23:48.16maejreps/to be read/to be sent/
23:49.04cr2wince dex puts 0x1 byte before the cmd in the buffer
23:49.20cr2if there are external parameters
23:51.03*** join/#htc-linux Kuma (n=John@e179103181.adsl.alicedsl.de)
23:54.22maejrepso why not just take care of adding that in the driver, instead of doing it in the function call?
23:55.12maejrepie, why pass dex( 0x18a, data1, 0), vs dex(0x8b, 0, 0), when you could just call dex( 0x8a, data1, 0 ), and let dex() add the 0x100 to the command, when data1 != 0

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