IRC log for #htc-linux on 20081212

00:00.44rolkpdev->id seems to be 1,2,3 or 4 in all legal cases.
00:01.03rolkAnd msmsdcc_pclks is defined as { NULL, "sdc1_pclk", "sdc2_pclk", "sdc3_pclk",
00:01.03rolk<PROTECTED>
00:01.15dwaradzynrolk: which line is it in msm_sdcc.c? (cant find pc_clk string in file)
00:01.19dzopclk is the peripheral bus clock and I don't think we have control of that, i think i just commented out the code that set it, i'll just check
00:01.24dcordesdwaradzyn, how would a function look that only runs msm_update_screen when kaiser cam button is pressed?
00:01.32rolkSo, for all legal cases, the clocks are identified as  "sdc1_pclk", "sdc2_pclk", "sdc3_pclk",
00:01.32rolk<PROTECTED>
00:01.36dcordesdwaradzyn, do I use the keypad driver or use the gpio directly?
00:02.22dcordesrolk, do you know which code dzo uses on the vogue?
00:02.33dcordesit's the htc-voge branch on ltg
00:03.23dzomy pc_clk_get_rate looks like: static unsigned pc_clk_get_rate(unsigned id)
00:03.25dzo{
00:03.25dcordesxperia usb woks.
00:03.26dzo<PROTECTED>
00:03.28dzo<PROTECTED>
00:03.29dzo<PROTECTED>
00:03.31dzo<PROTECTED>
00:03.32dzo<PROTECTED>
00:03.35dzo<PROTECTED>
00:03.35dzo}
00:04.01*** join/#htc-linux Shinto (n=John@g227183018.adsl.alicedsl.de)
00:04.28rolkThe pc_clk_get_rate is somewhat similar:
00:04.29rolkstatic unsigned pc_clk_get_rate(unsigned id)
00:04.30rolk{
00:04.30rolkif(id==SDC1_CLK)
00:04.30rolkreturn get_sdcc_host_clock(SDC1_CLK);
00:04.30rolkif(id==SDC1_PCLK)
00:04.31rolkreturn get_sdcc_host_clock(SDC1_PCLK);
00:04.33rolkif(id==SDC2_CLK)
00:04.39rolkreturn get_sdcc_host_clock(SDC2_CLK);
00:04.41rolkif(id==SDC2_PCLK)
00:04.42rolkreturn get_sdcc_host_clock(SDC2_PCLK);
00:04.43rolkprintk("Unknown clock!\n");
00:04.45rolkreturn -EINVAL;
00:04.47rolk}
00:05.10rolkBut the mmc driver gets an -EINVAL back, so it must be the case that the id it provides is not equal to any of the listed CLKs.
00:05.56dzoor it could be the return value from get_sdcc_host_clock
00:08.06rolkYes, true.
00:08.53rolkunsigned int get_sdcc_host_clock(unsigned id) {
00:08.53rolkint n;
00:08.53rolkint index;
00:08.53rolkunsigned val0;
00:08.54rolkunsigned val1;
00:08.54rolkif(sdcc_host_clock!=0)
00:08.56rolkreturn sdcc_host_clock;
00:08.58rolkindex=clock_to_index(id);
00:09.00rolkval0=readl(MSM_CLK_CTL_BASE + sd_clock_regs[index].offset);
00:09.02rolkval1=readl(MSM_CLK_CTL_BASE + sd_clock_regs[index].offset+4);
00:09.04rolk
00:09.06rolkfor(n=0;n<ARRAY_SIZE(sd_clock_parameters);n++)
00:09.10rolkif (sd_clock_parameters[index][n].val0==val0 &&
00:09.12rolk<PROTECTED>
00:09.14rolk<PROTECTED>
00:09.17rolk}
00:09.19rolkreturn -EINVAL;
00:09.25rolk}
00:09.47*** join/#htc-linux camden (n=camden@136-9-178-69.static.gci.net)
00:10.05camdenhello
00:10.44rolkCould it be that the id is actually SDC3_CLK or SDC4_CLK, and then int clock_to_index(unsigned id)
00:10.44rolk{
00:10.44rolk<PROTECTED>
00:10.44rolk<PROTECTED>
00:10.44rolk<PROTECTED>
00:10.44rolk<PROTECTED>
00:10.46rolk<PROTECTED>
00:10.48rolk}
00:10.52dzoi see, clock to index returns 0 for an id of SDC1_PCLK
00:11.40rolkI should put some more diagnostics there. But its 1:11 now, and I need to work tomorrow.
00:11.45dzosince we can't get or set the PCLK, try just returning 66MHz
00:11.57rolkWhat is your timezone dzo?
00:12.43dcordesalso late here. good night
00:12.57Bally3night dcordes
00:13.30dwaradzyndcordes: see you today :)
00:13.59Bally3so what do you think we need to do then dzo? are we on the right track you think?
00:14.20rolkI've patched the pc_get_clk_rate function.
00:14.23*** join/#htc-linux kuhlivisj (n=kuhlivis@s5592d82c.adsl.wanadoo.nl)
00:14.25dzoits 1.15 pm on friday in NZ, we're always ahead of the world!!
00:14.35Bally3lol
00:14.38rolkI will create one more image and then I'm off to sleep.
00:14.56Bally3nice one rolk :)
00:15.02dzook, got to work now, bye.
00:15.16imfloflonight guys goo dwork
00:15.19Bally3whens the best time to catch you dzo?
00:15.30imfloflooh dzo is here
00:15.32Bally3would you come back here tomorrow?
00:15.35imflofloso i have a question
00:15.49Bally3please....
00:15.51dzoemail me is best but i'm going away for 2 weeks on sunday.
00:15.52imfloflois it possible to tell us how we can do with the Sd issue ? to test  it
00:16.13imfloflowhich files?
00:16.13Bally3flo: rolk and dzo discussed it already
00:16.15Bally3:P
00:16.33imfloflook i had too drunk so :-#
00:16.36dzojust trial and error and lots of thinking is usually the best way forward....
00:16.44Bally3thanks dzo.. would love to see some progress before you disappear on sunday
00:16.47imfloflowaiting report on polaris trhead
00:16.54imfloflogn all
00:16.59Bally3night flo
00:17.10rolkSo, booting....
00:17.20Bally3but you think rolk is on the right track?
00:17.22imfloflothks
00:17.43Bally3the sd card has stunped everyone here..
00:17.45dzoi'll still check my mail when i'm away but won't be able to do much devel. looks like you are getting on top of it anyway.
00:18.13Bally3it would be nice to think so.. from what I get told this has been ongoing for months
00:18.43Bally3if we get sd card boot then everyone else can get involved.. finally :)
00:18.56dzoone more idea: have you tried smaller values for the block size and max block count.
00:19.21Bally3you mentioned this in your pm.. but it stumped most of everyone..
00:19.29rolkWell, this certainly is part of the story, but not quite the grail yet. The PCLK value is now 66000000, as patched but still the MMC times out.
00:19.33Bally3is that in the config file or the default,txt?
00:19.41dwaradzyni'm not sure it is the right track, mine sd also shows 4294967274 hz, but it basically works. if it were that big error the symptom should be that it does not work at all
00:20.19dzowhen does it time out, on the initial detect or when transferring data?
00:20.24Bally3what about the block size and max block count dwaradzyn?
00:20.27rolkinitial detect
00:20.37dwaradzyndzo: i played with blocksize and it did not solve anything, but when i tested it i noticed that smaller blocksize will get better stability
00:20.39dwaradzynslightly betther but noticable one
00:20.56dzothe initial detect doesn't even use dma and it is supposed to time out on some of the requests.
00:21.18rolkYes, 3 or so.
00:21.22dwaradzyndzo: it gets several timeouts during init
00:21.28rolkBut not 10 in a row.
00:21.57dwaradzyni have only seen 3 and 4 timeouts during tests
00:22.19Bally3so whats causing the instability?
00:22.45rolkGuys. Its goodnight to you all. I'm off to sleep. I'll try to make some time available for this this weekend.
00:23.08Bally3goodnight rolk... thanks for the efforts mate :)
00:23.16dwaradzynrolk: count me in. i'll be here tomorrow about the same time as today
00:23.57Bally3dzo.. did you have any instability issues when you were doing this?
00:24.59dzoyes, lots... have you got  mdelay(250); in mmc_sd_init_card ? (in drivers/mmc/core/sd.c)
00:25.37Bally3it seems the card is detected but its not stable enough..  where can I change the blocksize and max block count? (sorry not so techical as these guys.,. but good at project managing) :)
00:25.59Bally3dwaradzyn:?
00:26.17dwaradzynBally3: about the block size and max blocks - these are constants defined in kernel source, i just played with different values (but only on blocksize) and it was not a answer to sd issue
00:26.37dwaradzyndzo: we have mdelay(250) with comment from san there
00:26.56dcordestmzt_, thought I should notify you about dwaradzyn having found a way to make msm_fb work with X
00:27.43dzoin msmsdcc_probe,  mmc->max_blk_size= 512; and  mmc->max_blk_count = 127; try smaller numbers.
00:27.44Bally3did you get the kaiser then dzo?
00:28.06dzoit's on it's way but will arrive when i'm away
00:28.14Bally3doh!
00:29.08Bally3pity there isnt another way to get you what you need to help us
00:29.26dzook, i've really got to go now.... bye all.
00:29.47dwaradzyndzo: bye, and happy holidays our hero :)
00:29.48Bally3thanks for all your help dzo :)
00:30.34Bally3and thats all she wrote.. as they say in the states :P
00:30.36Bally3what do you think dwaradzyn?
00:30.45Bally3do we have any more to go on?
00:31.19Bally3I think you and rolk need to pair up...  you seem to be the most head up on this
00:31.42Bally3I'll get others involved.. bring them on here
00:32.17Bally3I think the sd card issue will get fixed .. I'm confident of it.. damn if it wasnt for compiling I'd be at it right now :P
00:32.38dwaradzynBally3: we do not have concrete things, but this timing thing (pc_clk_get_rate) will be worth checking
00:32.43Bally3but I need to get a decent linux environment set up first
00:33.21dwaradzynBally3: i can get you mine - it has everything there, and it is vmware image (about 5gb)
00:33.33Bally3no we dont.. but this is the second outing with dzo and he is still pointing to timing and block sizes.. if that isnt it then we'll need a complete change of direction
00:33.42Bally3GREAT
00:33.47Bally3how do I ge tit?
00:34.25dwaradzyni was thinking about posting it on rapidshare and putting links on xda
00:34.37Bally3I need to learn linux anyway.. what I do know should be enough to get me started..
00:35.15Bally3that would be a great idea.. I'll post it on the first page along with the files we're working with.. and tell everyone who wants to get involved to use the same setup/files
00:35.26dwaradzynlets put it that way - you can be beta tester, before releasing it on xda
00:35.32dwaradzynlets go prv on details
00:35.37Bally3there are lots of people eager to get involved.. they just dont know where to start
00:35.44Bally3ok
00:40.56tmzt_dcordes: hey, is everything moving to goog 2.6.27 and trout? do we know how to make that kernel/board work with minimal changes?
00:41.59tmzt_cr2: if you are still here, if you have any information on asic3_mmc so we can get a working kernel for BA over the next few weeks??, can you paste it here
00:43.55*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
00:46.59*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
00:49.38*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
00:54.13*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
00:54.37Bally3night all
00:58.24*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:03.16*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:08.29*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:11.42*** join/#htc-linux axe_hm (n=weechat@217.116.62.236)
01:14.11*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:18.37*** join/#htc-linux Tinyboom (n=nahh@178.80-202-153.nextgentel.com)
01:21.21*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:27.14*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:30.55*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:34.24*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:37.29*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:41.00*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:44.08*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:46.26infernixxjust fyi
01:46.42infernixxswetland mentioned that they got PIO working first for SD
01:46.55infernixxand it took quite some time after that to get DMA working
01:47.46infernixxim not up to speed on kaiser sd development but i hope PIO is the main focus
01:47.57infernixxsince DMA is apparently a PITA on msm7k
01:50.58*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:54.17*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
01:57.23*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
02:00.44*** join/#htc-linux kring (n=kring@211.155.128.98)
02:00.46*** join/#htc-linux ilovethisplace (n=ilovethi@152.sub-70-198-251.myvzw.com)
02:04.21*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
03:06.27*** join/#htc-linux apt_ (i=ibot@rikers.org)
03:06.27*** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup.
03:17.03*** join/#htc-linux axe|hm (n=weechat@217.116.62.236)
03:18.44*** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1)
03:25.54*** join/#htc-linux paulproteus (n=paulprot@2002:db69:2513:0:0:0:0:1)
03:25.54*** join/#htc-linux Tinyboom (n=nahh@178.80-202-153.nextgentel.com) [NETSPLIT VICTIM]
03:25.54*** join/#htc-linux swetland (n=swetland@nat/google/x-ac2328226c12fbc1)
03:25.55*** join/#htc-linux Poohba (n=poohba@c-71-58-20-66.hsd1.nj.comcast.net) [NETSPLIT VICTIM]
03:25.55*** join/#htc-linux nizox (n=none@2a01:e35:8a13:a2b0:21c:c0ff:fe25:ff68) [NETSPLIT VICTIM]
03:25.55*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net)
03:36.35*** join/#htc-linux axe|hm (n=weechat@217.116.62.236)
03:42.32*** join/#htc-linux apt (n=ibot@rikers.org)
03:42.32*** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup.
05:13.46tmzt_NetRipper: hello? are you in #android?
05:13.55tmzt_hello,
05:38.05*** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no)
05:43.59maejrep<NetRipper>     maejrep, can you pastebin your default.txt used for haret?   <-- http://privatepaste.com/1bXeGkIukx
05:45.27maejrepI've tried the RAMSIZE line both commented and uncommented, and I've tried each of the INITRD lines.  They all get to the same place and stop.  If I comment out the RAMADDR line, it never gets past the haret "booting linux" progress bar in winmo
05:47.00tmzt_maejrep: you have the raph100?
05:47.07maejrepraph800
05:47.09maejrepcdma/sprint
05:47.24tmzt_is that one supposed to be working?
05:48.03maejrepyes, hillsdale was able to get the mddi client working, which NetRipper included in one of his recent patches in git
05:48.15maejrepit used to at least boot to a console for me, and now I can't even get that far
05:48.35maejrepwith touch of jobo's RGB444 change, it appears to fix the color issue
05:48.53tmzt_any messages appear on the screen? you said it stops at booting linux
05:49.04maejrepno that's not the problem
05:49.09maejrepthat only happens with the RAMADDR line
05:49.30tmzt_ok, so there is not enough memory for your initrd?
05:49.35maejrepthe problem I'm having is after booting past the TCP/ether stage, there are 4 something_pwrsink_set:STUB! lines
05:49.38maejrepand that's the last thing I see
05:50.01maejreps/with/without/
05:50.58maejrepthe same initrd I'm using now, I've used in the past (say, about 1-2 weeks ago), and was able to boot to the console, calibrate the screen, and use the onscreen keyboard
05:51.06tmzt_ok, panics if you use no initrd?
05:51.10tmzt_ok, it
05:51.56maejrepbut since I've updated to latest git, which includes NetRipper's version of hillsdale's original patch to get the framebuffer working, lavender.t's patch for usb_ether, and some other minor fixes
05:52.04maejrepit doesn't get past those 4 STUB lines
05:52.11maejrepI haven't tried it with no initrd .. is that valid? :x
05:52.40maejrepi mean, i know it's valid, but since there's no root fs to mount, I assumed it would fail
05:52.42tmzt_well, it should panic but it's a standard message so it helps
05:53.07maejrepas in, it'll help determine if it's hanging loading the initrd or if it hangs before that?
05:53.10maejrep1 second,
05:53.35maejrephttp://www.netripper.com/raphael/20081202_dmesg.txt
05:53.37tmzt_it's not clear whether you are getting to 'freeing init memory' which is when the kernel boot process ends and /sbin/init (or /init) is launched in userspace
05:54.06maejrepmy boot looks more or less like that, except after the 4 "trout_pwrsink_set:STUB!" lines, it just stops
05:54.20maejrepyes, I see Freeing init memory: 100K
05:54.37tmzt_and found initramfs before that?
05:55.13maejrep"Unpacking initramfs... done" ?
05:55.30*** join/#htc-linux surgex0 (i=surge@pool-98-118-165-224.bflony.fios.verizon.net)
05:55.41tmzt_ok, trout, I thought NetRipper was using halibut
05:55.51maejrephe's using trout for everything except the keyboard, afaik
05:56.08tmzt_but sd also does not work on this kernel?
05:56.31maejrepwell, I get similar messages to what's in NetRipper's dmesg, re the sd
05:56.43maejrepbut haven't ever tried to use it
05:56.56maejrep1 sec, I'll boot it now
05:57.50maejrepyeah, I see: [    1.407873] mmc0: Qualcomm MSM SDCC at 0x00000000e1000000 irq 24,0 dma -1
05:57.56maejrepup to "Polling status mode enabled"
05:58.26tmzt_sorry, just trying to understand what NetRipper was saying yesterday
05:58.33maejrepand, in fact, I don't see "Freeing init memory"
05:59.03maejrepI'll copy NetRipper's dmesg and point out what lines of his I also see
06:01.38*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
06:03.51maejrephttp://privatepaste.com/a3f1WyIOQW
06:04.09maejrepthat's essentially what I see on the screen when it freezes
06:04.40maejrepit gets to line 39, then pauses for about 9 seconds, prints 3 more lines, pauses for 10 seconds, then the rest prints out
06:05.18maejrepat line 57, where I marked with ***, that line is mostly cut off, where I can only see the top half of each letter, basically
06:05.36maejrepthen the last 4 STUB lines, and a new line with just a "_" printed on the left
06:06.42maejrepnetripper's dmesg does not have the 10-second pauses -- at most it's like 1 second, and his gets all the way through calibration in about 7 seconds
06:08.14maejrepre the cutoff at line 57, it's possible that the "Freeing init memory" line is *supposed* to be printed there, under the hctosys.c rtc line but the display glitch causes it to just not show up..  I don't know for sure though
06:13.27tmzt_you might be right if something is reading /dev/rtc0
06:18.30maejrepyou think that would cause the hang?
06:18.37maejrepNetRipper's prints the same message though
06:19.17tmzt_no, but I don't know
06:19.26tmzt_it seems this is the clocks
06:20.19tmzt_I don't mean the rtc, but the actual clocks
06:26.19maejrephmm, so you'd recommend some debugging lines around the rtc / hctosys parts of the kernel?
06:27.08tmzt_if this is being called from userspace, I don't see how that will provide more information than you already have
06:27.22tmzt_you are using fbcon for the user console?
06:27.40tmzt_not druidu console
06:27.40tmzt_?
06:28.06maejrepyeah, it successfully does the framebuffer console handoff after hillsdale's patch for the additional mddi client
06:28.53tmzt_ok, should init or the init scripts be printing anything?
06:29.11tmzt_it wouldn't be in dmesg, so you would have to see if it prints on the screen
06:29.51maejrepI can't actually get a dmesg -- what I see is only what's printed on the screen.  the link on netripper's site is his dmesg, which I just modified to match what I see
06:30.15maejrepThe next steps I should be seeing would be the touchscreen calibration
06:30.39maejrepbut even if I just go through the steps of calibration without being able to see anything, it doesn't respond after this
06:41.35*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
06:47.38*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
07:14.53*** join/#htc-linux kiozen (n=oeichler@p5492991C.dip0.t-ipconnect.de)
07:17.57*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbf836f.pool.einsundeins.de)
07:26.25*** join/#htc-linux dsr_ro (i=dsr@89.39.110.83)
07:26.34*** part/#htc-linux dsr_ro (i=dsr@89.39.110.83)
07:49.31*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
07:57.29*** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net)
07:59.53*** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde)
08:03.35*** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com)
08:15.32*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-a52683d1054d8894)
08:24.43*** join/#htc-linux kilian_ (n=kilian@92.66.94.81)
08:25.25*** join/#htc-linux zule (i=foglem@shadowmite.com)
08:29.26*** join/#htc-linux timebomb (n=tb@e176105083.adsl.alicedsl.de)
08:34.36*** join/#htc-linux Xime (n=xime@dag94-3-82-233-170-230.fbx.proxad.net)
08:44.20*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
08:52.01*** join/#htc-linux stefan_schmidt (n=stefan@w1583.wlan.rz.tu-bs.de)
08:53.12NetRippermaejrep, uncomment the RAMSIZE and set mem=96M in the cmdline
08:54.18NetRippermaejrep, and try this package: http://www.netripper.com/raphael/20081204-01_raph_diam_angstrom_usb/
09:36.36*** join/#htc-linux Babel1 (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
09:51.37*** join/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig)
09:51.43*** part/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig)
10:23.13*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
10:29.01Marajinmornin BabelO_
10:29.12BabelO_morning Marajin
10:29.22Marajinhow's it going?
10:30.06BabelO_Marajin: good, and you ?
10:30.26Marajinnot bad, trying to find a usable Windows GPS nav software though
10:30.26BabelO_i m playing with microsoft virtual server, cause we have a bug on it :(
10:30.47Marajinwhat's the bug?
10:42.17BabelO_Marajin: the bug is related to bad USB driver support
10:42.39BabelO_Marajin: there is no USB on virtual server, and got some software bug related to that
10:50.56Marajinah
10:51.02Marajinthat's a bit pathetic
11:06.00*** join/#htc-linux mokolade (n=mokolade@85.221.112.173)
11:34.17*** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net)
11:37.35*** join/#htc-linux infernixx (n=nix@unaffiliated/infernix)
11:37.53*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-c98a048a640a0e6d)
11:45.19*** join/#htc-linux timebomb (n=tb@p5B3E594C.dip.t-dialin.net)
11:59.07*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
12:22.17*** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net)
12:42.09kiozenhttp://www.redferret.net/?p=11407
12:44.21kiozenand another usb joke for BabelO_ http://news.softpedia.com/news/Two-Gadgets-That-Will-Have-You-Fired-82801.shtml :)
13:23.44*** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl)
13:24.31*** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com)
13:30.50*** join/#htc-linux LunohoD (n=alex@e180070185.adsl.alicedsl.de)
13:32.53*** join/#htc-linux kuhlivisj (n=kuhlivis@s5592d82c.adsl.wanadoo.nl)
13:37.11*** join/#htc-linux LunohoD (n=alex@e180070185.adsl.alicedsl.de)
13:51.18*** join/#htc-linux LunohoD (n=alex@e180070185.adsl.alicedsl.de)
14:04.24*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
14:13.10*** join/#htc-linux pichurri (n=pishuri@194.230.154.96)
14:13.20pichurrihello everybody
14:13.40pichurriI have a htc blackstone, also known as touch hd or t8282...
14:13.52pichurriI'm trying to run linux / android on it
14:14.24pichurriI took as base, the work done on the htc raphael and diamond
14:14.31pichurriI get to boot android
14:15.39pichurriand angstrom
14:16.08pichurriI can connect via usb to the angstrom and execute commands...via ssh
14:16.33pichurribut the screen is scrambled, in both cases
14:16.39pichurriandroid and angstrom
14:16.51pichurriany ideas
14:17.03pichurriI've been over the framebuffer and touchscreen code
14:17.30Bushmanhmm...
14:17.44Bushmanbut windows works fine?
14:17.45pichurribut I'm not a kernel / driver developer (yet), so far I changed the resolution from 640x480 to fit the blackstone 800x480...
14:18.06Bushmanhmm...
14:18.07pichurriyeah, on windows screen works correctly
14:18.35pichurrialso
14:18.38pichurriwith haret
14:18.50Bushmanhuh?
14:19.00Bushmanwhat do you mean?
14:19.28pichurriI've dumped the mmu, and hopefully a screenshot
14:19.57Bushmando you mean that it works with haret or not?
14:20.16pichurriI ran in haret: pd 0x1686a000 768000 and dump mmc
14:20.32pichurriyes haret starts the kernel I compiled and boots,
14:21.02pichurribut the screen is scrambled.
14:21.12Bushmanand what happen when haret finished loading and the hernel started to output to the screen?
14:21.22Bushmanright away?
14:21.41pichurriI did a video: http://www.youtube.com/watch?v=Siai2KspElE
14:22.48pichurribrb
14:24.02Bushmantell me, does it stay like this (like in the end of the video) or anything changes later?
14:26.38*** join/#htc-linux myxor (n=myxor@pdbn-4d08976a.pool.mediaWays.net)
14:28.36*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
14:28.36pichurriat least once, I think the hole boot process went through
14:28.39pichurrias in http://www.youtube.com/watch?v=_MrWIxDMCsE
14:29.24pichurribut the raphael/diamond kernel has screen calibration during the kernel boot process
14:29.29pichurriI taped 5 times
14:30.34pichurriand then screen went black, except for, what I suppose is the the famous moving dot, after 1-2 secs, screen went all black
14:31.35pichurriSo, I guess android booted correctly but with a scrambled screen
14:31.36Bushmanlooks like it has wrong resolution
14:31.43pichurriyeah
14:31.44Bushmanon your video
14:32.26pichurribut after that one, I compiled a kernel and changed the resolution, but still, scrambled screen
14:33.34Bushmanwhat was the one on the video?
14:33.41Bushmanres?
14:34.20pichurriany ideas? been looking into drivers/video/msm/msm_fb.c drivers/video/msm/mddi_client_toshiba.c
14:35.27pichurrithat was a first try, a vanilla raphael/diamond version
14:35.33pichurrifrom netripper
14:36.09pichurrihttp://www.netripper.com/raphael/20081204-01_raph_diam_android_v0.8.exe
14:36.17pichurribrb
14:36.54Bushmantell me what was the resolution in the kernel that was shown on the video
14:37.10Bushmanyour video :http://pl.youtube.com/watch?v=Siai2KspElE
14:37.15Bushman* http://pl.youtube.com/watch?v=Siai2KspElE
14:40.55pichurri640x480
14:43.38Bushmanand AFTER you changed it and compiled what was the resolution?
14:45.53pichurri800x480
14:53.23*** join/#htc-linux letestdun00b (n=aaabraca@62-244-191-249.cust.exponential-e.net)
14:54.27*** part/#htc-linux letestdun00b (n=aaabraca@62-244-191-249.cust.exponential-e.net)
14:56.26pichurriany ideas?
14:56.57pichurriin the meantime I thought about dumping data and post it on the wiki, thats why I asked about haret....
15:22.10*** join/#htc-linux kilian__ (n=kilian@92.66.94.81)
15:47.51NetRipperpichurri, nice to see that the HD display works on the kernel
15:48.29NetRipperpichurri, you compiled the kernel yourself?
15:49.59NetRipperpichurri, please look through the dmesg to see which panel it detects.. somewhere during boot there's a line like this: "[    4.624821] mddi_pmdh: publish: mddi_c_d263_0000
15:50.12NetRipperi'd like to know that mddi_c_XXXX_XXXX
15:50.12*** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes)
15:50.13NetRipper:)
15:50.17NetRipperhid ChanServ
15:50.18pichurrihey netripper!!!
15:50.19NetRipperuh
15:50.21NetRipperhi dcordes
15:50.24dcordeshi all
15:50.25pichurriread a lot bout you
15:50.37pichurriI mean in the thread of the diamond/raphael
15:50.39pichurri:)
15:50.43NetRipperyer ;)
15:50.46pichurriyep, I compiled the kernel
15:51.00NetRipperok can you check which panel it detects?
15:51.47dcordespichurri, you've got raph100 (gsm) ?
15:52.01NetRipperdcordes, touch hd
15:52.17dcordespichurri, you know the blackstone linux thread?
15:52.33dcordespichurri, did you boot linux successfully?
15:53.25NetRipper15:21:42 < pichurri> I did a video: http://www.youtube.com/watch?v=Siai2KspElE
15:53.27dcordesNetRipper, do you have the initrd where you can test-paint yellow dots for ts?
15:53.30pichurri[    4.654241] mddi_pmdh: publish: mddi_c_4ca3_0000
15:53.32dcordesgood
15:53.39NetRipperpichurri, ok
15:53.59dcordespichurri, is this video produced with the raphael kernel built from htc-msm-2.6.25 with raphael_defconfig?
15:54.16pichurriyes linux boots correctly I used angstrom from diamond/raphael and got shell via ssh
15:54.30dcordesbon
15:54.30NetRipperpichurri, same panel as raph800
15:54.35pichurritoshiba
15:54.42dcordespichurri, do me a favor and boot this zImage http://linuxtogo.org/~lgorris/builds/kernel/xperia/zImage-x1-02.bin
15:55.12pichurritesting...
15:55.16dcordesthanks
15:55.59dcordesat least the white bar at the bottom should disappear.
15:56.00NetRipperpichurri, at the top of mddi_client_toshiba.c there's a function toshiba_enable_panel_raph800 which sets width and height, you can change that to correct res and see if that helps.. (even better, you could try commenting out the assignments to width and height - perhaps it detects it correctly
15:56.16dcordesseems to me msm_fb.c needs some geometry tweak for hd
15:56.32NetRipperi gtg again, am still at work ;)
15:56.37dcordes:P
15:57.13dcordesthe blackstone really is one fine devicer
15:57.15dcordesdevice
15:57.28dcordesXmoo123 (vor 15 Stunden) Anzeigen Ausblenden
15:57.28dcordes0 Schwacher Kommentar Guter Kommentar
15:57.28dcordesAls Spam markiert
15:57.28dcordesAntworten
15:57.29dcordesCopy my zImage from the Xperia, This will help to get fullscreen and maayb the GUI to work!
15:57.29dcordeslol
15:57.29pichurrisame thing
15:57.39pichurridid you change the resolution to 800x480?
15:57.40dcordeshe talks about the 02 build
15:57.43dcordesexactly
15:58.22pichurrialso tried the xperia, from http://www.xmoo.org/X1/linux/Android%200.8/zImage
15:58.25pichurribut no good
15:58.36*** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de)
15:58.44dcordesthis is a copy of one of the zImages at same url as above
15:58.49pichurriahhh
15:59.02dcordesinitially it was just the raphael kernel image, then I did the panel tweak
15:59.05pichurrialso I got some dumps from haret
15:59.17pichurriI tried pd 0x1686a000 0xBB800
15:59.21dcordesas I said it seems to me you need to change geometry in msm_fb.c
15:59.44pichurricouldn't it be a sync problem
15:59.51pichurri?
15:59.51dcordeswas hoping you've got the same panel as x1
16:00.03dcordeshm no clue
16:00.14dcordesmaybe you need more size for the framebuffer?
16:00.37cr2hi
16:00.45cr2kiozen: here ?
16:01.09kiozenyes
16:01.15pichurriwould a mmu dump from haret help?
16:01.23dcordesI have one already
16:01.32pichurrifrom the blackstone?
16:01.35dcordeshttp://linuxtogo.org/~lgorris/misc/blackstone-mmu.txt
16:01.36cr2dcordes: blackstone spl found ?
16:01.42dcordescr2, no but I have the x1 spl
16:01.57cr2kiozen: it seems that the polish guy will be out of business soon :)
16:02.06dcordespichurri, can you provide cr2 with the blackstone spl?
16:02.23kiozencr2: don't think so
16:02.47cr2blackstone has mtype ?
16:02.48pichurriI thought the spl didn't work with the blackstone...
16:02.52kiozengpsmapedit has another focus than mkgmap
16:03.09cr2kiozen: time to put the last nail after christmas
16:03.32kiozenrouting?
16:03.36cr2kiozen: gpsmapedit != cgpsmapper
16:03.38cr2yes
16:03.56cr2routing is already working
16:04.06cr2with mkgmap
16:04.06kiozenbut what is it worth in GT? it will never calc the same rout as the device
16:04.10dcordescr2, yea http://www.arm.linux.org.uk/developer/machines/?action=list&id=1951
16:04.21cr2dcordes: ok
16:04.21dcordescr2, do we need to update haret?
16:04.43cr2dcordes: yes, mach-types.h
16:05.05cr2kiozen: it's about marketing
16:05.40dcordescr2, let's add the shift and notify Kevin2
16:05.46kiozenno, a source of endless user complains "Why doesen't GT calc the same route as my Garmin?"
16:06.27cr2kiozen: ok, but isn't mapsource calculating the different route too ? afaik
16:06.47*** join/#htc-linux metter (n=metter@213-88.1-85.cust.bluewin.ch)
16:06.48kiozenyes, that is why I know the complains :)
16:06.59cr2A* is heuristics anyway
16:07.03kiozenbut it does a 90% job
16:07.17kiozenwe don't know the weights
16:07.22cr2so it's not an optimal route anyway
16:07.48cr2time=distance/speed
16:07.53kiozenimho this stuff is more important for navit and roadmap
16:08.42kiozenthe hard beaten garmin user will set waypoints and let the device calc the route :)
16:08.43cr2yes, but all suck desktop apps support route planning
16:08.51cr2s/suck/such/
16:08.57kiozenlol
16:09.10cr2:)
16:09.24kiozenlet's see if someone comes up with it
16:09.25*** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com)
16:09.50kiozenimho M needs attention badly after xmas
16:10.10cr2compile a new qtextended image
16:10.35cr2and we need to extract your spl somehow
16:10.43cr2direct off the flash.
16:10.47kiozenyes, that and rewrite M to be portable to wince
16:11.22cr2maybe. so it runs faster on linux :)
16:11.56cr2i've tried the BabelO .exe, it works, but is really slow
16:12.05*** join/#htc-linux infernixx (n=nix@unaffiliated/infernix)
16:12.05cr2probably because of the debugging
16:13.09cr2dcordes: an updated haret will be nice, so it detects all the phones known to us
16:15.20dcordescr2, we figured the X on msm_fb problem.
16:15.52dcordesmsm_fb_update needs to be called in order to refresh
16:16.42dcordesnow I wonder what is the way to make it update automatically when required
16:16.49*** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net)
16:17.13dcordesI'm about to make camera gpio call the function like with the polaris keyboard so I can test
16:17.48kiozenbbl
16:17.57dcordesmsm_update_screen()
16:23.37*** join/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig)
16:23.45*** part/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig)
16:23.46dcordespichurri, what's at 0x1686a000 ?
16:26.56cr2dcordes: a vsync gpio irq ?
16:27.36pichurrithe framebuffer memory, no?
16:28.03cr2pichurri: print "%x" VRAM
16:28.12pichurrion haret?
16:28.32cr2yes
16:28.50*** join/#htc-linux imfloflo (i=5bcfd11d@gateway/web/ajax/mibbit.com/x-ab601ac1fb487f46)
16:29.44pichurricr2: 16044800
16:29.52*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
16:30.00cr2kiozen: http://www.sueddeutsche.de/wissen/293/451009/text/print.html
16:30.26cr2pichurri: ok, then it's your framebuffer address in wince.
16:30.56pichurrihow can I take a screenshot dumping the memory...
16:31.08pichurricr2: and would that be of any use...?
16:31.33imfloflowith another  apn
16:32.26cr2pichurri: pwf screensho VRAM xsize*ysize*16
16:36.54pichurricr2: it created a file, screensho, what should I do with it...
16:37.05BabelO_cr2: hi, i already generate an OSM map with routing for test :)
16:37.36cr2BabelO_: with which program ?
16:37.51cr2pichurri: you've asked how to create a screenshot
16:38.35pichurricr2: gimp doesn't open it thou...
16:38.56BabelO_cr2: mkgmap and also tried osm2mp then mkgmap from mp file :)
16:39.12BabelO_cr2: there is mkgmap --net in beta version
16:39.26cr2pichurri: it's raw hexdump, you may convert it into .pnm of sometrhing.
16:40.00cr2BabelO_: yes, i've seen. but how do you test the result ? do you have a garmin device ?
16:40.19dcordes./arch/arm/mach-msm/board-htcraphael.c:#define MSM_FB_BASE             MSM_PMEM_GPU1_BASE + MSM_PMEM_GPU1_SIZE
16:40.35BabelO_cr2: no garming device i just lot result file in gpsmapedit to see if i see arrow on the street
16:40.48BabelO_cr2: if you want i can generate a town for you ?
16:42.26dcordespichurri, what's your actual fb base now?
16:43.04pichurridcordes: sorry, base?
16:43.20dcordesraphael is 1666a000
16:43.42dcordesframebuffer memory address
16:44.04pichurridcordes: apparently 16044800. On haret,  print "%x" VRAM gives that address
16:44.33dcordeslet's put it in the board.c then and try
16:45.44pichurridcordes: in the kernel I don't have a board.c...
16:46.59dcordesarch/arm/mach-msm/board-htcraphael.c
16:47.29dcordes2621440 is enough for blackstone fb size ?
16:47.33dcordes0x280000
16:47.43dcordesit seems ok on the x1
16:48.49*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:50.26pichurridcordes: 0x280000 should go in : "#define MDDI_CLIENT_CORE_BASE"?
16:50.52pichurridcordes, sorry, in MSM_FB_SIZE
16:51.28*** join/#htc-linux Dubbeld00 (n=opera@82-168-116-233.ip.telfort.nl)
16:52.34dcordesyea
16:54.05pichurridcordes: I ended up with: #define MSM_FB_BASE             0x16044800. #define MSM_FB_SIZE             0x280000.
16:54.13pichurridcordes: compiling and testing
16:54.32dcordesjust compiled with same values
16:54.48dcordesdid you also put the resolution in the mddi client ?
16:58.08pichurridcordes: yes, I have full screen. should the penguin go to the right or left?
16:58.28dcordesleft iirc
16:58.40pichurridcordes, I have most of it on right top,
16:58.43dcordesdid you just replace 640 with 800 in the toshiba client?
16:58.51pichurriyep
16:58.57pichurribut also...
16:59.03dcordesthat is also in the zImage-x1-02.bin
16:59.43pichurrion drivers/input/touchscreen/msm_ts.c
16:59.46pichurri+#define MSM_TS_ABS_Y_MAX       799
16:59.56pichurri-#define MSM_TS_ABS_Y_MAX       639
17:00.03dcordesah :)
17:00.22pichurrialso in drivers/input/touchscreen/msm_vkeyb.c
17:00.28cr2msm_ts ? does the irq work now ?
17:00.33pichurri-#define MSM_VKEYB_LCD_HEIGHT   640
17:00.33pichurri+#define MSM_VKEYB_LCD_HEIGHT   800
17:00.38dcordesok
17:00.51pichurriand in drivers/video/msm/mddi_client_toshiba.c
17:00.57cr2why does the ts driver need to know the display size ?!
17:01.05pichurri-       panel->height = 640;
17:01.06pichurri+       panel->height = 800;
17:01.06cr2sounds braindead to me
17:01.13dcordesoh come on. not that harsh
17:01.21cr2:)
17:01.21*** join/#htc-linux Kuma (n=John@f054236114.adsl.alicedsl.de)
17:01.31dcordesat least there is a working ts driver, no?
17:01.42pichurriI guess
17:01.46cr2no idea
17:02.04pichurriI think the kernel I use, does a touchscreen calibration
17:02.28pichurriand I've seen the amazing moving dot when android starts...
17:02.31dcordesit expects you to tap top left and top right corner
17:02.35dcordesNetRipper, correct?
17:02.41pichurrijust 2 taps?
17:02.52dcordesnot sure druidu made the driver
17:03.09dcordesalso the msm console hack and the on screen keyboard. he's also on the xda forum
17:03.20pichurriafter some taps, screen went black and something moved on the center
17:03.29pichurriafter that, all black...
17:04.13cr2suckers ;)
17:04.18cr2dcordes: monatliche Grundgebühr34,95 € (ab dem 7. Monat 44,95 Euro)
17:05.03cr242.4125€ per month
17:06.17cr2Datenflatrate ohne Volumenbegrenzung
17:06.54dcordessounds ok. do you also get call minutes and text messages?
17:08.19cr2no
17:08.41cr2but they pay back 420€ in 2 months
17:08.48*** part/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:09.39dcordesshouldn't the calibration be done in userspace?
17:10.05dcordesalso, is there no on screen keyboard in android?
17:10.17dcordeswould also be useful for the vogue users
17:10.26pichurriTHERE IS
17:10.29pichurrisorry,
17:10.39pichurrithere is a keyboard
17:11.22dcordesI don't mean the kernel keyboard
17:13.04*** join/#htc-linux LunohoD_ (n=alex@e180079204.adsl.alicedsl.de)
17:13.30*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
17:19.05*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
17:20.13Bally3boo!
17:20.46tcccpeeeek!
17:22.48dcordespichurri, you still have the LSD colors?
17:23.03pichurriyep
17:23.18dcordespichurri, it is the same problem on the raphael800 and xperia x1
17:23.20pichurriwait
17:23.26pichurriI think the colors are fine
17:23.45*** join/#htc-linux oktopouce (n=oktopouc@3.69.73-86.rev.gaoland.net)
17:23.50pichurridoes this devices have refresh rates and sync?
17:24.03pichurriI think it is more that kind of problem...
17:24.14dcordesgrep msm_fb.c
17:24.21dcordesdrivers/vidoe/msm/
17:24.26dcordesvidö
17:24.35Bally3dcordes.. to run the haret/initrd setup, do you have to have an ext3 partition set up first?
17:25.07dcordesno the initrd is for the sort of situation where you have no such partition or ability to access a loopfile or such
17:26.15Bally3thanks matey.. did you check the changes rolk made last night? dwaradzyne posted up a zimage with the changes.. we seem to be making some progress..
17:26.33Bally3could really use your input on it tho
17:26.50pichurridcordes, have to leave...but I'll be coming back in 6-7 hours I think...
17:27.38dcordespichurri, see you
17:28.07dcordestmzt_, ping
17:32.13Bally3dcordes.. dzo put 0800000 whatevver as his RAMSIZE we have 0780000  - does it make a difference?
17:32.35Bally3a few more zeroes but I I'm not in it at the mo to check :P
17:43.17dcordeswhat is #define MDDI_CLIENT_CORE_BASE  0x108000 ?
17:49.37tmzt_dcordes: hey
17:49.50tmzt_maejrep: did you get that message from NetRipper ?
17:50.38dcordestmzt_, need your help
17:51.33dcordestmzt_, how can we call msm_update_screen automatically in order to make X work?
17:51.44dcordesliek it is done in http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/vogue-ts.c;hb=refs/heads/htc-msm
17:52.10dcordesthere it's used to update the screen when the on screen keyboard is called
17:52.21dcordesbut it also makes X draw as a side effect
17:56.44tmzt_I guess put back the virtual VBI timer from the early dzo msm_fb
17:57.30dcordesdo you know where the early dzo msm_fb is?
17:57.49tmzt_2.6.24?
17:58.58dcordessorry I mean where can I get it?
17:59.12*** part/#htc-linux oktopouce (n=oktopouc@3.69.73-86.rev.gaoland.net)
18:02.00*** part/#htc-linux Dubbeld00 (n=opera@82-168-116-233.ip.telfort.nl)
18:08.56tmzt_dcordes: is the 2.6.24 tree still on ltg?
18:09.19dcordestmzt_, htc-msm ?
18:10.07tmzt_yes
18:10.45dcordesyea in that branch dwaradzyn used X on the polaris
18:10.56dcordespressing the cam button to refresh
18:11.03dcordeshttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/vogue-ts.c;hb=refs/heads/htc-msm
18:11.25tmzt_I mean as in a timer, an irq that is triggered 60 times a second or whatever
18:11.39tmzt_does pressing the camera button refresh X?
18:11.43dcordesyes
18:11.50dcordesbecause it calls msm_update_screen
18:12.17tmzt_we need to find someone who knows how to write a ddx then
18:12.33dcordesddx?
18:13.16tmzt_display dependent x / dix is display independent x (or x means something else)
18:13.30tmzt_basically the driver part of the X server
18:13.58dcordesyou want to call msm_update_screen from X ?
18:14.14tmzt_you can't call a kernel function from X
18:14.30tmzt_you need a ioctl or syscall or netlink or something
18:14.33dcordeshow do you want to make the msm_fb refresh then?
18:14.54dcordesso ioctl mediates between kernel and userspace?
18:15.16tmzt_anything that calls msm_update_screen should work, setting the yoffset (and double buffering), using PAN
18:15.45tmzt_or we could just add an UPDATE_SCREEN for our driver, but it would be better to be compatible with google
18:16.26tmzt_ioctl is an operation on a device, called through a file descriptor (fd) which has been used to open that device
18:19.27tmzt_we could also probably use MSM_BLIT if we can figure out the semantics for calling it
18:20.29tmzt_we know it takes a source region and destination region, but we are not using offscreen pixmaps (which would be implemented using the extra framebuffer memory)
18:21.09tmzt_we want to draw directly into the framebuffer like the fbdev driver normally does (using memory pixmaps if neccessary in the display independent part of X)
18:22.26dcordestmzt_, ok. for now I should confirm on kaiser what dwaradzyn did on polaris
18:22.32tmzt_right
18:22.58tmzt_you can also take out the onscreen keyboard part and just make camera refresh the display (call msm_fb_update)
18:23.06dcordesI would like to make a button call the function
18:23.14dcordesright
18:23.49dcordesboard-kaiser-keypad.c would be a good place?
18:24.01dcordesI added "extern void msm_update_screen(void);"
18:24.47dcordes{KEY_CAMERA, KEY_CAMERA, EGPIO_6_5_KEY_CAM1, 0, "Camera 1"},
18:27.43dcordestmzt_, we could also have pendown call it
18:29.31cr2dcordes: btw, what about changing from CPQ/itsy to NetChip/rndis gadget on 720xA ?
18:29.37cr2is the msm usb rndis-capable ?
18:30.01dcordescr2, feel free to commit the patch I guess
18:30.08dcordesdo you have access?
18:30.19dcordesyes it is
18:30.48*** join/#htc-linux woodson (n=CDP@c-76-101-90-149.hsd1.fl.comcast.net)
18:30.58cr2no i don't have the access.
18:31.00cr2somebody should check it first too
18:31.12cr2but imho it's a reasonable change
18:31.38cr2the ids are 0x0525 / 0xa4a2
18:34.10dcordesin http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=arch/arm/mach-msm/tsc2003.c;hb=refs/heads/htc-msm how can I make pendown call msm_upadte_screen ?
18:39.41*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
18:41.33NetRipper18:02:31 < dcordes> it expects you to tap top left and top right corner
18:41.33NetRipper18:02:36 < dcordes> NetRipper, correct?
18:41.37NetRippertop left, lower right
18:42.14*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
18:43.29*** join/#htc-linux earthman (n=chatzill@diamond.la.net.ua)
18:43.32NetRipperand yes - calibration should eventually be done in user space.. currently, the first 3 taps provide calibration.. to make the driver returns calibrated results, as android 0.8 didn't have a calibration screen
18:45.01Bally3hi rolk
18:45.25rolkHi
18:45.48*** join/#htc-linux dwaradzyn (n=dwaradzy@chello089079197022.chello.pl)
18:45.58Bally3did you give any thoughts to last nights doings?
18:46.11Bally3lo dwaradzyne :)
18:46.26dwaradzynhi there
18:46.32rolkGi D,
18:46.34*** join/#htc-linux bertramt (n=chatzill@63.246.89.17)
18:46.39rolkHi D.
18:47.03dwaradzyni read again what dzo said, and he was talking about different two values
18:47.24dwaradzynthe zimage i posted is not really good for testing
18:48.22rolkI've booted the kernel and initrd D. posted a few more times, and each time the SD card is successfully detected. 3-4 timeouts, no more. File operations (modest size, no stress testing) seem to work fine.
18:48.23cr2NetRipper: do you have usb working ?
18:48.31dwaradzyni think we need a test scenario and put some experiments with different max_block_count i max_block_size
18:48.51Bally3again we seem to have moved forward after the sd card detection?
18:48.55rolkI retrieved the config file from that kernel, and am rebuilding from the patched LTG sources.
18:49.12dwaradzynrolk - it was going fine from months. we need stress tests
18:49.32cr2guys, i'll suggest the sd clock documenting project
18:49.38Bally3can you post up the config file please rolk?
18:50.12rolkYes, that should be no problem.
18:50.17cr2please dump the a0 and a4 clock regs for sd0 and sd1, and put them somewhere in wiki
18:50.27cr2naming the device and the (SD or MMC) card that was used
18:50.38dwaradzynalso i did not change clock to 66mhz as dzo suggested
18:52.53*** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl)
18:56.43dwaradzyncr2: how do we do that? do we put some printks in sd init code?
18:57.33*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
18:58.06Bally3damn died big time :S
18:58.14*** join/#htc-linux Dubbeld00 (n=opera@82-168-116-233.ip.telfort.nl)
18:58.40Bally3hey dubbeld00
18:59.07Dubbeld00hello Bally3
18:59.52dwaradzyncr2: or can it be done using haret only?
19:02.21dcordesdwaradzyn, hi, can you help with my question?
19:02.34dwaradzyndcordes: yes?
19:03.12dcordesI'd like to call msm_update_screen in a loop or on ts press
19:03.14dcordespendown
19:04.17*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
19:06.07Bally3hi rogro :)
19:06.36cr2dwaradzyn: actually, we may just dump the whole clock area, and create an archive
19:06.37dwaradzyndcordes: does kaiser use vogue-ts.c?
19:06.59cr2dwaradzyn: yes, just use 'pd' on the 0xa86* MSM_CLK area
19:07.12*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
19:07.24dwaradzyncr2: so it is haret then
19:07.45cr2yes
19:08.10cr2then you don't write weird stuff into clock registers
19:08.11cr2and let wince do it :)
19:08.26cr2the 7200 values are not appropriate for 720xA
19:08.43Bally3polaris is 7200?
19:09.15dwaradzynok i'll try, i only used haret cosole once and it was with your guidance :)
19:09.26dwaradzynBally3: yes its 7200
19:09.29cr2and my 720xA spl research shows different values than actually used by wince.
19:09.30cr2but at least it's the documented and clearly undestodd code with bitmask group manipulation
19:10.10Bally3can you post up the config file we're using dwaradzyn please
19:10.10*** join/#htc-linux thejigsaw (n=thejigsa@77.29.75.249)
19:10.18cr2i.e. there is not better reference anyway
19:10.24dcordesdwaradzyn, nope. it uses tsc2003.c
19:10.30cr2unless somebody will leak the msm .pdf docs ;)
19:10.32thejigsawhi to all
19:11.21thejigsawi saw that polaris  developement team is gathering today at 8 o clock
19:11.30thejigsawi wanted to help but i have a little work
19:11.44thejigsawso i come to express my support and count on me for future
19:13.00Dubbeld00great :)
19:13.15thejigsawi install ubuntu
19:13.27thejigsawso from tomorow i will help too as much as i can
19:14.00Dubbeld00btw, little question, how can you checkout the git using a commit hash (so I want to checkout a specific commit)?
19:14.22thejigsawany news on the progress
19:14.23thejigsaw<PROTECTED>
19:14.24*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:14.36dwaradzyngit-reset --hard <commit id>
19:14.52Dubbeld00tnx dwaradzyn (sorry to lazy to read the man page ;))
19:14.58dcordescr2, what about looking at the clock dlls with a rather big machine?
19:15.16dcordescr2, that's how ginge got the 7200 mmc clock.
19:15.52cr2dcordes: they contain some convoluted code, referencing other dlls
19:15.58cr2there is  no direct hw access there
19:16.17dcordeshow did ginge get the mmc clocks out of them then?
19:16.27cr2at least i don't see it, and nobody proved the opposite
19:16.50cr2don't know, we need to ask him directly
19:17.09cr2keep also in mind that 7200 != 720xA
19:17.23dcordesI asked him how I can try it on my own. but I still didn't buy a copy of the disassembly program and didn't come to learn asm
19:18.08dcordesthat's why I said 7200
19:18.42cr2the msm_clk problem is certainly the wrong task to start with
19:19.16cr2if it was easy, i've already done it :)
19:19.28dcordeswhat about "<cr2> guys, i'll suggest the sd clock documenting project" ?
19:19.33cr2like gpio assignment
19:19.58cr2dcordes: dump your a0 and a4 regs in wince
19:20.39cr2or just the 0x200 bytes from the clock area
19:20.52dwaradzyndcordes: try putting msm_update_screen() in tsc2003.c in tsts_thread just after the line pendown = 1
19:21.08dcordesok
19:26.13Bally3dwaradzyn:  didnt that vm link?
19:26.25Bally3dwaradzyn:  didnt get that vm link?
19:27.51dwaradzynbally, i did not upload it yet. i'll compress that and open ftp for you in a while
19:28.15Bally3thanks
19:29.31Bally3sohow come you didnt make 66mhz change dwaradzyn
19:32.51dwaradzynBally3: its a simple change in code - i'll do that later
19:33.23Bally3so where we at?
19:35.16dwaradzyncr2: so according to kaiser memory map there are 12 clock values unser MSM_CLK. size for one value is 32 bits?
19:38.59dwaradzyncr2: my dumps are here http://pastebin.com/m2f50f25d, could you take a look and tell it is what we need?
19:40.57rolkThe config file I retrieved from the working zImage is here: http://rapidshare.com/files/172786952/confi
19:41.11rolkhttp://rapidshare.com/files/172786952/config
19:41.33rolkSorry for the typo.
19:42.33Bushmani've fell asleep -.-
19:42.35Bushman._<'
19:42.40Bushman* >_<'
19:43.14rolkD. I recompiled the LTG+full_keyboard.diff patch with this config file, but got a different zImage. I've been looking for an easy way to disassemble the zImage from you and the one I just compiled. I'd like to understand the difference.
19:46.05dwaradzynrolk: post link to git commit you checked out - i want to be sure we are talking about the same sources
19:47.55rolkD. The branch is htc-msm, commit 1082670ccae30e6592311cc9dee93ba978382a25.
19:49.12Rogro82hiya
19:49.14cr2dwaradzyn: documented values. the other registers are used for other clocks that we don't know about
19:49.14cr2dwaradzyn: do your a0 and a4 values match kernel code ?
19:49.36cr2dwaradzyn: yes, 1 clock reg is 4byte=32bit
19:50.03dwaradzyncr2: where in kernel i can check a0 and a4 values?
19:50.23rolkD. That .config and that code base + patch now seems to give me a kernel that more or less reliably detects the SD card.
19:50.28cr2dwaradzyn: you can just dump the 0x200 block with 'pd 0xa8600000 0x200'
19:50.36cr2in the SD related driver
19:50.51cr2a0 and a4 clock registers are SD0 related
19:51.01cr2the a8 and ac are for the SD1
19:51.12Rogro82i dont now what im doing wrong but somehow my zImage tries to mount the partition on the sd card before it gets initialized... did i miss something?
19:51.16cr2aka wifi
19:51.35rolkIts odd, as the differences between the .config I used yesterday and the one I retrieved from your kernel seem all 'unrelated' to SD. Except perhaps the  general config switch 'CONFIG_BLK_DEV'.
19:51.39dwaradzynRogro82: add rootdelay=5 to default.txt to beat that
19:51.48Rogro82k thnx
19:52.31dwaradzyncr2: reading the code...
19:52.37dcordesRogro82, add a rootwait to cmdline
19:53.42cr2dwaradzyn: the current clock code is a hack, and therefore a fscking mess :)
19:54.09dwaradzyndcordes: you always correct me that way :) and as always i ask you: what is the difference between rootdelay and rootwait ?
19:54.45dwaradzyncr2: damn it, but i still want to try
19:54.47cr2rootwait is something new
19:56.27Bally3how do you log whats happening on the screen when you run haret? I had an interesting screen tellig me that mmc0 was found but it disappeared too fast
19:57.04Bally3I'm sure using dwaradzyn's zimage the sd card error isnt reported
19:57.10cr2Bally3: if the see the linux messages, haret is already over
19:57.34Bally3ok.. so how do I get it from linux? the thing crashes at that point so reboot
19:57.50cr2as in "completely dead and overwritten"
19:57.50dwaradzynBally3: check linux command: dmesg
19:57.56cr2like wince
19:57.59Bally3but  dont see a log file anywhere
19:58.18dwaradzynin that case it is not logged anywhere...
19:58.29Bally3where dwaradzyn? I cant get into linux
19:58.38cr2dmesg dumps an internal kernel buffer
19:59.00Bally3can you place that in your default file to generate it?
19:59.22Bally3I cant get at a console to type anything
19:59.39Bally3black screen and freeze only
20:00.11*** part/#htc-linux Dubbeld00 (n=opera@82-168-116-233.ip.telfort.nl)
20:00.55dcordesdwaradzyn, it will just wait until everything is ready
20:01.11dcordesI think it mounts when the device is up
20:01.19Bally3what did you get from your zimage dwaradzyn? it looked like it had got past the sd init
20:01.30dwaradzynbally: one way is to connect to device by telnet/ssh and run "dmesg | tail -f". if you have luck there will be something reported before device reboots
20:01.49dcordesdwaradzyn, msm_update_screen works
20:02.05dwaradzyndcordes: ok - just looked it up an now i know the difference :)
20:02.06Bally3ok .. thanks... will try that when I get your set up I guess
20:02.23dwaradzyndcordes: that great
20:03.16*** join/#htc-linux RgR (n=irc@195-241-90-16.ip.telfort.nl)
20:03.23rolkAnyone an idea why the experimental 64 bit memory and io configuration setting is enabled in the kernel config?
20:03.53dwaradzynrolk: i have no idea, but it was there all the time AFAIR
20:04.21dwaradzynrolk: didn't have guts to change that :P
20:04.34dcordesrolk, compare with msm_defconfig
20:07.03rolkD. have you checked the commit?
20:07.40dwaradzynBally3: about your logging question. the only way to connect through network to polaris now is to connect it to 3g and do a reverse ssh. there was an angstrom initrd that had scripts for doing that
20:08.45dwaradzynrolk: give me few mins, i needed to shut down vmware with linux for a while
20:09.02Rogro82:-S still failed to mount sd card
20:09.23Bally3thanks dwaradzyn ..  may be worth looking at... Im sure there was something there
20:09.40dwaradzynRogro82: what are your symptoms?
20:10.40Rogro82its trying to mount /dev/block/mmcblk0p1... that fails then the polling is triggered and the mmc is initialized :S
20:11.12dwaradzynRogro82: did it fall back to shell?
20:11.35Rogro82it hangs
20:12.00Bally3you loading angstrom Rog?
20:12.11Rogro82no android
20:12.29dwaradzynRogro82: could you pastebin last few messsages you have onscreen ?
20:12.41Bally3black screen?
20:12.55Rogro82the last few are the ones that show the initialization of the mmc card you want those or the failing ones?
20:13.11cr2rolk: wtf 64bit access on a 32bit cpu ?
20:13.43dwaradzynRogro82: pastebin both
20:13.44cr2afair even alpha used only 48bit
20:13.45Rogro82mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such device or address
20:13.56Rogro82Failed to mount SD Card
20:14.14cr2~ping NetRipper
20:14.15aptpong NetRipper
20:14.17dwaradzynRogro82: use www.pastebin.com for that
20:18.08*** join/#htc-linux dcordes_ (n=dcordes_@unaffiliated/dcordes)
20:18.55Rogro82http://pastebin.com/d37b08fda
20:20.19dcordes_rootdelay=5 ?
20:20.20dwaradzynRogro82: if you put those messages in order they were shown on screen then it is clearly the case that sd needs more time to init
20:20.25NetRippercr2, hi
20:20.38Rogro82yeah already tried rootdelay
20:20.48cr2NetRipper: do you have working usb ?
20:21.07Rogro82also rootwait
20:21.15dwaradzynRogro82: can you pastebin your default.txt?
20:21.25NetRippercr2, yes
20:21.30*** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl)
20:21.33NetRippercr2, i have a few dmesg's on my open dir
20:21.51cr2NetRipper: can you switch to netchip/rndis ids ?
20:22.32NetRipperwhat are the id's? and how does netchip/rndis work (wouldn't the phone need dhcpd running/)
20:22.38NetRipper/=?
20:23.02cr20x0525 / 0xa4a2
20:23.34cr2no, it's standard cdc_ether (with rndis extension) like implemented on pxa
20:23.43Rogro82http://pastebin.com/d477c0ab1
20:24.37cr2the cpq/itsy is a very antiquated way of doing cdc_ether
20:24.41NetRippercr2, i think rndis is not implemented
20:24.53dwaradzynRogro82: i see it now. rootdelay and rootwait won't work for you as there is no root=/dev/... specified
20:25.07cr2then use 0x0525 / 0xa4a1
20:25.16dwaradzynRogro82: you seem to be trying to boot android 1.0 from vogue, right?
20:25.30Rogro82already tried root=/dev.
20:25.33dcordes_dwaradzyn, to have an ugly but working hack, how would I run msm_update_screen() in a loop and what interval should I use? or do you know a better way?
20:25.52Bushmanis there any mips linux related channel?
20:27.02NetRippercr2, for my info, what's wrong with 0x049F/0x505A? is that the antique way you mentioned?
20:27.06dwaradzyndcordes_: i think polaris does have a infinite refresh loop, you can even enable fps counter in vogue_ts
20:27.14Bushmannevermind, found one
20:27.32tmzt_cr2: any idea on msm_fb to make it refresh in X?
20:28.02dwaradzyndcordes_: it was about 60 fps all the time i checked it last times. you can safely use 20ms interval
20:28.09cr2NetRipper: i think it's the protocol used on zaurus sl5500, and there are some quirks
20:28.17Rogro82k gotta run
20:28.19NetRippercr2, aha
20:28.28cr2NetRipper: netchip is the standard cdc_ether way
20:28.30NetRippercr2, ok i'll test the 0x0525 / 0xa4a2
20:28.37cr2ok
20:28.54dcordes_dwaradzyn, can you give me an 'example' ? :)
20:29.51cr2tmzt_: i don't get it why the fb driver does not autorefresh. seems as a really awkward way of doing things to me
20:29.57dwaradzynRogro82: the mounting in androig 1.0 is done in /init script. it is inside initrd.gz. in order to make it work you should edit this script and change "sleep 1" line to "sleep 5"
20:30.40dcordes_obviously android rendering mechanism sends ioctls or syscalls or whatever to achieve the update?
20:31.12NetRippercr2, someone mentioned the fbdev mmaps the framebuffer.. which wouldn't include dma'ing the mddi.. couldn't that explain why X isn't refreshed?
20:31.20cr2then android is a fucked up piece of software ;)
20:31.21dcordes_and msm_fb.c is ignoring anything but android gui
20:31.56dwaradzyndcordes_: try doing something similiar to tsts_thread with infinite loop and wait inside
20:32.06cr2NetRipper: but why should the app developer take care of the hw refresh ?
20:32.28cr2i don't understand what you can win by controllig it in software
20:32.34dcordes_dwaradzyn, should this really stay in the touchscreen function?
20:32.36NetRippercr2, performance reasons maybe? and it doesn't take care of hw refresh.. it would just update the fb dev memory
20:32.58dwaradzyndcordes_: i have no idea...
20:33.05cr2NetRipper: i suspect that there is some evil DRM conspiracy behind it.
20:33.35dcordes_dwaradzyn, we should put something that works in msm_fb.c and enable it with a config MSM_FB_NON-ANDROID
20:33.51NetRippercr2, that's a pretty wild thought
20:34.00dcordes_or rather the other way around, excluded it for android configs and use it in all the htc msm kernels
20:34.22cr2NetRipper: they name DRM as one of the resons for developing MDDI
20:34.31cr2NetRipper: they=qualcomm
20:34.40dcordes_would a loop calling the refresh drain any performance or is the operation tiny enough?
20:34.48dwaradzyndcordes_: second solution seems better to me
20:35.08dwaradzyndcordes_: 60fps takes 0.5% of cpu AFAIR
20:35.56dwaradzyndcordes_: but i think it uses dma, so there could be some performance drain not visible in top
20:36.19dcordes_ok. if I want to put the 20ms loop in msm_fb.c must I do an extra function or do I just put it in the prsent msm_update_screen ?
20:36.20NetRippercr2, but, then it must be some sort of hardware limit? as the drivers so far are fully open source.. in which case we'd be able to remove certain checks
20:37.14dcordes_cam driver isn't
20:37.38NetRipperyes but we're not using cam driver yet
20:37.41NetRippernor wifi
20:37.44dwaradzyndcordes_: i never did something like that before. i was planning to do it this weekend. have not started yet
20:37.51dcordes_wifi only has the firmware
20:38.08cr2NetRipper: they are so opensource, that the people can't thge palette issue for more that a month now
20:38.53NetRippercr2, that's also a matter of experience and available time.. i mean the palette issue is just cmda.. it's not that big a community
20:38.56Bally3rog di you get a black screen freeze?
20:39.38cr2it's just good luk that the g1 driver works on raph100 as is
20:40.10cr2NetRipper: blackstone too, afaik
20:40.15dwaradzynBally3: rogro needs to modify initrd.gz as i did
20:40.31NetRippercr2, blackstone and raph800 have the same panel..
20:40.44NetRippercr2, at least, same panel id is detected
20:41.08cr2ok, but it does not really mean anything
20:41.15Bally3so did either of you get a frozen black screen or di you get to a prompt?
20:41.21cr2it's not just some $random 64bit uuid
20:41.30NetRippercr2, using your id's "unsupported MDLM descriptors"
20:41.45cr2a4a1 ?
20:41.55NetRipper<PROTECTED>
20:41.55NetRipper<PROTECTED>
20:41.58NetRippera4a2
20:42.01cr2i think unsupported MDLM descriptors are rndis
20:42.10NetRipperit doesn't create a usb0
20:42.26NetRipperwant me to try a4a1?
20:42.36cr2lsusb ?
20:42.36cr2yes
20:43.09cr2i'll check the pxa source
20:43.17NetRipperok
20:43.46NetRippercr2, do you have any hints on where to start looking to solve mmc problem?
20:44.19dcordes_NetRipper, I would test trout-mmc
20:44.26NetRipperi have, no luck
20:44.40NetRipperalthough i can't fully boot trout, i inited the trout-mmc from my halibut board
20:44.51dcordes_you built board-trout-mmc* ?
20:44.54NetRipperyes
20:45.03NetRipperand inited it
20:45.11NetRipperdoes nothing different
20:45.31dwaradzynrolk: i checked your commit id. with which zimage built by me did you compare the one built by you?
20:48.12cr2*/
20:48.12cr2#define CDC_VENDOR_NUM0x0525/* NetChip */
20:48.12cr2#define CDC_PRODUCT_NUM0xa4a1/* Linux-USB Ethernet Gadget */
20:48.30cr2NetRipper: it's from ether.c gadget source
20:48.42NetRippercr2, same message, unsupported mdlm descriptors
20:48.54cr2NetRipper: we need to fix the broken clk_ api
20:49.08cr2NetRipper: what do you have on the host side ?
20:49.38NetRippercr2, host side, mmc or usb? :p
20:49.46cr2usb
20:50.07NetRippereverything as usual
20:50.11NetRipperno strange messages
20:50.29rolkdwaradzyn: That would be the one you posted on the 'Polaris' thread on www.xda-developers.com
20:50.48NetRipperlet me try again with the subclass suggested by lavender.t
20:50.57dwaradzynrolk: which post# ?
20:51.02*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
20:51.05cr2ok
20:51.41cr2NetRipper: it should be netchip/a4a1. so something else is wrong too.
20:51.43NetRippercr2, clk api is proc_comm?
20:52.03cr2goes through proc_comm only on g1
20:52.12rolkI think it is post #51.
20:52.17cr2we need to have direct access
20:52.51dcordes_cr2, doesn't dzo perform pm operations using proc_comm ?
20:53.17NetRippercr2, ah ok, the kaiser/vogue way? but why do we need the clk api? aren't all clocks initialized by winmo already? i'd like to get it working first - before we add support of switching sd cards (which implies clock changes)
20:54.04dcordes_I think you need the mmc clocks either way
20:54.17cr2NetRipper: i think wince switches the clock on demand.
20:54.18cr2it saves power
20:54.31cr2and we have complete mess in the current code
20:54.35NetRipperok but since i boot from sd, i'd say sd is pretty active
20:54.37NetRipper:p
20:55.02dcordes_I don't see how the clocks can be mess when ginge has them from the dll
20:55.24cr2dcordes_: i'd like to hear the full version first
20:55.45cr2because the clock settings between wince and spl differ too.
20:55.58rolkAnyone here that has an idea of the 'loops per jiffie' value on Polaris?
20:56.38dwaradzynrolk: ok i see it clearly now. the patch from post 51 is broken. it just adds full_keyboard.c and does not contain changes to other files (as well as .config).
20:56.59cr2NetRipper: btw, do the smem smd channels work ?
20:57.16NetRippercr2, only receiving, not send
20:57.42cr2dcordes_: yes, dzo uses proc_comm. it needs bettwe docs though.
20:57.57cr2NetRipper: so gps works ?
20:58.01cr2NetRipper: it's strange that send does not work.
20:58.17NetRippercr2, regarding usb, with 0x00 as subclass i don't get the MDLM error anymore, but i don't get usb0 either..
20:58.19dcordes_cr2, unfortunately he didn't use the wiki
20:58.39cr2ok
20:58.40NetRippercr2, looking at the usb function ether code it's really limited, so maybe it is the minimum
20:58.57dcordes_I also find the broken AT send on raph100 strange. on the x1 it works with the trout code both ways
20:59.02NetRipperCE: hpet increasing min_delta_ns to 15000 nsec
20:59.03cr2ok, so leave it as is.
20:59.11cr2seems weird to me though-.
20:59.17dwaradzynrolk: i see that this sd code is completely time dependent and based on magic timer values. thats a mess. i have no idea what jiffies mean
20:59.27*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
20:59.46cr2NetRipper: what about gps ?
20:59.56NetRippercr2, haven't tried gps, i can do that in a bit
20:59.59NetRipperlet me revert usb
21:00.15cr2ok
21:01.17NetRipperi flashed elite RC2 rom but it can be annoying.. sometimes it hangs during boot (known issue) but means i sometimes have to soft reset a few times before it loads again :p
21:01.27cr2dcordes_: dzo uses the 3 parameter g1 proc_comm proto
21:01.53cr2dcordes_: but wince has more variations
21:02.06cr2hehe
21:02.24dcordes_yea he explained the 3 parameter thing when I asked him about the battery. btw bat should be easy
21:02.42dcordes_I can forward the info from the mail exchange about it if somebody wants to try
21:02.48dcordes_it didn't work for me on the kaiser
21:03.13rolkI'm trying to delay the printk messages using the boot_delay parameter. But for that , I need a loops-per-jiffie value that isn't too far from reality.
21:03.53NetRippercrap forgot to init gps before loading haret
21:03.53NetRipper:P
21:04.24cr2dcordes_: i've documented the battery in wiki pretty well
21:04.39cr2NetRipper: it's an AT command to be sent ?
21:04.47cr2hm. it does not work now ;)
21:04.55dcordes_cr2, yes I looked the regs up but didn't know where to put
21:05.20dcordes_and hat several other problems as always when I destroy code
21:05.33cr2ok
21:05.40NetRipperrolk, msleep()? :)
21:05.56NetRipper(once irq is init'ed :P)
21:06.40NetRippercr2, what's an AT command? to enable gps? but i can't send from linux
21:07.37rolkOk. On my Polaris, lpj=1277952.
21:07.53dcordes_cr2, I'm currently trying to make msm72* work with the frameworkd witht he moko devs
21:08.19rolkdwaradzyn: Good work with the full keyboard, by the way!
21:08.54dwaradzynrolk: i'm editing that post and there will be correct diff
21:09.01NetRippercr2, locks up during boot when gps is enabled
21:09.13NetRipperfreezes
21:09.34cr2strange
21:09.38dcordes_arm9 watchdog
21:10.01dcordes_or the gps channel writes somewhere it destroys something important?
21:10.34NetRipperwouldn't arm9 watchdog reset the device completely, like soft reset?
21:10.58cr2it may do it. if it gots the command
21:11.12cr2NetRipper: the ts irq still not show up ?
21:11.46NetRippercr2, no.. although i've seen 'touch of jobo' comment it out in his .diff.. not sure why.. maybe he saw it fire
21:12.05NetRipperor maybe he was just playing with it
21:12.22cr2ok
21:12.24tmzt_dcordes_: pen down makes sense for your onscreen keyboard, but an X apllication shouldn't need input to refresh the screen
21:12.33cr2there are 2 irqs actually. and they are seen in wince
21:13.00NetRippercr2, i havent actually bothered with irq anymore
21:13.14dcordes_tmzt_, yea I already figured that cause I need to pendown permanently. idk hwo to make the loop
21:13.43cr2ok
21:14.14cr2NetRipper: do you have a linload with a working usb ?
21:14.26NetRipperyes
21:14.28NetRipperits on wiki
21:14.42NetRipperlatest progress entry
21:14.42cr2NetRipper: and the small ramdisk. i don't need the nadroid bloatware :)
21:14.47cr2ok.
21:14.47NetRipperhttp://wiki.xda-developers.com/index.php?pagename=RaphaelLinux#Progress
21:14.52NetRipperit uses angstrom
21:14.59NetRippergives you quite some commands to play with
21:15.15NetRippercredits to dcordes;p
21:16.21NetRipperi need more tea, brb
21:18.36dcordes_crap I need a new laptop
21:19.32dwaradzynrolk: check post 51 again
21:20.41rolkOk.
21:25.09dcordes_NetRipper, did you try the x11 initrd?
21:25.45tmzt_gone?
21:26.19dcordes_http://members.home.nl/j0b0/boot-linux-x11.mp4
21:27.14dwaradzynnice quality video :P
21:27.38rolkdwaradzyn: what is the purpose of the full_keyboard2.diff? It worked already quite good without that patch. I don;t doubt that it is needed, can you elaborate?
21:28.22dcordes_dwaradzyn, and nice quality vga display
21:29.19dcordes_dwaradzyn, it's the raph100 in the video. It seems refresh works there
21:29.49dwaradzynfull_keyboard.diff did nothing :( if you apply full_keyboard2.diff and compile you should see completely different keyboard (not the green one)
21:30.53NetRipperdcordes_, yes, i had a black screen right away.. no cursor.. haven't tried more than once though
21:31.22dcordes_try touching where the on screen keyboard is
21:31.29dcordes_so you get the refresh
21:31.49NetRipperit works then?
21:32.04dcordes_I'm trying to figure
21:32.21NetRipperit should update the whole screen, whenever you click anywhere
21:32.57dwaradzyndcordes_: when i tried older openomo build back in september i had exatly the same screen output as in this video (qvga of course).
21:33.50NetRipperi need to apply that msm_fb patch so that onscreen keyboard doesn't flicker anymore in android
21:34.36dwaradzynNetRipper: i was trying to fight that flicker issue. is there a patch for it?
21:34.52NetRippersomeone put a diff on diamond linux thread
21:35.05NetRipperdwaradzyn, but im working on raphael/diamond (not to get things confused)
21:35.17rolkdwaradzyn: The build completes, and the zImage is still slightly different. Perhaps this can be explained by the fact that I use an arm-none-linux-gnueabi- toolchain that is used in our company.
21:35.24NetRipperand oi, where'd cr2 go :p
21:35.40NetRipperwho gave him permission to leave ;)
21:36.14rolkI'd like to break the zImage open, and have a look at the disassembly, but that will have to wait.
21:36.28dwaradzynNetRipper: is there a video showing flicker on raph/diam? i want to make sure that its the same issue
21:37.37NetRipperdwaradzyn, dont think so
21:38.04dwaradzynrolk: i use arm-none-linux-gnueabi-, version arm2008-q1
21:42.28rolkOk. I don't know how to check the too
21:42.33rolklchain version.
21:43.11*** join/#htc-linux OpnSrc1 (i=harisha1@gateway/tor/x-574f750592c329b2)
21:43.34OpnSrc1hello
21:44.00dwaradzynrolk: arm-none-linux-gnueabi-gcc --version
21:44.04OpnSrc1hi Bally, Dwaradzyn
21:45.01dwaradzynrolk: mine is (Sourcery G++ Lite 2008q1-126) 4.2.3
21:45.11dwaradzynOpnSrc1: hi, whats up
21:45.26rolkarm-none-linux-gnueabi-gcc (CodeSourcery Sourcery G++ Lite 2007q3-51) 4.2.1
21:45.26rolkC
21:45.46rolkIt seems like a slightly older toolchain.
21:45.54Bally3did you get any feedback about the x64 config line rolk?
21:46.16rolktrying that now. I think it can be safely disabled.
21:46.28dwaradzynBally3: we should check if other config have that enabled
21:46.47Bally3checking vogue one now
21:47.00OpnSrc1I've been following xda-developers for a while, I'm upto date.
21:48.00OpnSrc1Applying git-diff-2.6.25-170908.diff patch to git://git.android.com/kernel.git results in error.
21:48.16Bally3config_RESOURCES_64BIT=y
21:48.31OpnSrc1I've built zImages before off of linuxtogo.org repo.
21:48.41NetRipperOpnSrc1, seeing as it's a patch from 17-09-08, i'd say you need a git from about that date ;)
21:48.44Bally3thats it
21:49.04rolkI'm going to focus on getting the usb device controller on Polaris to work, I want a virtual Ethernet connection.
21:49.27NetRipperOpnSrc1, and you may need to select the correct branch
21:49.30Bally3so that you can debug rolk?
21:49.31OpnSrc1Ok,
21:49.45rolkCorrect bally3
21:50.02OpnSrc1I've checked out android-msm-2.6.25
21:50.06*** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de)
21:50.13Bally3makes sense.. the errors we get are hard to trace
21:50.37cr2NetRipper: back
21:50.49NetRippercr2, welcome ;)
21:50.53NetRippercr2, tried the linload?
21:51.17cr2NetRipper: i don't undertstand why i2c and mmc show their virtual addresses in /proc/iomem
21:51.21Bally3can someone post up the polaris config file please??
21:51.28cr2yes, even ssh is working :)
21:51.43cr2but there is a lot of google code to be removed :)
21:52.28cr2NetRipper: did you change the SD detect gpio ?
21:52.43cr2btw, i can't boot off the SD
21:52.44NetRippercr2, no, i just manually set it to return 1
21:52.51NetRippercr2, you can't? strange
21:53.02Bally3CONFIG_MMC_MSM700XA=y
21:53.05NetRippercr2, what happens when you do?
21:53.22cr2the keyboard does not show up, and the whole thing hangs after the power sink STUB messages
21:53.41NetRippercr2, same as some people on forum are reporting
21:53.55NetRippercr2, do you still run stock rom?
21:54.32cr2NetRipper: i think much google crap should be removed, and the virt address issue to be fixed first.
21:54.32cr2yes
21:55.02Bally3whats MTYP?
21:55.07Bally3MTYPE even
21:55.29NetRippercr2, i've compared it to how other drivers use the phys/virt mem and it works exactly the same
21:55.44dwaradzynOpnSrc1: checkout according to post #40 on polaris thread, everything should go cleanly
21:56.41cr2NetRipper: cat /proc/iomem on the desktop machine. it's all physical
21:57.32cr2dcordes_: can you cat /proc/iomem and pastebin the output ?=
21:57.36Bally3thanks dwaradzyn just noticed the confog file :)
21:57.46dwaradzynkaiser people: you have tried to enable usb on kaiser, don't you? i dont think its possible to enable usb host on kasier/polaris, but can it work at least as usb client?
21:57.57NetRippercr2, i know.. i just havent been able to find the reason
21:58.02cr2dwaradzyn: can you pastebin the /proc/iomem ?
21:58.18OpnSrc1Dwaradzyn: ok, post #40, let me try that.
21:58.23dwaradzyncr2: no problem
21:58.40OpnSrc1let me blow away this folder.. & start over again.
21:58.45cr2NetRipper: i donb't see an obvoius reason too, but it's wrong to have virt addresses in /proc/iomem
21:59.41tmzt_does mddi use internal sram for display memory?
22:00.19Bally3CONFIG_MMC_MSM7X00A=y - why is this still set in the polaris config rolk?
22:00.35NetRippercr2, i think dcordes did that earlier, kaiser also showed virtual addresses
22:02.31cr2NetRipper: then it's a kernel bug
22:03.48dcordes_dwaradzyn, I need to find a good solution to call msm_update_screen() first
22:03.48Bally3anyone?
22:04.28dcordes_dwaradzyn, I think ginge looked at kaiser usb
22:04.45dcordes_usb host on the kaiser would be ace
22:04.48rolkBally3: It causes the msm_sdcc.c to be included in the kernel build.
22:05.20dwaradzyndcordes_: i will try to code periodic update and try that on polaris. i'll tell you tomorrow if i succeeded
22:05.27Bally3but someone mentioned our device is not 7200A does that not matter?
22:05.39tmzt_I assume when google renamed there files/config options they decided to make it MSM7X00A instead of halibut or 7200 or whatever it was
22:06.35cr2good night
22:06.44Bally3ok..so thats not an issue then
22:06.47dwaradzyncr2: http://pastebin.com/m67e7300d
22:06.52dwaradzyntoo late :P
22:06.57Bally3lol
22:07.33dwaradzynrolk: can you see prv messages i sent you earlier?
22:07.40NetRipperdwaradzyn, same problem as we have - msm_i2c and msm_sdcc show virtual addresses
22:08.15dcordes_dwaradzyn, hm is it complex to try the perioidic update? I just finished a X image build which I would like to try
22:08.26Bally3how do I post mine to pastebin?
22:09.05dcordes_either write it to the card or copy it manually or run the command remotely from gprs terminal
22:09.23Bally3thaks dcordes
22:10.20dwaradzynBally3: this is how i did it: boot angstrom, cd /media/mmcblk0p1; cat /proc/iomem > iomem.txt; reboot and send the iomem.txt file from sdcard to pastebin using sdcard usb adapter :)
22:11.30Bally3but I cant boot angstrom with the image you posted up and thats the one I want to check as Im sure i'm getting different results.. but it hangs after the trace to a black screen
22:13.01*** join/#htc-linux Bally3_ (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
22:13.13dwaradzynBally3: use kernel from post 51, everything should work with that one
22:13.27Bally3ok :)
22:13.57OpnSrc1Dwaradzyn: Kernel on post 51 is with no patches applied (expect for the KB) right ?
22:14.24Bally3did i just leafve or has another bally3 just joined?? :S
22:15.20Bally3damn whoever you are change yer name :S
22:16.14dwaradzyndcordes_: i will just copy the tsts way of creating threads and see if it does the job of refreshing. i will need to merge that into tsc2003.c later and learn how to make #ifdefs configurable in .config
22:17.57dwaradzynOpnSrc1: yes, thats right
22:19.02dcordes_asd
22:19.29dcordes_oops playing with vnc
22:20.25dcordes_dwaradzyn, what's a thread?
22:22.22OpnSrc1hi decordes, is there any easy way to recreate the SD card issue? without relying on the failure of 1.0 boot off of SD as an indication?
22:22.54dcordes_boot a console initrd and move large files
22:23.38dcordes_http://linuxtogo.org/~lgorris/kaiser-bootkit/angstrom-20081127.cpio.gz
22:24.43NetRippererm, any c expert
22:24.43NetRippervkeyb_landscape = !!(readl(MSM_GPIO2_BASE + 0xC20) & 0x00400000);
22:24.44dwaradzyndcordes_: an example of thread is in tsc2003.c, function tsts_thread gets daemonized and it is visible as process (ie in top command)
22:24.51NetRipper!! is the same as nothing, isn't it?
22:24.51NetRipper:)
22:24.56NetRipperas no ! at all i mean
22:26.07dwaradzynNetRipper: i think you are right
22:26.55rolkNetRipper: not really.
22:27.05rolk!!a means !(!a)
22:27.30rolkIf a is 0, then !a is 1. And !!a is 0 again.
22:27.45rolkIf a is not 0 then !a is 0 and !!a is 1.
22:28.05rolkSo, !!a == 0 only if a == 0 otherwise it is 1.
22:28.17NetRipperrolk, ah, so it would evaluate to 1, when the result between ( and ) could be 0x123
22:28.33rolk!!0x123 == 1
22:28.36NetRipperexactly
22:28.37NetRipperthanks
22:28.51NetRipperi was afraid it was a typo, but that makes sense :)
22:31.40tmzt_it that for the orientation sensor?
22:31.44tmzt_is
22:32.22OpnSrc1decordes_: thanks, I've angstrom on my kaiser. how big a file would hang-up ? 20 MB file?
22:33.00dcordes_yes
22:33.13dcordes_and I have no clue why this is the limit
22:33.54tmzt_block layer/caching? maybe it triggers larger reads on larger files
22:46.59dwaradzynOpnSrc1: try running a script that is running parallel copys. it will die in seconds
22:47.38rolkAha! I just found out something interesting.
22:47.47rolkMaybe this is old news, maybe not.
22:48.21dwaradzynrolk: yes?
22:48.22rolkI've had success booting the kernel version from dwaradzyn and detecting the SD card.
22:48.35rolkThen, it failed 5 times in a row.
22:48.54rolkI think I know the 'variable' that influences the success factor.
22:49.08dcordes_..
22:49.12rolkNote: this is not a stability issue, this is the 'detection issue'
22:49.22rolkIf I access the card from WinMob
22:49.38rolkprior to starting haret, and booting, it finds the card allright.
22:50.03rolkIf I soft reset, and do not touch the sd card from WinMob and then start haret and boot, it fails.
22:51.14dcordes_hm I never ran into problems with detection
22:51.19rolkSo, WinMob leaves the card interface in a proper state, and linux simply does not initialize it, but uses it.
22:51.37rolkWell, just reporting my findings.
22:51.43dcordes_but I have at least haret on the card always
22:51.52rolkFigures.
22:52.00dcordes_so there is always access on boot
22:52.03rolkThen you access the card from WinMob.
22:52.40dcordes_you could easily boil it down booting without the card inserted
22:53.08rolk?
22:56.47dwaradzynrolk: what exactly do you mean by "accessing the card"?
22:57.26tmzt_do we have the right proc_comm's for vreg? for the mmc port
22:57.30rolkWith 'file explorer' listing a directory seems to be enough.
22:57.40tmzt_it's different in halibut and trout it seems
23:02.27dwaradzynrolk: i always do it before launching linux, i have everything on sd, so it is accessed just before boot
23:04.50rolkOK. Same thing as with dcordes.
23:05.18rolkI have haret, default.txt, initrd and zImage all on internal flash...
23:06.10rolkI was trying to boot from an ext3 partition on the sd card, so I figured I better boot from internal flash storage.
23:09.35tmzt_if it's not a SDHC (or they work on yours), make a small boot partition at the beginning usually works
23:09.45tmzt_or just access the sd to power it up
23:17.52Bally3please wait... extracting data image rm: cannot remove /sdcard/data.img: no such file or directory
23:18.03Bally3and I now see the new keyboard
23:18.58Bally3I never had that last message before
23:19.27dwaradzynBally3: the rm is not an issue, this message will be there because the init script is written that way
23:19.27rolktmzt: what's up with that proc_comm?
23:22.48Bally3ok
23:23.55rolkOk. That same procedure seems to work as well with the android-msm-htc-2.6.25 code base.
23:24.03*** join/#htc-linux stefan_schmidt (n=stefan@p5B034B1F.dip.t-dialin.net)
23:25.04dcordes_dwaradzyn, did the ts calibration work for you in the magician image?
23:25.06dwaradzynrolk: nice find
23:25.17dwaradzyndcordes_: no it did not
23:25.39dcordes_how did you try things in it?
23:26.31dwaradzyni saw calibration back in september. this time openmoko started to homescreen without calibration
23:27.14dcordes_maybe because /etc/pointercal is present
23:27.24tmzt_rolk: I mean I don't think the card itself is being powered up.  Look at the halibut and trout versions of board-*-mmc or whatever it's called. the vreg that is used has a different name and might be a different proc_comm (command to the arm9 core through the shared memory area)
23:27.29dcordes_yea it has the magician pointercal
23:28.34*** join/#htc-linux timebomb (n=tb@e176105083.adsl.alicedsl.de)
23:37.09rolkOk. This seems to be a reliable procedure... First access the card from WinMob before booting linux. That fixes my detection problem for the moment.
23:37.27rolkI check a few more times.
23:39.37rolks/check/checked/
23:39.47rolkYes.
23:45.19*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
23:46.10*** join/#htc-linux dwaradzyn (n=chatzill@chello089079197022.chello.pl)
23:54.17rolkdwaradzyn: I applied your patches to the android branch, and the full keyboard is working there as well.
23:55.00dwaradzynrolk: ok
23:55.14dwaradzynrolk: but it blinks?
23:55.36dcordes_dwaradzyn, did you manage to test updater?
23:55.54rolknope, no blinking
23:56.26dwaradzynwhich updater?
23:57.21dcordes_fb
23:57.35rolkI'm 'stress' testing the sdcard now.
23:57.50rolkJust wrote 20MB of data to partition 3 (ext3).
23:57.59dwaradzyndcordes_: not yet
23:58.14dcordes_rolk, I just got the mmc0: Transaction timed out error
23:58.29rolkI'm now mv-ing that 20MB from part. 3 to part. 2 (both ext3).
23:58.41rolkI don't get any messages, but it's slow.
23:58.45dcordes_Aborting DMA operation for MMC

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