IRC log for #htc-linux on 20130207

00:10.47*** join/#htc-linux Ondalf (~ondalf@cable-roi-50ddf8-39.dhcp.inet.fi)
00:39.07*** join/#htc-linux |lippa|^ (~lippa@CPE-121-214-10-65.lnse3.win.bigpond.net.au)
00:42.23*** join/#htc-linux the-leviathan (~quassel@c-82-192-226-27.customer.ggaweb.ch)
00:46.08*** join/#htc-linux lipp[a] (~lippa@CPE-58-170-236-230.lnse4.win.bigpond.net.au)
00:49.10*** join/#htc-linux the-leviathan (~quassel@c-82-192-226-27.customer.ggaweb.ch)
00:50.09jonprydetule, you cracked the code?
00:58.38*** join/#htc-linux lipp[a] (~lippa@CPE-137-147-16-195.lnse7.lon.bigpond.net.au)
01:02.38*** join/#htc-linux |lippa|^ (~lippa@CPE-121-219-76-204.lnse1.lon.bigpond.net.au)
01:07.09*** join/#htc-linux lipp[a] (~lippa@CPE-137-147-3-241.lnse7.lon.bigpond.net.au)
01:11.09*** join/#htc-linux |lippa|^ (~lippa@CPE-121-214-110-208.lnse4.lon.bigpond.net.au)
01:15.08*** join/#htc-linux d3tul3 (~detule@unaffiliated/d3tul3)
01:17.39*** join/#htc-linux lipp[a] (~lippa@CPE-137-147-179-251.lnse7.win.bigpond.net.au)
01:19.34d3tul3jonpry, insert enough debugging statements and something will come up
01:20.43d3tul3the first fifteen buffers or so have normal addresses 0xb59f4000 and looks like they are actually getting processed....at some point weird buffers start getting queued and the vfe starts spitting out axi errors
01:22.02jonpryah
01:23.08*** join/#htc-linux lipp[a] (~lippa@CPE-124-180-131-215.lnse4.lon.bigpond.net.au)
01:23.38d3tul3how's the n4?
01:24.29jonpryi'm trying to boot a custom kernel on it
01:24.56d3tul3can't be that hard
01:25.31jonprywe shall see
01:25.34d3tul3just make sure your ramdisk  is at a correct offset !:p
01:29.40*** join/#htc-linux |lippa|^ (~lippa@CPE-121-220-77-143.lnse2.win.bigpond.net.au)
01:35.40*** join/#htc-linux lipp[a] (~lippa@CPE-121-220-82-171.lnse2.win.bigpond.net.au)
01:36.04jonpryit isn't terribly happy
01:44.49d3tul3shows signs of life though?
01:44.58jonpryfixed now
01:45.05jonpryfully functional
01:45.19d3tul3broke a sweat there eh
01:45.40jonpryi made the mistake of reading a guide
01:45.50jonpryof foolishness
01:46.24jonprythis fastboot thing is pretty nice
01:46.51d3tul3memboot
01:47.07jonpryyeah same as touchpad
01:47.34jonprynot entirely sure why we were trying to flash bootloaders and things
01:56.01jonpryi think it was that guy "craptain"
01:56.23jonpryhe appealed to my jealous nature :p
01:56.44d3tul3who's that
01:56.52d3tul3didn't he have to do something with the touchpad
01:56.55d3tul3back in the day
01:57.00jonpryyeah
01:57.09jonpry<PROTECTED>
01:57.30jonpryand then i was like wth do i want fastboot, and later i just had to have it
01:58.04d3tul3i don't think the s3 has fastboot
01:58.35jonpryin theory that is fixable
01:58.43jonpryjust chain boot it
02:00.03jonpryyou can probably run moboot on that thing
02:01.16d3tul3yeah lk would be a nice idea
02:01.51jonpryso i guess to work on dsp. i need to make a kernel that breaks audio and pil
02:21.06jonpryhrm
02:21.30jonpryi figure this pil_trusted stuff is no good
02:21.35jonpryyou have that?
02:30.09d3tul3i don't understand this interaction between pmem and ion on my kernel
02:30.19d3tul3pil_trusted?
02:30.33jonprypil_q6v4.c
02:30.45jonprystatic struct pil_reset_ops pil_q6v4_ops_trusted
02:31.09jonpryany idea where the dsp hole is?
02:31.24d3tul3yeah it's my 3.4 kernel
02:31.38d3tul3there's a whole in my kernel at afe
02:31.41d3tul30xafe00
02:31.50d3tul3nevermind
02:32.02jonprylike the memory map is atags right?
02:32.18d3tul3yeah
02:32.36jonpryMemory: 134MB 74MB 7MB 1MB 253MB 1456MB = 1925MB total
02:33.05jonpryobviously some serious pmem
02:33.44d3tul3you see something like 08-11 22:01:05.240 WARN : Early memory PFN ranges
02:33.45d3tul308-11 22:01:05.240 WARN :     0: 0x00080200 -> 0x00088d00
02:33.45d3tul308-11 22:01:05.240 WARN :     0: 0x0008f200 -> 0x0008f700
02:33.45d3tul308-11 22:01:05.240 WARN :     0: 0x00090000 -> 0x000afe00
02:33.45d3tul308-11 22:01:05.240 WARN :     0: 0x000ba702 -> 0x000ea000
02:33.45d3tul308-11 22:01:05.240 WARN :     0: 0x000ea100 -> 0x000f7cff
02:33.52d3tul3plenty of holes there
02:34.15d3tul3i know afe000 is where vidc loads firmware on my kernel so that hole is there for a reason
02:34.28jonpryso how to correlate a hole with something?
02:34.57d3tul3yeah no idea write to it with dev/mem and see what breaks
02:35.15d3tul3i came across what afe00 is used purely by chance on my kernel
02:35.45d3tul3wait dev mem won't let you write there nevermind
02:35.51jonprypfn_shift=12?
02:37.38d3tul3yes
02:38.27jonpry80200000-887fffff : System RAM
02:38.28jonpry<PROTECTED>
02:38.28jonpry<PROTECTED>
02:38.28jonpry89000000-8d9fffff : System RAM
02:38.28jonpry8f700000-8fdfffff : System RAM
02:38.28jonpry8ff00000-8fffffff : System RAM
02:38.30jonpry90100000-9fdfffff : System RAM
02:38.32jonprya3900000-fe9fefff : System RAM
02:40.25*** join/#htc-linux DuperMan (Duper@85-250-37-220.bb.netvision.net.il)
02:46.50jonpryfwiw the qdsp entry point is at 0x8da0 0000
02:47.41d3tul3how did you find it
02:47.45d3tul3hole # 1
02:48.25jonpryi patched pil loader thing
02:48.43jonpryi'm not sure that the entire hole belongs to it
02:49.17fakkerslaps jonpry
02:49.49jonpryneed to dump this whole elf header
02:54.20d3tul3i don't get this, it's not like it allocates physical buffer multiple times here
02:54.32d3tul3it allocates it once, and then keeps using the same thing
02:54.55d3tul3so how the hell does it relocate to an abnormal physical location
02:57.10jonprymemory corruption maybe?
03:00.23d3tul3maybe when buffers are released to userspace something bad happens....
03:21.09jonpry<PROTECTED>
03:21.10jonpry<PROTECTED>
03:21.10jonpry<PROTECTED>
03:21.10jonpry<PROTECTED>
03:21.10jonpry<PROTECTED>
03:21.11jonpry<PROTECTED>
03:23.44jonprylooks like all of 8da to 8f7 - 1
03:23.54jonpryyours is the same btw
03:25.16d3tul3you see some 8960 tags there?
03:25.29jonpryyou sent me the firmware
03:25.30d3tul3or it's not device specific
03:25.46jonpryreadelf -a q6.mdt
03:26.01d3tul3thanks
03:29.02jonprygtg
04:05.17d3tul3Chad " Installing a custom version of Linux that is used by Qualcomm developers. It has all their tools installed by default. "
04:05.28d3tul3i heard Chad
04:05.34d3tul3s/heard/heart/
04:23.05*** join/#htc-linux Ondalf (~ondalf@cable-roi-50ddf8-39.dhcp.inet.fi)
04:46.29*** join/#htc-linux d3tul3 (~detule@unaffiliated/d3tul3)
04:46.52d3tul3jonpry, fixed it
04:52.11*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
05:06.22*** join/#htc-linux DuperMan (~Duper@85-250-37-220.bb.netvision.net.il)
05:12.47*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
05:42.42*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
05:52.29jonpryd3tul3, no shit
05:52.36jonprywhat was it?
06:42.08*** join/#htc-linux eR^zeRa` (~zzeratul@ip-84-42-202-42.net.upcbroadband.cz)
06:53.34*** join/#htc-linux kiozen (~kiozen@p578a42db.dip0.t-ipconnect.de)
07:03.34*** join/#htc-linux lamikr (lamikr@nat/nokia/x-layzkbbfumkmqtkd)
07:21.43*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
07:26.43*** join/#htc-linux |lippa|^ (~lippa@CPE-121-219-187-124.lnse2.lon.bigpond.net.au)
08:17.12*** join/#htc-linux lipp[a] (~lippa@CPE-138-217-88-187.lnse4.lon.bigpond.net.au)
09:05.37*** join/#htc-linux a-st (~a-st@unaffiliated/a-st)
10:55.12*** join/#htc-linux |lippa|^ (~lippa@CPE-124-176-178-128.lns3.win.bigpond.net.au)
10:59.42*** join/#htc-linux lipp[a] (~lippa@CPE-121-219-38-122.lnse1.lon.bigpond.net.au)
11:12.42*** join/#htc-linux |lippa|^ (~lippa@CPE-121-219-244-246.lnse1.win.bigpond.net.au)
11:46.52*** join/#htc-linux teemodk (~teemodk@80-62-117-30-mobile.dk.customer.tdc.net)
11:55.25*** join/#htc-linux d3tul3 (~detule@unaffiliated/d3tul3)
11:55.42*** join/#htc-linux teemodk (~teemodk@80-62-117-30-mobile.dk.customer.tdc.net)
12:06.01*** join/#htc-linux gauner1986 (~Adium@87.253.171.203)
12:16.59*** join/#htc-linux nearst (~c0re@pdpc/supporter/monthlybyte/nearst)
12:35.46*** join/#htc-linux helicopter88 (~helicopte@host83-54-dynamic.40-79-r.retail.telecomitalia.it)
13:07.31*** join/#htc-linux Cotulla (~myfakemai@109.205.253.11)
13:09.18Cotullahey
13:09.33nearsthi
13:31.02*** join/#htc-linux d3tul3 (~detule@unaffiliated/d3tul3)
13:49.29*** join/#htc-linux jonpry (~jon@2602:306:c417:8aa0:e107:cfb:6290:8135)
14:02.07Marchi
14:02.33MarcCotulla: changing initrd offset to 16M fixes boot with initrd.gz
14:03.00Marctested with cLK with 16M offset and kernel compiled with 0x12800000 offset (I think that was it)
14:04.19Cotullayes
14:06.07Marcand audio init fail seems to be related to SMD
14:07.18Cotulladid u found reason?
14:08.14Marcdal_open_channel fails
14:08.23MarcI yet have to find out where exactly
14:09.52Marcyey, printk ftw
14:11.23Cotullau slow
14:11.24Cotulla:(
14:12.35Marcwhat? :D
14:12.39MarcI'm making it pretty :P
14:12.52Marcand I didn't do anything yesterday
14:13.35Cotullaokay
14:14.17Marcbtw, I'm actually seeing the second boot animation now ^^
14:14.42Cotullacool
14:16.19Marcsmd_open: -19
14:16.37Marcthat's also what qmi_open is saying
14:16.47detulesmd_open fails at start always
14:17.00Marcthen fix it :P
14:17.11Cotulladetule u sure it's our case?
14:17.22MarcENODEV
14:17.24detuleit does for me...it fails before the modem is up
14:17.38Marcit just keeps reporting -19 ;)
14:17.45Marcso I'm guessing that is not the case here
14:19.40detule08-19 05:37:26.164 INFO : pil pil2: modem_fw: Brought out of reset
14:19.40detule08-19 05:37:28.715 INFO : pil pil1: modem: Brought out of reset
14:19.40detule08-19 05:37:28.720 ERROR: smd_tty_open: DATA1 open failed -19
14:19.40detule08-19 05:37:28.724 ERROR: smd_tty_open: DATA1 open failed -19
14:19.40detule08-19 05:37:28.729 ERROR: smd_tty_open: DATA1 open failed -19
14:19.40detule08-19 05:37:28.733 ERROR: smd_tty_open: DATA1 open failed -19
14:20.38Cotulladelute it's not applicable
14:20.41Cotullait's MSM8960
14:20.50Cotullawe are talking about our dear QSD8250B
14:20.55Cotulla^^
14:21.28detulei am just saying i've seen smd open failing on the rhod as well at boot....might not be the same for you guys
14:22.06detuleCotulla, ' detule ' doesn't mean anything in russian?
14:23.11Cotullanothing
14:24.25MarcI have the feeling smd_get_channel fails big time
14:24.27Marclet's see
14:25.27MarcIn case of emergency: blame detule
14:25.40Cotulla?
14:25.48Marcjust need someone to blame :P
14:25.59Marcwhy is fastboot boot so freaking slow? -.-
14:25.59Cotullabad approach
14:26.01Cotullajust fix it
14:26.07Cotullafrom LK?
14:26.12Marcyeah -.-
14:26.22Marctotal time is always something like 55 seconds
14:26.35Cotullacuz it's LK
14:26.36Cotulla:)
14:26.58Marcfix magldr and I'm back to that :)
14:27.34Marcand yes, smd_get_channel fails
14:29.55detulethere's all those magic offsets when looking for those smd channels
14:30.42Marcyeah -.-
14:32.24MarcI'll just add something like they fixed there: http://sourceware.org/ml/glibc-cvs/2013-q1/msg00115.html
14:32.48Cotulla:D
14:34.17Marcwho would've thought that TWO is in fact -2.0? ^^
14:35.59Marcok, we are looking for channel: DSP_DAL_AQ_AUD, type: 0
14:36.21Marcleft is always the looked for value, right is what we actually have
14:36.24Marcname: DSP_DAL_AQ_AUD vs. DAL_AQ_AUD, type: 0 vs. 1
14:36.30Marcfail there ^^
15:12.14MarcCotulla: looking at the CAF qdsp6 driver it looks like we also shouldn't use smd_open() anymore
15:12.19Marcat least in dal.c
15:16.24*** join/#htc-linux paulk-desktop (~paulk@lib33-1-82-233-88-171.fbx.proxad.net)
15:23.35MarcCotulla: http://pastebin.com/9uP6DzyS
15:27.51fakkerhttp://pic.twitter.com/HZAuEBUm
15:29.50fakkeris hard at work
15:31.06helicopter88fakker, that dolan is very nice
15:31.39fakkerthanks :)
15:33.42fakkerhelicopter88, http://pic.twitter.com/K53Lb1nB my other one
15:34.03helicopter88fakker, the one on the top is nice
15:34.09*** join/#htc-linux nearst (~c0re@pdpc/supporter/monthlybyte/nearst)
15:34.12helicopter88the bigger one is a bit less dolan
15:34.20fakkeryup, it was the first quick drawing
15:34.26fakkeri am filling my notebook full of them
15:34.31helicopter88lol
15:35.05*** join/#htc-linux a-st (~a-st@unaffiliated/a-st)
15:41.21Marcfakker: I was just like "porn or bs?"
15:41.31Marcseems like the latter one
15:42.12fakkerit's not bs
15:46.07helicopter88Marc, it's dolan
16:01.30MarcCotulla: I just booted into android :)
16:01.49fakkeri can too
16:01.51fakkerturns his phone off
16:01.51Marcthen again, it just made a soft reboot :D
16:01.53fakkerturns his phone on
16:01.58Marcwith the 3.0.16 kernel :D
16:02.17fakker3.0.31?
16:02.26Marcno
16:02.29Marc3.0.16
16:02.37fakkeri did 3.0.31
16:02.42fakkercatch up, n00bs
16:03.04arrrghhhRHOD had 3.4
16:03.09fakkerfu
16:03.09arrrghhhfor like a year now.
16:03.17arrrghhhtrolololol
16:03.20fakkerpls see my twitpic link
16:03.22fakkerread text
16:03.24fakkerand do so
16:03.31helicopter88runs 3.0.62
16:03.34arrrghhhhah
16:03.45fakker:p
16:04.55fakkerfuck all of you
16:04.59fakkeri am outta here
16:06.47*** join/#htc-linux paulk-desktop (~paulk@lib33-1-82-233-88-171.fbx.proxad.net)
16:10.21nearstlol
16:12.36Cotullafixed?
16:17.55MarcCotulla: yep, audio seems to actually start now
16:18.01Marcand I'm at the lockscreen :D
16:18.07Cotullahow u fixed it?
16:18.11Marcbut it reboots after a few seconds of doing anything
16:18.44nearstwhat u all working atm
16:19.13Marchttps://github.com/marc1706/android_kernel_leo_3.0.16/commit/bacfe30e82e0b0095cc633f86f26f90468457cf1
16:19.42Marclol, I actually just saw that I nubbed something :)
16:20.23nearstouh, mach-msm :)
16:21.27Marcnow: https://github.com/marc1706/android_kernel_leo_3.0.16/commit/25ac01da5809435b4a8a2f9d9a82244023586b39
16:22.54Cotullalooks not bad
16:23.02MarcCotulla: looking at the 3.0.16 qdsp6 from codeaurora actually helped :)
16:23.37Marcmounting actually seems to fail as far as I can see
16:24.06Marcand the stupid rom is trying to load bcm4329
16:24.13Marcwhich we do not have in the 3.0.16 kernel right now
16:27.15Cotullajust 3.0?
16:32.37Marcwhat do you mean with just 3.0?
16:33.37Marcwell I could add the bcm4329 driver to the 3.0 kernel but the bcmdhd driver is actually the newer driver
16:33.47Marca combined driver for bcm4329 and bcm4330
16:34.38Cotullawhich version is there?
16:34.43Cotulla5.X?
16:37.55Marc5.90.195.75
16:38.27Marctook a while to open that file as my computer is freakishly slow right now :D
16:38.34Marcconverting a video ^^
16:39.05Marcand I have like 420 MB of RAM left xD
16:39.21Marcof 6 GB :D
16:40.26detulewe had bcm4329 running on 3.x on the rhod....perhaps grabbing them from our tree is not a bad idea
16:40.46detulei never figured out where jonpry got them from....some weird lineage
16:41.38Cotullayes new
16:41.50Cotullacode quality is still same
16:41.54Cotullahowever
16:42.15Marchehe
16:46.10Marcit really sucks that you can see the pixels of the leo screen while shooting a video in full hd
16:46.18Marcstupid leo screen :P
16:46.43Marcsmashes the screen with a hammer to increase pixel density
16:50.56*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
17:03.06Cotullajonpry ping
17:07.35Marcjumps in front of junpry
17:07.40Marcjumps in front of jonpry
17:07.41Marc:P
17:07.43Marcpong
17:07.44Marc:P
17:11.29MarcCotulla: also fixed the missing code for creating the partitions in msm_nand: https://github.com/marc1706/android_kernel_leo_3.0.16/commit/0dec1ff54f777f4f2cf795709b107a828f31b1b1
17:12.45Cotullawhy no comments?
17:12.57Marccomments for that function?
17:13.02Marcor in the commit? ^^
17:13.06Cotullafor commit, for changes
17:13.19Marcshould be self-explanatory
17:13.23Marccan add them if you want though
17:13.36Cotullawell
17:13.42CotullaI don't really know why u removed "\n" :D
17:13.47CotullaI have a guess
17:13.48Cotullabut still
17:13.51Marcbecause it's stupid
17:13.58Cotullabut it worked before
17:15.25Marcthere, fixed: https://github.com/marc1706/android_kernel_leo_3.0.16/commit/ef3a4c7e1975feaeebe12b4c58f3e9baad82510d
17:15.45Cotullayeah better now
17:16.20fakkerstupid
17:16.33Cotullafakker.
17:16.36fakkernice work Marc
17:16.52Marcthx
17:17.04MarcI was wondering why adb wasn't working; this explains it: [USB] init(): Failed to register androidplatform driver
17:17.34*** join/#htc-linux nearst (~nearst@pdpc/supporter/monthlybyte/nearst)
17:17.35Marcoh, and rpc is still really broken ^^
17:26.10Cotulla<PROTECTED>
17:26.25Cotullapff in kernel
17:26.26helicopter88/Tiem to eat them
17:30.18Cotulla"which should not roll over until Hell freezes over" :O
18:07.57*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
18:22.49*** join/#htc-linux a-st (~a-st@unaffiliated/a-st)
18:54.12*** join/#htc-linux kiozen (~kiozen@ppp-93-104-67-180.dynamic.mnet-online.de)
19:13.52*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
19:51.03*** join/#htc-linux ltxda (~anon@c-98-194-107-10.hsd1.tx.comcast.net)
19:51.06*** join/#htc-linux ltxda (~anon@unaffiliated/ltxda)
19:52.06jonpryCotulla, pong
19:53.06Cotullahey
19:53.12Cotullalooked today to q6 kernel more
19:53.33CotullaMMU still not clear
19:54.05jonprywhat is the problem?
19:54.17jonpryi'm working on using PIL on v4
19:54.28Cotullamost SMP are using CPU id inside switch_mm() I assume it's done inside HVM
19:56.17Cotullaalso
19:56.30Cotullapage table entries should be mapped to TLB
19:56.39Cotullaitself
19:56.48Cotullato be able access them at tlbmiss
19:57.06Cotullafor the first level it's not hard
19:57.09Cotullajust 6 x 4096
19:57.23Cotullabut the second level is not clear
19:57.54Cotullathere is pte_alloc_one() which just allocate one kernel page
19:58.01Cotullabut not clear how it's mapped
19:59.47jonpryi'll have to look at this
19:59.59jonprynot clear on how this is all implemented on linux
20:00.35Cotullado u got my doubts?
20:00.47Cotullathe first level 1024 x 4
20:00.54Cotullaeach describe 4mb
20:01.03Cotullasecond level 1024 x 4 - each describe 4K
20:02.27Cotullaso we need to be able access second level
20:02.30Cotullainside tlbmiss
20:09.33*** join/#htc-linux a-st_ (~a-st@unaffiliated/a-st)
20:19.51*** join/#htc-linux BabelO (~fcr@2a01:e35:8adc:3150:21e:8cff:fe2d:7d3f)
20:19.51*** join/#htc-linux BabelO (~fcr@unaffiliated/babelo)
20:52.11*** join/#htc-linux a-st (~a-st@unaffiliated/a-st)
21:13.44*** join/#htc-linux helicopter88_2 (~helicopte@host161-93-dynamic.22-79-r.retail.telecomitalia.it)
21:25.14*** part/#htc-linux Cotulla (~myfakemai@109.205.253.11)
23:07.37*** join/#htc-linux detule (~d3tul3@unaffiliated/d3tul3)

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