IRC log for #htc-linux on 20111130

00:00.50*** join/#htc-linux TheXev (user@54.sub-75-214-32.myvzw.com)
00:04.05d3tul3WisTilt2, this guy http://pastebin.com/eNfdEzA6 ?
00:04.28WisTilt2yeah thats it.
00:04.30rpierce99i think my dmesg is too spammy, and since i can't adb during boot, i can't find "mask" in my dmesg
00:04.55WilldDon't you have last_kmsg?
00:05.06rpierce99is that bigger than dmesg?
00:05.07WisTilt2it will be around the 30second range of boot
00:05.11Willdrpierce99: I reckon so
00:08.00rpierce99cat /proc/last_kmsg | grep mask (and gpu) returned nothing, am i doing this wrong?
00:08.25WilldShould have done it..
00:08.26WisTilt2make sure its build #9
00:08.51WisTilt2im sure i put the right one up there but who knows
00:09.03rpierce99it's #9
00:09.06arrrghhhrpierce99, how 'bout that command with /proc/kmsg
00:09.10d3tul3rpierce99, adb usb support is in the autobuild
00:09.29rpierce99i don't think WisTilt2 pulled it though did he?
00:09.34WisTilt2you might have to run a 3d app to set it, but bootani should have done that
00:09.51WisTilt2not in that build no. ill pull it now
00:10.39d3tul3ok so in this derived table i don't see pll0/4
00:12.59WisTilt2highest pll0 freq is 245760 as its running.  gpu register is defaulted at /4 from there
00:14.05WisTilt2gpu divider isnt in that table btw, im looking at what its register is set to
00:14.21d3tul3i need to get this document with these secret registers somehow
00:15.43WisTilt2lol, well you can develop a device with this msm chip and they give it to you, of course you'll be spending quite a few $
00:16.02d3tul3i'm on it
00:16.27arrrghhhhah
00:16.29WisTilt2they do a pretty good job of keeping the datasheet off the internet too
00:16.36rpierce99i think i'm getting there on this grep, most of my time is spent inserting a pipe
00:16.45rpierce99the osk doesn't want to come up for me :)
00:16.50d3tul3doesn't fn + y work?
00:16.56rpierce99<3
00:17.03arrrghhhon f22's rootfs
00:17.07arrrghhhi don't think that made it to the autobuild
00:17.10d3tul3it is
00:17.10arrrghhhdid it?
00:17.11WisTilt2rpierce99 im building you another build #10 that has the adb fix
00:17.12rpierce99it's in this one
00:17.13arrrghhhoO
00:17.15arrrghhhnice
00:20.21WisTilt2rpierce99 kernel is up with your mac adb fix
00:20.31rpierce99tyvm :)
00:20.56WisTilt2d3tul3 did all the work though, i just rebuilt:)
00:21.05d3tul3watch it not work now
00:23.17*** join/#htc-linux sykosoft (~sykosoft@67-61-60-19.cpe.cableone.net)
00:23.39sykosoftWas watching the logs. rpierce99, did you do a case insensitive grep using -i?
00:23.51rpierce99haha no
00:24.08arrrghhhthat's fancy talk
00:24.15WisTilt2lol
00:24.21WisTilt2it is all caps btw
00:24.37rpierce99oh well, booting into adb kernel now
00:26.19rpierce99[   53.763122] GPU MASK: 2219ff2f
00:26.19rpierce99[   53.783081] GPU MASK: a99
00:26.30WisTilt2thats what i needed thanks
00:26.44rpierce99<3 adb
00:26.52WisTilt2thank god its the same on cdma as gsm
00:27.50sykosoftI noted a reversion to cfq as the io scheduler, but don't know why. Anyone know?
00:28.53arrrghhhsykosoft, i know emwe was messing with different schedulesr
00:28.55arrrghhher
00:28.56arrrghhhyea
00:29.07arrrghhhschedulers.  trying to see which one works best...
00:29.17arrrghhhthe results seemed to differ depending on the underlying file system.
00:29.31sykosofthmm, I'd be shocked if cfq actually performed better than deadline in most cases
00:29.38sykosoftbut yes, filesystem would matter
00:29.52sykosoftgiven the nand type, no-op may be the fastest
00:30.08arrrghhhwell most here are still on HaRET
00:30.14arrrghhhi guess SD cards still use NAND flash.
00:30.15sykosoft(was just about to say that)
00:30.21arrrghhhstupid misnomers.
00:34.59sykosoftIs glemsom's autobuild down? 500 error
00:35.38arrrghhhit was down the other day
00:35.41arrrghhhuse the mirror
00:35.46arrrghhh(on incremental updates page)
00:36.30sykosofthmm, it doesn't appear that the mirror also builds .39
00:36.37arrrghhhit does not
00:36.46arrrghhh.39 hasn't built from glemsom's site in ages anyways...
00:39.03arrrghhhlike, months
00:39.19arrrghhhi did mean to ping glemsom about the site being down tho
00:40.21d3tul3arrrghhh, you're somewhere in the midwest right? ohio state fan?
00:40.31arrrghhhno, and no
00:40.32arrrghhh:P
00:40.36arrrghhhwhere'd that come from!?!
00:41.17d3tul3just fishing for ohio state fans, need to talk smack with them tonight, guess wrong channel
00:41.50arrrghhhlol
00:41.56arrrghhhfair enough.  i'm not a big sports guy...
00:42.24arrrghhhi play soccer, but get bored watching sports.  hockey's fun to watch sometimes.
00:43.28arrrghhhsykosoft, not trying to start a war over LK, i just feel the way it is now is a much better compromise than how it was before...
00:45.12*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
00:59.31*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
01:06.33d3tul321.0fps neocore
01:09.59*** join/#htc-linux lnX\ (~n0kie@nelug/member/lnx)
01:15.43sykosoftoh, I'm not trying to start a war either. I have no say/sway in the matter. However, at least for my wife (rhod400 user just like me), it's definitely inconvenient
01:16.02sykosoftIf it doesn't get better/change, then so be it, we're still better off
01:20.58*** join/#htc-linux TheXev (user@54.sub-75-214-32.myvzw.com)
01:25.33*** join/#htc-linux XirXes (~XirXes@67-2-24-4.slkc.qwest.net)
01:31.50*** join/#htc-linux XirXes_ (~XirXes@67-2-15-82.slkc.qwest.net)
01:31.51sykosoftIs lk able to read the sd card?
01:32.15sykosoftPerhaps a config file allowing one to define behavior. Defaulting to fastboot when usb is plugged in. Allow that to be disabled.
01:35.41*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
01:36.24*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
01:49.10crypticmofoanyone got a good keyboard in mind ?
01:49.15crypticmofoi don't like this default keyboard
01:58.09*** join/#htc-linux hardwalker (~hardwalke@122-117-115-146.HINET-IP.hinet.net)
02:03.44WisTilt2heading home guys.  should have a test for you later tonight with a faster gpu.  incorporating this into our existing code is, well, no comment.
02:04.19arrrghhhlol
02:04.30arrrghhhi'm going to go with "enthralling"
02:06.11arrrghhhsykosoft, everyone can contribute.  like i said, if you have a better way to do it we're all ears.
02:06.35arrrghhhi don't see why you can't just charge with the device off, or wait for it to boot before plugging the charger in...
02:18.19*** join/#htc-linux ellisway (~ellis@188-223-85-44.zone14.bethere.co.uk)
02:46.06*** join/#htc-linux Rajko (~rajkosto@2001:470:d76b:da7a:d0a6:5870:cab8:4a50)
02:46.15*** join/#htc-linux TheXev (user@54.sub-75-214-32.myvzw.com)
02:47.13*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:d0a6:5870:cab8:4a50)
02:47.39*** join/#htc-linux WisTilt2 (~wisgreg@wireless248.wirelesstcp.net)
02:49.51*** part/#htc-linux lnX\ (~n0kie@nelug/member/lnx)
02:56.06*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:d0a6:5870:cab8:4a50)
03:09.43*** join/#htc-linux bartman (~bart@2607:f2c0:a000:175:2e0:81ff:fe47:3d01)
03:16.40jonprydur
03:23.46arrrghhh?
03:26.30jonprythe latest problem is that i can only allocate gpu memory from a specific thread. and this happens to always be not the thread that things request it on
03:26.58arrrghhhnaturally :P
03:28.42d3tul3jonpry, you can't pass the fd somehow along
03:28.46d3tul3dup?
03:28.58jonprycan't create the fd
03:29.04d3tul3or keep a global heap?
03:29.34jonpryi have to get opengl to allocate the memory. and the opengl context is thread specific
03:30.03jonprymaybe not have to. but this is the architecture i think will work best
03:30.59jonpryso the context is really running on the surfaceflinger drawing thread. which is probably about the worst place it could be
03:32.34d3tul3uh that sounds less than optimal, btw i like what emwe was saying about the defconfigs, perhaps it's a good idea to run msm_defconfig through menuconfig
03:32.58d3tul3and  try to make all subsequent changes via menuconfig?
03:33.23d3tul3i know I am guilty of just sticking lines in there somewhat randomly
03:33.24jonpryi use xconfig. but that is my general method
03:34.11jonprysticking things directly in the config has a good chance of shooting you in the foot
03:34.56d3tul3i agree, part of the learning curve for me
03:35.24jonpryxconfig is very nice because it will explain why a particular option is not selectable
03:35.40jonprylike requires foo=y bar=n | bam=y
03:36.01d3tul3menuconfig does something similar
03:37.38jonpryah
03:46.07d3tul3..and apparently i can't get xconfig to work
03:46.30arrrghhhlol
03:57.30*** join/#htc-linux dr1337 (~textual@112.97.96.58.static.exetel.com.au)
03:59.28*** join/#htc-linux XeKToReX- (~xTx@CPE-124-188-18-211.hdbq1.win.bigpond.net.au)
04:03.26*** join/#htc-linux bartman (~bart@2607:f2c0:a000:175:2e0:81ff:fe47:3d01)
04:09.30d3tul3jonpry, hm menuconfig might be a bit too good, it takes out CONFIG_ARM because i guess it's not in any Kconfig, but i can't imagine CONFIG_ARM is not needed
04:11.50d3tul3i see config_arm is added to .config by 'make ARCH=arm msm_defconfig'
04:16.24*** join/#htc-linux frustro (~frustro@67.41.36.76)
04:18.24*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
04:18.35arrrghhhd3tul3, i'm in one of those GP_Timer slowdowns (i think)
04:18.39arrrghhhclock has seemingly stopped
04:18.46d3tul339?
04:18.48arrrghhhwon't wake worth a damn
04:18.49arrrghhhyea
04:19.08arrrghhhis there anything i can do to help diagnose?
04:19.16d3tul3can you wake the screen at all?
04:19.20arrrghhhi did once
04:19.28arrrghhhhaving trouble waking it again...
04:20.34d3tul3i think some of the recent IDLE stuff may have exacerbated how frequently these occur, though at the same time for me now they disappear when the screen cycles on/off
04:20.44d3tul3_sometimes_
04:21.45arrrghhhhttp://pastebin.com/KtH3Z1GC
04:21.56arrrghhhnot sure if that'll help, but it's a dmesg
04:21.56arrrghhhgot the phone to wake back up
04:21.58arrrghhhclock is still almost 90 minutes behind.
04:23.02d3tul3whoa 've never seen this: [71282.627502] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
04:23.03d3tul3[71282.627563] msm_set_i2c_mux: NOT IMPLEMENTED
04:23.21d3tul3is this a test kernel or just straight out of the autobuild?
04:23.30WisTilt2problem i believe is in the clocks as i am deep into them with this gpu oc stuff.  there are registers not being set fully that are probably causing a lot of this stuff
04:24.31d3tul3at the same time the clocks used to be identical to 27 when we had JBs clocks and now they are identical to 35 and both those kernels dont see this
04:24.33WisTilt2that i2c mux error starts right at boot when something tries setting up i2c device 0 that doesnt exist i think
04:25.35WisTilt2arrrghhh im almost done with this gpu oc so ill have a test for you in a bit
04:25.39arrrghhhok
04:26.42arrrghhhgonna go pickup some cancer to eat
04:26.43arrrghhhi'll bbl
04:26.50arrrghhhd3tul3, sorry test kernel
04:27.08WisTilt2d3tul3 that i2c mux thing has been in .39 since i can remember.  it errors right at the start of dmesg but i never pursued it, now i see wth is going on with these clock registers as we have them
04:28.09d3tul3i have never seen that i2c mux error, and i've seen my share of .39 dmesg, certainly not in this obsessively repeating fashion
04:28.38arrrghhhheh
04:28.49d3tul3when i was getting rid of the i2c write errors i got to a point where i would do a "dmesg | grep i2c" and return no hits so I am positive it hasn't been there forever
04:32.23WisTilt2d3tul3: you've never seen any of this in .39?
04:32.24WisTilt2[    0.532623] msm_i2c_probe
04:32.24WisTilt2[    0.532836] msm_set_i2c_mux: NOT IMPLEMENTED
04:32.25WisTilt2[    0.532958] msm_i2c_probe: clk_ctl 35d, 100000 Hz
04:32.25WisTilt2[    0.533813] i2c i2c-0: Invalid 7-bit I2C address 0x00
04:32.25WisTilt2[    0.533874] i2c i2c-0: Can't create device at 0x00
04:32.26WisTilt2[    0.534088] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 0
04:32.55d3tul3yeah sure i mean look at the log arrrghhh posted that error is choking his log
04:33.31WisTilt2this is the root of it.  arrrghhh which test kernel are you running?
04:34.29d3tul3i wasn't clear I don't see i2c errors/messages past the boot
04:36.30WisTilt2i need to finish this gpu oc then ill take a closer look at that mux register.  we need to also get rid of that 30fps vsync limit because im now pegged at 30fps in neocore:)
04:37.09d3tul3good man
04:39.40servergodthis is my 5-6th visit to this chan, dont want to be off topic, but I feel smarter listening to you guys...I never talk here..ok, done with the adoration and imput.
04:40.16d3tul3that (NOT_IMPLEMENTED) message is the correct return as it matches the return value of set_i2c_mux on both 35 and 27
04:44.10d3tul3also i2c-msm.c seems to be fine at first glance
04:44.12arrrghhhWisTilt2, sorry stepped out.  i was running the mem OC kernel IIRC.
04:44.15arrrghhhwould the kernel version help?
04:44.59arrrghhhWisTilt2, #48
04:45.19arrrghhhg6be4e91 - although i think all the test kernels have that.
04:45.19WisTilt2those kernels have all kinds of weird stuff in them so wouldn't go by them at this point.
04:45.25arrrghhhheh
04:45.26arrrghhhfair enough
04:46.47d3tul3jonpry, menuconfig is doing some strange strange things, like it's taking out that IO_REMAP clutch config
04:51.49d3tul3i am out goodnight folks
04:52.21*** join/#htc-linux Rob2223 (~Miranda@p5DE4B7B9.dip.t-dialin.net)
05:11.33*** join/#htc-linux swc|666 (~gecko@unaffiliated/swc666/x-4934821)
05:14.15*** join/#htc-linux Bry8Star (~Bry8Star@gateway/tor-sasl/bry8star)
05:27.16arrrghhhservergod, lol i just read your comment on an xda article.
05:28.14arrrghhhWisTilt2, how goes it sir?
05:28.42arrrghhhdid you see how the evo4g fixed the 30fps limit?  i think you already talked to acl about it.
05:28.46WisTilt2sorry, i mucked up the clock to the modem and backtracking what i did
05:28.50arrrghhhi think it was irrelevant to our device
05:28.54arrrghhhoic.  np
05:29.06WisTilt2comment on xda article?  whats that
05:29.16arrrghhhirrelevant, sorry :P
05:29.26arrrghhhi was reading an article on the HD2
05:29.37arrrghhhand servergod commented on the article
05:30.05WisTilt2gotcha.  yeah we really need to lift that limit if we can
05:30.24arrrghhhsomeone sent me the evo patch, if you are interested.
05:30.31arrrghhhIIRC acl said it was useless for us tho.
05:31.22arrrghhhhttp://htc-linux.org/wiki/index.php?title=Novatek_NT35582/FPS_Hack
05:31.26arrrghhhevidently it's just a hack
05:32.47WisTilt2yeah but our panels only support 50-70hz so we are still somewhat limited
05:36.28arrrghhhi see
05:39.17WisTilt2ok i think i found it so we should have smoke coming out of this thing this build if we're lucky
05:39.38arrrghhh:)
05:44.16*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:d0a6:5870:cab8:4a50)
05:46.23*** join/#htc-linux kiozen (~kiozen@ppp-93-104-83-75.dynamic.mnet-online.de)
06:03.46WisTilt2arrrghhh, i need to make a kernel for your phone to verify a couple registers are the same so this oc doesnt mess up anything if they're not the same.
06:05.33arrrghhhthat's fine
06:09.14*** join/#htc-linux kiozen (~kiozen@ppp-93-104-83-75.dynamic.mnet-online.de)
06:20.33arrrghhhpoop.  it's late... i should go to bed.
06:21.34arrrghhhWisTilt2, sorry man.  tried to hold out.  gotta get up early tomorrow... i'll read up on the logs, or you can always email me.  take it easy, talk to you tomorrow ;)
06:21.36WisTilt2sorry, this is not cooperating with the modem clk.  ill get it to you tomorrow
06:21.43WisTilt2np, sorry to hold you so long
06:21.47arrrghhhnp man, it happens.
06:21.52WisTilt2didnt expect the modem issue
06:21.56arrrghhhlol i was just watching futurama.  don't sweat it.
06:22.10WisTilt2ill catch ya tomorrow
06:22.32arrrghhhsounds good, g'nite
06:23.00rpierce99i'm still around for a bit if you need a rhod
06:23.03rpierce99w
06:23.17WisTilt2i need a 400 in my hand is what i need:)
06:23.36WisTilt2i can have you try this once i fix what i did to mess it up
06:24.45*** join/#htc-linux lipp[a] (~lippa@ppp118-209-98-131.lns20.mel4.internode.on.net)
06:30.17*** join/#htc-linux Ondalf (~ondalf@unaffiliated/ondalf)
06:42.46WisTilt2rpierce99: ok i have that test kernel up.  grep dmesg for MASK.  also run neocore just to make sure it runs and looks normal.  you should only be around 20fps or so with this one.
06:45.16rpierce99[   52.440704] MASK0: 2219ff27
06:45.16rpierce99[   52.460662] MASK1: 2219ff2f
06:45.16rpierce99[   52.460693] MASK0: 3a84
06:45.17rpierce99[   52.480621] MASK1: 3a84
06:45.22rpierce99still booting, neocore in a sec
06:46.09WisTilt2that looks good
06:48.40rpierce99runs like normal, no textures cuz i'm not running the new egl stuffs
06:51.50WisTilt2need to get the lib fixes.  im putting 1 more test up, need that same mask info if you can.  let me make sure it finishes booting first
06:53.55WisTilt2ok its up and good to go
06:54.02*** join/#htc-linux sykosoft (~sykosoft@67-61-60-19.cpe.cableone.net)
06:54.04sykosoftWisTilt2, how long do you need a rhod400 for? I have one without service, would that suffice? You can hold on to it for a few months, but I would like it back eventually (it's a spare)
06:55.15WisTilt2sykosoft that would be great if its just sitting around.  dont need service, just need to work out some of these cdma differences
06:55.32WisTilt2probably a couple weeks would be enough
06:55.38sykosoftit is just sitting around. I use my rhod400 internationally, and refuse to upgrade, so it's a spare
06:55.45sykosoftand both me and wife carry rhod400s
06:55.53WisTilt2what u located?
06:56.02sykosoftIdaho
06:56.51WisTilt2if you get on tomorrow ping me and ill give you info to get it here
06:57.04sykosoftSounds good
06:57.23WisTilt2thanks, was about to look for one on ebay just to have for this
06:57.50sykosoftAlso, does anyone know for sure if all rhods use the same battery?
06:58.08WisTilt2that i dont know
06:58.36sykosoftI'll see if I can send an extra battery in case you want to mod it for power measurements
06:58.58WisTilt2if it takes the same i have plenty and one already modded for that
06:59.09sykosoftI'll look into it
06:59.41*** join/#htc-linux Mavy (mavfree@unaffiliated/mavy)
07:00.02WisTilt2thanks.  i wont have to take so much time from arrrghhh and rpierce99.  they have put many hours in tracing things for me on those 400's
07:00.10*** join/#htc-linux ychavan (ychavan@nat/redhat/x-celhmzwcvzjelxkw)
07:00.19sykosoftsure, no problem
07:00.33sykosoftRight now, I'm running winmo on one, and acl's nand on another
07:00.35rpierce99wouldn't be so bad if the time difference wasn't such a PITA :)
07:00.59WisTilt2time diff is a problem for sure
07:07.01WisTilt2rpierce99 did that last one blow up your phone?
07:07.16rpierce99oh you said you wanted to make sure it booted, sorry
07:07.17rpierce99lol
07:07.35rpierce99oh missed the next msg
07:08.06WisTilt2i do that frequently
07:11.46rpierce99grep MASK again?
07:12.24WisTilt2yep
07:12.27rpierce99[   47.851562] MASK0: 2019ff27
07:12.27*** join/#htc-linux bukington (~bukington@fac34-2-82-228-151-145.fbx.proxad.net)
07:12.27rpierce99[   47.871520] MASK1: 2019ff2f
07:12.27rpierce99[   47.871520] MASK0: 2a84
07:12.28rpierce99[   47.891479] MASK1: 2a84
07:12.57WisTilt2ok thats good too
07:13.05rpierce99i kexeced on this one, #34 is correct?
07:13.11WisTilt2yes
07:13.23rpierce99sweet, <3 having adb and kexec
07:14.24WisTilt2how are you kexec'ing cmd line?
07:15.06rpierce99huh? what i meant was i couldn't adb push before, no way to get kernel onto sd card, so now adb push + kexec = good
07:16.37WisTilt2saves a lot of time and glad detule figured out that mac prob with adb
07:22.50*** join/#htc-linux toastcfh (~toastcfh@41-32.200-68.tampabay.res.rr.com)
07:23.22sykosoftlooks like the batteries are the same
07:23.48WisTilt2nice.
07:26.00*** join/#htc-linux kiozen (~kiozen@p5DDF2ABC.dip.t-dialin.net)
07:32.42rpierce99anything else quickly before i head to bed WisTilt2 ?
07:33.23WisTilt2no that is good for now.  i still have a conflict with the modem clock so ill work on it tomorrow.  thanks again as usual:)
07:33.33rpierce99yep, gnight
07:33.58WisTilt2im out too.  sykosoft thanks again on the 400 and ill catch you tomorrow
08:01.56*** join/#htc-linux lamikr (lamikr@nat/nokia/x-dzttdfbxfkllzzkn)
08:25.09*** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl)
08:45.03*** part/#htc-linux sykosoft (~sykosoft@67-61-60-19.cpe.cableone.net)
08:52.04*** join/#htc-linux mes (~mes@24.69.210.121)
09:07.32*** join/#htc-linux LjL (~ljl@unaffiliated/ljl)
09:15.11*** join/#htc-linux dobrin (~dobrin@85.91.150.26)
09:57.33*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
10:04.45*** join/#htc-linux gauner1986 (~Miranda@87.253.171.209)
10:13.29*** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl)
10:24.52*** join/#htc-linux furtardo (~mks@nat/yahoo/x-jhxbfubkwtpuwpxy)
11:04.21*** join/#htc-linux ychavan (ychavan@nat/redhat/x-aqgyubxhtduvcsos)
11:06.40*** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl)
11:07.10*** join/#htc-linux lamikr (lamikr@nat/nokia/x-fmgqpvlhrrcqdxkz)
11:57.40*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:f183:1393:4233:9d2c)
12:02.46*** join/#htc-linux ychavan (ychavan@nat/redhat/x-qwafpdyqkcayxyiu)
12:04.01*** join/#htc-linux MethoS- (~clemens@134.102.106.250)
12:11.40*** join/#htc-linux NetRipper (~netripper@tikkie.net)
12:13.37*** join/#htc-linux ychavan (ychavan@nat/redhat/x-mxpamrwighzacdbo)
12:38.34*** join/#htc-linux infernix (nix@unaffiliated/infernix)
12:46.55*** join/#htc-linux Sandvold (~Sandvold@213.236.244.131)
12:47.49*** join/#htc-linux Andreyxxl1 (~Andreyxxl@94.52.236.39)
12:53.57*** join/#htc-linux Sandvold (~Sandvold@213.236.244.131)
13:02.51*** join/#htc-linux GNUtoo (~gnutoo@host40-58-dynamic.116-80-r.retail.telecomitalia.it)
13:07.19*** join/#htc-linux bikerer (~bike@ti0128a380-dhcp0338.bb.online.no)
13:16.22*** join/#htc-linux bartman (~bart@2607:f2c0:a000:175:2e0:81ff:fe47:3d01)
13:29.31*** join/#htc-linux detule (~detule@hw-ma-6l13f61.mat.jhu.edu)
13:31.28*** join/#htc-linux Sandvold (~Sandvold@207.80-202-111.nextgentel.com)
13:36.56*** join/#htc-linux lardman|work (~lardman@138-38-179-9.docking.bath.ac.uk)
13:37.54lardman|work~seen lkcl
13:38.03aptlkcl <~lkcl@host86-131-183-114.range86-131.btcentralplus.com> was last seen on IRC in channel #arm-netbook, 151d 11h 45s ago, saying: 'night.  or... morning.  ouch :)'.
13:38.12lardman|workoh
13:38.30lardman|workAnyone here have any info about PowerVR USSE opcodes/assembly?
13:53.12*** join/#htc-linux toastcfh (~toastcfh@unaffiliated/toastcfh)
14:08.21*** join/#htc-linux vinceweis (4463ed13@gateway/web/freenode/ip.68.99.237.19)
14:20.13*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
14:24.43*** join/#htc-linux rzk (~rzk@95-24-54-101.broadband.corbina.ru)
14:26.45*** join/#htc-linux paulk (~paulk@lib33-1-82-233-88-171.fbx.proxad.net)
14:28.07*** join/#htc-linux TheXev (nat32@1.sub-75-242-112.myvzw.com)
14:41.26*** join/#htc-linux helicopter88 (~helicopte@188.11.59.253)
14:41.27*** join/#htc-linux newbie (~helicopte@188.11.59.253)
14:41.30*** join/#htc-linux newbie1 (~helicopte@188.11.59.253)
14:47.55*** join/#htc-linux TheXev (nat32@1.sub-75-242-112.myvzw.com)
14:48.50*** join/#htc-linux bikerer (~bike@ti0128a380-dhcp0338.bb.online.no)
14:54.11*** join/#htc-linux rzk (~rzk@95-24-54-101.broadband.corbina.ru)
14:57.01*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
15:00.41*** join/#htc-linux crypticmofo (~crypticmo@c-67-164-217-108.hsd1.ca.comcast.net)
15:28.08*** join/#htc-linux kiozen (~kiozen@p5DDF2ABC.dip.t-dialin.net)
15:29.44*** join/#htc-linux emwe (~mweirauch@cable-86-56-10-252.cust.telecolumbus.net)
15:31.36*** join/#htc-linux LordDeath (~LordDeath@xdsl-87-78-106-12.netcologne.de)
15:34.44*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
15:36.16*** join/#htc-linux EdLin (~EdLin@securabit/listener/edlin)
15:45.55*** join/#htc-linux mitsutaka (~mitsutaka@KHP222227247006.ppp-bb.dion.ne.jp)
16:36.59*** join/#htc-linux Cotulla (~myfakemai@nat100-255-205-109.tvoe.tv)
16:37.27Cotullahi
16:38.34*** join/#htc-linux kiozen_ (~kiozen@p5DDF2ABC.dip.t-dialin.net)
16:40.11*** join/#htc-linux x1o (57f54144@gateway/web/freenode/ip.87.245.65.68)
16:40.33*** part/#htc-linux x1o (57f54144@gateway/web/freenode/ip.87.245.65.68)
16:42.28*** join/#htc-linux kiozen (~kiozen@p5DDF2ABC.dip.t-dialin.net)
16:42.47arrrghhhCotulla, what's up
16:43.45*** join/#htc-linux mastermerlin (~Adium@pD9E2EA77.dip.t-dialin.net)
16:49.07*** join/#htc-linux kiozen (~kiozen@p5DDF2ABC.dip.t-dialin.net)
16:51.08*** join/#htc-linux [acl] (~abel@96.246.167.90)
16:51.19[acl]Cotulla: my good man.. got a minute ?
16:51.38*** join/#htc-linux WisTilt2 (~wisgreg@wireless251.wirelesstcp.net)
17:00.40arrrghhhWisTilt2, how goes it
17:00.44Cotullayeah
17:01.53WisTilt2morning arrrghhh
17:03.07WisTilt2arrrrghhh does neocore run in winmo and if so what kind of fps?
17:04.38[acl]Cotulla: just wanted to compare some notes with you
17:04.43Cotullanotes?
17:04.47Cotullaokay
17:04.59[acl]Cotulla: about gsm panel. You are on a rhod210 right ?
17:05.27Cotullamy is T-Mobile from USA, without front camera
17:05.39[acl]Cotulla: i have no idea what that is
17:05.41[acl]lol
17:05.44rpierce99it's a 210
17:05.46[acl]coo
17:05.57Cotullatell me SMEM address where it stored I don't remember it
17:06.06[acl]Cotulla: for rhod 300 the vregs for panel are 11 and 13. I just wanted to see if it was the same for 210
17:06.13arrrghhhWisTilt2, i don't know of any benchmark apps on winmo.  neocore won't run for sure.
17:06.15rpierce99Cotulla: its under the battery
17:06.18arrrghhhi'll see what i can dig up
17:06.39Cotullalol
17:06.39WisTilt2just wanted some kind of comparison but no biggie
17:06.49[acl]Cotulla: im sure by now you got the whole panel shit sorted out.. so spill the beans :-p
17:06.54Cotullarpierce99, epic
17:06.58Cotullalet me check
17:07.28CotullaNM8RHOD210
17:07.30*** join/#htc-linux crypticmofo (~crypticmo@c-67-164-217-108.hsd1.ca.comcast.net)
17:07.30Cotullalol really
17:08.17arrrghhhWisTilt2, perhaps this will help...? http://forum.xda-developers.com/wiki/index.php?title=Developing_a_graphics_driver_for_Windows_Mobile
17:08.47[acl]Cotulla: spill it !!!
17:09.04Cotullaw00t?
17:09.30[acl]Cotulla: vregs yo.. same on 210 as 300? just wanna make sure.
17:09.35Cotullabeans?
17:09.42[acl]lol
17:10.21CotullaI don't know about vregs exactly
17:10.28[acl]how is this possible?
17:10.40arrrghhhfake Cotulla
17:10.40CotullaI am using modified code from .27 :)
17:10.46Cotullabut if same rom runs on both devices
17:10.48CotullaRhodium
17:10.52Cotullaso it must be same too
17:11.04[acl]Cotulla: i havent even submitted the patch for vreg on .27
17:11.04Cotulla300 is GSM too?
17:11.11[acl]Cotulla: yeah gsm too
17:11.20[acl]Cotulla: whats on .27 now is wrong
17:11.22arrrghhhCotulla, 100, 110, 210 & 300 are all GSM only.
17:11.42[acl]Cotulla: anyways, so you arent powering down the panel i take it.
17:11.49Cotullawait
17:12.20CotullaI remember when we turns on GPS panel turns off
17:13.07Cotullabut same WM rom can work on both devices
17:13.11Cotullaso vregs also must be same
17:13.14Cotullaright?
17:13.38emwedifferent codepaths per variant?
17:13.50Cotullawait
17:14.07emwe[acl]: i can confirm vreg 3/4 and 11/13 kill data for me on sleep quite immedeately on suspend.
17:14.20[acl]emwe: but thats on cdma right
17:14.20emwe(RHOD400 for those forgetting like me)
17:14.27emwerunning GSM
17:14.29Cotulladisptools.dll
17:15.26CotullaMDDI_Bridge_PowerUp
17:15.59Cotullathey touch only BIT_PM_VREG_RFTX  BIT_PM_VREG_RFRX2  from comments
17:16.02Cotullabut maybe they lie
17:16.03[acl]yup
17:16.07[acl]no thats right
17:16.17Cotulla0x800 & 0x2000
17:16.20Cotullamasks
17:16.28CotullaGPIO82
17:16.31[acl]11 and 13
17:16.35[acl]like i said
17:16.44[acl]so you confirm thats on 210 as well.. awesome..
17:16.44Cotullaya
17:16.50[acl]now thos poor bastards 100
17:16.52[acl]will suffer
17:16.54Cotullait's inside disptools.dll
17:17.01Cotullaand rom can work on 210 too
17:17.08Cotullait's GSM rom dump
17:17.09[acl]Cotulla: thats how i got it too.
17:17.13Cotullanot from RhodiumW
17:17.20[acl]Cotulla: rhodiumW is a diff animal
17:17.26[acl]no traces of vregs on disptools
17:17.52[acl]just uses gpio 0x63 0x62 and sets em to 1 or 0
17:17.56[acl]but thats not enough to power up
17:18.00[acl]so something is missing
17:18.17Cotullaare u talking about RHOW now?
17:18.21[acl]yeah
17:18.26Cotullasend me disptools
17:18.27[acl]just saying how its just complately diff
17:18.31Cotullaand I will open the truth for u :P
17:18.33[acl]i dont have it on me. maybe later
17:18.37Cotullaok
17:18.46Cotullait's different devices
17:18.47Cotulla:P
17:18.54[acl]yup
17:18.55emwe[acl]: RHODW panel won't come up on nand, do i get that right?
17:19.11[acl]emwe: well it does because mddi is powered on bootloader
17:19.29[acl]so we just power down the pannel via mddi reg instead of killing vreg
17:19.43emweand vreg stays on?
17:19.45[acl]but its more stable than gsm, so it never botherd us
17:19.53[acl]yeah vreg must stay on since i cant find what it is
17:19.57emwek
17:19.59[acl]ill send cotulla the disptools to help
17:20.16emwei only got the topa 2.53S2 around. won't help likely
17:20.26[acl]yeah wont help
17:20.37emwei even found a TIAGC.csv for tpa2016d2 speaker amplifier in my topa rom dump
17:20.44emweperhaps it also has that chip ...
17:21.03CotullaI have 2.53 tpz too
17:21.10Cotullano TPZ doesn't have it seems
17:21.21emwethen htc just shipped the csv for no good reason.
17:21.29Cotullajust copy & paster
17:21.30Cotulla:)
17:23.02Cotullait maybe good reason to disable copy & paste
17:23.11Cotullato prevent copy and paste errors
17:23.12Cotulla:)
17:28.25[acl]Cotulla: so what else is new? still drinking bad milk ? :-p
17:28.26[acl]ol
17:28.59Cotullafound one issue in MAGLDR . . . fixing it
17:29.36*** join/#htc-linux helicopter88 (~helicopte@188.11.59.253)
17:30.22*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
17:31.04[acl]prob an issue with vreg
17:31.05[acl]:-p
17:31.24Cotullait's on Samsung Focus  . . .
17:31.39Cotullaissue - imprecise data abort
17:34.42[acl]damn magldr on sammy ?
17:34.45[acl]crazy
17:35.17Cotullayes
17:35.20jonprythats the worst kind of data abort
17:35.30Cotullaright, boat owner X_x
17:35.43jonprynot anymore
17:35.48Cotullait's @^(*%$%6%267442345^@%@%$@$%^%@ &@& ^&@^  * @*$&@*$& !!! $@(*$(* (( @($@$@$ (*@($@)((((((((((((
17:36.01Cotullawhat happened?
17:36.11CotullaJack Sparrow captured it?
17:36.13jonprywhoa magldr is in scheme?
17:36.28jonpryno i am moving back to dry land
17:36.29[acl]jonpry: how goes your 3d adventures ?
17:36.56Cotullasorry jonpry ur 3d in another castle?
17:37.04jonpryi fixed the rendering bugs so it looks pretty good now
17:37.07Cotullaoh
17:37.10[acl]sexy
17:37.13Cotullaso where was a problem?
17:37.32jonpryneed to make it faster. i more or less have a scheme for doing high speed texture updates
17:37.41jonprybut there is one really fugly part
17:38.00[acl]lol
17:38.38jonpryall gralloc's have to take place from the surfaceflinger drawing thread
17:38.48jonpryso need to make some queues and stuff like that
17:39.05[acl]jebus
17:39.10jonprythen things will be able to gralloc at the system framerate
17:40.15jonpryoh rendering problem was the bad blob
17:40.47[acl]bad blob?
17:40.55[acl]your binary was effed up?
17:41.15jonpryyeah the 1.1 blob was no good, but i patched it up for ya
17:41.33[acl]hmm interesting. i patched my own and i dont think i released it to anyone
17:41.40[acl]what was wrong with it
17:41.52jonpryfrx7.1 has some kind of gles 1.1 binary
17:42.04[acl]mine came from omgb so i patched that one up
17:42.13jonpryit was allocating textures in the middle of the framebuffer
17:42.20[acl]ahh
17:42.22[acl]memory
17:42.34jonprybut now we haz working necore in gingerbread
17:42.40[acl]makes sense
17:42.55[acl]what are we pumping on neo right now ?
17:43.04jonpry20.1?
17:43.07[acl]hmm
17:43.18[acl]im tempted to try the alex panel hack
17:43.23[acl]and mdpi this bitch
17:43.32[acl]he was around 27/28 with mdpi
17:43.34jonpryWisTilt2 has overclocked the ram to over 200mhz
17:43.50[acl]lol
17:43.56jonpry28's or so
17:44.15WisTilt2and had meltdown:)  above 200 is no good unless you keep the device nice and cool
17:44.24[acl]i can imagine
17:45.16[acl]the advantage of halving our res is that we dont need to OC
17:45.37[acl]and if we did, well then you max out at 30 probabbly
17:46.28jonprythat would really suck for compositor
17:46.43[acl]30 woudl suck?
17:46.49jonprymdpi
17:46.54[acl]why?
17:47.05[acl]we can use the original blob
17:47.09jonprythrowing away half the screen
17:47.26jonprygames is one thing. but all apps at half res. ugh
17:48.02[acl]well how would the compositor even know
17:48.32[acl]the change itself would be on the panel
17:48.39[acl]so we would add it to the fb as mdpi
17:48.54[acl]alex can answe this i guess. he is doing it now
17:49.00jonpryit wouldn't know. it would just look like crap
17:49.22arrrghhh[acl], but KOVS is MDPI is it not?
17:49.31arrrghhhqvga or whatever
17:49.53emwewvga
17:50.04emweon a 3" or so screen
17:50.05arrrghhhemwe, i thought that was rhod's screen res
17:50.07emweeven smaller then topa
17:50.14arrrghhhoh poop
17:50.15arrrghhhyou're right
17:50.17*** join/#htc-linux Alex[sp3dev] (~alexander@178.176.159.104)
17:50.20arrrghhhit is 480x800
17:50.20emwethere he is
17:50.22arrrghhhspeak of the devil
17:50.25Alex[sp3dev]rumours of me using mdpi have been greatly exaggerated!
17:50.29emwelol
17:50.30arrrghhhlmao
17:50.39emwei knew he is a log stalker as well arrrghhh :)
17:51.07Cotullalol alex
17:51.14Alex[sp3dev]WisTilt2: could you share your overclock diff?
17:52.03[acl]Alex[sp3dev]: my good man
17:52.12[acl]Alex[sp3dev]: so whats your pixle double poop
17:52.33WisTilt2Alex[sp3dev]: sure, when i get it all integrated in our current clock code.  right now im using our own portion of clocks that we use on our own device.
17:52.36[acl]arrrghhh: haha.. yes Alex is the devil
17:52.37Alex[sp3dev][acl]: i'm not using it, because it looks even worse than a native qvga screen
17:53.03[acl]Alex[sp3dev]: fuck but your screenshots were almost unnoticeable .. or do i need glasses ?
17:53.03[acl]:-(
17:53.18*** part/#htc-linux Alex[sp3dev] (~alexander@178.176.159.104)
17:53.19*** join/#htc-linux Alex[sp3dev] (~alexander@178.176.159.104)
17:53.21Blistaexit
17:53.24Alex[sp3dev][acl]: well, for 3d, maybe
17:53.41[acl]im still interested in trying
17:53.42[acl]lol
17:53.48Alex[sp3dev]but for ui and fonts.. horrible. even more horrible than my sgs ;)
17:53.52Blistais termo-dyslexic again
17:53.56WisTilt2[acl]: will changing the panel refresh to 70hz do us any good?  thats as fast at these panels will go.
17:54.21[acl]WisTilt2: means our theoretical max will go from 30 to 35
17:54.31[acl]so not bad
17:54.32[acl]lol
17:54.37WisTilt2yeah sounds like it.  these only do 50hz - 70hz
17:54.47Alex[sp3dev]damn i've deleted my cm7 tree to free up some space to try cm9 on iconia... is cm9 usable with software rendering on msm7k?
17:54.56Cotullaformats Blista's brain again and installed DOS instead behh
17:55.02[acl]Alex[sp3dev]: yeah.. but its FUCKING SLOW
17:55.20[acl]im tracking the evervolv team who is just wronging cm9 for hero and heroc
17:55.33rpierce99oh good glad you're on an iconia Alex[sp3dev], just bought one on sunday, still waiting for it to get here, but was hoping there was someone doing dev work on it
17:56.00Alex[sp3dev]rpierce99: i've shoved ubuntu and chromeos 2.6.38 kernel there back in july
17:57.50rpierce99what do you run day to day on it
17:58.11Alex[sp3dev][acl]: hum.. don't feel like checking out cm7 again.. we'll see how slow this cm9 thingie is
17:58.40[acl]Alex[sp3dev]: i did one last sync myself. Cm7 itself is so slow i just lost all faith
17:59.04jonprywhy is cm7 slower than xdandroid?
17:59.08Alex[sp3dev][acl]: just throw away cm7 adw
17:59.28Alex[sp3dev]jonpry: cause they're using a special version of adw that's like 10 times slower than a paid adw
17:59.41jonpryhmm
18:00.19[acl]Alex[sp3dev]: im happy with omgb. fuck cm bro..lol just not for me
18:00.28jonpryi have cm9 setup for armv6j jit and what not
18:01.01Alex[sp3dev]rpierce99: i'm mostly running android because ubuntu is not really finger-friendly.. maybe i should look into it
18:01.26Alex[sp3dev]jonpry: tried war3z adw launcher ex? or maybe launcherpro?
18:01.59jonpryno not yet. i'm hoping hw composition will make it fly regardless
18:04.16[acl]jonpry: you never let me down.. so i dont think you will begin.. i have faith on your composition project
18:04.24[acl]ur still stab worthy ..lol
18:04.48[acl]i know bzo gets jealous he is only punch worthy.. but hey.. you know the rules
18:04.56jonprylol
18:05.28[acl]Alex[sp3dev]: bro.. ever dove into that jpeg poop for camera ?
18:05.59jonpryi can't get it done pretty easily. but i am not sure other 3d apps will ever work right with it
18:06.07Alex[sp3dev][acl]: not yet.. so you have poop on 27 and your drivers/media is the same as our main tree?
18:07.09[acl]i think so
18:07.18[acl]gsm is consuming all my time recently
18:07.44[acl]Alex[sp3dev]; but im content with the party party stop gap, but idealy the cm jpg is the way to go.
18:07.47Alex[sp3dev]and btw.. who da fuck made ril default to cdma when htc_hw is not found?
18:08.10[acl]Alex[sp3dev]: lol. i have a modded ril so i dunno about the stock one
18:08.19[acl]I had to change some stuff but it works fine so far
18:09.40*** join/#htc-linux balans2 (~user@82-170-217-205.ip.telfort.nl)
18:11.01[acl]Alex[sp3dev]: no other build has perms like xdandroid, so had to butcher the way things are done. took ideas from how samsung does this stuff
18:11.23Alex[sp3dev][acl]: which kind of perms? i've just set everything to like 666
18:11.40[acl]Alex[sp3dev]: no like ril starting up ppp
18:11.45[acl]and doing cdma. setprops
18:12.13Alex[sp3dev]ah. i just copied your stuff but 'refactored' ril a bit and named the property xda_pppd instead of cdma_pppd
18:12.16[acl]i highly doubt cm will bend over for my build, so had to change ril
18:12.26[acl]i had to rename it again
18:12.27[acl]for gms
18:12.29[acl]*gsm
18:12.40[acl]now its called ppp_runner which is a wrapper for ppp
18:12.41[acl]lol
18:12.56[acl]i swer those gsm fucks better be greatful
18:13.06Alex[sp3dev]that's starting to be javayly (if that is a word)
18:13.41[acl]Alex[sp3dev]: ive yet to successfully power down and up the panel on gsm. We have the vreg and the lcd reset gpio. But the panel does not come back up
18:13.52*** join/#htc-linux kiozen (~kiozen@ppp-93-104-83-75.dynamic.mnet-online.de)
18:13.55[acl]i know you have this working flawlessly right ?
18:13.57[acl]any advice ?
18:14.17[acl]vreg itself works, but once the reset gpio is triggered it goes down and not coming back up
18:14.27Alex[sp3dev][acl]: panel was the first thing i did on the kovsky project.. so i just did like wince disptools does
18:14.54[acl]yeah same here, so i wonder if its my init. gsm disptools is diff than cdma
18:14.56Alex[sp3dev]well, after the reset you have to reinit mddi.. and timings are critical
18:15.02[acl]so my original panel regs may be wrong
18:15.48[acl]i guess something that i can fix with another all nighter
18:16.32Alex[sp3dev][acl]: does alarm clock always work in your builds?
18:16.45[acl]depends on the radio
18:17.01[acl]arrgg uses it religiously apparently but on older radios it kinda poops a bit
18:17.04[acl]so does gps
18:17.15[acl]arrrghhh: yoo. how alarm go for you?
18:17.54arrrghhhalarm?
18:18.11[acl]yeah..
18:19.12[acl]cuz there was this one dood who said it works, but then the panel would nto come up. and all i saw on his logs were radio errors.
18:19.41Alex[sp3dev]actually it's mostly alarm ioctls that fail. but again, on my sgs they fail too but it always works
18:19.57[acl]i think the biggest pain in the ass right now
18:20.00[acl]is the ringer
18:20.09[acl]when the phone is asleep
18:20.22[acl]and i make a call to it, its like a full 2 or 3 seconds the phone wakes up
18:20.39[acl]log wise it wakes up pretty fast, but by the time the damn phone app fires up its just way too late
18:21.43arrrghhhthe phone app is a complete bag of ass
18:21.48arrrghhhmakes me rage
18:22.01Alex[sp3dev]android is a complete bag of dicks
18:22.17arrrghhhlol
18:22.50Cotulladicks? not cunts?
18:23.04Cotulla:D
18:34.26*** join/#htc-linux helicopter88 (~helicopte@188.11.59.253)
18:46.25*** join/#htc-linux kiozen (~kiozen@ppp-93-104-83-75.dynamic.mnet-online.de)
18:47.52*** join/#htc-linux gauner1986 (~Miranda@tmo-102-87.customers.d1-online.com)
18:49.10*** join/#htc-linux newbie1 (~helicopte@host121-199-dynamic.181-80-r.retail.telecomitalia.it)
18:50.11*** part/#htc-linux Alex[sp3dev] (~alexander@178.176.159.104)
18:58.37*** join/#htc-linux gauner1986 (~Miranda@tmo-103-108.customers.d1-online.com)
19:01.29*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
19:41.19*** join/#htc-linux avinashhm (~avinash-h@192.94.92.14)
19:48.53WisTilt2[acl]: i changed vsync on panel to 70hz and something else must be locking it to 30fps. hits 30.1fps now and then but same as with 60hz.
19:49.29[acl]WisTilt2: that's the only limit that im aware of
19:50.26WisTilt2maybe 30fps is all these things can do.  doesnt go any higher even with gpu oc'd
19:51.13[acl]question here is if we can verify the vsync is actually going at 70
19:51.30[acl]you may need to mod up a kernel and enable some time debug prints.
19:51.34[acl]not sure how else to verify
19:52.06WisTilt2it is, at least i have the panel configured at that rate.  panning stuff looks less blurry but that could be a placebo effect
19:53.13[acl]how about lowering it to 50. In realitythat should lower our fps
19:53.20WisTilt2i slowed it down to 50hz and it is quite noticeable even on switching desktops
19:53.40WisTilt2it did slow it down in neocore but only by 4fps
19:53.55[acl]well take 3d out of the equation
19:53.58detulecan't you count interrupts
19:54.01[acl]concentrate on 2d
19:54.20WisTilt2didnt even try 2d so ill give that a go
19:54.21[acl]2d will hit the limit easy
19:54.29[acl]we do now at 30
19:54.32[acl]no OC needed
19:54.38[acl]breaking that is the goal
19:54.52detulepowertop ftw
19:55.19[acl]detule: you can count interrupts or just change the code around to report fps based on vsync
19:55.23[acl]depends how much time you have
19:55.27[acl]and if you have a full time job
19:55.28[acl]:-p
19:55.47[acl]i think the msm_fb has some of this in there you can enable
19:55.59detulejust need a debian chroot, you can use powertop it will count all interrupts for you
19:56.22[acl]but how will you know when to start and end
19:56.23[acl]?
19:56.27[acl]vsync is always on
19:56.33detuleit gives you per second numbers
19:56.37[acl]ahh
19:56.42[acl]a rate you mean
19:56.45detuleas in the frequency
19:56.54[acl]sexy
19:57.13[acl]i forgot the app we used before to test for 30
19:57.26detulefps2d?
19:57.33detulethat guy hits 29.5 or something
19:57.33[acl]probably
19:57.40[acl]we hit 30 now
19:57.45[acl]thats how we know its the limit
19:57.46[acl]lol
19:59.18jonpryrhod can do 90 no prob
19:59.39jonprylittle little liquid n2, vcore at like 5volts
19:59.58[acl]lol
20:00.18[acl]you are close.. i think someone hit 84 before with panel off meaning no vsync
20:01.58jonpryi dunno if wistilt2 has started turning up the juice for these OC experiments yet
20:02.09jonprygotta be the next step
20:07.21WisTilt2jonpry: so these things can do 90fps in 2d?
20:07.46jonprywith the right clocking and cooling
20:08.12WisTilt2and yes i am pouring the juice to the gpu now but 30fps is where it is stuck
20:08.32WisTilt2gets a lot warmer so might be hitting it a bit too much
20:08.46jonpryyou upped the regulator voltage?
20:08.59WisTilt2no only clock
20:09.23jonprylpddr should be run at 2v
20:09.34WisTilt2what is its default do you know?
20:09.38jonpry1.8
20:11.17WisTilt2hmm, that will just make it hotter wont it? its clocking higher now, just cant get past 30fps.  if i slow it down i can see it drop to 29,28 etc, and going up another 20% from 29fps only gets it to 30fps
20:12.05jonpryvoltage==speed
20:12.29WisTilt2ill try 2v and see if it starts smoking:)
20:12.39jonpryi ran a piece of it at almost 3v for a while
20:12.51jonpryblew up the processor, but memory was fine
20:13.13[acl]lol
20:14.01jonprythis is really only useful if you want to get 230mhz to work right
20:21.37jonprythere are some comments in surfaceflinger that talk about how if you can't render in 1/vsync time the framerate will be halved. but this doesn't make much sense to me
20:22.41*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
20:23.37jonpryif thats true for whatever reason, shouldn't that make you get more or less stuck at factors of vsync?
20:24.13jonpryer 10,12,15,20,30 ?
20:28.24[acl]jonpry; yeah
20:28.27[acl]vsync is a whore
20:28.48[acl]i dont know if we have the ability to not wait for vsync
20:30.18detulewait but we see a range of fps, not just those notches
20:33.38jonpryyeah like that
20:34.20rpierce99but those are averages, no? if it bounces between 20 and 30, but stays more on the 20 than the 30, you could get 20.1
20:34.21jonpryi don't see where its waiting for vsync. presumably we can do something a little more bold because of this strange tripple buffering thing that is going on
20:35.25jonpryrpierce99, thats true. but i think the distribution would make it very difficult to get say 25. most things will be very near the bin
20:38.26WisTilt2detule: i cleaned up the 3.0 autobuild so we're building clean now
20:40.10WisTilt2i need to grab lunch and head off to a meeting so catch you tonight guys.  arrrghhh let me know how that slowdown test kernel works so i know i have the right register for cdma.
20:40.26*** join/#htc-linux NeoMatrixJR (~chatzilla@173-20-63-62.client.mchsi.com)
20:52.10*** join/#htc-linux lardman|work (~lardman@138-38-179-9.docking.bath.ac.uk)
21:09.01arrrghhhcrap.
21:10.23*** join/#htc-linux LordDeath (~LordDeath@xdsl-87-78-106-12.netcologne.de)
21:12.52*** join/#htc-linux swc|666 (~gecko@unaffiliated/swc666/x-4934821)
21:26.24arrrghhhjonpry, you thar?
21:28.19jonpryyo arrrghhh
21:28.40arrrghhhdo you know what wistilt2 wanted out of that test kernel he is having me try?
21:28.50arrrghhhhe said something about it being really slow, 10fps in neocore or smth.
21:28.52[acl]Cotulla: yooo
21:28.56[acl]Cotulla: still here ?
21:29.01[acl]Cotulla: http://dl.dropbox.com/u/12183048/htctopaz/re/disptools.rhod.sprintmr1.dll
21:29.04[acl]tell me the truth !!!
21:29.05jonpryarrrghhh, yeah wanted to know if its slow on your cdma
21:29.07arrrghhhbut it's not.  i put in your egl and GLES libs, and it's faster... i'm getting 20-22fps.  textures are SOL
21:29.23arrrghhhjonpry, it's certainly not slow.  but textures are missing still.
21:29.42jonpryhard to tell speed when it isn't fully rendering though
21:29.57jonpryshould be close to 30 with no textures i think
21:30.14[acl]effin qcom cheats
21:30.19[acl]i think they use compressed textures
21:30.36Cotullahey [acl]
21:30.36jonprywho doesn't
21:30.38Cotullau fucking fast
21:30.49[acl]jonpry: android itself since they cant compress on the fly
21:30.55[acl]so all android textures are raw
21:31.16jonprybut we don't have hw composition yet
21:31.26[acl]gl wise it makes a difference
21:31.42jonpryneed moar gpu1
21:31.53[acl]Cotulla: dll time
21:32.02Cotullayes there no vregs at all
21:32.03Cotullafor mddi
21:32.08Cotullaonly gpio
21:32.10Cotullathey
21:32.16*** join/#htc-linux avinashhm (~avinash-h@192.94.92.14)
21:32.21Cotullaconfig 98
21:32.25Cotullaconfig 99
21:32.28Cotullasleep 20
21:32.34[acl]yeah we have this
21:32.34Cotullaset 81
21:32.39Cotullasleep 10
21:32.40[acl]vreg !!!
21:32.42[acl]we want vregggg
21:32.43Cotulla*82
21:32.56Cotullaset clear set
21:32.59Cotulla82
21:33.31Cotullathere no vregs 100% inside disptools
21:34.49[acl]damnit
21:34.51[acl]where could it be
21:34.59Cotullau sure u have right code?
21:34.59Cotullashow
21:35.04[acl]disptools
21:35.06[acl]what else
21:35.14[acl]kernel has power down only, no power up
21:35.19[acl]same code too
21:35.59[acl]theory is that power is being done via some iclt somewhere else.
21:36.00Cotullabut maybe problem in details
21:36.44Cotullabtw do u solve issue with button in LK?
21:37.15*** join/#htc-linux TheXev (~user@pool-108-11-141-16.eriepa.dsl-w.verizon.net)
21:37.26[acl]Cotulla: nahh, people were happy they press less buttons
21:37.26[acl]lol
21:37.32[acl]so i didnt bother.
21:37.37[acl]but i should try
21:38.14[acl]besides this is just gsm issue. cdma is happy :-)
21:38.43[acl]Cotulla: another version of the file. Not sure if it will help. prob same shit
21:38.43[acl]http://dl.dropbox.com/u/12183048/htctopaz/re/disptools.rhod.2.07S2_ger.dll
21:40.07Cotullashow ur linux code?
21:40.41Cotullathis is with VREGS and it's from GSM?
21:40.55Cotulla800 & 2000
21:41.17[acl]oops nevermind then
21:41.22[acl]first one is cdma ..
21:41.34[acl]Cotulla: http://gitorious.org/~acl/linux-on-qualcomm-s-msm/linux-msm-rhod-nand/blobs/70f67aaf0402580831518d424e14a4f08f7dadb9/arch/arm/mach-msm/board-htcrhodium-panel.c#line417
21:43.26Cotulla98 99
21:43.28Cotullawhy there 1?
21:43.33Cotullais 1 means that it's alternate 1?
21:44.47[acl]ignore 1. means its a func
21:45.04Cotullafunc?
21:45.05[acl]i think its func, direction, pull, etc etc
21:45.19Cotullayes, but function is must be 0?
21:45.35Cotullaotherwise it some specific function, not gpio output
21:45.38Cotullacheck it
21:46.04[acl]hmm
21:46.08Cotullahttp://gitorious.org/~acl/linux-on-qualcomm-s-msm/linux-msm-rhod-nand/blobs/70f67aaf0402580831518d424e14a4f08f7dadb9/arch/arm/mach-msm/board-htcrhodium-proximity.c
21:46.09Cotullalook here
21:46.15CotullaDEX_GPIO_CFG(PROXIMITY_GPIO,
21:46.15Cotulla38                                0,
21:46.17Cotullahere 0
21:46.53Cotullaand inside config_camera_on_gpios() also 0
21:46.59[acl]ahh shit
21:47.00Cotullau sure it must be function #1 there?
21:47.07[acl]you are right i think ..
21:47.10CotullaI think it's just power gpio
21:47.12[acl]copy and paste casualty
21:47.12Cotullaso try ^^
21:48.01[acl]i like how you use my own code to prove me wrong..
21:48.02[acl]lol
21:48.45Cotullawhy not
21:48.50[acl]its the best way
21:48.53[acl]but you are right
21:49.00Cotullatry it and we know truth
21:49.00[acl]and the reason why i may have made this mistake
21:49.08[acl]is because that was a recent addtion
21:49.15Cotullaif policy of truth won't capture us before
21:49.17[acl]note i commented out the original wherere i just set the gpio
21:49.25[acl]instead do the whole long function
21:49.51[acl]originally it was just gpio_set_value(0x63,1); for on
21:49.55Cotullahttp://www.youtube.com/watch?v=4ty812aSdLo
21:49.55[acl]0 of off
21:50.26[acl]it was blocked in my country :-(
21:50.49Cotullahttp://www.youtube.com/watch?v=3q8bXxPPKno
21:50.51Cotulla?
21:52.43[acl]now i just need speakers
21:52.44[acl]:-(
21:52.53Cotullalol
21:52.55Cotullaepic
21:53.31[acl]this is odd
21:53.39[acl]on my new prox code, this msm_gpio_set_function isnt even needed
21:53.50[acl]or is it.. let me check
22:00.26*** join/#htc-linux mes (~mes@S0106000ce55186df.cc.shawcable.net)
22:03.57*** join/#htc-linux vinceweis (4463ed13@gateway/web/freenode/ip.68.99.237.19)
22:14.21*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
22:17.44Cotullafixed ACL?
22:19.59[acl]i dont think so. ill tell you tomorrow for sure
22:20.11[acl]my new prox code doesnt use the set function
22:20.16[acl]but it works
22:20.50Cotulla?
22:20.52Cotullawhat about camera?
22:20.55Cotullathere 0
22:21.03[acl]yeah
22:21.08[acl]some testing tonight will show
22:21.09[acl]:-)
22:21.14Cotullaokay
22:22.39[acl]anyways i gotta get ready to go.. ill ttyl
22:22.40[acl]thanks
22:33.31*** join/#htc-linux bukington (~bukington@fac34-2-82-228-151-145.fbx.proxad.net)
22:36.40*** join/#htc-linux Echo31 (~olivier@lan31-9-88-177-158-48.fbx.proxad.net)
22:39.58*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:dc31:1d3d:2ec3:442c)
22:41.13*** join/#htc-linux rajkosto (~rajkosto@2001:470:d76b:da7a:dc31:1d3d:2ec3:442c)
22:41.14*** join/#htc-linux mastermerlin (~Adium@pD9E2EA77.dip.t-dialin.net)
22:59.39*** join/#htc-linux MethoS- (~clemens@134.102.106.250)
23:11.42*** part/#htc-linux Cotulla (~myfakemai@nat100-255-205-109.tvoe.tv)
23:13.59*** join/#htc-linux furtardo (~mks@nat/yahoo/x-orwedahkpmfljbwf)
23:17.46*** join/#htc-linux Rajko (~rajkosto@2001:470:d76b:da7a:dc31:1d3d:2ec3:442c)
23:44.18*** join/#htc-linux lardman|home (~lardman@138-38-179-9.docking.bath.ac.uk)
23:46.07*** join/#htc-linux rzk (~rzk@95-24-54-101.broadband.corbina.ru)
23:58.45*** join/#htc-linux furtardo (~mks@nat/yahoo/x-qxkeptsmidcknlmd)

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