IRC log for #htc-linux on 20090922

00:02.52mdrobnakali1234, you here?
00:02.59ali1234hi
00:03.25mdrobnakSo it sounds like you have some ideas :-)
00:03.42ali1234sure.
00:03.49ali1234LOADS
00:04.13mdrobnakLOL
00:04.15ali1234the first one is to try only using the upper bank
00:04.32mdrobnakDon't remember if I tried that one.
00:05.27ali1234mi->bank[0].start = PAGE_ALIGN(PHYS_OFFSET+0x10000000);
00:05.27ali1234mi->bank[0].node = PHYS_TO_NID(mi->bank[0].start);
00:05.27ali1234mi->bank[0].size = (128 * 1024 * 1024);
00:05.29mdrobnakSo am I modifying the fixup?
00:05.36mdrobnakI'll take that as a yes.
00:05.37mdrobnak:-)
00:05.38ali1234and dont enable bank[1] at all
00:06.29*** join/#htc-linux nozze (n=nozze@u193-11-162-41.studentnatet.se)
00:06.56ali1234the second one is to put more debugging into pmem.c to see where exactly it is actually triggering the crash
00:07.17mdrobnakI enabled that small amount of debug to get as much as I did..
00:07.43ali1234the third one is to disable the OOM killer and really test out the memory banks
00:08.08mdrobnakAlso, building my own copy of Android had no difference, it was using the generic Software OpenGL, and that crashed..
00:08.16ali1234yes
00:08.22ali1234the problem is in the pmem driver somehow
00:08.23mdrobnakso it's definitely a mapping issue either in pmem or some reserved area
00:08.25ali1234i'm sure of that
00:08.37ali1234but looking at it i can't see a reason why it crashes
00:08.54ali1234it doesn't touch anything inside what you have mapped as general memory
00:09.01ali1234at least it isn't supposed to
00:09.24mdrobnakheh
00:09.29mdrobnak*supposed to*
00:09.33ali1234yeah
00:09.55ali1234all i can think is that it can;t grab a big enough uninterrupted stretch of virtual memory to map into
00:10.22ali1234the thing is pmem only does it's mapping when the pmem device is opened
00:10.29ali1234that's why it only crashes when android starts using the pmem
00:10.48ali1234so you could maybe write a small test program to exercise pmem rather than booting all of android
00:10.55ali1234that's idea number 4
00:11.23ali1234actually 'cat /dev/pmem' might be enough to crash it (or whatever the device node is called)
00:12.24mdrobnakOk, with the rest of the #defines at the default, it does not boot with the 128MB bank only.
00:12.48mdrobnakI think I *did* try that.
00:13.29mdrobnakThat's because MSM_LINUX_BASE is at 0x100000
00:13.54mdrobnakOr..
00:14.29ali1234try changing it to 0x2000000
00:14.33ali12340x20000000
00:14.49ali1234then you'll have to change the bank size to 89
00:15.08*** join/#htc-linux thedicemaster (n=thedicem@j89051.upc-j.chello.nl)
00:15.29ali1234how it works is you have a ram bank at 0x10000000 which is 128mb
00:15.57ali1234up to 0x15900000 is general purpose, and after that is reserved and shared with the FB/DSP etc
00:16.07ali1234and that region is accessed through pmem
00:16.35mdrobnakSo here's my confusion..
00:16.42ali12340x59 being 89mb
00:16.56ali1234then pmem operates within the rest
00:17.25mdrobnakOn the RaphaelMemoryMap page, it looks like 2 banks...1 of 9xMB and the other is 128MB which total is around 220MB...
00:18.02mdrobnakOk, so yeah, we're on the same page, sorry.
00:18.04mdrobnaktook me a sec.
00:18.29ali1234you have (in theory) 0x10000000 to 0x15900000 (which is 89 * 1024 *1024 bytes) and 0x20000000 to 0x28000000 (128mb)
00:18.49ali1234and 0x15900000 to 0x18000000 is where pmem is operating
00:19.03ali1234the defines in board-raphael.h set all that up
00:19.10ali1234so try playing around with those
00:19.18ali1234but i suspect the pmem areas are fixed in hardware
00:19.50ali1234but since there is no overlap at all between pmem and general memory, i can't see a reason why you cant use only the upper bank
00:20.41ali1234all pmem does is give you a memory mapped file representing a block of physical ram - exactly like /dev/mem does, except limited to some small fixed regions
00:20.47ali1234at least that's what i understand
00:20.58*** join/#htc-linux rashire2 (n=ed1112wa@pool-98-114-209-5.phlapa.fios.verizon.net)
00:21.06ali1234i hope this is making sense to you
00:21.28mdrobnakIt does for the most part.
00:22.10mdrobnakI'm just having fun with device connectivity :-)
00:23.09ali1234hmm... so it doesn't boot at all with only the upper bank selected?
00:23.24ali1234maybe the upper bank is not a full 128 mb like the lower one
00:23.28mdrobnakNope, still not working.
00:23.39mdrobnakUnless I screwed something up.
00:23.40mdrobnakone sec
00:23.42ali1234try just the upper bank, but set the size to 64mb
00:24.43mdrobnakCrap. I updated the .h but not the .c for 89MB
00:24.49ali1234the h?
00:24.55ali1234you shouldn't need to touch that
00:25.35mdrobnak#define MSM_EBI_BASE            0x20000000
00:25.35mdrobnak#define MSM_EBI_SIZE            0x5900000
00:25.50ali1234yeah, leave those exactly as they were before
00:25.55mdrobnak#define MSM_LINUX_BASE          MSM_EBI_BASE
00:25.55mdrobnak#define MSM_LINUX_SIZE          0x5900000
00:25.57ali1234we dont want to move the pmem
00:26.10mdrobnakWell, that was 0x1000000, not 20
00:26.14ali1234right
00:26.32ali1234they only affect the pmem mapping i think
00:26.46mdrobnakhmm.
00:27.07ali1234i dont think MSM_LINUX_BASE is used outside that file even
00:27.19ali1234it's just used to say "pmem is after this much general ram"
00:27.47ali1234really it should be used in the .c file to set the size of bank 0
00:27.55ali1234but for our experiemtn, just leave it at 0x10000000
00:28.16mdrobnakok.
00:29.18mdrobnak<PROTECTED>
00:29.18mdrobnak<PROTECTED>
00:29.18mdrobnak<PROTECTED>
00:29.23mdrobnakSo that's the only change for now.
00:33.10ali1234no make it 128 :)
00:33.28mdrobnakThat's what I did the first time, and it didn't boot.
00:33.37ali1234hmm
00:33.45ali1234ok, in that case try 64
00:33.49ali1234to be safe
00:33.59ali1234it might be even smaller than the other one
00:34.55mdrobnakThe device is supposed to have 288MBs..'
00:35.04ali1234it's just a test...
00:35.29ali1234288mb doesnt make much sense
00:35.34ali1234256 + 32?
00:35.54ali123432 is the proc_comm at 0x0, not general purpose
00:36.02ali1234then there's the two 128mb banks
00:36.12ali1234of which one is 89mb + pmem
00:36.21ali1234and the other is shared with god knows what :)
00:36.24mdrobnakheh
00:36.33mdrobnakyeah I always thought 288 was a odd #
00:38.07mdrobnakgetting windows mobile to connect in ubuntu is a pain in the butt
00:38.13ali1234it sure is
00:38.17ali1234i dont even bother
00:38.38ali1234just put kernel on sd card :)
00:40.23ali1234the point of the tests is to narrow down what the real problem is
00:40.41mdrobnakDoes not boot with 89MB.
00:40.52ali1234hmm
00:41.03ali1234ok
00:41.17mdrobnakDoesn't even go to the console. It freezes at Go Go Go
00:41.17ali1234how about if you make bank 0 have only 1mb and bank 1 be 128mb
00:41.32ali1234ah i think i know why
00:41.35mdrobnak(none so far have passed that point)
00:41.46ali1234kernel is in bank 0 by bootloader
00:41.53ali1234so kernel cant run itself
00:42.09mdrobnakOH DUH
00:42.11ali1234try making bank 0 be small, eg 16mb, and bank 1 128mb
00:42.23mdrobnakNo, I can change the ram addr to be 0x20000 instead of 10..
00:42.33ali1234it might not run properly if oyu do that
00:42.41ali1234it might expect to be at 0x10000000
00:43.05mdrobnakWell, if we do that, we're in the exact same situation again of two split banks.
00:43.11ali1234right
00:43.24mdrobnakI'm going to try 20 firs
00:43.25ali1234at the moment i have several theories of what is happening
00:44.59mdrobnakI have noticed windows takes longer to boot since I'm messing with this stuff
00:45.18ali1234yes i get that too
00:45.18ali1234seems to help if you remove the sd card
00:45.26ali1234of course i use totally different hardware :)
00:45.32mdrobnakwhat are you using?
00:45.41ali1234wizard/omap
00:45.48ali1234it has nothing like this crazy stuff :)
00:45.56ali1234but it only has 64mb anyway
00:46.09ali1234and no crazy proc_comm
00:46.18mdrobnakOh, the 8125.
00:46.21mdrobnakThat's a good phone.
00:46.45ali1234from what i have seen, the TI architecture is a lot nicer than MSM
00:46.58ali1234to program for, anyway
00:47.06mdrobnakThe MSM architecture gets no love from the devs, lets put it that way lol
00:47.49ali1234have oyu ever tried making both banks 89mb?
00:49.15mdrobnakNO
00:49.18mdrobnaksorry
00:49.19mdrobnaknope
00:49.31ali1234that would be the last thing to try here i guess
00:49.36ali1234before we move on to idea 2
00:51.03mdrobnakUGH
00:51.09mdrobnakIt's not showing up as a drive now
00:51.17mdrobnakI want to throw it across the room
00:51.18mdrobnaklol
00:51.22ali1234here's a tip
00:51.30ali1234there's a little ftp server for WM
00:51.34mdrobnakThis is what makes it so frustrating - this is not developing code on a pc and debugging, it's MUCH MUCH harder.
00:51.40mdrobnakreally?
00:51.44ali1234connect on wifi and upload kernel that way
00:51.46mdrobnakWhat's the name?
00:51.48ali1234it never fails
00:51.50mdrobnakYes, that sounds like a good idea.
00:51.55ali1234hmm i forget
00:52.00ali1234it's made by some japanese guy
00:52.02ali1234hang on
00:52.28ali1234i used to use it all the way back to ce 3.0
00:52.34ali1234still works fine on WM
00:52.52ali1234maybe i have it on a cd somewhere... hang on
00:53.41mdrobnakheheh
00:53.58mdrobnakhttp://www.mochasoft.dk/freeware/ftpd.htm ?
00:55.16ali1234thats not the one i used but sure
00:55.20ali1234whatever works
00:55.43mdrobnakWell, it's only in exe so far..
00:55.47mdrobnakwhich is useless in Ubuntu
00:55.47mdrobnaklol
00:55.56ali1234wine
00:56.00ali1234but hang on
00:56.04ali1234found the cd i think
00:56.23mdrobnakFound
00:57.57ali1234http://hp.vector.co.jp/authors/VA002682/ftpd52d.exe
00:58.00ali1234i think that's it
00:58.06ali1234also exe
00:58.22ali1234but it may well be a windows ce exe :)
00:58.48*** join/#htc-linux LTxda (n=anon@unaffiliated/ltxda) [NETSPLIT VICTIM]
00:58.48*** join/#htc-linux furtardo (n=mks@nat/yahoo/x-ecrqseykaxwnrjfl) [NETSPLIT VICTIM]
00:58.48*** join/#htc-linux mickey_away (i=mickey@openmoko/coreteam/mickey)
00:58.55mdrobnakhehe
00:59.40ali1234wait that's a windows server
00:59.46ali1234lol, not the one
01:00.08ali1234http://www.oohito.com/wince/arm_j.htm
01:00.24ali1234that's the real one, i remember the name eiichiro ito
01:02.03ali1234it's a zip, you can download it straight onto the device :)
01:02.14mdrobnakThis one works OK.
01:02.18mdrobnakIt looks so funny
01:02.21mdrobnakcause it's from PPC 2003
01:03.08ali1234(this is why i suggested tftp support for haret btw)
01:03.22ali1234but then i realised i dont even know how to compile haret, much less hack on it
01:04.29mdrobnakheh
01:04.57mdrobnakWell, that didn't work.
01:05.20mdrobnakSo tell me what your other ideas are
01:05.56ali1234still crashed like before?
01:06.17ali1234ok so the next step is to drill down through pmem and see where it is actually crashing
01:06.19mdrobnakYeah, I see half the screen, half black
01:06.32ali1234more interested in dmesg really
01:07.35mdrobnakwell lets see if there is anything there
01:07.39*** join/#htc-linux tmzt (n=tmzt@adsl-99-52-65-233.dsl.akrnoh.sbcglobal.net)
01:08.29ali1234anyway, i'd like to know if you can cause the crash without loading android
01:09.05mdrobnakwell I dont know of anything else using pmem.,.
01:09.48ali1234there should be a pmem device in /dev (maybe four of them depending how it works)
01:10.44*** join/#htc-linux marcin88 (n=marcin@chello089078160132.chello.pl)
01:11.01mdrobnakGetting dmesg now
01:11.36ali1234do you have a shell on the device?
01:12.32mdrobnakYeah. Just need to swap the root image.
01:13.56mdrobnakNope, this dmesg is from this morning.
01:14.16mdrobnak<PROTECTED>
01:14.55ali1234hmm.. meaning what?
01:16.15mdrobnakThat compile was from this morning.
01:16.19mdrobnakIt didn't even boot the kernel.
01:17.08ali1234with 89+89?
01:17.41mdrobnakNo, just the upper bank of 89.
01:17.44mdrobnakYou wanted 89+89?
01:18.10ali1234right
01:18.17ali1234try 89+89, then we give up on this
01:18.29ali1234unless that works, which changes everything
01:18.44ali1234or be conservative, do 89+64
01:18.51mdrobnakIt'll boot, but crash.
01:18.55mdrobnakBoth will.
01:18.57ali1234right
01:19.07ali1234if you're sure about that, then no need to try it
01:19.17ali1234so, the next thing is messing with pmem
01:19.59mdrobnakftp is so much easier
01:19.59mdrobnaklol
01:20.53mdrobnak89+89 boots
01:21.04ali1234does it crash at android?
01:21.18ali1234or if you are on shell, can you crash it by messing with the pmem device?
01:21.30mdrobnakcrahsed at android
01:21.42mdrobnakShould reboot in a moment.
01:21.57mdrobnakI'm looking at pmem, nothing looks crazy.
01:22.12ali1234pmem.c?
01:22.58mdrobnakyeah
01:23.04mdrobnakdidnt reboot, had to hit it
01:23.30ali1234that's different?
01:23.57ali1234pastebin dmesg from that please
01:24.08ali1234if you can get it to do anything different to usual i want to see dmesg :)
01:26.38mdrobnakgetting dmesg
01:26.49mdrobnakwell, I've had it go both ways
01:27.02mdrobnaksometimes it reboots on its own, sometimes not.
01:27.58mdrobnakstill going
01:28.02mdrobnakdone
01:30.01mdrobnak[   17.023590] [RR] send control message cmd=7 srv.cmd=7 prog=00000001:d2dcfb60 id=-752902312:c0164318
01:30.01mdrobnak[   31.225646] [drivers/misc/pmem.c:pmem_open:335] current 139 file d3c84860(1)
01:30.01mdrobnak[   31.241516] [drivers/misc/pmem.c:pmem_allocate:388] no allocator<6>[drivers/misc/pmem.c:pmem_map_pfn_range:510] map offset 0 len 800000
01:30.18mdrobnakcr2 said that the id being negative on the RPC shows the memory is corrupt.
01:30.26mdrobnakIt should be a 0 or 1
01:30.39mdrobnakThat's the same crash as usual.
01:31.50mdrobnakhttp://pastebin.com/m2453c087
01:33.28mdrobnakOk booted to shell.
01:33.29ali1234got a line number showing negative rpc?
01:33.58mdrobnak510 right before the crash
01:34.16mdrobnakthis rootfs doesn't have a /dev/pmem
01:36.34ali1234maybe not created
01:36.37ali1234no matter
01:36.43ali1234here's what to do:
01:38.36ali1234[   31.455291] Unable to handle kernel paging request at virtual address c7184000
01:38.40ali1234is the real crash
01:39.02ali1234the question is why that happened
01:39.12ali1234first step is to find what line of code caused it
01:39.27ali1234to me it looks very pmem related
01:39.58ali1234so add lots of debugging into the pmem driver (using DLOG)
01:41.28ali1234can you paste a dmesg with 1 bank and no crash, for comparison?
01:43.27mdrobnakI can just boot with mem=89M. Sure, one minute.
01:43.42ali1234in pmem.c i would add a lot debugging into these functions:
01:44.04ali1234pmem_setup around anything involving ioremap/kmalloc
01:44.53ali1234pmem_ioctl, especially PMEM_MAP
01:45.06ali1234pmem_remap maybe too
01:46.06mdrobnakHey, here's a crazy idea.
01:46.11mdrobnakOne last thing to try
01:46.15ali1234pmem_remap_pfn_range since that shows up on the dmesg
01:46.21mdrobnakbut my math is off
01:46.48mdrobnakHow can we remap all the PMEM and above stuff to the end of the memory (0x28000000)
01:47.57*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
01:49.27ali1234just add 0x10000000 to all of them
01:49.34ali1234but, i dont think that will work
01:49.55ali1234since it is shared memory with the dsp it is probably at a fixed address
01:50.03ali1234but try if oyu want
01:52.30mdrobnakgoing to boot with mem=89M in a sec first
01:54.33mdrobnak"Android/PMEM: The PMEM (physical memory) driver is used to provide contiguous physical memory regions to userspace libraries that interact with the digital signal processor (DSP) and other hardware that cannot cope with scatter-gather."
01:54.39mdrobnakHmm you may be right
01:55.05ali1234yeah i know, i read that  too :)
01:55.29ali1234sooo...
01:55.47ali1234i could be completely off here
01:56.03ali1234but it looks like the pmem is having trouble when the second bank is enabled
01:57.23ali1234that's all i'm really sure of
01:57.34mdrobnakdoh wrong rootfs
01:57.41mdrobnakand I have to look up some pf rule stuff soon
01:58.00mdrobnakreplacing a redicuously expensive firewall with OpenBSD, lol
01:59.02mdrobnakYeah, I have only seen one mailing list item about pmem
02:02.08mdrobnakOk android booting this time
02:02.47mdrobnakThis is interesting
02:02.57mdrobnakso even when it DOES NOT crash, I see one line with a negative RPC call
02:03.01mdrobnakusing mem=89M
02:03.04mdrobnakok, at home screen.
02:03.51mdrobnak[   17.004302] [RR] send control message cmd=7 srv.cmd=7 prog=00000001:c4ed3c20 id=-992038144:c02cf17c
02:03.51mdrobnak[   31.150970] [drivers/misc/pmem.c:pmem_open:335] current 141 file c4ba64a0(1)
02:03.51mdrobnak[   31.167602] [drivers/misc/pmem.c:pmem_allocate:388] no allocator<6>[drivers/misc/pmem.c:pmem_map_pfn_range:510] map offset 0 len 800000
02:03.51mdrobnak[   31.415039] [drivers/misc/pmem.c:pmem_open:335] current 141 file c3029f40(1)
02:03.51mdrobnak[   31.416015] [drivers/misc/pmem.c:pmem_ioctl:1147] connect
02:03.52mdrobnak[   31.416107] [drivers/misc/pmem.c:pmem_connect:833] connect c3029f40 to c4ba64a0
02:03.54mdrobnak[   31.424255] [drivers/misc/pmem.c:pmem_open:335] current 141 file c3029ec0(1)
02:03.56mdrobnak[   31.424835] [drivers/misc/pmem.c:pmem_ioctl:1147] connect
02:03.58mdrobnak[   31.424896] [drivers/misc/pmem.c:pmem_connect:833] connect c3029ec0 to c4ba64a0
02:04.00mdrobnak[   31.425262] [drivers/misc/pmem.c:pmem_open:335] current 141 file c3029e40(1)
02:04.02mdrobnak[   31.425476] [drivers/misc/pmem.c:pmem_ioctl:1147] connect
02:04.04mdrobnak[   31.425537] [drivers/misc/pmem.c:pmem_connect:833] connect c3029e40 to c4ba64a0
02:07.07mdrobnakGood job to those working on power management, it nicely dims the LCD :-)
02:07.16mdrobnakhttp://pastebin.com/m61c36904
02:07.33mdrobnakThat's a working boot. I didn't get the first few seconds, but it's the same as a crash probably.
02:08.11mdrobnakI have a /dev/pmem now
02:08.21mdrobnak# ls -l pmem
02:08.21mdrobnakcrw-rw----    1 1000     1003      10,   1 Sep 21 22:02 pmem
02:10.01ali1234yes, i think that negative number is caused merely by a signed/unsigned mismatch in the logging code
02:10.25ali1234ie it's a red herring :)
02:10.49mdrobnakyet another :-)
02:11.10ali1234the interesting part is the pmem stuff line 161 - 171
02:11.25mdrobnakShutting down android. Going to try my crazy remap idea.
02:11.29ali1234the crash happened right in the middle of that
02:11.39mdrobnakYeah right after "no allocator"
02:11.59ali1234actually no
02:12.08ali1234notice the missing /n concatenates two lines
02:12.22ali1234"no allocator" is correct for two of the four pmem devices anyway
02:12.51ali1234i suspect the problem is with the second device which does have an allocator - and happens when the allocate happens
02:13.08*** join/#htc-linux pleemans (n=toi@d54C2A96D.access.telenet.be)
02:14.22mdrobnakOuch.
02:14.31mdrobnakReboots at FB handover hehe
02:17.30mdrobnakSo I'm not sure what we do.
02:17.42ali1234we put loads and loads of debugging into pmem.c
02:17.54ali1234until we find the exact line where it crashes
02:18.12ali1234or rather, you do :)
02:18.35*** join/#htc-linux stickboy (n=anonymou@128.153.211.18)
02:19.07mdrobnak<PROTECTED>
02:19.24mdrobnakThat's already in pmem_setup, but I don't see that in dmesg.
02:20.24ali1234it might be much earlier
02:21.03ali1234as a last resort, put DLOG on every other line of the whole damn driver
02:22.21mdrobnaklol
02:23.19mdrobnak[    3.403503] pmem: 1 init
02:23.19mdrobnak[    3.409790] pmem_adsp: 0 init
02:23.19mdrobnak[    3.416137] pmem_gpu0: 0 init
02:23.19mdrobnak[    3.422515] pmem_gpu1: 0 init
02:24.24ali1234you need to read through the driver and get a feel for the flow of execution, then try to narrow down the problem location
02:24.41ali1234it isn't in early init for sure
02:24.53ali1234it happens when something actually opens the device
02:25.17ali1234one question which would be easy to answer is which of the four devices actually bugs out
02:25.38ali1234i suspect it is the adsp
02:26.27mdrobnakActually I think it's gpu0
02:26.34mdrobnakI shouldn't say actually.
02:26.39mdrobnakI think it's gpu0
02:26.40mdrobnak:-)
02:29.04ali1234well, what to do is add more verbode debugging so you know which device the messages refer to
02:29.34ali1234expect to be looking at the dmesg dumps a few hundred times :)
02:30.52mdrobnakActually, I think we'll get it fast because I just added process name and type being opened :)
02:31.04ali1234cool
02:31.26mdrobnakOr not.
02:31.29mdrobnak:-/
02:31.30ali1234hmm
02:32.04ali1234have a look in menuconfig, at the kernel hacking section
02:32.11ali1234maybe something in there can debug memory mappings
02:32.21ali1234it will produce a lot of output though
02:33.24mdrobnakwell at least I will get the calling proc name this time
02:33.53ali1234yes
02:34.07ali1234looking at the android code to see what order it does things may help too
02:36.05mdrobnakDoh
02:36.10mdrobnakforgot to remove the + 0x100000
02:42.45mdrobnakOk, lets see what dmesg says now
02:48.17*** join/#htc-linux root2 (n=root@rgnb-5d874ded.pool.mediaWays.net)
02:54.27mdrobnak[   31.287231] [drivers/misc/pmem.c:pmem_open:335] current 146 file d7e75420(1)
02:54.28mdrobnak[   31.302673] [drivers/misc/pmem.c:pmem_open:336] name: SurfaceFlinger<6>
02:54.33mdrobnakNot much of a surprise there.
02:55.00mdrobnakwe could look in surfaceflinger to see what pmem it uses
02:55.27tmztinteresting that it gets the name of the requester
02:55.29tmztI didn't know that
02:55.52tmztyou don't really want to look at surfaceflinger directly though
02:55.59tmztprobably libagl
02:56.02tmztor pixelflinger
02:57.12mdrobnakwell, I put in a current->comm into the log
02:58.21tmztwhat is comm?
02:58.48mdrobnakProcess Name :-)
02:58.59mdrobnakI think command Line actually
03:00.46tmztyeah, that makes sense
03:00.50mdrobnak<PROTECTED>
03:00.51mdrobnak<PROTECTED>
03:00.51ali1234just grep the android source for /dev/pmem and you'll find the culprit
03:01.02ali1234^ wheee
03:01.03mdrobnakWell, it looks like it uses the main pmem on firs allow
03:01.05mdrobnak*alloc
03:01.32mdrobnakIt tries to allocate 8MB
03:01.55ali1234hmm
03:02.13ali1234makes me think
03:02.40ali1234maybe android allocates a buffer in normal memory and tries to use accelerated copy between that, and the pmem device
03:02.50ali1234and maybe that fails if they are in different banks
03:02.53tmztif you have it all checked out try repo for-all git grep
03:02.58tmztbut not sure that's right
03:03.17mdrobnakyeah I have the whole thing :-)
03:03.49mdrobnakI built it from source, to answer if that would fix it, because of people saying OpenGL is broken..
03:04.01mdrobnakwell the default build uses software OpenGL
03:04.04tmztbroken how?
03:04.21tmztyeah, you have to have libhgl and dzo's fixes to tell the amss to use 3d
03:04.22mdrobnakI dunno, that's what cr2 thought might have been a problem.
03:04.35ali1234the default build doesn't use pmem at all does it?
03:04.52mdrobnakyeah, pmem is used in a few places I think
03:05.02ali1234of course it probably doesnt have dialer support either
03:05.12ali1234meh, i dont know
03:05.21mdrobnaktmzt: repo grep pmem will do it
03:05.28ali1234keep drilling down on the pmem driver until you find the exact line where it crashes
03:05.41tmzthah, they fixed it
03:05.52dzomdrobnak: if you disable pmem, abdroid should still boot, just won't use accel 2D.
03:05.57mdrobnakexternal/opencore/android/samples/android_surface_output_fb.cpp:static const char* pmem_adsp = "/dev/pmem_adsp";
03:05.57mdrobnakexternal/opencore/android/samples/android_surface_output_fb.cpp:static const char* pmem = "/dev/pmem";
03:06.07ali1234ah, an expert :)
03:06.14mdrobnaktmzt - well it broke in the middle
03:06.16tmztdzo: looks like smi64 is broken
03:06.17mdrobnakHey dzo
03:06.43mdrobnakWell, hell, if that gets me 214MBs of RAM until we figure out how to fix pmem, lets try that!
03:06.50dzoso does it die accessing pmem or pmem_adsp?
03:07.00tmztI can't even boot :)
03:07.14tmztbut it's pulling git right now, to remote storage and very slow
03:07.28dzojust take the pmem entries out of the board file.
03:07.53tmztnot enough to disable in .config?
03:08.42mdrobnakdzo: Can't tell if it's pmem or pmem_adsp
03:08.49mdrobnakin the samples refs adsp
03:09.00mdrobnakbut libsurfaceflinger in VRamHeap.cpp is just pmem
03:09.04dzotmzt: that will work too, but if you take them out of devices[], they won't be loaded either.
03:09.16tmztwell, it didn't work
03:09.22tmztwhen I tried that a few days ago
03:09.25dzothen pmem isn;t the problem.
03:09.30tmztright
03:09.43tmztit vibrates twice and never gets to fbcon
03:09.58ali1234tmzt: are you talking abut the same problem as mdrobnak?
03:10.10dzocan you allocate any of the second bank as ram?
03:10.11tmztwhat device does he have?
03:10.18ali1234raph
03:10.22mdrobnak110
03:10.29ali1234with two ram banks
03:10.34tmztpossibly
03:10.40mdrobnakdzo: if I pull out pmem, qdsp5 adsp_driver and hw3d won't build
03:10.41dzowhat if you only have 1 bank starting at 0x20000000, does that work?
03:10.50mdrobnakwe tried that earlier
03:10.56mdrobnaknot sure if I did it right
03:11.03mdrobnakbut no, it didn't
03:11.30dzook, take them out of devices[] in the board file.
03:11.41tmztcan we add smi to device specific?
03:12.15dzoyes, sure. just change the addresses before the device is added.
03:12.56tmztok, then how do I integrate the seperate headers from diamond into a raphael board file?
03:13.42tmzt-               msm_proc_comm_wince(&vibra, 0);
03:13.44tmzt+               blac_set_vibrate(1);
03:13.56mdrobnakmaking
03:14.12ali1234mdrobnak: if all else fails (ie there's a unfixable hardware reason why two banks doesn't work) then you could always implement the second bank as a swap device :)
03:14.29mdrobnakThat would work fine lol
03:14.32tmztwe can only do what the radio lets us
03:14.45dzouse mach_is_htcdiamond() etc..
03:15.12tmztthat would mean recombining the devices or spliting the board based on smi size instead of raph/diam
03:16.26mdrobnaklets see
03:16.41mdrobnakSorry, no dice.
03:17.01mdrobnak09-21 19:16:33.555 I/SurfaceFlinger(  137): SurfaceFlinger is starting
03:17.01mdrobnak09-21 19:16:33.565 I/SurfaceFlinger(  137): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
03:17.01mdrobnak09-21 19:16:33.565 E/MemoryHeapBase(  137): error opening /dev/pmem: No such file or directory
03:17.01mdrobnak09-21 19:16:33.565 E/SurfaceFlinger(  137): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake
03:17.02mdrobnak09-21 19:16:33.715 D/SurfaceFlinger(  137): pid 137 requesting gpu core (owner = -1)
03:17.04mdrobnak09-21 19:16:33.715 W/SurfaceFlinger(  137): couldn't grant gpu core to pid 137
03:17.06mdrobnak09-21 19:16:33.715 D/EGL     (  137): requestGPU returned -1
03:17.08mdrobnak09-21 19:16:33.725 E/GLLogger(  137): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
03:17.10mdrobnakStill crashed.
03:17.22mdrobnakDoes that rule out pmem?
03:17.24tmztonly android? so your kernel works on raph110?
03:17.45mdrobnakI've tested it with memtester to 200MB of RAM no problems
03:18.14mdrobnakI'm curious to see dmesg
03:19.22mdrobnakgetting it now
03:19.51ali1234you could selectively disable pmem devices until you find the one that crashes...
03:20.30ali1234wait, it crashes anyway?
03:20.39ali1234interested to see dmesg too :)
03:21.29dzoif you disable pmem and it still crashes then pmem can't be the problem. are you sure the banks are set up correctly? node 0
03:24.04mdrobnakAll pmem devices disabled, still crashes on SurfaceFlinger
03:24.44mdrobnakhttp://pastebin.com/m6c997f5c
03:25.13ali1234lol
03:25.20ali1234pmem is nothing to do with it then
03:25.23ali1234damn
03:32.21mdrobnakdzo: Thoughts?
03:35.43ali1234you could try allocating all the memory in the upper bank so that nothing can touch it
03:35.52ali1234(within the kernel)
03:36.14ali1234maybe the other core is using some region in it, and you're corrupting that
03:37.27mdrobnakThat's possible. Maybe the proc_comm stuff is to blame.
03:38.03mdrobnakor maybe our map is incorrect. I'm not sure.
03:38.44ali1234you could also make the upper bank size 1 page long
03:38.53ali1234and try various addresses in the bank for that 1 page
03:39.02ali1234to minimize collision possiblity
03:39.17ali1234over even
03:39.27ali1234make two banks in the lower ram
03:39.45ali1234that might be really enlightening
03:40.09ali1234it would confirm or rule out whether the problem is intrinsic to having two banks defined
03:40.27ali1234assuming it actually boots
03:41.26mdrobnakhah
03:41.27mdrobnakwell
03:41.34mdrobnakit's way past bed time here
03:45.01mdrobnakI have to get to sleep. If people leave me commands to run, I'll do it when I get a moment and report back. I'm not sure how to break up the banks and what I'd have to do with the .h stuff, so I'd need some more guidance / a patch..
03:51.38*** join/#htc-linux x29a (n=x29a@unaffiliated/x29a)
04:03.49*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
04:24.02*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
04:34.17*** join/#htc-linux droid0011 (n=g1@p4FDCEBEB.dip.t-dialin.net)
04:42.51*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
04:44.46*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
04:49.57*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
05:07.44*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
05:15.46*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
05:22.38*** join/#htc-linux luc (n=luc@89.115.128.35)
05:29.11*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
05:52.22*** join/#htc-linux x29a (n=x29a@unaffiliated/x29a)
05:52.25*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
06:01.10*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
06:06.34*** join/#htc-linux kiozen (n=oeichler@84.146.19.92)
06:15.49*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
06:27.12*** join/#htc-linux JDShadowline (n=JDShadow@97.101.243.247)
06:33.21*** join/#htc-linux Kevin2 (n=Kevin2@207-237-194-161.c3-0.avec-ubr2.nyr-avec.ny.cable.rcn.com)
06:37.26*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
06:41.15*** join/#htc-linux pleemans (n=toi@d51A49C45.access.telenet.be)
07:03.18*** join/#htc-linux dzo_ (n=dzo@121.98.128.127)
07:07.46*** join/#htc-linux c4software (n=vbrossea@217.112.64.97)
07:12.30*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
07:12.57c4softwareHi everyone
07:24.10NetRipperim not everyone, but hi
07:24.23c4softwareHi NetRipper
07:24.24c4software:)
07:24.30NetRipper:)
07:31.11*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
07:33.08*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
07:36.38*** join/#htc-linux FR^2 (n=frzwo@2001:41d0:1:ed2f:0:0:0:cafe)
08:05.46*** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz)
08:11.06*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
08:28.38*** join/#htc-linux dzo_ (n=dzo@121.98.128.127)
08:43.35c4softwaredzo: are you here ?
08:44.52*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
08:58.25*** join/#htc-linux Captnoord (n=Captnoor@81.71.164.123)
09:05.34*** join/#htc-linux c4software1 (n=vbrossea@217.112.64.97)
09:39.02*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
10:01.11*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
10:02.45Captnoordmdrobnak I wonder if we handle CopyRegions
10:08.37*** join/#htc-linux Gnutoo (n=gnutoo@host142-37-dynamic.117-80-r.retail.telecomitalia.it)
10:14.22*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
10:15.35CaptnoordPMEM Heap address
10:15.35Captnoord0xA80811DC
10:15.46CaptnoordPMEM heap size 0x700000
10:16.33Captnoordnope
10:16.36Captnoord0xA80811DC is main memory end
10:16.57CaptnoordPMEM physical address is 0xA80811D8
10:22.08*** join/#htc-linux leaigor (n=laigor@188.134.36.14)
10:24.58*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
10:48.52CaptnoordNKForceCleanBoot
10:48.53Captnoordlol
11:19.48*** join/#htc-linux StarLite` (n=nnscript@85.145.108.166)
11:21.54mdrobnakstumbles into room. Morning.
11:22.16mdrobnakNo coffee yet :-)
11:22.17ali1234morning :D
11:22.50mdrobnakYou're here? When do you sleep? hehehe
11:23.38Captnoordmorning
11:23.58Captnoordregarding your adventures with getting more ram.....
11:24.19Captnoordin nk.exe there is a bit of info regarding PMEM
11:24.40mdrobnak? really?
11:24.43mdrobnakthat's interesting.
11:24.49mdrobnakI thought that was an Android-only thing
11:24.51Captnoordyup
11:24.54Captnoord.text:80005E60 aKMainmemoryend unicode 0, <[K] MainMemoryEndAddress = 0x%08X>
11:24.54Captnoord.text:80005E60                                         ; DATA XREF: .text:aKMainmemoryendExo
11:24.54Captnoord.text:80005E60                 DCW 0xD
11:24.54Captnoord.text:80005E60                 DCW 0xA
11:24.54Captnoord.text:80005E60                 unicode 0, <>,0
11:24.57Captnoord.text:80005EA8 aKPmemheapphyad unicode 0, <[K] PmemHeapPhyAddr = 0x%08X>
11:24.57Captnoord.text:80005EA8                                         ; DATA XREF: .text:aKPmemheapphyadExo
11:25.00Captnoord.text:80005EA8                 DCW 0xD
11:25.00Captnoord.text:80005EA8                 DCW 0xA
11:25.04Captnoord.text:80005EA8                 unicode 0, <>,0
11:25.07Captnoord.text:80005EE8 aKDwpmemheapsiz unicode 0, <[K] dwPmemHeapSize  = 0x%08X>
11:25.16Captnoordbut I don't know if its the same....
11:25.29ali1234Mainmemoryend suggests it is
11:25.39Captnoordyup
11:25.45ali1234but we rules out pmem as direct cause of crash by disabling it...
11:25.49ali1234*ruled
11:25.55mdrobnakYes.
11:26.08Captnoordyea... I have read that
11:26.14Captnoordor is it red
11:26.15Captnoordnah
11:26.26CaptnoordI was more interested in finding the 2e bank stuff
11:26.28Captnoordbut found this
11:26.32mdrobnakSomething bothers me - why does WinCE break the memory into 4 banks, and we only use 2. It *looks* contiguous, but what's the reason?
11:26.51Captnoordpaging......
11:26.56CaptnoordDMA
11:27.08mdrobnakWouldn't we be subject to the same issues in Linux?
11:27.17Captnoordcopying big amount of data from 1 page to the other
11:27.18mdrobnakIe, aren't those hardware issues?
11:27.21Captnoordmore pages.....
11:27.23Captnoordwould be better
11:27.36Captnoordyup they are...
11:27.40Captnoordjust speaking my mind
11:27.59mdrobnakThen I think we should try breaking it into 4 regions, like in Windows.
11:28.01ali12344 banks? how
11:28.17mdrobnakali1234,  Look at the memory map.
11:28.24mdrobnakIt shows 4 seperate address regions
11:28.45mdrobnakPerhaps banks were the wrong term to use.
11:28.52Captnoordand in the same nk.exe
11:28.53Captnoordthere is
11:28.53CaptnoordOEMEnumExtensionDRAM
11:29.06Captnoordand for what I can see
11:29.13ali1234i think xda wiki is broken
11:29.17Captnoordhmm hard to explain....
11:29.19ali1234trying to dl the php file :(
11:29.22Captnoordlemme pastebin
11:30.00Captnoordhttp://pastebin.com/m758c17b0
11:30.13mdrobnakali1234,  Use http://htc-linux.org
11:30.22Captnoordand i'm especialy interested in
11:30.22Captnoord.text:80057324                 ORR     R1, R1, #0x300000 ; 0x8E000000 | 0x300000 = 8E300000
11:30.23Captnoord.text:80057328                 ORR     R0, R0, #0x900000 ; 0x8B000000 | 0x900000 = 8B900000
11:30.23Captnoord.text:8005732C                 ORR     LR, LR, #0x900000 ; 0x88000000 | 0x900000 = 88900000
11:30.23Captnoord.text:80057330                 ORR     R2, R2, #0xA00000 ; 0x85000000 | 0xA00000 = 85A00000
11:30.30Captnoordthe comments are mine
11:30.31Captnoordbtw
11:30.34mdrobnakhttp://htc-linux.org/wiki/index.php?title=Raphael
11:31.13mdrobnakOn the memory page, Captnoord ?
11:31.23Captnoordyea I kow
11:31.26Captnoordchecking now
11:31.48ali1234mdrobnak: you mean the 4 parts of bank 2?
11:31.56mdrobnakCaptnoord,  Or the comments on the .text code you just pasted?
11:31.59mdrobnakali1234, Yes.
11:32.51Captnoord; 0x8E000000 | 0x300000 = 8E300000
11:32.54Captnoordthose are mine comments
11:32.58mdrobnakAh.
11:33.13mdrobnakSorry. Still early.
11:33.24Captnoordnah my crap english
11:33.34mdrobnakHah, you do fine.
11:33.40ali1234mdrobnak: well they are not mapped contiguous on WM that's why they're listed separately
11:33.50ali1234but that's doesn't really tell us much
11:33.59mdrobnakWell, we have it as one big block.
11:34.17ali1234yeah
11:34.21ali1234virtual mapping though
11:34.29mdrobnakBut in terms of addressing, they *look* contiguous.
11:34.32ali1234it's general purpose so we dont care how the virtual mapping looks
11:34.41ali1234in physical addressing they are
11:34.42mdrobnak0x20000000  0x26  SDRAM (bank 2)
11:34.46ali1234but look at the wince mapping
11:34.51mdrobnak0x22600000  0x17  SDRAM (bank 2)
11:34.53ali1234there are gaps
11:35.05mdrobnak0x23d00000  0x27  SDRAM (bank 2)
11:35.10mdrobnak<PROTECTED>
11:35.19mdrobnakAh, I see what you're saying
11:35.20ali12340xa5a00000 + 0x02600000 != 0xa8900000
11:35.34ali1234but that's just virtual addresses, and tells us nothing really
11:35.45Captnoordnope
11:35.53mdrobnakOk, so maybe the MS guys *are * just crazy. LOL
11:36.07Captnoordthere is always a reason
11:36.18mdrobnakI was so focused on the physical addresses, didn't notice the gaps in the virtual.
11:36.19ali1234sure. we just dont know it
11:36.27Captnoordbut... what I supposed to say was that it seems that the 2e bank also has a limit
11:36.31CaptnoordI mean
11:36.44Captnoordsomewhere you shouldn't write... or use it for our purposes
11:36.49CaptnoordI think
11:36.49ali1234yep
11:37.16mdrobnakHere's what I know.
11:37.23Captnoordwithin the OEMinit function
11:37.28mdrobnakWhen we moved PMem, and then started messing with the ranges...
11:37.45Captnoordthere are some links with paging.....
11:37.50CaptnoordI dono if thats interesting?
11:38.15mdrobnakWhen I didn't use 0x20000000 through 0x21000000 , and had it set to 32MB size, it booted to Android all the way. And it ran for a minute or two, then crashed. No other configuration more then 89MB booted or ran that far.
11:38.37ali1234you never said that...
11:38.51mdrobnakThat was from days ago
11:38.53mdrobnaksorry
11:39.02ali1234so you did get some kind of success?
11:39.20ali1234this is why i suggest 89mb in bank[0] and 1 page (4kb) in bank 1
11:39.27ali1234and try putting it the start and the end
11:39.38mdrobnakAs soon as you tried to do anything useful it crashed. Didn't get a dmesg for it though
11:41.38mdrobnakThing is, according to the Memory Map on the wiki, it should be perfectly usable.
11:41.50ali1234maybe it is wrong or has missing info
11:41.51mdrobnakI also wrote values to 0x200000 and read them back no problem in haret.
11:42.03mdrobnak(err 0x20000000)
11:42.04ali1234it's 0x20000000
11:42.14ali12348 digits always :)
11:42.23c4software1dzo: With your lastest modification disable pwrsink my screen don't turn off. Just the backlight is turned off.
11:42.54mdrobnakHere's a thought -- maybe the low level routines to address the other bank of ram has an issue?
11:42.59mdrobnakMaybe the map itself is right?
11:43.05ali1234maybe. check it
11:43.23mdrobnakI'll get right on that.
11:43.24mdrobnaklol
11:43.36ali1234i have no idea where it is
11:43.38mdrobnakI've never done this low-level of stuff before
11:45.21mdrobnakCaptnoord, any ideas? :-)
11:45.51Captnoordwhere to look?
11:46.11mdrobnakWell, then again, even if I knew where to look, I'd have no idea if it was right or wrong..
11:46.36Captnoordbut you know and read the flow
11:46.40Captnoordif you check it
11:47.39Captnoordthe init function also init's the L1 and L2 cache of the cpu
11:47.48CaptnoordI dono if we can use that
11:48.36Captnoordhmmmm
11:48.58CaptnoordI think I found something that is something like a global var related to the memory stuff
11:49.18Captnoordas its used as a argument for both the extended DRAM and the normal ram init
11:49.19mdrobnakWhat file?
11:49.24Captnoordnk.exe
11:49.25Captnoordasm
11:49.33Captnoordreading the asm atm...
11:49.38Captnoordwince file from the spl
11:49.45Captnoordor....
11:49.46Captnoordnah
11:49.55Captnoordcore application I mean
11:51.01mdrobnakoh
11:51.01Captnoordhmmmmm
11:51.20Captnoordarm asm is wierd stuff if your used to x86
11:51.24mdrobnakwhat device is that dump from? A 100?
11:51.43Captnoordaaahhh
11:51.43Captnoordlol I see now its a branch
11:51.43Captnoordyup
11:51.54CaptnoordLDREQ is a load if equal branch
11:52.49CaptnoordI think it checks if a second bank is there
11:53.05mdrobnakThat's useful code..
11:53.18CaptnoordCMP     R3, #0x100
11:53.22Captnoordthats obviouse
11:53.28CaptnoordR3 contains
11:53.34CaptnoordLDR     R3, [R5]
11:53.42Captnoordso r3 = *r5
11:54.05Captnoordand r5 = 0xA80810C0
11:56.33Captnoordhooking my phone now
11:56.39Captnoordto check the address
11:58.45mdrobnakSo you have a RAPH100 Captnoord ? What have you tried to run on it in terms of Linux stuff?
11:58.52Captnoordyup
11:58.55Captnoordandroid runs on it
11:58.58Captnoordsound works
11:59.28Captnoordbut atm I run windows mobile bleh... as its best for battery
11:59.30Captnoordfor now
12:00.47mdrobnakAndroid runs, but with how much RAM? :-)
12:01.15CaptnoordI haven't checked... i'm atm working on windows as i'm working on school stuff
12:01.24Captnoordso can't build myself a fresh kernel
12:01.54Captnoordbut i've helped cr2 a bit with the rpc stuff
12:02.04Captnoordbut ya all might know that
12:02.33Captnoordlol
12:02.43Captnoordneeded to download that mobility centre
12:02.51Captnoordbleh
12:03.10mdrobnakI've been spinning my weels on this RAM stuff - I was trying to debug the RIL a bit, but without more RAM, it's hard to use.
12:03.34mdrobnakAt least the RIL can get the MCC / MNC now by itself.
12:03.52Captnoordhehe
12:04.09CaptnoordI think
12:04.12Captnoordthat OEMEnumExtensionDRAM function
12:04.28Captnoordis to map the continues addresses to the second mem bank
12:04.36Captnoordsomehow
12:04.44Captnoordas it kinda a callback somehow
12:05.11Captnoordbut that would be stupid
12:08.36Captnoordalso messages like
12:08.37Captnoord.text:80002BD8 aErrorXipRegion unicode 0, <ERROR! XIP region span accross discontigious memory!!! Sy>
12:08.37Captnoord.text:80002BD8                                         ; DATA XREF: .text:off_8003B810o
12:08.37Captnoord.text:80002BD8                 unicode 0, <stem Halted!>
12:10.06Captnoordbut xip is rom space?
12:11.22Captnoordlol
12:11.25Captnoordthat took forever
12:11.26Captnoordlolz
12:13.42mdrobnakxip = Execute In Place
12:13.48mdrobnakYes, XIP is ROM I think
12:13.56CaptnoordHaRET(7)# vdump 0xA80810C0 4
12:13.56Captnoorda80810c0 | 00000100                            | ....
12:14.05CaptnoordCMP     R3, #0x100
12:14.27mdrobnakThat would be true :-)
12:14.30Captnoordbut I don't know if this is hardcoded
12:14.34CaptnoordI mean....
12:14.37Captnoordhardware wise
12:14.41Captnoordin the mem map
12:14.56CaptnoordI would need someone who doesn't have the second bank
12:14.57Captnoordtodo the same
12:14.59*** join/#htc-linux thedicemaster (n=thedicem@j89051.upc-j.chello.nl)
12:15.06Captnoordif it would return 0
12:15.14Captnoordthen we might know something
12:15.41mdrobnakI should probably check there LOL
12:15.45mdrobnakj/k
12:16.01mdrobnakSomeone with the RAPH500 should be able to answer that question
12:16.22Captnoordor a diamond
12:18.17Captnoordso
12:18.24Captnoordmain mem addr end
12:19.09CaptnoordHaRET(10)# vdump 0xA80811D8 4
12:19.09Captnoorda80811d8 | 00200000                            | .. .
12:19.21Captnoordpmem physical addr
12:19.35CaptnoordHaRET(11)# vdump 0xA80811D8 4
12:19.35Captnoorda80811d8 | 00200000                            | .. .
12:19.39Captnoordthats obviouse
12:19.40Captnoordlol
12:20.01Captnoordand pmem heap size
12:20.12CaptnoordHaRET(12)# vdump 0xA80811DC 4
12:20.13Captnoorda80811dc | 00700000                            | ..p.
12:20.20Captnoordlets check the second bank init stuff
12:21.00Gnutoo~seen druidu
12:21.50Captnoordnope can't tell anything from that
12:22.01Captnoordand how helps me
12:22.02Captnoordor*
12:26.18*** join/#htc-linux phnom (i=simomn@pub99-168.pub.luth.se)
12:30.29*** join/#htc-linux FR^2 (n=frzwo@2001:41d0:1:ed2f:0:0:0:cafe)
12:30.53Captnoordhttp://bolingconsulting.com/blog/?p=4
12:32.02*** join/#htc-linux cr2 (n=cr2@109.84.201.73)
12:32.30Captnoordcr2 you got a phone with 1 mem bank?
12:33.27cr2Captnoord: i've read a lot of BS in the log
12:33.56Captnoordyea
12:33.59CaptnoordI know shit
12:34.02Captnoordi'm just speaking my mind
12:34.16mdrobnakCaptnoord, that's interesting about the WinCE memory model.
12:34.21cr2it's all documented in wiki
12:34.33cr2there are 3 banks on raph100
12:35.31cr232M@0x0 (aka SMI) 128M@0x10000000 (aka EBI1) and 128M@0x20000000 (don't know the name, probably EBI1 too)
12:36.12cr2parts of SMI and EBI1 are used by wince SPL, QCSBL, OEMSBL, AMSS
12:36.28cr2and are "hardware" protected (aka MPU)
12:36.59cr2maybe we can add some html colors to wiki, so it's visible
12:37.30cr2some MPU bits can be disabled, you you can see what is there (and maybe change ;)
12:38.10cr2i doubt that something in 128M@0x20000000 is protected by MPU , but can't prove it
12:38.50cr2the 89M limit for EBI1 is pure software (board-*.h)
12:39.20cr2the real MPU/AMSS limit is 128M-13M=115M
12:40.00cr2the free (non-MPU'd) SMI ram can be reused too
12:40.35cr2so if you are not interested in android, the 3 bank linux ram layout can be made
12:41.17cr28.5MB@0x0 + 115MB@0x10000000 + 128M@0x20000000
12:41.30Captnoordthanks... for this insight :D
12:41.30cr2err
12:41.43cr28.5MB@0x80000 + 115MB@0x10000000 + 128M@0x20000000
12:42.16cr2but the spl MPU can be disabled (see diamond code of dzo)
12:42.30cr2for you can wipe the SMI copy of spl too
12:42.37cr2and free more 512K
12:43.14cr2but then you need to take care of dynamic RAM allocation for the FB (should be easy)
12:43.31cr2and ADSP,MDP and CAM (and GPU and GPU1)
12:44.09cr2btw, we are missing the CAMERA block in the raph board file (cf. sapphire)
12:44.44cr2what are the requirements for the ADSP block, MDP and CAM (also ADSP actually) needs to be clarified.
12:44.49cr2back to work :)
12:45.13Captnoordlol
12:45.17Captnoordwe got owned
12:45.31ali1234HA
12:46.05*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
12:46.21ali1234the requirements of ADSP, GPU0 and GPU1 are pmem mappings, and they are entirely within the lower bank (0x10000000) according to the board file
12:46.39mdrobnakCaptnoord, lol
12:46.42ali1234so none of that explains why enabling the upper bank is causing a crash
12:46.54mdrobnakLOL
12:47.19mdrobnakI think I should try changing 89 -> 115 and seeing if that doesn't crash. I think it's going to.
12:47.40mdrobnakAlas, I'm working on PF firewall rules, then need to go to work.
12:47.40ali1234unless the dynamically allocated ram has to be in the samr ram bank as the pmem sections (which is entirely possible, and you should check what other memory the drivers allocate)
12:48.15CaptnoordI think its totaly related to android as cr2 mentioned he tested this all with ramdisk stuff
12:48.17Captnoordor
12:48.18Captnoordmemtest
12:48.21Captnoordor what ever
12:49.12ali1234anyway you slice it, a kernel crash is a kernel bug
12:51.01mdrobnakWell, here's the thing - has anyone tested something OTHER then Android that was not just a ramdisk running a memory test? Ie, used the framebuffer, and sound, at the same time?
12:51.17mdrobnakI did the ramdisk thing too, and it worked fine.
12:51.33mdrobnakBut obviously something's not right.
12:51.51mdrobnakIf someone had a working OpenMoko build I'd try that.
12:52.03mdrobnakI tried looking into it, and it looked like a pain to build.
12:54.52ali1234try a gizard rootfs
12:54.54Captnoordlol
12:55.00ali1234it has a framebuffer X server
12:55.01Captnoordmaybe check pmem_android.h
12:55.20Captnoordandroid_pmem.h
12:55.26Captnoordjust speaking my mind guys
12:55.51mdrobnakSame with all of us, lol.
12:56.02ali1234lots of rootfs tarballs here you can play with: http://tinderbox.dev.gentoo.org/embedded/linwizard
12:56.33ali1234the binaries should be ok on msm, even if not fully optimized, they should at least run
12:56.35mdrobnakWhat's that compiled for? Will that work on the MSM?
12:56.45mdrobnaklol nevermind
12:57.19ali1234we dont have any sound support in there
12:57.38ali1234no sound on our phones yet
12:57.55mdrobnakwell, why wouldn't we? Our kernel has support, no?
12:58.11ali1234probably not alsa sound, no
12:58.19mdrobnakOh.
12:58.28ali1234but either way we have no apps in those tarballs that can use sound
12:58.51mdrobnakWell, if the drivers are loaded, and we can exercise video, that's a start.
12:58.58mdrobnak(audio drivers)
12:59.07mdrobnak(not alsa audio, I know)
13:00.22mdrobnakAnyway, off to get ready for work. Back in 8-9 hours.
13:08.10*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
13:08.20*** join/#htc-linux GlemSom (n=glemsom@0x5da34bca.cpe.ge-1-1-0-1105.sdnqu1.customer.tele.dk)
13:17.46*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
13:21.37*** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215)
13:28.42*** join/#htc-linux townkat_work (n=townkat_@89.122.203.209)
13:40.44ali1234yeah, excalibur it is
13:40.55ali1234whoops, wrong window
13:45.04*** join/#htc-linux scheich (n=georg@79.197.219.51)
13:51.18*** join/#htc-linux MethoS- (n=clemens@134.102.106.250)
13:58.46*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
14:10.52*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
14:31.36*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
15:04.16*** join/#htc-linux SOG (n=SOG@n219079053203.netvigator.com)
15:22.15*** join/#htc-linux luc (n=luc@89-115-128-35.cl.ipv4ilink.net)
15:28.17*** join/#htc-linux richard333 (n=richard@adsl-072-149-006-119.sip.mia.bellsouth.net)
15:28.22richard333hey guys
15:32.31richard333adb devices returns my phone
15:32.34richard333but when i try eclipse
15:32.40richard333its not detected there
15:32.43richard333running windows xp 32bit
15:35.59richard333ddms works it shows the running processes
15:36.11richard333but i can't get eclipse w adt working, anyone help pls?
15:41.23*** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215)
15:48.58*** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
15:55.03*** join/#htc-linux onen|openBmap (n=quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr)
15:58.33*** join/#htc-linux jarski (n=jarski@82-128-214-231-Karjasilta-TR1.suomi.net)
16:01.49*** join/#htc-linux jarski (n=jarski@82-128-214-231-Karjasilta-TR1.suomi.net)
16:13.32*** join/#htc-linux pH5 (n=ph5@e178215097.adsl.alicedsl.de)
16:32.34*** join/#htc-linux stickboy (n=anonymou@128.153.211.18)
16:38.43jarskiHi guys, I have blac100. I took latest raphael android package from connect UTB and replaced kernal image with dwaradzyns and it boots...
16:39.37jarskibut I get message box in android that "power off" shutting down
16:40.28jarskiI guess it is something with pm and battery
16:40.57jarskiany ideas how to get pass that problem?
16:59.25*** join/#htc-linux stickboy (n=anonymou@128.153.178.77)
17:04.17*** join/#htc-linux randomblame (n=kevin@173.12.174.62)
17:08.26*** join/#htc-linux FR^2 (n=frquadra@frquadrat.de)
17:09.02randomblameWe gonna rock down to Electric Avenue
17:09.02randomblameAnd then we'll take it higher
17:24.58*** join/#htc-linux MrPippy (n=pip@adsl-75-36-57-196.dsl.sndg02.sbcglobal.net)
17:26.17*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
17:28.54*** join/#htc-linux balans (n=Administ@83.84.58.101)
17:36.08*** join/#htc-linux Nanto (n=Vegita@54031C33.catv.pool.telekom.hu)
17:47.18richard333hey jarski r u there?
17:47.47jarskiyep
17:48.13richard333i have a raph100
17:48.21richard333and i tried the latest pckg from connect utb
17:48.35richard333do the files go in the root of the sd or do they go in sd/tmp like before?
17:48.48jarskiroot
17:50.08richard333have u gotten it to boot up yet?
17:50.16richard333btw whats a blac100?
17:50.37jarskiblac100 is blackstone i.e. touch HD
17:51.21*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
17:52.09richard333nice, have u seen the htc leo?
17:52.45randomblamelol if I owned a touch hd I'd be pissed off to see the leo
17:52.58jarski:)
17:53.07richard333or excited to have an even better phone down the line
17:53.17richard333that is if u can afford to sell ur current one and pay the difference
17:53.57richard333id get the touch hd but theres no usa 3g
17:54.13randomblameyeah thats a serious drawback
17:55.58randomblameoooh Karmic Koala comes out oct. 29
17:57.55*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
17:58.35*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
18:04.56richard333alright great its running
18:04.59richard333but its super slow
18:05.17richard333its not even the hero build and its hella slow trying to do anything
18:05.34jarskiok :)
18:06.15richard333how can i browse my phone's content on android via usb on my computer?
18:06.29richard333i tried ddms file explorer but it doesnt load anything
18:10.11thedicemasteri think it's easier to just do that in windows mobile.
18:11.28*** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
18:14.43richard333yeah but having to restart to go to winmo, just to copy a file to the system seems kinda impractical
18:14.53richard333i'd like to remove any dependencies to having to go to winmo
18:26.31*** join/#htc-linux stickboy (n=anonymou@128.153.178.77)
18:30.19*** join/#htc-linux pleemans (n=toi@84.194.169.109)
18:46.42*** join/#htc-linux cr2 (n=cr2@109.85.29.232)
18:47.22*** join/#htc-linux dwaradzyn (n=chatzill@chello089079067084.chello.pl)
18:47.27dwaradzynhi cr2
18:48.08dwaradzyncr2: could you summarize how audiopaths should be changed in order to enable audio for blac100 (and not break other devices)?
18:49.22dwaradzyni think its the msm_audio_path(int i) in msm_hw.c is our target. but what is missing there?
18:51.22cr2dwaradzyn: you need to load some data for the dsp at some magic address
18:52.00cr2dwaradzyn: do you know how dzo accesses /sys/class/vogue_hw/audio in the android libs ?
18:52.44dwaradzyncr2: no. i can look into it, if it is the right thing to do
18:53.07cr2i think that the current config is phone-only
18:53.27cr2the code for kaiser is more extensive
18:54.02cr2but afaik the kaiser does not support BT headset
18:55.57*** join/#htc-linux kiozen (n=kiozen@rgnb-5d87d769.pool.mediaWays.net)
18:57.00cr2hi kiozen
18:57.30kiozenhi cr2
18:58.19kiozenany news in the htc-linux corner?
18:58.29kiozenlooking forward to the palm pre
18:58.59kiozenthink this will be my 1st smart phone
18:59.09*** join/#htc-linux pr0p (n=asdf@87.70.54.117)
19:01.10cr2we are moving forward, the only difficult thing remaining is BT
19:01.22cr2does palm pre support gps ?
19:01.34cr2which cpu is that ?
19:02.42dwaradzyncr2: i see it now. it is far more complicated in htc-vogue branch. there is a lot of magic in that code too
19:03.02kiozencr2: yes has gps
19:03.35pr0phello cr2 and dwaradzyn : came from the xda forums :) , with my HTC in my hand !
19:03.54cr2kiozen: which gps chip ?
19:04.38pr0pcan i compile with portable ubuntu ? or i have to compile on a non-portable one ?
19:04.46kiozencr2: http://de.wikipedia.org/wiki/Palm_Pre
19:04.46cr2dwaradzyn: i think you should dump the 0x140 bytes for +0xfc300 for each audio state.
19:05.24cr2dwaradzyn: it's a tedious work, but i don't see any other way to do it.
19:05.39dwaradzyncr2: indeed we currenty have audio path 2 and 5 which seem to be phone audio start and phone audio end. does audio work only for calling on raphs and diams now?
19:06.32dwaradzyncr2: well i'll try to do that. its a chance to get familiar with haret. and repeticio mater studiores est :)
19:06.35cr22 and 5 are "random" numbers
19:06.43cr2lol
19:07.02*** join/#htc-linux MrPippy_ (n=pip@adsl-75-36-57-196.dsl.sndg02.sbcglobal.net)
19:07.12cr2dwaradzyn: actually you may dump the whole audio-relevant area
19:07.22cr2of even the full 1MB each time
19:07.58cr2kiozen: nothing about gps ?
19:08.35cr2320x480
19:08.41kiozenhm, seems to be agps :(
19:09.12cr2it may mean everythng
19:09.49*** join/#htc-linux osilvan (n=o@87.222.122.224)
19:09.50cr2on msm they use phone DSP to process the gps signal
19:15.06kiozenbeats me, I can't find any information about the chip
19:21.04dwaradzynpr0p: don't know
19:23.02cr2dwaradzyn: actually it may be an easier way than to analyze the wavedev.dll disassembly
19:24.05cr2dwaradzyn: btw, where did you get the alt gpio settings for blac100 SD ?
19:25.02dwaradzyncr2: ?
19:25.43dwaradzyncr2: for the xda builds i only changed max clock rate, nothing else
19:26.27cr2each alt gpio has the alt parameter (write-only)
19:27.00cr2sdc3 DAT3 2,184,0
19:27.03cr2things like that
19:27.17*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
19:27.30*** join/#htc-linux patp (n=patp@87-194-56-160.bethere.co.uk)
19:27.34cr2blac100 values are not entered here -> http://www.htc-linux.org/wiki/index.php?title=Raphael_GPIO
19:28.02cr2they may be the same as raph100, but it needs to be checked.
19:28.14patpdwaradzyn hi
19:28.32dwaradzynpatp: hi
19:28.33cr2i want to edit topaz wiki, and think about the best layout for them
19:29.05*** join/#htc-linux yak007 (n=yak007@ip4da92b8e.direct-adsl.nl)
19:29.45patpstill some prob getting sd support using your kernel build; I don't get it, I have /dev/mmcblk0p1 using the old build but not with your new one.
19:30.27cr2patp: do you have the sdhc.dll from your phone ?
19:30.32tmzthey cr2
19:30.39tmztpulling
19:30.48cr2tmzt: hehe :)
19:31.02patpcr2: need reboot, hangon
19:31.16tmztcr2: Pre is omap3450
19:31.28cr2tmzt: what about gps ?
19:31.40tmztprobably in the msm6800, not sure though
19:32.45cr2ok
19:32.58tmztwe are using apm emulations?
19:33.11cr2don't know
19:33.29*** join/#htc-linux dcordes (n=luke@unaffiliated/dcordes)
19:33.42dcordeshi
19:33.44dwaradzyntmzt: i think palm pre is omap3430 (same as nokia n900)
19:34.40tmztah, yeah
19:34.49cr2dcordes: what do you think about becoming the haret patch master ?
19:36.06*** part/#htc-linux droid0011 (n=g1@p4FDCEBEB.dip.t-dialin.net)
19:36.48dcordescr2, that would be nice. but I can't tell how much time I will have left for all this when university starts in few days.
19:36.49dwaradzynpatp: mmc works for me out of the box. i don't have another card atm to test but sandisk 16gb class2 works every time
19:38.09cr2dcordes: ok
19:39.17*** join/#htc-linux yak0072 (n=yak007@ip4da92b8e.direct-adsl.nl)
19:39.52*** join/#htc-linux onen|openBmap (n=quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr) [NETSPLIT VICTIM]
19:42.31patpcr2: http://www.4shared.com/file/134636931/5e370968/SDHC.html
19:43.37patpdwaradzyn: mine's a Sandisk 4gb class 4.
19:45.20yak0072hi all, have a question about the latest blac kernel and the raphael andriod port, it boots but it goes straight to shutdown?
19:45.49yak0072and tnx for all the work on the kernelstuff
19:46.07yak0072is it possible to "disable" the poweroff?
19:47.01dwaradzynpatp: i am incredibly lucky with sd cards and linux then :) on my polaris it was working too when others reported that it is not working for them... could you pastebin full dmesg?
19:51.51townkatdwaradzyn: how close are we to android with audio ?
19:52.33tmzton?
19:52.39dwaradzyntownkat: not really close. a lot of reversing is needed for blac
19:54.34*** join/#htc-linux pattp (n=patp@87-194-56-160.bethere.co.uk)
19:55.08pattpsorry, got bsod.
19:55.13cr2lol
19:55.59thedicemasterbetter look up the error on that BSoD
19:56.09pattpdwaradzyn: can't get dmesg, as I haven't been able to do the ssh over usb thing in windows or vbox-ubuntu
19:56.40pattpthedicemaster: nah, it immediately rebooted. screw it, when you use windows, it's like weather.
19:57.05*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:57.10dwaradzynpattp: you can dump ram_console (in haret use command "pwf ram_console.txt 0xe000d 0x20000")
20:01.08cr2hm. the DEX crash may be avoided if the code will check the dex_ready flag.
20:06.01luchey cr2
20:06.16lucwhat driver do you use for wireless?
20:06.22lucti or Kalle Valo ?
20:07.10tmztI'm trying something, I've split out the cdma500 and cloned the diam include file
20:07.19cr2luc: not yet
20:07.41lucwill be beter tu use Kalle Valo ?
20:07.48pattpdwaradzyn: OK, I have haretconsole connected. when I run that cmd it produces a file on the phone, but that file doesn't have dmesg in. Should I boot linux?
20:08.02lucdid you test any of them?
20:08.05tmztI hope to rename that to raph-smi32 raph-smi64 or something similar
20:08.43cr2tmzt: on may phones this config is reported by oemsbl/amss in smem
20:08.51cr2s/may/many/
20:08.54tmztwhat is?
20:09.01dwaradzynpattp: yes. after reset repeat haret thing. do you use my build?
20:09.10pattpdwaradzyn, no wait, I'm an idiot, it is a dmesg. I didn't recognise it, not being white on black!
20:09.32cr2tmzt: 32 vs 64
20:09.41tmztah, ok
20:09.55tmztI can add the detect later but I already have an mtype
20:10.01cr2ok
20:10.14tmztHTC Raphael CDMA phone 500 (MACH_HTCRAPHAEL_CDMA500) [Y/n/?] (NEW) y
20:10.18cr2if there any ANDROID config option ?
20:10.27tmztI wonder if I ever included the proper mach definition before
20:10.48cr2so the android-specific things can be wrapped
20:11.14tmzton 2.6.31
20:11.58pattpdwaradzyn: https://privatepaste.com/20K4Dlkx0j
20:12.21tmztnow it's not booting at all
20:12.26pattpkernel was compiled from new git clone today
20:16.04cr2pll0=mpll
20:16.18cr2topa nk is interesting
20:16.33tmztis it tcx0 or tcxo?
20:16.47tmzttcxo is temperature-controller crystal oscillator
20:16.59tmztcontrolled
20:21.11pattp[    3.383178] mmc0: Slot eject status = 1
20:21.18tmztwhat client chip is raphael panel for?
20:21.22pattp[    3.577697] mmc1: Slot eject status = 0
20:21.44cr2bic 0xa00
20:21.59cr2tmzt: tcx0 is 19.2MHz
20:22.02pattp[   75.956054] mmc1: Slot status change detected (1 -> 0)
20:22.25cr2bic 0xa00 for clock disable ?
20:22.34tmztwe have so many symbol conflcts
20:22.36cr2i2c in this case
20:22.57cr2raph should support epson and tishiba
20:23.16tmztis there a reason for including the board header in that file?
20:25.08tmztI can't see why, (in mmc), it uses gpio numbers not names
20:25.35cr2tmzt: ?
20:26.02tmztok, in -panel it's the resources
20:26.05cr2we need to add human readable names for toshiba and epson, since we know them
20:26.08tmztmaybe we should move that to the board
20:26.23tmztright, but that should be by client/lcm, not machine
20:26.30cr2tmzt: it's much better in codeaurora code
20:26.35tmztyeah, true
20:26.43tmztbut I'm trying to avoid duplication
20:27.18tmztand we need to keep our tree buildable also
20:27.40*** join/#htc-linux c4software (n=Adium@roo49-2-88-161-139-221.fbx.proxad.net)
20:30.07pattphmmm. anyone know where mtype sets the sdcc id?
20:30.22tmztper device fixup?
20:32.43cr2pattp: ok, looking at your file
20:35.13c4softwarehi everyone
20:35.14c4software:)
20:36.30cr2alt is 48
20:38.54cr248 on raph100 too
20:38.56cr2hmm
20:39.50cr2vreg is 800000
20:40.20cr2"gp6",BT 23  0x800000
20:40.51cr2the same on rarh100
20:41.49cr2sd detect 026
20:42.09cr2like on raph800
20:42.25c4softwarealways any sign of dzo ?
20:42.27cr2dwaradzyn: which sd detect pin you use ?
20:42.31tmzthow do I get this to boot/init the htcfb again?
20:42.36tmztI'm using the same code
20:42.54dzoi'm here but only for 5 mins
20:42.55dwaradzyncr2: how do i find that out?
20:43.30c4softwaredzo, have you seen my pm ?
20:44.15c4softwarefor the backlight issue when you have disabled the pwrsync option ?
20:45.27dzoit looks like the mddi commands are correct perhaps the client power is slightly different or it could be timing problems.
20:46.13dzoi think it's close, you will need to do some more tracing. try tracing gpios while turning the panel on.
20:46.20c4softwarethe backlight is correctly turned off. But the screen say on. (with the panel option at 2 in startup.txt
20:46.49c4softwareif you explain how i have to do this i will do this for you :)
20:47.36cr2.sdcard_status_gpio = 38,
20:47.42cr2dwaradzyn: it's ok
20:48.21cr2dwaradzyn: must be something else
20:48.30dzosorry, i don't have time now, i'll look at the code later and see if i can spot anything. the gpio addresses to trace are 0xb2e00000 + 0x00400000
20:49.05dwaradzyncr2: i have four times mmc1: command timeout in dmesg. but no more
20:49.26c4softwareokay. i note this on a document on my computer. maybe some people can help my to trace gpio :)
20:50.02dzoc4software: you are using the diamond mtype right?
20:50.02c4softwareif i found something i send to you a pm
20:50.38c4softwareokay ?
20:50.40c4softwareyep
20:50.45dzothanks, a dmesg might help too.
20:51.04c4softwarei Used the 1805 mtype
20:52.36pattpcr2, dwaradzyn: do you want to see a dmesg from a boot that works (using kernel from Feb)?
20:53.55*** join/#htc-linux Reactor16 (n=Reactor1@ns1.ultravpn.fr)
20:54.20dwaradzynpattp: not needed. but you may want to see mine dmesg. its at: http://pastebin.com/m258f5cf3
20:54.53c4softwaresomeone have time to help me to track gpio and dmesg ?
20:56.14tmztah, I left out a mach check in -panel
20:56.21tmztbut it worked before
20:57.23townkati am building a linux virtual machine with vmware , what linux distribution should i use for kernel building ?
20:57.37ali1234ubuntu
20:57.51tmztubuntu server is fine
20:57.59townkatthnx
20:58.25c4softwareanyone :$
20:59.02pattpdwaradzyn: what ROM do you have on your HD? Mine is Topix 3.0, which is a mongrel build
20:59.34*** join/#htc-linux dwaradzyn (n=chatzill@chello089079067084.chello.pl)
21:00.21ali1234c4software: did you read this http://handhelds.org/moin/moin.cgi/HaRET_20Documentation ?
21:00.33c4softwareim on it :)
21:00.57dwaradzynpattp: duttys xt 3.3. i think rom this does not matter here
21:01.45c4softwarei always forgot the haret shell. ^^
21:02.08c4softwarethanks for the link ali1234 :)
21:06.07pattpdwaradzyn: are you sure it doesn't matter? The hw is initialized by windows drivers, maybe there is something different in the Topix ROM - some of the drivers are from Topaz for example.
21:07.19ali1234apt, gpio tracing?
21:07.20aptsomebody said gpio tracing was at http://handhelds.org/moin/moin.cgi/HaRET_20Documentation
21:07.20c4softwareali1234: you have time to help me a little :$. i'm a little bit confused :S
21:07.25ali1234\o/
21:07.52ali1234c4software: what's up?
21:08.05c4softwarei think i tracing the good things wirq 0xb2e00000 << to trac the 0xb2e00000 adress its correct ?
21:08.26ali1234dunno, that doesn't sound like gpios
21:09.09ali1234i never tried to trace interrupts
21:09.57c4softwareerf :S
21:10.45townkattmzt, why server? desktop won't do it ?
21:11.51ali1234townkat: because kernel compile is done entirely in a shell, installing desktop will just waste space and cpu time
21:12.16townkatthnx
21:12.51ali1234also i think you need to install from the server disk to get a kernel with pae support, without that it wont work in a vm
21:13.01ali1234although they may have fixed that by now
21:13.40c4softwaredamn
21:13.42c4softwareHaRET(3)# clear TRACES
21:13.42c4softwareHaRET(4)# addlist TRACES p2v(0xb2e00000)
21:13.43c4softwareHaRET(5)# wirq 10
21:13.46townkati am downloading the server right now, i may need more help later, thnx alot :)
21:13.49c4softwareits hang the telnet conenction :S
21:14.04c4softwareand my diamond too :S
21:14.31ali1234it will hang for 10 seconds
21:14.56c4softwareoO
21:15.01c4softwarewhy ?
21:15.20ali1234because tracing all interrupts is quite processor intensive
21:15.29ali1234and you told it to do it for 10 seconds
21:15.58c4softwarei have sft reset the phone i will do this again. but i maybe don't watch the good things ?
21:16.04c4softwarei'm not sure
21:17.26c4softwarei have restart the command :) wait for a result
21:18.17ali1234try wirq 1 first
21:18.22ali12341 second
21:18.58c4softwaredamn connectin with diamond lost.
21:21.48c4softwarewirq 1
21:21.59c4softwarewaiting for a result
21:22.13ali1234hmm
21:22.45c4softwarediamond hang. damn :P
21:22.49ali1234wel, irqs are tricky, if the wrong one is lost, it will crash
21:23.00c4softwarei do something wrong maybe
21:24.14ali1234maybe you didn't filter the irqs with ibit, and it is just spamming itself to death
21:24.48ali1234or maybe it just doesnt work on your hardware yet
21:25.40c4softwareon diam100 ?
21:26.21c4softwarejoinlist TRACES GPIOS << If i do this its seems working
21:26.34c4softwarei have a lot of data on screen
21:26.35c4software:D
21:26.55c4softwarebut its all GPIOS i just want 0xb2e00000
21:27.32ali1234you probably want mmutrace for tracing memory access?
21:28.53c4softwareto be exact i don't really know what exactly i have to trace : dzo say to me "the gpio addresses to trace are 0xb2e00000 + 0x00400000"
21:31.53ali1234i'm not familiar with that hardware architecture so i can't help any further, sorry
21:32.50c4softwareno problem :) thanks for your help ali1234:)
21:43.00*** join/#htc-linux cr2 (n=cr2@109.85.29.232)
21:43.28*** join/#htc-linux [1]Captnoord (n=Captnoor@81.71.164.123)
21:44.54cr2lol, it was some java programmer
21:44.58cr2<PROTECTED>
21:45.00cr2<PROTECTED>
21:45.03cr2<PROTECTED>
21:45.03cr2<PROTECTED>
21:52.21cr2<PROTECTED>
21:52.23cr2<PROTECTED>
21:52.24cr2<PROTECTED>
21:52.26cr2<PROTECTED>
21:52.27cr2<PROTECTED>
21:52.39cr2quite different numbers. for msm7x27
21:54.05cr2real innovation in usb functions. tcp/ip is not good enough.
21:54.35tmztmore usb functions?
21:55.45cr2<PROTECTED>
21:55.47cr2<PROTECTED>
21:56.12cr2cdc_ether is not include.
21:56.15*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
21:56.56cr2wtf i would like generic nmea usb multiplexed function ?
21:57.06cr2i will better run gpsd over cdc_ether
21:58.22cr2we need to recheck the SND endpoint list:
21:58.25cr2<PROTECTED>
21:58.27cr2<PROTECTED>
21:58.28cr2<PROTECTED>
21:58.30cr2<PROTECTED>
21:58.30*** join/#htc-linux Patrick_Bateman (n=infidel2@unaffiliated/swc666/x-4934821)
21:58.31cr2<PROTECTED>
21:58.33cr2it may be quite different
21:59.03cr2i know only 4 on raph.
21:59.26cr2may be different on blac100 (at least the order)
22:00.59cr2<PROTECTED>
22:01.16richard333hey guys sorry to disturb, i have a problem on the kaiser sometimes when i make/receive a call the earpiece doesn't work, they can hear me but i cant hear them
22:01.32cr2they use builtin lcdc more often
22:02.11cr2richard333: something is wrong in the audio routing, quite complex area ;)
22:04.11richard333maybe i could change the radio version i have, or do i have to just wait for a newer rom w this issue fixed?
22:04.18cr2heh
22:04.24cr2still dm1 ;)
22:04.27cr2&msm_device_uart_dm1
22:05.39cr2it is mdp gpio ?
22:05.43cr21129 static struct msm_panel_common_pdata mdp_pdata = {
22:05.45cr21130         .gpio = 97,
22:06.23cr2tmzt: i like such code
22:06.26cr21133 static void __init msm_fb_add_devices(void)
22:06.28cr21134 {
22:06.29cr21135         msm_fb_register_device("mdp", &mdp_pdata);
22:06.31cr21136         msm_fb_register_device("pmdh", 0);
22:06.32cr21137         msm_fb_register_device("lcdc", &lcdc_pdata);
22:06.34cr21138 }
22:06.36cr2want to switch to codeaurora :)
22:10.49cr2another combination
22:10.54cr2<PROTECTED>
22:10.55cr2<PROTECTED>
22:10.57cr2<PROTECTED>
22:10.58cr2<PROTECTED>
22:11.00cr2<PROTECTED>
22:11.54townkatis this guide good for blac too ?
22:11.54townkathttp://htc-android.com/viewtopic.php?f=13&t=172
22:16.07townkatnever mind, i found the one for blackstone
22:16.37*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
22:20.17tmztcr2: what is this?
22:20.28tmztI like the msm_fb_register_device
22:20.34tmztI would also like to see htc_hw used
22:21.55*** join/#htc-linux kvaster (n=kvaster@live.bn.by)
22:25.56townkatis this adress good ? git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
22:26.41townkatis in the wiki and is pretty old, i was wondering if its still actual
22:30.08cr2PM  0x30000061   pm_*
22:30.11cr2tmzt: aa
22:30.26cr2#define PMIC_RPC_PROG   0x30000061
22:31.40cr2<PROTECTED>
22:31.41cr2<PROTECTED>
22:32.08cr223,24 on raph
22:32.19tmztI can't figure this out
22:32.29tmztraph100?
22:32.53cr2107 #define MIC_SET_VOLT_PROC 30
22:33.11cr228 on raph100
22:34.09*** join/#htc-linux Untouchab1e (n=Untoucha@239-15-8.connect.netcom.no)
22:43.45cr2<PROTECTED>
22:46.07tmztwell, I think I might have found the problem
22:46.18tmzt-gps.o is only included on HTCRAPHAEL, not the cdma devices
22:46.24tmztbut it's in the devices list
22:47.24cr2cdma is different
22:47.38tmztyeah, so I can't see why it's in the list
22:47.58tmztthe framebuffer is not being initialized now that I've changed the files
22:48.01tmztand I can't see why
22:48.08tmzteven htc_fb
22:48.14cr2strange
22:50.10cr2tmzt: do we demux the dex irqs ?
22:50.22cr2i doubt it
22:50.41tmztdon't think so
22:50.55tmztwe don't even give them irq numbers do we?
22:52.56cr2m2a_6
22:57.52*** join/#htc-linux cr2 (n=cr2@109.85.29.232)
22:58.07cr2looks familiar
23:06.53tmztwell, putting the .config back fixes it (with raph800 mtype)
23:07.04tmztcompletely lost
23:09.38tmztah, it could be because I'm using diam gpios, not raph
23:09.40tmztin my header
23:09.57tmztI thought the device fixup would work though
23:12.12cr2good night
23:29.58*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-172-111.dynamic.mnet-online.de)
23:43.40*** join/#htc-linux stickboy (n=anonymou@128.153.211.18)
23:44.09*** join/#htc-linux pronik``` (n=user@g229177001.adsl.alicedsl.de)

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