IRC log for #htc-linux on 20090830

00:00.28cr2druidu: is it better to have an ifdef there ?
00:00.34Bally3aah.. no.. still working on polaris wifi as yet.. and reading up about setting up the sources
00:00.47tmztso what branch are you working on now?
00:01.08cr2druidu: the most smart was will be to trap the proc_comm, and do the right thing for wince (if amss=wince)
00:02.32tmztthere's a proc_comm api right?
00:02.47tmztthere should be an ops table
00:03.00cr2int msm_proc_comm(unsigned cmd, unsigned *data1, unsigned *data2)
00:03.32cr2and it hides gpio config, vreg & DEX, and clocks+rpc
00:03.38tmztotherwise it will be hard to support trout as well
00:05.40cr2tmzt: is the gpio alt config protected by MPU on g1/g2 ?
00:05.56cr2tmzt: if not, then our code may be used on g1/g2 too
00:06.17tmztI don't know, I guess we could enable it though
00:06.33cr2you mean disable
00:06.37tmztyeah
00:06.39tmztright
00:06.53tmztwho was building openmoko-msm again?
00:08.23cr2tmzt: there is a nice rpc call clk_regime_sec_msm_get_clk_freq_khz()
00:08.47cr2but it has some clock handle as a parameter
00:09.16tmztnice
00:09.30tmztso there's a copy_smem_user or something?
00:09.37tmztwhat kind of pointers are these?
00:14.12cr2i'vedited clk_regime_msm AP here
00:14.18cr2http://www.htc-linux.org/wiki/index.php?title=MSM_CLK
00:14.28*** join/#htc-linux Shinto (n=John@f049070072.adsl.alicedsl.de)
00:15.08druiduwtf is clamshell anyway?
00:17.04tmzthe means the slide on the keyboard
00:17.52druidumicrop-ksc: rewritten kovsky clamshell support -- this still breaks the build if compiling without CONFIG_MACH_HTCKOVSKY
00:17.57cr2btw, why does clock-wince.c set pmdh clock to 0xa00 when it's 0xa19 for rap100 and 0xa41 for raph800 ?
00:18.11cr2and g1 has a different value too
00:18.33druiduno idea :D
00:18.39cr2CONFIG_MACH_HTCKOVSKY is evil
00:19.05cr2druidu: sometimes i'm wondering why the LCD works at all :)
00:19.19cr2most things there are setup differently in wince.
00:19.30tmztdoes the clock really matter?
00:24.28druiducr2: simple, we just write stuff in the buffer and do a dma transfer, everything else is just for transition to the android firmware :)
00:25.09cr2tmzt: the mddi speed
00:25.43tmztyeah, but if it being wrong doesn't affect the screen how could it be used?
00:25.55tmztor it's just close enough?
00:25.58druiduanybody know address at which to push git changes?
00:26.02cr2druidu: we also push mddi speed setting and toshiba config. even if the mddi client is epson. and it still works :)
00:26.53druiduhey, that's what I call robust design... works even if you push bullshit
00:27.23cr2it may be interesting to cal clk_regime_sec_msm_get_clk_freq_khz(0x38) on wince
00:27.33cr2s/cal /call /
00:27.53cr2and (probably) get the mddi clock speed
00:27.58tmztwe could list the proper clock settings?
00:29.03cr2(at least) only for the clocks with regime idx, and those with known clock algorithm (BT and SD/wifi)
00:29.46cr2i2c is 0x2f , for example
00:30.02tmztthere's clk_regime_sec, is there a non-sec
00:30.03cr2i'm wondering if it'll report the ~100 or ~400kHz clock
00:30.09tmztA clocks
00:30.11cr2most are sec
00:30.46cr2it can be an interesting rpc test driver too
00:30.56cr2or calling it inside haret.
00:31.50cr2on linux it's an rpc call 0x3000000f ,0, 0x25
00:32.08cr2and for wince it's possible to just use the clock API
00:36.04cr2ali1234: about mdoc_g34.c the g3/g4 should be a module parameter probably. and g4 may have a different register location
00:36.13druidushit, I pushed the wrong changes
00:36.18druiduhow can I undo a git push? :D
00:36.33tmztwhere did you push it?
00:36.35tmzthow recently?
00:41.27cr2ali1234: http://belgarath.falguerolles.org/download/mio_a701/docs/disassembly/RomBootStrap.S
00:41.30druiduright now
00:41.37druiduhttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.27
00:42.37druiduwell, I was going to push it anyway but didn't get to test it so there will be some more changes
00:42.50druiduany ideas?
00:44.24druiduso I want to reset HEAD to abfb31f3e1d5e8096eb6668401963d1ec5212889
00:48.17*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-61-155.dynamic.mnet-online.de)
00:49.01cr2Sapphire (MACH_SAPPHIRE) [Y/n] (NEW) n
00:49.22cr2<PROTECTED>
00:50.37cr2arch/arm/mach-msm/qdsp5/adsp.c: In function ‘msm_adsp_probe’:
00:50.38cr2arch/arm/mach-msm/qdsp5/adsp.c:805: warning: assignment makes integer from pointer without a cast
00:50.40cr2arch/arm/mach-msm/qdsp5/adsp.c:806: warning: assignment makes integer from pointer without a cast
00:50.41cr2arch/arm/mach-msm/qdsp5/adsp.c:807: warning: assignment makes integer from pointer without a cast
00:50.47marexcr2: Support for OpenBSD (OPENBSD) [simply Y] ;-)
00:51.43cr2marex: linux is the one true operating system :-)
00:52.00marexcr2: try telling that to the mighty OpenBSD $DEITYs ;-)
00:52.25marexnow that'd be one hell of a rough flamewar ;-)
00:52.28druiduwohooo, managed to undo the commit :P
00:52.33druidu-f (force) rulez
00:53.24marexcr2: it's an university project ... and it allows me to build my own little empire (without RMS anywhere close) in the OpenBSD kernel ;-)
00:53.59tmztmarex: what device?
00:54.14marextmzt: palms ...
00:54.24marextx t5 ld z72
00:54.39cr2marex: lol. i don't mind switching to a gplv3 licensed os
00:54.57cr2drivers/usb/function/msm_hsusb.c: In function ‘usb_find_descriptor’:
00:54.59cr2drivers/usb/function/msm_hsusb.c:1755: warning: large integer implicitly truncated to unsigned type
00:55.05marexcr2: seen windows7sins already ?
00:55.12marexcr2: Im starting to be suspicious of RMS
00:55.24marexor rather of his overall mental health
00:55.40druiduRMS?
00:55.43ali1234anybody know about qualcomm pistachio?
00:55.45cr2$windows is filtered out by my brain automatically
00:56.07cr2ali1234: it's an L4 based microkernel
00:56.11ali1234druidu: RMS is overall arm linux maintainer
00:56.21marexali1234: bullcrap ... RMK is
00:56.29ali1234oops
00:56.30marexRMS is the GPL fatman ;-)
00:56.31ali1234yeah
00:56.58ali1234damn TLAs
00:56.59marexI dont mind RMK ... even though in the OpenBSD kernel Im the RMK to some extent ;-)
00:57.06marex(it really does feel great :-) )
00:57.23ali1234well RMS, hasn't everyone know he's crazy for years?
00:57.44marexali1234: yeah, but they are afraid to put him under lock into some madhouse ;-)
00:58.06marexpossibly the psychiatrists are scared they'd get infected or something ... ;-)
00:58.16druiducr2: any descriptions for your patches?
00:59.17marexcr2: btw. it's good to know more OS internals besides linux ;-)
00:59.36cr2adsp irq and parameters, bt clocks and halt implementation
00:59.49druidu2nd one is power off support right?
00:59.51cr2marex: make n560 resume, then i'll listen to you :)
00:59.57druiduah, halt
01:00.05cr2halt=poweroff
01:00.18marexcr2: you're getting me heated up ... I might end up porting openbsd to it too ;-)
01:01.17cr2BT clocks are derived from PLL0, while SD clocks are from PLL1 and TCX0
01:01.31cr2marex: make resume work in any os.
01:01.40cr2wince != os
01:01.54marexcr2: hey that's cheating
01:02.35marexcr2: Ballmer calls it an OS and this time I'll take his word for it ... so go ahead, finish sound on N560
01:03.22cr2marex: it's of little use without resume. talk to kiozen
01:04.09cr2druidu: but i need to write some demonstrating code and comments for clock-wince.c about it
01:04.18marexcr2: it's certainly very useful ... dont try to talk your way out of it ;-)
01:04.56cr2marex: ok, i promise you to write the sound driver, once the resume will work.
01:05.30marexcr2: it works in wince
01:06.55marexcr2: I'll look into the resume once I have some free time ... but fttb it's x86 assembler till 8th sept ... then I have to design some serial-GPIB bus converter ... then work on the OpenBSD some more (yay!) ... so possibly sometimes after those are sorted out
01:07.02*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
01:07.27marexbtw the asoc audio is a piece of cake and you know it :/
01:07.39tmztwhat are those for?
01:09.19cr2GPIB is not difficult
01:09.54cr2druidu: how do i roll back your commit ?
01:11.42*** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34)
01:11.58marextmzt: exam from x86 asm (including the lovely FPU, yummy MMX and tasty SSE in all it's beauty) I have on 8th -- and then some voluntary work at uni (GPIB) -- and the OpenBSD port is an university project (and I like it anyway)
01:12.13marextmzt: that's just cr2 who doesnt understand what a real UNIX should be like
01:13.20cr2marex: x86 is the most evil cpu i know
01:14.05*** join/#htc-linux marajin_ (n=marajin@87-194-102-189.bethere.co.uk)
01:14.20rafyvittohey guys
01:14.57marexcr2: I can agree with that more than fully ... the x86 assembler makes me want to cry and vomit
01:15.13marexrafyvitto: hello
01:15.32rafyvittodid you guys ever read about this http://forum.xda-developers.com/showthread.php?t=388273&highlight=linux
01:15.59rafyvittoits a dual boot linux/windows mobile 6.1 for the typhoon
01:16.42rafyvittosome chinese guys made it happen
01:19.09rafyvittois this usefull in anyway for the raph android port?
01:20.01tmzt3.SD card (linux mirror and wince XIP boot from SD card)
01:20.03tmztnice
01:20.35rafyvittois this method better than haret?
01:21.11tmztyeah, if it works
01:21.18tmztthe console sounds interesting, what is it?
01:21.34rafyvittoi dont have a clue
01:21.53rafyvittoi have always wonder how does chinese dudes made it happen
01:22.23tmztwe could use source
01:22.28rafyvittohttp://forum.xda-developers.com/showthread.php?t=388231 here are some screenshots
01:22.30tmztfor the bootloader
01:23.05rafyvittosomeone would have to contact the project leader or main dev
01:23.13rafyvittoand see if he could share the source
01:23.32rafyvittoproblem is, hes chinese ><
01:26.22druiducr2: pushed your patches: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.27
01:29.45tmztrafyvitto: you in #xda-devs?
01:40.14*** join/#htc-linux stickboy (n=anonymou@128.153.211.117)
01:48.30rafyvittoyes
01:53.15rafyvittowait if your asking if im that channel no xD, i though you meant the forum it self
01:53.22rafyvittoin*
01:53.25*** join/#htc-linux miknix_ghost (n=miknix@bl4-81-27.dsl.telepac.pt)
01:55.48rafyvittohey tmzt
02:05.17*** join/#htc-linux Rafyvitto (n=rafymerc@24.54.253.34)
02:06.56*** join/#htc-linux Rafyvitto (n=rafymerc@24.54.253.34)
02:18.51*** part/#htc-linux Rafyvitto (n=rafymerc@24.54.253.34)
02:59.02*** join/#htc-linux AFBCamaro (n=Criton@fl-71-52-102-205.dhcp.embarqhsd.net)
03:00.00AFBCamaro.
03:07.14*** join/#htc-linux surge (i=surge@pool-98-118-154-21.bflony.fios.verizon.net)
03:17.44*** join/#htc-linux jlcox (n=root@5.30.233.220.static.exetel.com.au)
03:50.08*** join/#htc-linux Amaranth (n=travis@ubuntu/member/Amaranth)
03:59.41*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
04:00.37*** join/#htc-linux MrPippy (n=pip@adsl-75-37-163-177.dsl.sndg02.sbcglobal.net)
04:08.48*** join/#htc-linux Moku (n=John@f054169173.adsl.alicedsl.de)
04:25.04*** join/#htc-linux droid001 (n=g1@p4FDCEB43.dip.t-dialin.net)
07:24.27*** join/#htc-linux ArteK (n=Artur@81.15.241.96)
07:25.43*** join/#htc-linux kiozen (n=kiozen@rgnb-5d87c9a0.pool.mediaWays.net)
07:27.28*** join/#htc-linux stickboy (n=anonymou@128.153.211.117)
07:28.42*** join/#htc-linux niccoswe (n=niccoswe@78-70-202-58-no156.tbcn.telia.com)
07:31.11*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
07:39.37*** join/#htc-linux niccoswe (n=niccoswe@78.70.202.58)
08:02.06*** join/#htc-linux niccoswe (n=niccoswe@78-70-202-58-no156.tbcn.telia.com)
08:05.14*** part/#htc-linux niccoswe (n=niccoswe@78-70-202-58-no156.tbcn.telia.com)
08:13.08*** join/#htc-linux cr2 (n=cr2@ip-77-25-155-176.web.vodafone.de)
08:13.28cr2Application stopped. Please contact your administrator
08:13.33cr2eh?
08:28.03Perkkahey guys...
08:28.10Perkkathis it totally off topic...
08:28.35Perkkabut a nice gift for my gf who goes 22 in a few days...
08:28.45Perkkaideas? :P
08:37.34*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
08:57.06Echo31cr2: pH5: hi
09:08.50*** join/#htc-linux xperia (n=chatzill@80-218-229-113.dclient.hispeed.ch)
09:09.00xperiahello to all.
09:10.31xperiacr2: i am analysing the microp wiki changes. a lot of the new stuff makes sense for me now. i think there are one or tewo things that are missing.
09:16.23xperiaas a example the lines cc,14,<0a,x pointsequence cmd+buf; wr mul and  cc,41,3c,x -> LED TBL (hardcoded) ; wr mul
09:18.12xperiaP.S. can somebody look why the htc-linux logger from netripper dont work since yesterday ? http://irclog.netripper.com/?chan=htc-linux wihout a log the people will miss a lot of conversation
09:18.28*** join/#htc-linux Squarc (n=Squarc@82.217.32.29)
09:18.39dzohi cr2, i got myself a diamond. does audio work on raph yet?
09:19.14druidunot yet dzo
09:19.31dzoon diamond it doesn't register the m2a rpc and calls the wince ept.
09:19.38*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
09:19.39dzofor the adsp.
09:20.50dzoperhaps something wrong with rpc startup. since wince has already registered the rtosadsp rpc we cant take it over.
09:21.20dzoi might try smsm change state to reinit rpc on the a9.
09:22.03dzoi've got some questions too do you have some time?
09:22.34druidume? not sure if I can help you, but you can ask :D
09:22.50dzois there no cpld on these devices?
09:25.40druidudon't know...
09:26.12xperiacr2: in my i2c traces i have this here.
09:26.14xperiacc,14,<0a,x pointsequence cmd+buf; wr mul
09:26.15xperia003451: mmutrace 7805fd34: e5863000(str) b2300000 000001cc (00000000)
09:26.17xperia003451: mmutrace 7805fd74: e5863000(str) b2300000 00000014 (00000000)
09:26.18xperia003451: mmutrace 7805fddc: e5863000(str) b2300000 00000094 (00000000)
09:26.20dzonever mind, i'll come back later and see if cr2 is around.
09:26.20xperia003523: mmutrace 7805fddc: e5863000(str) b2300000 00000228 (00000000)
09:26.21xperiaand this here
09:26.23xperiacc,41,3c,x -> LED TBL (hardcoded) ; wr mul
09:26.24xperia003751: mmutrace 7805fd34: e5863000(str) b2300000 000001cc (00000000)
09:26.26xperia003751: mmutrace 7805fd74: e5863000(str) b2300000 00000041 (00000000)
09:26.28xperia003751: mmutrace 7805fddc: e5863000(str) b2300000 00000000 (00000000)
09:26.29xperia003808: mmutrace 7805fddc: e5863000(str) b2300000 00000000 (00000000)
09:26.31xperiaMy first question to you is the 0x3c right for the hardcoded LED TBL ?
09:28.24xperiaP.S. the two lines after the 41 lines is not a clearing. i have just posted the first two lines after 0x41 from nearly 40 (str) lines.
09:34.36cr2dzo: good news :D the sound does not work, but the latest 2.6.27 git should be a good start.
09:35.43dzoyes, i saw that, how far does it get for you, does it start to write to the adsp?
09:36.14cr2dzo: there is a 3000ffff amss server, which sends data to arm11 even while in linux. we may reregister some dummy client for it.
09:36.52dzook, i'll look at that, thanks, got to go now, bye.
09:36.57cr2it sends the audiomgr rpcs without a problem, but then hangs the machine
09:38.35cr2druidu: do you have BT in .config ?
09:39.10cr2xperia: 0x3c is the size
09:40.07cr2dzo: 7x01A phones have enough gpios, so they don't use cpld
09:40.51dzoexcept dream and saphire, they do.
09:41.07cr2dzo: no known wince phones
09:41.25dzook, that makes things simpler anyway.
09:41.28cr2dzo: this is the latest doc collection http://www.htc-linux.org/wiki/index.php?title=Raphael
09:42.03dzoyes, i saw that. has anybody looked at power collapse?
09:42.58dzoand data is on smd7, yes?
09:43.40dzois the smd_private table correct?
09:47.29xperiacr2: ahh great. the size of the buffer. what i dont understand now is how this Hardcoded Led Table is created. when i compare the source table with the i2c log they are two differnt things.
09:47.29xperiahere a litlle example
09:47.29xperiathat is the i2clog here http://pastebin.com/d6ffcb25b
09:47.29xperiaand that here should be the hardcoded table. http://pastebin.com/m48c21e8b
09:51.06druiducr2: actually, i'm trying to get android to work again... don't know why it locks up at boot
09:51.13druiduanybody have a working diam100 image?
09:53.14druidunone of the download links on connect-utb work
09:55.45druiduhmm, why do I keep getting "msm_i2c: msm_i2c.o: Warning bus was busy (xx)
09:56.36druiduwhile booting android, it keeps showing this error on the console while the android logo flashes
10:00.00xperiacr2: are you sure about the size? becouse i have as a size value zero.
10:00.02xperiathe anoying thing is that we have two blocks that repeat in my i2c logs.
10:00.03xperiafirst three lines with writes. 100 mili seconds delay
10:00.05xperiafour lines writes 60 miliseconds delay
10:00.06xperiarepeat the whole again.
10:00.08xperiaDo you have also such a thing or is this only on my device becouse I am having on the htc-kovsky device a spectral colour effect when the leds turn on.
10:00.09xperiafor me my i2c log show the change of the spectral colour.
10:00.11xperiabut i cant find the sources or the buffer in the sources with this numbers that are sended to be stored.
10:00.12xperiahttp://www.colour.org.uk/spectrum.gif
10:03.21*** part/#htc-linux druidu (n=druidu@78.97.155.94)
10:07.36*** join/#htc-linux ogr3_ (n=ogr3@adsl-99-3-81-175.dsl.lsan03.sbcglobal.net)
10:07.49xperiacr2: here is a full i2c log for blinking of a led http://pastebin.com/m6eb4b420
10:09.28Echo31cr2 : Hi
10:09.44cr2dzo: you have a gsm diam ?
10:09.53cr2Echo31: hi
10:10.53cr2Echo31: what is the full url to pH5 git ? let's try to compile the kernel
10:11.06cr2xperia: looking at your data
10:15.03Echo31cr2: PH5 want to add the patches only the next week.
10:17.12cr2Echo31: i'll try if it works for me
10:17.43Echo31cr2: ok
10:18.37Echo31cr2: I tries to implement ATA ide on athena CS3. What is EGPIO1_C4_HTCATHENA_EPSON_POWER_SLEEP meaning (cpld1) ?
10:20.00cr2Echo31: i'll check it with the .dll . is it traceable ?
10:24.04Echo31cr2: The ide driver launches the hda: unfortunely, the error message displays with "hda: timeout in ide_busy_sleep" . I ll try to set this egpio to 1
10:24.32cr2check with 'pd' if it's enabled in wince. i think so
10:27.33Echo31cr2: I go to check it, now
10:30.17Echo31cr2: HaRET(1)# pd 0x08000000 16
10:30.17Echo3108000000 | 000e0004 00d00013 007e0000 000a0021 | ..........~.!...
10:31.28*** join/#htc-linux cbandarrinha (i=55f5b9ae@gateway/web/freenode/x-tdyvqazhhhzbrgso)
10:32.27*** join/#htc-linux mallochigh (n=Administ@cpe-173-169-235-155.tampabay.res.rr.com)
10:33.46xperiacr2: the led spectral settings has a time frame from 3.8 second till 5.2 seconds
10:33.48xperia003808: mmutrace 7805fddc: e5863000(str) b2300000 00000000 (00000000)
10:33.49xperia005235: mmutrace 7805fddc: e5863000(str) b2300000 00000208 (00000000)
10:33.51xperiathe setting of the led colour must be done in a routine.
10:34.21*** join/#htc-linux pH5 (n=ph5@g229065192.adsl.alicedsl.de)
10:34.53cr2Echo31: how is the epson dll called ??
10:35.20Echo31cr2: I don't know
10:36.58mallochighHowto htc raphael / touch pro android?
10:37.10mallochighSeems like a reading in the forum so I thought I would ask
10:37.13mallochighIts for my gf
10:38.26cr2Echo31:hmm. v03usbfn
10:38.47Echo31cr2 ATA_WRITEBACK.dll  with folder Epson-ata and FSD=FATFSD.dll
10:39.27cr2mallochigh: not there yet, but i guess with dzo joining in we will finish it soon.
10:39.38cr2Echo31: ok, sounds good.
10:39.59*** join/#htc-linux SOG (n=SOG@n058152150059.netvigator.com)
10:40.02cr2Echo31: don't have ATA*
10:40.13cr2heh. it's lowercase
10:41.00cr2looking
10:42.15cr2aee* is pxa gpio
10:46.31*** join/#htc-linux druidu (n=druidu@78.97.155.94)
10:46.33cr2Echo31: checks the board version (upper CPLD2 bits). do you print it out ?
10:47.15cr2orr_cpld1(3,0x10)
10:48.26cr2then something with the pxa gpio 0x10
10:48.35cr2msleep 0x4b0
10:50.59Echo31cr2: HaRET(10)# pd 0x0a000000 16
10:50.59Echo310a000000 | 00000000 00000000 00000000 00000000 | ................
10:51.06cr2GPIOC4   0x0010   epson power sleep 4b0
10:51.32cr2ok, that means 'on=1, msleep 0x4b0)
10:51.50cr2editing the wiki
10:52.24cr2GPIO 68   00000010   EPSON power?   O
10:52.30cr2need to check this one too
10:53.08cr2+0x20 bit
10:54.23cr2#define GPSR2           __REG(0x40E00020)
10:54.38cr2ok, so pxa gpio68=1
10:56.03cr2#define GPCR2           __REG(0x40E0002C)
10:56.07cr2on off=0
10:59.37cr2Echo31: is the gpio68 changing ?
11:00.49Echo31cr2:  I set the GPIO68 to 1 but egpio not yet
11:01.32cr2ok
11:01.56Echo31cr2 : sleep 4b0 ?
11:02.20cr2msleep 4b0 ?
11:02.56cr2mdelay(1200)
11:04.00Echo31cr2: I must expect a mdelay
11:04.27cr2after setting 2 gpios, delay for 1.2s
11:05.44Echo31cr2: But I set the egpio during the initlialisation of cpld1
11:06.54cr2?
11:07.31*** join/#htc-linux phh (n=quassel@lns-bzn-50f-81-56-224-142.adsl.proxad.net)
11:07.44cr2it's not for the initial value
11:08.26Echo31cr2: I set 0x10 for the inital value
11:08.41cr2it's wrong
11:09.25*** join/#htc-linux x29a_ (n=x29a@unaffiliated/x29a)
11:12.54*** part/#htc-linux ArteK (n=Artur@81.15.241.96)
11:13.09Echo31cr2: I set EGPIO register C of CPLD1 with 0x10 value ?
11:15.16cr2GPIOC4=1
11:16.04cr2GPIO68=1
11:16.10cr2mdelay(1200);
11:16.24cr2to powerup epson
11:16.39*** join/#htc-linux ArteK (n=Artur@81.15.241.96)
11:21.10cr2Echo31: btw, why are you using joystick for accelerometer ? afair the raph accelerometer driver is not using it.
11:23.15Echo31cr2: GPIOC4= 1  ->  initiale value=0x10 and I cannot wait 1200 because the pata_platfor and cpld1 are initilised at the same time in platform_add_devices
11:25.15cr2why can't you just set gpio ?
11:25.34cr2.init is a completely wrong place for setting this gpio
11:25.52cr2eventually we will remove the LCD .init bits too.
11:26.05cr2because they do not belong there
11:27.08Echo31cr2: I set GPIO068 before   the function of platform_add_devices
11:29.06Echo31cr2: the Gsensor for athena is the raph acelerometer but on I2C
11:29.43cr2ok, then you can only hope that it will work
11:30.03druiducr2: i get a `ARM9 has CRASHED` `smem: DIAG ''` when booting android with latest kernel
11:30.05druiduany tips?
11:30.12cr2raph accelerometer is also i2c, just a different chip
11:30.37druidubtw, your halt works... before disabling panic on oops it shut down completely
11:30.52cr2druidu: boot with angstrom initrd. if it will work (works for me) then it's an android fault
11:31.12druiduit books ok into console mode
11:31.17druiduI can telnet to it even
11:31.28druiduthen while booting android, the flashing logo, I get that ARM9 has crashed
11:31.38druidujust before that is a request suspend state: wakeup
11:31.44cr2disable power off, then you'll see the crash reason
11:31.59cr2does the android ram console work ?
11:32.27cr2nobody looked into suspend/resume yet
11:32.31druiduI disabled panic on ops and this is all I get
11:32.42druiduthing is, latest update from upstream needs CONFIG_HAS_EARLYSUSPEND=y
11:32.50druiduso I activated that
11:33.08cr2disable it
11:33.56druiduwon't work with the latest upstream ver, it needs that to compile htc_pwrsink.c
11:34.11druiduI'll try again without that patch, see if it works
11:35.05cr2pwrsink is not needed
11:37.56druidubtw
11:37.57druidu<PROTECTED>
11:37.57druidu<PROTECTED>
11:37.57druidu<PROTECTED>
11:38.11druiduso that's what happened, handle_modem_crash was called
11:38.45cr2we can reboot only with a DEX call
11:39.08cr2the purpose of gpio25 is not 100% clear
11:40.41druidu<PROTECTED>
11:40.46druiduthis is just hilarious :)
11:46.19Echo31cr2: sorry, the athena Gsensor chip used from htc-shift chip. The i2c between  LIS3LV02DL and device is ok but the polling function don't yet work . I don't know why.
11:48.43Echo31cr2: Where can i find the raph accelero ? name and url ?
11:49.55druiducr2: your power_down is the weirdest thing ever
11:50.26druiduit doesn't actually shut down (leds are still glowing), soft reset button doesn't do anything and the power button resets the device :)
11:50.57druiduit's a kind of deep sleep
11:51.07cr2Echo31: drivers/i2c/chips/kionix-kxsd9.c
11:51.39Echo31cr2: thanks
11:52.36cr2druidu: the leds are controlled by a microcontroller
11:53.00cr2druidu: the power_off is only for the pmic
11:53.35cr2at least it is more useful than RESET_ARM9 :)
11:54.14cr2druidu: is 'soft reset' a gpio ?
11:55.56druidudon't now, doubt it
11:56.03druiduworks right after I boot the kernel
11:56.08druiduso no drivers, no nothing
11:56.53druiduyou might be able to disable it though, maybe
11:59.32*** join/#htc-linux phh (n=quassel@lns-bzn-50f-81-56-224-142.adsl.proxad.net)
12:00.32Echo31cr2: the raph accelero is based on hrtimer for polling : the htc-shift uses input-polldev. I ll try with hrtimer
12:10.15Echo31cr2: for epson, i must to set GPIOC4=1 ( 0x10 to cpld1 register C) and GPIO68=1. However, I cannot wait mdelay(1200)
12:11.01cr2Echo31: the device driver should be able to set power. also suspend/resume
12:19.01druiducr2: ok, this is weird, while booting android I just get a "Power down." message then msm_pm_power_off is called
12:19.13druiduno other message printed on the console
12:24.10phhprint the backtrace at the start of msm_pm_power_off
12:29.20druidugood idea
12:29.37druidulol, I can play mp3s in android, even if I can't hear them :)
12:35.10*** join/#htc-linux Bally3 (n=Bally3@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
12:42.29druiduLOL
12:42.44druidulooks like the batter driver doesn't work and because of that android thinks it's best to shutdown
12:42.47druiduso calls sys_reboot
12:46.40*** join/#htc-linux x_coRe_x (i=coRe@95-37-233-84.dynamic.mts-nn.ru)
12:49.04parmaster_wow cr2 is back! we're saved!
13:22.44*** join/#htc-linux leaigor (n=laigor@188.134.36.14)
13:23.02*** join/#htc-linux dream_kill (n=nospam@89.131.127.37)
13:23.58phhdruidu: "doesn't work" means report 0 ?
13:24.38druidudamn, just noticed
13:24.46druiduboard diamond doesn't register the battery driver
13:24.48druiduso it's not there
13:25.05druidugonna port some stuff from board-htcraphael to diamond
13:26.50*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
13:27.01druidukdiff3 rulez again :)
13:29.03phhoh you're doing diamond's port ? great. if i can help with my diam100+ a diam 160 battery (not the standard one but a 2Ah, don't know if it changes anything)
13:29.15phh(but way too lazy to setup a crosscompiler.)
13:29.23*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
13:29.57*** join/#htc-linux marajin (n=marajin@87-194-102-189.bethere.co.uk)
13:32.58Echo31cr2: I tried some ways, but  platform_add_devices function  initialises in the same time the pata_platform ( ata ide) and cpld1. I cannot insert a mdelay.
13:39.07Echo31cr2: Your Idea is it to suspend  the pata_platform during 1200 for the initiatlisation of devices, and do after a resume ?
13:40.44cr2Echo31: i'm surprised. how does this driver look like ?
13:43.25Echo31cr2: what ?
14:18.08Echo31cr2:  I do
14:18.09Echo31init GPIO68,
14:18.09Echo31platform_add_device,
14:18.09Echo31mdelay(1200);
14:18.09Echo31platform_device_register(&athena_device_ide0);
14:26.28*** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34)
14:27.45*** join/#htc-linux marex (n=marex@thor.hackndev.com)
14:28.21cr2Echo31: does athena_device_ide0 support .probe, .init, .exit, .suspend, .resume functions ?
14:28.52cr2why should you put the power init before the platform_device_ register ?
14:29.27cr2registering device just creates some structures and calls already predefined functions.
14:30.31cr2druidu: still here ?
14:31.27Echo31cr2: I think   athena_device_ide0 supports .probe, .init, .exit, .suspend, .resume functions
14:34.23druiduyes
14:34.25druidufinally, it works
14:34.50druiduI ported all the raphael stuff to diamond (the lack of a battery driver was causing the shutdown anyway)
14:35.11druiduwhat is *really weird* is that I distinctly remember booting a certain android image yesterday
14:35.12rafyvittohey cr2
14:35.26druiduand that image had a touchscreen driver which reported the size of the touched area!!!
14:35.35druiduand with latest kernel this doesn't happen
14:35.43*** join/#htc-linux mrmoku|away (n=mrmoku@ppp-82-135-3-67.dynamic.mnet-online.de)
14:35.43rafyvittodid you guys ever heard about this http://forum.xda-developers.com/showthread.php?t=388273&highlight=linux
14:36.03rafyvittodual os on the htc typhoon linux/windows mobile
14:36.23druiduyeah, somebody mentioned it here yesterday :)
14:36.32rafyvittome
14:36.34rafyvittoxD
14:36.38druiduhehe
14:36.57rafyvittoanyways im out guys, gl to all and keep up the good work cheers to all of ya
14:37.01druiduit's not a priority anyway, it won't make phone or gprs magically work :)
14:37.07druidubye
14:37.23rafyvittoyeh but its an alternative to booting linux xD
14:37.27rafyvittoinstad of using haret
14:37.36rafyvittoinstead*
14:37.59druiducr2: ok, so the pointer location app from dev tools clearly and correctly showed touch area size
14:38.00*** join/#htc-linux Gnutoo (n=gnutoo@ABordeaux-152-1-40-189.w83-193.abo.wanadoo.fr)
14:39.06*** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes)
14:40.10Gnutoohi cr2
14:40.20Gnutoocr2, did you get my mail?
14:43.44cr2Gnutoo: yes.
14:44.03cr2Gnutoo: fyi, i don't write non-free software.
14:44.22Gnutoocr2, ok so what's the license
14:44.23Gnutoo?
14:44.30Gnutoobtw thatnks a lot and it's great
14:44.46cr2but since most of the code is taken from android source, it's apache license i guess.
14:44.54Gnutoook
14:44.59Gnutooapache is like BSD
14:45.10Gnutoo+ a close against patents agression
14:45.17cr2ok
14:45.36Gnutooso if it's apache you are free to make it proprietary that's why I mailed you
14:45.45Gnutoothe original is apache 2.0
14:45.52cr2lol
14:46.26xperiacr2: new stuff for the raphael microp wiki page
14:46.27Gnutooand unfortunately a source file without a license is proprietary by default
14:46.28xperiahttp://pastebin.com/m3299b929
14:46.32Gnutooso I needed your permission
14:47.15cr2gplv2+ is ok in my eyes, but as i've said, this code is mostly cut'n'paste
14:47.36Gnutoocr2, ok could you send it or pastebin to me a version with the apache header?
14:47.57Gnutoome too I prefer GPLv3
14:48.04Gnutoobut it realy depend on the goal
14:48.13Gnutooor Agplv3
14:48.34cr2ok. leave it apache2.0 and paste the license from android
14:48.39Gnutoook
14:48.41Gnutoothanks
14:57.54druiducr2: should the accelerometer work?
14:58.18druidu<PROTECTED>
14:58.36druiduI get some debug output but sensors don't update in android
15:04.22cr2druidu: it works as input device
15:04.32cr2druidu: od -x /dev/input/event*
15:13.48druiduwhat's the stuff about memory banks in board fixup?
15:13.55druidudiamond only has one memory bank?
15:15.50cr2128MB
15:16.08cr2there may be a 256MB diamond, i don't know
15:16.31cr2the sram parts may be reused too
15:16.35druiduRAM-capacity:  192 MiB
15:16.38druiduaccording to specs
15:17.00cr2but the g1 kernel prefers to use static allocation
15:17.12cr2192=64+128 ?
15:17.29cr2you have 64MB sram ?
15:17.34druiduah, I see touch pro has RAM:capacity:  288 MiB  (accessible: 201 MiB)
15:17.47cr2raph has 32+256=288
15:18.02cr2"accessible" is useless
15:18.28cr2but parts of sram and main sdram are used by arm9, and are protected by MPU
15:18.45cr2maybe we can disable this protection, i don't know
15:18.56druiduwell, maybe arm9 really needs`em
15:18.57cr2the spl in sram is protected, for example
15:19.00druiduit does run the AMSS
15:19.01cr2lol
15:19.11cr2yes, it's the amss ram
15:19.24druiduhow can I find out how big the ram module are?
15:19.28cr2are you sure that you have 64MB sram ?
15:19.28druiduWM doesn't show
15:19.31druiduonly that I have 192
15:19.35druidutotal
15:19.47druiduso it must be 2 modules, there's no 192 ram module
15:19.51cr2this info should be in the MFG section in nand
15:20.02druiduMFG?
15:20.13druiduhow can I access it?
15:20.20cr2192 means 64MB sram and 128MB sdram
15:20.34cr2in linux ?
15:20.40druidudunno, wherever
15:20.44cr2MFG is the manufacturer area
15:20.57druiduso which one is first?
15:21.01druidu64 or 128?
15:21.10cr2in linux you need a patched haret, to provide the partition table as on g1
15:21.20cr2sram is at 0x0
15:21.32cr2the sdram is at 0x10000000
15:21.49cr2if you have a second bank (like raph), then it's at 0x20000000
15:22.24cr2look at http://www.htc-linux.org/wiki/index.php?title=RaphaelMemoryMap
15:23.26druiduwhat I still don't get it is how it comes up with 89 for raphael
15:23.34druidu<PROTECTED>
15:26.25cr2See board-htcraphael.h
15:26.46*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
15:27.03cr2some ram is reserved by amss, and there is android static allocation
15:27.05druiduaaah, #define MSM_LINUX_SIZE          0x5900000 /* 89mb */
15:27.36cr2i guess we can get rid of the static allocation, at least for the non-android use
15:30.00cr2druidu: can you test BT ?
15:31.45druiduhmm, driver's active
15:31.47druidutell me how
15:34.24druidudmesg shows: HCI UART, HCI H4, HCI BCSP, HCILL, L2CAP, SCO, RFCOMM, BNEP
15:34.40druidubut it doesn't show that any device was detected
15:35.46cr2did you enable msm uart hs in .config ?
15:36.06*** join/#htc-linux slawson (n=kw@adsl-178-60-36.gnv.bellsouth.net)
15:36.22cr2the HCI* et al. is a higher level protocol
15:39.33druiduyeah, noticed
15:39.47druiduI added all the drivers to the board- file, gonna check config now
15:39.57druidubut don't know what happened that all my buttons are messed up
15:40.33druiduback and home don't work anymore :-s
15:41.21druidu(I configured the end call button to be the home button)
15:42.56slawsonmy back and home never worked :o
15:44.25cr2i'm not familiar with diamond
15:44.48cr2the only problem i have is the wrong keyboard leds
15:45.53slawsonYour radio works etc?
15:49.51druiduok, accelerometer works
15:50.16druiduhome worked (after configuring it in spare parts app)
15:50.22druiduand back too
15:50.32slawsonAmazing.
15:50.45*** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-167-109.ewe-ip-backbone.de)
15:50.46cr2slawson: gsm and umts work for me.
15:50.56slawsonah i am diam500
15:50.56druidubtw, when you mean gsm
15:51.05druiduyou can actually call or receive calls?
15:51.22cr2druidu: AT works (i.e. SMS too)
15:51.36druidubecause when I receive a call, it is automatically rejected (and the caller hears a busy signal, like when you push the hang up button)
15:51.39cr2druidu: but sice the ADSP does not work as expected, you don't have sound
15:51.47druiduand it shows up a missed call
15:52.04cr2android does not send ata
15:52.13druiduata?
15:52.15druidusms works too for me
15:52.17cr2you need some ril library
15:52.37cr2ata is ATA
15:52.41druidu[    6.150367] warning: `rild' uses 32-bit capabilities (legacy support in use)
15:52.42cr2answer the call
15:52.56cr264bit cpu ?
15:53.12druidudunno, this shows up right after booting android
15:53.24druiduin dmesg
15:55.32druidubtw, od /dev/input/event0 (navipad) shows total garbage... I keep pressing the upper left button and except one value that goes to 1 while it is pressed and 0 when it's not, all is garbage
15:57.22druiduah... I think I understand what it does
15:59.26*** part/#htc-linux ArteK (n=Artur@81.15.241.96)
16:01.01druiduSERIAL_MSM_HS
16:01.03druiduit was enabled
16:01.04druiducr2:
16:01.26cr2ttyHS1 in the dmesg ?
16:02.03druiduhmmm
16:02.07druiduyou disabled the clock
16:02.12druiduin clock-7x01a.c
16:02.16druiduclock-7x01a.c:  CLOCK("uartdm_clk",     UART2DM_CLK,    &msm_device_uart_dm2.dev, OFF),
16:02.38cr2it's ok
16:02.40druiduAug 30 18:33:05 (none) user.info kernel: [    1.686317] msm_serial_hs.1: ttyHS1 at MMIO 0xa0300000 (irq = 53) is a MSM HS UART
16:02.53cr2yes
16:02.57druiduAug 30 18:33:05 (none) user.info kernel: [    1.788062] msm_hsusb: functions bound. starting.
16:02.57druiduAug 30 18:33:05 (none) user.info kernel: [    1.796577] hsusb: IDLE -> ONLINE
16:02.57druiduAug 30 18:33:05 (none) user.info kernel: [    1.808295] hsusb: reset controller
16:03.13cr2it's usb
16:03.26cr2what does stty -F /dev/ttyHS1 say ?
16:03.45druidu# stty -F /dev/ttyHS1
16:03.45druiduspeed 9600 baud;
16:03.45druiduintr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O;
16:03.45druidumin = 1; time = 0;
16:03.45druidu-brkint -imaxbel
16:04.00cr2ok
16:04.04cr2enable power
16:04.21cr2in /sys/class/rfkill/*
16:04.21druidudon't know BT commands :D
16:04.26cr2not bt
16:04.42druiduok
16:04.42druiduwait
16:04.45cr2it's just a serial port
16:04.57cr2no BT commands
16:05.03druiduecho 1 > /sys/class/rfkill/rfkill0/power/wakeup ?
16:05.15druiduno, wait
16:05.31cr2<PROTECTED>
16:05.38druiduyeah, rfkill0 is brf6300 which sounds like BT
16:05.51druidu[ 1954.767158]    bluetooth rfkill state ON
16:06.00druiduand some clock messages
16:06.12cr2call stty again. and get the hard lock ;)
16:06.36druiduLOL
16:06.43druidunow I see what you mean by hard lock
16:06.44druidu=)
16:06.53cr2yes, it's my status for today
16:06.55druidugood sign right? :)
16:06.58cr2must be some DMA problem.
16:07.37cr2g1 kernel put uart2dm tx on channel 10
16:07.42druiduproblem is we get absolutely no console feedback
16:07.49cr2which is already used by usb = braindead
16:07.51druiduI could try to do that while having the tty win open
16:07.55druidumaybe something shows up?
16:08.04cr2but i've changed it to 9
16:08.16cr2wince uses channel 8
16:08.24cr2but we use 8 for SD dma
16:08.33cr2wince does not support SD dma
16:08.35cr2btw
16:08.36druidutest-root/init.rc:service hfag /system/bin/sdptool add --channel=10 HFAG
16:08.36druidutest-root/init.rc:service hsag /system/bin/sdptool add --channel=11 HSAG
16:08.42druiduin init.rc
16:08.44druidusome daemon
16:09.26druidunot sure what's with that...
16:09.26cr2we need to make uart rx/tx work first
16:09.26cr2before talking about any BT-related things
16:09.30cr2another difference to g1 is the clock setup
16:09.37druiduso bluetooth is basicly standard +AT commands? :)
16:09.58cr2androids use 4X clock speed. probably to avoid the bps < 1500
16:10.35cr2BT is a protocol stack used over (RF) uart (usually)
16:11.14cr2btw, can you run with SD dma on channel 9 ?
16:11.33druiduhmm, dunno lemme see
16:11.39cr2we don't know the DMA constoller capabilities, because there are no CPU docs
16:12.21druidu#define DMOV_USB_CHAN         11
16:12.30druiduwe have cpu docs
16:12.31cr2#define DMOV_SDC1_CHAN        8
16:12.37druidu#define DMOV_SDC1_CHAN        8
16:12.48druidu#define DMOV_HSUART2_TX_CHAN   4        // =1 in wince ??
16:12.50cr2#define DMOV_HSUART2_RX_CHAN   9        // wince value, does not clash with USB
16:12.51druidu#define DMOV_HSUART2_RX_CHAN   9        // wince value, does not clash with USB
16:12.56cr2yes, i've mixed the numbers
16:13.20cr2can you exchange DMOV_SDC1_CHAN         and DMOV_HSUART2_RX_CHAN   ?
16:13.23druidudid you get any console after crash? any msg at all?
16:13.37druiduI can try to see if there's any message with the console active
16:13.45cr2nothing. the machine is locked, no irq processing anymore
16:14.10druiduI was hoping that a message would show before that
16:15.07druiduwhat is _CRCI?
16:15.29cr2the easiest thing to test is SD on DMA9
16:15.40cr2then we can put UART2DM on DMA8 and will have more or less the wince setup
16:16.03cr2it's some throttling mechanism for DMA
16:16.16druiduah, so we don't need to mess with it
16:16.16cr2forget about it for now.
16:17.24cr2echange 8 and 9 and try to boot
16:18.09cr2another thing to try is reducing the uart2dm clock by 4 times, so we will have wince setup there too.
16:21.10*** join/#htc-linux Dunedan (n=dunedan@phoenitydawn.de)
16:30.11druidubtw, except audio routing for gsm, would playing sound work?
16:31.48*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
16:32.14cr2no
16:32.22cr2at least not for me
16:33.00cr2try it. i got some rpc messages with playwav2 and then it locked too
16:37.44druiduwhat's the audio device?
16:37.58druiducat /dev/random > /dev/sound or whatever might also be good to test :))
16:42.36*** join/#htc-linux phh (n=quassel@lns-bzn-50f-81-56-224-142.adsl.proxad.net)
16:44.06druiduwhat's the major/minor for ttyHS1 ?
16:50.33cr2<PROTECTED>
16:50.50cr2drivers/serial/msm*hs.c
16:53.41druidusame
16:54.01druidu(neah, I was trying without android booted up and had to look up the device in /sys/devices)
16:54.48cr2same ?
16:55.05cr2does the SD work with dma9 ? can you post the dmesg ?
17:02.41druiduLOL
17:02.45druiduI have debug output!!!
17:02.49druidufrom the console
17:03.10druidupc_clk_set_rate: id=35 rate=7372800
17:03.44druiduset mdns: 35, 7372800; bitidx=26 offset=dc, ns=0
17:03.51druiduLOOOL
17:03.56druidujust got a stacktrace
17:04.49druiduuart_open => uart_startup => msm_hs_startup => request_irq => setup_irq + 0x0/0x2ac
17:05.07druidurequest_irq+0x94/0xbc
17:06.30druiduhmm, there's also some backtrace before that, looks like inside the hrtimer_interrupt
17:13.33cr2yes, it's a problem in irq processing
17:13.45cr2i think it all starts with some DMA timeout
17:14.41druiduweird thing is that it was hung but only apparently
17:14.52druiduafter like 1 minute, the screen refreshed and I could see the backtrace
17:15.08druiduthey request 2 irqs, one if wakeup is enabled
17:17.18druidualso, having BT enabled before booting kernel doesn't help
17:19.42cr2i don't really know how to debug the dma
17:22.50marexcr2: use a scope ... there's no other way
17:23.07marexcr2: or possibly jtag and trace memory accesses ... but that's all you can do about dma
17:27.57cr2ok, i must leave now.
17:27.58cr2bbl
17:28.57druidutried outputting stuff directly to /dev/msm_pcm_out but get somethink like [   99.780616] audio_disable() in dmesg and no sound
17:28.59druiduok, later
17:30.50druidubtw, just enabling the device causes msm_hs_startup to request two irqs: 53 and 85, and no crash yet
17:32.10druidubtw, back and home buttons magically work again...
17:33.11*** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net)
17:44.38*** join/#htc-linux slawson (n=nnscript@adsl-178-60-36.gnv.bellsouth.net)
17:48.00slawsonDoes the cdma radio work yet?
17:51.32*** join/#htc-linux mblancom (n=mblancom@193.Red-79-149-207.staticIP.rima-tde.net)
17:52.36druidudunno, I have a gsm one
17:53.14druidubtw, back and home now magically work again
17:53.44druidu(home as in the end call button, configured in spare parts app)
17:54.13slawsonHmm.
17:54.22slawsonAre you the only one working on this project?
17:55.55*** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net)
17:56.40slawsonyeah cdma radio doesn't work
17:57.59druidufor diamond I could be the only one, but code is 99% identical to raphael
17:59.38slawsonYou said that accelerometer works?
17:59.40slawsonwhat build
18:01.04druiduworks but not in android
18:01.27druiduI'm compiling from sources, latest git version with a few mods
18:01.41druidumostly porting all the raphael board code to the diamond board
18:01.47druiduI'll post some patches after I test some more
18:01.56slawsonOkay awesome
18:02.00slawsonGreatly appreciate it
18:02.08slawsonif i had a linux box i would be compiling
18:04.04druiduanyway, you can test accelerometer by doing (after booting the kernel from cmd line or via telnet): od /dev/input/event3
18:06.35*** join/#htc-linux ArteK (n=Artur@81.15.241.96)
18:13.29*** join/#htc-linux MrPippy (n=pip@75.37.163.177)
18:38.12*** part/#htc-linux mblancom (n=mblancom@193.Red-79-149-207.staticIP.rima-tde.net)
18:42.19*** join/#htc-linux phh (n=quassel@2a01:e35:2e4b:b2b0:250:8dff:fee1:c793)
18:43.05*** join/#htc-linux Amaranth (n=travis@ubuntu/member/Amaranth)
18:54.55*** join/#htc-linux Bally3_ (n=Bally3@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
18:55.08Bally3_http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
18:55.17Bally3_you mean this?
18:56.16*** join/#htc-linux Bally3__ (n=Bally3@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
18:58.18xperiaBally3_ the source that druidu is working are here
18:58.20xperiahttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=tree;h=refs/heads/htc-msm-2.6.27;hb=refs/heads/htc-msm-2.6.27
18:58.21xperiathe board files you can find in arch/arm/mach-msm
18:58.23xperiaHe use the raph boardfile with new changes
18:58.54druiduyep
18:59.26druiduexcept the keypad there are very few differences between raphael and diamond
19:00.14druidulol, actually he just left
19:00.34*** join/#htc-linux fon (n=fon@5ac08d96.bb.sky.com)
19:00.47druiduhm, or not
19:03.44Bally3thanks xperia  :)
19:06.07Bally3sorry.. was tryng to use linux in a vm..  :S
19:08.58Bally3I take it this is for the hermes port?
19:09.52druidunot really, diamond/raphael :)
19:10.41Bally3oh
19:10.47Bally3:S
19:11.08Bally3I donthave a damond or a raphael tho
19:12.05Bally3actually snce I got you two here with raoh and diamoind.. can you tell me if these listed are software?
19:12.41Bally3http://www.htc-linux.org/wiki/index.php?title=Raphael_IRQ
19:13.42Bally3I'm trying to find the wifi irq for polaris.. we know the kaiser one is "93" ...used haretconsole to watch gpios.. now lost
19:14.30*** join/#htc-linux darkstone (n=LOL@78-86-59-180.zone2.bethere.co.uk)
19:16.44*** join/#htc-linux pH5 (n=ph5@g229065192.adsl.alicedsl.de)
19:18.30Bally3xperia: sorry for the confusion mate..I pasted that link in the wrong room.. now I understand what you were talking about lol
19:30.34*** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net)
19:32.34*** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net)
19:33.43*** join/#htc-linux luc_ (n=luc@89.115.128.35)
19:35.51*** join/#htc-linux Bally3 (n=Bally3@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
19:43.26*** join/#htc-linux toi (n=toi@d54C2AAB7.access.telenet.be)
19:44.22*** join/#htc-linux ogr3_ (n=ogr3@adsl-99-62-2-195.dsl.lsan03.sbcglobal.net)
19:49.09*** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz)
19:53.44*** join/#htc-linux pH5 (n=ph5@g229239070.adsl.alicedsl.de)
20:00.11*** join/#htc-linux glyph` (n=glyph@c-76-24-223-175.hsd1.ma.comcast.net)
20:00.12*** join/#htc-linux marajin (n=marajin@87-194-102-189.bethere.co.uk) [NETSPLIT VICTIM]
20:00.15*** join/#htc-linux mrb__ (n=mrb@160.89-10-30.nextgentel.com) [NETSPLIT VICTIM]
20:00.15*** join/#htc-linux maejrep (n=madCoder@68.64.144.211) [NETSPLIT VICTIM]
20:00.15*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) [NETSPLIT VICTIM]
20:10.51*** join/#htc-linux leaigor (n=laigor@188.134.36.14)
20:14.39*** join/#htc-linux x_coRe_x (i=coRe@95-37-233-84.dynamic.mts-nn.ru)
20:28.08*** join/#htc-linux mallochigh1 (n=Administ@cpe-173-169-235-155.tampabay.res.rr.com)
20:38.37*** join/#htc-linux mblancom (n=mblancom@193.Red-79-149-207.staticIP.rima-tde.net)
20:42.12*** join/#htc-linux x29a (n=x29a@unaffiliated/x29a)
21:01.22*** part/#htc-linux ArteK (n=Artur@81.15.241.96)
21:02.13*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
21:13.26*** part/#htc-linux fon (n=fon@5ac08d96.bb.sky.com)
21:40.32*** join/#htc-linux cr2 (n=cr2@ip-77-25-251-112.web.vodafone.de)
21:42.43*** join/#htc-linux cr2 (n=cr2@ip-77-25-251-112.web.vodafone.de)
21:43.08*** join/#htc-linux eway (n=ellis@78-86-162-166.zone2.bethere.co.uk)
21:45.32druiducr2:
21:45.34druiduI have news :)
21:45.44druiduI know what's happening to the bt driver
21:45.53cr2ok
21:46.10cr2the log is not available again
21:46.32cr2tell me
21:46.43druiduI didn't say anything on the channel anyway
21:46.43druiduso
21:46.54druiduin the moment the irq is requested
21:46.57druidu58
21:47.02druiduI think
21:47.16druiduit starts to fire constantly, like a few times / second
21:47.37cr2it's not that mich
21:47.50druiduand msm_hs_isr is called all the time
21:47.50cr2s/mi/mu/
21:47.53druidu<PROTECTED>
21:47.57druiduthis returns 0 all the time
21:48.31druiduwell bottom line is that the request_irq doesn't return
21:48.40druiduit hasn't got time... the irq keeps firing
21:48.55druiduI used printk before and after it
21:49.00cr2hmm. but g1 must have the same problem ?
21:49.03druiduand a printk in the _isr
21:49.17druiduit's true that I bias the results by adding a printk in the _isr, but the isr_status is always 0
21:49.24druiduso something's wrong
21:49.30cr2are there any 2.6.29 changes ?
21:49.32druiduthe isr is firing and we don't clear it
21:49.40druiduI'm gonna port the changes now
21:49.46cr2UARTDM_MISR_ADDR is ok. uport ?
21:49.53cr2great.
21:53.14druidudunno
21:53.22druiduuport is the _isr handler param
21:53.35druidushould be ok, it's a ptr to a structure
21:54.09druiduuport->irq is 53
21:54.59druidu#define INT_ARM11_DMA        (32 + 11)
21:55.01druiduhmmm
21:55.21druiduit is the dma :))
21:55.39druiduand because reading that port returns 0, the _isr doesn't do anything so the irq keeps firing?
21:56.07*** join/#htc-linux cr2_ (n=cr2@ip-77-25-43-175.web.vodafone.de)
21:56.51*** join/#htc-linux pH5 (n=ph5@g229239070.adsl.alicedsl.de)
21:57.39druiduactually, I just realized... if irq 53 is the dma one, it keeps firing because MDP used DMA right?
21:57.44druidu*uses
22:00.56druiduok, forget what I just said, it seems I have trouble adding numbers
22:00.56druidu#define INT_UART2DM_RX       (32 + 20)
22:00.57druidu#define INT_UART2DM_IRQ      (32 + 21)
22:01.03druiduthese are the uart2dm irqs
22:01.11druiduto irq 53 keeps firing
22:01.53*** join/#htc-linux stickboy (n=anonymou@128.153.211.112)
22:02.59Bally3druidu: can you tell me where to find the irq for wifi in the kernel source please so i can change it?
22:03.13cr2_it#s ok, in haret you can see a lot of them
22:03.24druiduall IRQs should be in arch/arm/mach-msm/include/mach/irqs.h
22:03.26cr2_but only because the .bts is loaded.
22:03.37Bally3thanks mate :)
22:03.44druidunp
22:03.45druiduhmm... but still, request_irq does not return
22:03.54druiduso the device doesn't actually lock
22:04.01druiduit's just overloaded
22:04.16druiduirq processing eats up all the cpu
22:05.45druiduBally3: actually, I'm not sure which one of those is the wifi irq
22:07.10Bally3I got a long print out from haret console ..after turning off and on wifi in winmo.. and saw where it spiked.. but dont know how to get the irq from that
22:07.48druidubut which one is the wifi driver anyway?
22:07.58druiduI don't see it anywhere around there
22:07.58Bally3wlan.ko
22:08.09Bally3oh
22:08.25druidubtw http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=d7fd4ed7de626c07d253d28ee194c89f3a593133
22:08.31druiduaaa, it's a separate module
22:08.34druiduright
22:09.34*** join/#htc-linux x29a (n=x29a@unaffiliated/x29a)
22:09.39druiduCSR unifi-105x WiFi device
22:09.45druiduor CSR unifi-60xx WiFi device
22:09.45druidu?
22:09.58Bally3you see that?
22:10.30druiduthat what?
22:10.30druiduhttp://android.git.kernel.org/?p=platform/vendor/csr/unifi-105x.git;a=tree;f=unifi_hostsw_linux_147;h=feba699ef19feafea13319b582c032ead2816f9c;hb=HEAD
22:11.05Bally3sorry where did you see the above?
22:15.47druidudunno, found it in the android projects
22:15.52druidubut I don't think it's that one...
22:16.04druidumight be the tools & stuff, but not the driver itself
22:17.48cr2_/* Read Only register */
22:17.49cr2_#define UARTDM_MISR_ADDR 0x10
22:18.10Bally3dont think it is either druidu
22:18.14Bally3never heard of it :S
22:18.51Bally3the kaiser and the polaris share the same firmware and driver except irq's are different as the kaiser has a keyboard.. the kaisers irq for wifi is "93"
22:20.13cr2_#define UARTDM_ISR_ADDR 0x14
22:20.20Bally3I now have the enviable task of trying to figure out and try he Polaris irq :S
22:25.24cr2_druidu: i don't understand how it can't return
22:26.12cr2_if isr_status == 0 it will just fall through
22:26.37druiduyeah
22:26.43druidubut then it fires again
22:26.46druiduand again
22:26.55druiduit's eating up all the cpu
22:27.02cr2_ok
22:27.06druiduand the _isr just returns _HANDLED
22:27.25druidubut it doesn't handle the condition that generated the irq in the first place
22:27.52druiduif it's an irq that's saying you can send data now, it's gonna keep firing (since we didn't disable it nor told it not to notify us of that)
22:28.26druiduone thing I'm not 100% sure if for first irq request it returns 0 too
22:28.30druiduit was too fast to see
22:29.14cr2_but why is the _isr=0 in the first place ??
22:29.27druiduisr_status
22:29.32cr2_i think at the beginning there was some dma error messages
22:29.36cr2_yes
22:29.49cr2_i need to grep through my logs
22:30.43cr2_<PROTECTED>
22:30.56cr2_is it trigger_high in wince ?
22:31.04druidudon't know...
22:31.18druiduI'm testing with latest upstream 2.6.27 now
22:31.36cr2_haret does not parse the gpio irq config i think
22:31.51cr2_you may change HIGH to re/fe maybe
22:32.39druiduit's irrelevant on the trigger I guess... the fact is something does change
22:32.44druiduand we don't handle it
22:32.53druidulet's try to make it work with not irq
22:32.55druidubusy waiting :)
22:33.14druidujust let it read and write from the port, raw mode
22:34.43tmztsl: what device? diam cdma?
22:35.00druiduwohooo, bootez with latest changes
22:35.06cr2_the trigger HIGH is strange anyway.
22:35.09druidudiam gsm
22:44.03tmzt13:37 < druidu> [    6.150367] warning: `rild' uses 32-bit capabilities (legacy support in use)
22:44.38tmztno, linux capabilities
22:44.44tmztsecuroty thing
22:53.10druiduI didn't understand that warning
22:53.17druiduit *is* a 32 bit system
22:53.20druiduwhy legacy support?
22:53.36druidu32bits capabilities vs what
22:53.37druidu?
23:08.44*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
23:11.18*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
23:13.39cr2_druidu: i still don't understand why is it triggered high
23:13.52cr2_maybe try "rising" ?
23:14.32druidulet's look at it this way... g1 uses same chip and the driver works, so well maybe our problem is with something else
23:14.43druiduhmmm
23:14.55druiduactually I see what you mean
23:14.58cr2_this is something to be compared with wince too
23:15.27tmzton the caps tjing, it's just a syscall with a 32bit field
23:15.37cr2_ok
23:15.51tmztwhich has changed to a 64bit fields to support more caps
23:16.22tmzt20:15 < tmzt> sl: what device? diam cdma?
23:16.30tmztI meant slawson:
23:17.29cr2_i think wince irqs are configured with a kioctl. and the parameter meaning is not known to me.
23:17.42cr2_but we can still compare with the other irqs
23:17.59*** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-167-109.ewe-ip-backbone.de)
23:18.41tmzt20:57 < cr2_> i think wince irqs are configured with a kioctl. and the parameter meaning is not known to me.
23:18.42*** join/#htc-linux marajin_ (n=marajin@87-194-102-189.bethere.co.uk)
23:19.26cr2_#define VIC_INT_TYPE1       VIC_REG(0x0044)  /* 1: EDGE, 0: LEVEL  */
23:19.31cr2_#define VIC_INT_POLARITY1   VIC_REG(0x0054)  /* 1: NEG, 0: POS */
23:19.51cr2_druidu: maybe dump these regs with bt enabled ?
23:20.17*** join/#htc-linux Tinyboom_ (n=nahh@41.80-202-154.nextgentel.com)
23:20.20*** join/#htc-linux mrb (n=mrb@160.89-10-30.nextgentel.com)
23:22.08cr2_#define MSM_VIC_PHYS          0xC0000000
23:22.27cr2_pd 0xc0000044 4
23:22.37cr2_<PROTECTED>
23:22.50*** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34)
23:23.10cr2_#define INT_UART2DM_RX       (32 + 20)
23:23.11cr2_#define INT_UART2DM_IRQ      (32 + 21)
23:23.22druiduyeah, I know
23:23.25druidu2nd one is 53
23:23.57cr2_20 and 21 bit
23:24.39druiduwhat does VIC stand for?
23:25.23ali1234something interrupt controller
23:25.30cr2_vector
23:25.36druiduah
23:25.41druiduI knew that :D
23:26.09cr2_druidu: dump the regs
23:26.49tmztvectored
23:27.03tmztsame as we would on pxa, cool
23:27.12tmztno tracing ce calls
23:35.51druidujust a moment
23:37.34druiduwith BT off
23:37.35druiduHaRET(2)# pd 0xc0000044 4
23:37.35druiduc0000044 | 0010003c                            | <...
23:37.35druiduHaRET(3)# pd 0xc0000054 4
23:37.35druiduc0000054 | 00000000                            | ....
23:38.07cr2_polarity is pos
23:38.28cr2_0,4,8,12,16,20,24,28
23:38.30druiduHaRET(9)# pd 0xc0000044 4
23:38.30druiduc0000044 | 0010003c                            | <...
23:38.30druiduHaRET(10)# pd 0xc0000054 4
23:38.30druiduc0000054 | 00000000                            | ....
23:38.33druiduBT on -- same
23:38.45tmztwhat happens if you change it in ce?
23:38.57tmztshouldn't it lockup?
23:39.03druidudunno
23:39.06cr2_20 is EDGE, 21 is level
23:39.33cr2_#define INT_UART2DM_RX       (32 + 20) <- edge
23:39.49cr2_#define INT_UART2DM_IRQ      (32 + 21) <- level
23:39.56cr2_which one do we have ?
23:40.30cr2_20 is rising, 21 is high
23:41.32druidubit 20 is 1, 21 is 0
23:41.53druidutrue
23:47.57druiduweeeeee, wince dmesg really rulez
23:48.50druiduI just can't find a logical explanation for the reason why microsoft made firmware with all that debug info, and shipped dlls compiled with debug info
23:49.47tmztthey didn't?
23:49.52cr2_it's htc, not m$
23:51.29druiduwell, don't know about this abut mine, but xperia sent me some dlls and they had debug info in them
23:52.06druidus/this abut //g
23:52.26druiduyeah, true
23:52.33druiduhtc actually released some sources
23:53.26druidudeveloper.htc.com - android kernel sources for dream and magic

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