| 00:17.45 | *** join/#htc-linux nashpa1 (n=dliviu@dliviu.plus.com) |
| 00:27.17 | NetRipper | j0b0, maejrep, found and fixed the msmfb problem (pushed it to git), but android is still not usable.. it doesn't respond to the touchscreen, probably because it is no longer event0, as event0 is now hardware keyboard ;) android doesn't seem to read from event1 (ts) and others (navi not working either)... |
| 00:27.32 | NetRipper | i suppose it's just a matter of configuration, but didn't find it yet ;) |
| 00:27.53 | NetRipper | done playing for today though, good night ;) |
| 00:37.14 | j0b0 | good night :) |
| 00:37.47 | j0b0 | will look at it. android does read from all devices, but has some reswtrictions on which combinations of events it needs |
| 00:48.22 | *** join/#htc-linux fnord_ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |
| 00:50.16 | *** join/#htc-linux bs2 (n=kra@87.72.13.87) |
| 00:55.43 | maejrep[w] | I don't think it was me o.0 |
| 00:56.03 | maejrep[w] | at least I don't recall fixing anything like that ;) |
| 01:26.02 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
| 01:38.40 | Balsat | Android does find the TS... logcat : I/EventHub( 68): New device: path=/dev/input/event1 name=MSM touchscreen id=0x10001 (of 0x2) index=2 fd=43 classes=0x4 |
| 01:39.27 | Balsat | But it hangs on W/ActivityManager( 68): Activity idle timeout for HistoryRecord{43809ac0 {com.android.launcher/com.android.launcher.Launcher}} |
| 01:46.09 | Balsat | After a second boot i'am seeing the Android screen... TS is working, but the Y-cord and mabye x-cord is way off |
| 01:47.01 | Balsat | Time is ok, and i got a provider |
| 01:48.35 | Balsat | When a toush the TS, the output form catlog say : W/InputManagerService( 66): Ignoring focus gain of: android.view.inputmethod.InputMethodManager$1@437e8e18 |
| 01:50.39 | Balsat | As netripper reported, the navipad keys don't work, but the vol keys do |
| 01:55.16 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 01:56.59 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 01:58.59 | Balsat | A google search gave me : the input framework depends on a working power driver. without an enabled android power driver, the framework will not handle the input-events correctly and constantly report x=0,y=0 as the location of the touch event. so either enable the android power driver in the kernel, or dig yourself into the android input framework. (com.android.server.KeyInputQueue is the place to start) |
| 01:59.12 | Balsat | http://groups.google.com/group/android-porting/browse_thread/thread/0dbeba5caa4ed709/357aa28e2798e0de?lnk=raot |
| 02:06.43 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 02:11.05 | *** part/#htc-linux Balsat (n=kll@87.72.13.87) |
| 02:15.22 | *** join/#htc-linux sdt555 (n=titus@70.114.152.91) |
| 02:37.43 | *** join/#htc-linux Shinto (n=John@f048224111.adsl.alicedsl.de) |
| 02:49.04 | *** join/#htc-linux Shinto (n=John@g227183010.adsl.alicedsl.de) |
| 05:11.37 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 05:17.29 | *** join/#htc-linux Beef (n=beef@unaffiliated/beef) |
| 05:35.41 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
| 05:56.51 | parmaster | does anyone have a 'sectera edge'? |
| 06:00.21 | parmaster | okay, besides obama |
| 06:02.43 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 06:20.12 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c2f1.pool.einsundeins.de) |
| 06:29.59 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-181-169.web.vodafone.de) |
| 06:35.56 | cr2 | hi |
| 06:36.33 | cmonex | hi cr2+ |
| 06:36.34 | cmonex | ! |
| 06:36.37 | cmonex | i wanted to ask you about something :) |
| 06:36.44 | cmonex | do you know much about mddi ? |
| 06:36.46 | cr2 | found my miniusb-A to miniusb-B cable |
| 06:36.59 | cr2 | not much, but something |
| 06:37.03 | cmonex | well |
| 06:37.11 | cr2 | ok |
| 06:37.14 | cmonex | i see stuff in raphaelmddi wiki like HSYNC, HSW, HDE_WAIT |
| 06:37.26 | cmonex | how do you set the right values for a specific resolution ? |
| 06:37.34 | cmonex | sorry |
| 06:37.36 | cmonex | HCYCLE |
| 06:37.37 | cmonex | not sync :) |
| 06:37.39 | cmonex | I'm a bit tired |
| 06:37.53 | cmonex | oh and same with V (vertical version) |
| 06:38.01 | cr2 | i think its not the mddi itself |
| 06:38.24 | cr2 | but the mddi client like toshiba or epson parameters |
| 06:38.56 | cmonex | right |
| 06:38.58 | cr2 | mddi (pmdh) is a controller like SD host or SATA host |
| 06:39.01 | cmonex | its lcm dependent. |
| 06:39.08 | cmonex | the values for the above |
| 06:39.15 | cr2 | yes |
| 06:39.18 | cmonex | but, i would like to know how you calculate the values for a given resolution. |
| 06:39.42 | cr2 | you need the panel datasheet and the toshiba/epson datasheet to know :( |
| 06:39.56 | cmonex | well there is android src for G1 |
| 06:40.07 | cmonex | http://android.git.kernel.org/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/board-trout-panel.c;h=bd15d4441e92645f37eb8b23789189196cb7bdf9;hb=android-msm-2.6.27 |
| 06:40.12 | cr2 | it does not help you very much |
| 06:40.14 | cmonex | stuff like |
| 06:40.14 | cmonex | <PROTECTED> |
| 06:40.52 | cr2 | you have the pixel clock (PCLK) |
| 06:41.15 | cr2 | how 6 relates to 14 ... |
| 06:41.26 | cmonex | thats simple |
| 06:41.32 | cmonex | you divide by 2 then subtract 1 |
| 06:41.34 | cmonex | but .. |
| 06:41.39 | cmonex | what i need to know i guess is for example |
| 06:41.44 | cmonex | how many PCLK |
| 06:41.51 | cmonex | and how many HCYCLE |
| 06:41.57 | cmonex | for VSW for example.. |
| 06:42.06 | cmonex | now thats what i get from datasheet ? |
| 06:42.13 | cr2 | well, try to look at the PXA for example |
| 06:42.23 | cmonex | eh, i need this for MSM7200 |
| 06:42.32 | cmonex | the mddi is toshiba |
| 06:42.36 | cr2 | but the general idea is the same |
| 06:42.54 | cmonex | general idea is same as this andeoid code i guess.. |
| 06:43.02 | cmonex | the above is what i get from datasheet? |
| 06:44.14 | cr2 | you will know what is the meaning of the values, and how to set them. |
| 06:44.30 | cmonex | how to set them is easy |
| 06:44.37 | cr2 | i think we can only document the known values for the known panels. nothing more |
| 06:44.39 | cmonex | send mddi commands (like the ones in raphaelmddi wiki) |
| 06:44.51 | cmonex | well that's bad because this panel is operating at 640x480 now |
| 06:44.52 | cr2 | not only the mddi |
| 06:44.58 | cmonex | and i want to tell it to do 800x480 |
| 06:45.13 | cr2 | some of these "mddi" commands are spi commands to the panel |
| 06:45.19 | cmonex | the lcd is 800x480, but current code leaves black borders at the right and left |
| 06:45.23 | cmonex | oh, i dont care about spi |
| 06:45.29 | cr2 | so you need to have the panel datasheet |
| 06:45.32 | cmonex | i have the function to call with command and value parameters |
| 06:45.37 | cmonex | (but it isnt spi, anyway) |
| 06:45.59 | cr2 | the spi commands are not documented even for the lcd panel of openmoko |
| 06:46.01 | cmonex | ok, how do i find out what panel it is |
| 06:46.06 | cmonex | all i know its CPT |
| 06:46.11 | cmonex | i dont care about spi commands :) |
| 06:46.34 | cr2 | the toshiba/epson have gpios to detect the panel |
| 06:46.39 | cr2 | you must care :) |
| 06:46.48 | cmonex | not really, as these dont use spi |
| 06:46.55 | cr2 | because the panel resolution is set over i2c/spi |
| 06:47.06 | cmonex | not here |
| 06:47.19 | cr2 | well, without the datasheet, how do you know ? |
| 06:47.23 | cmonex | SPL disassembly |
| 06:47.38 | cmonex | I see where it sets up resolution |
| 06:47.51 | cmonex | and I can tinker with it but I dont exactly know these PCLK things, so..it is not good yet :) |
| 06:47.54 | cr2 | you can set your HSW/etc values, but the panel needs to know how to interpret them |
| 06:48.02 | cmonex | I enabled the 800x480 but no image on it yet .) |
| 06:48.31 | cmonex | i can see even small error in value can be bad... |
| 06:49.12 | cmonex | what did yo mean by your last line ? |
| 06:49.40 | cr2 | take a "usual" tft panel |
| 06:50.01 | cr2 | you can set 2048x1536 resolution for your output |
| 06:50.16 | cr2 | but if it has only 1024x768 hardware pixels |
| 06:50.44 | cr2 | then it should downscale your data somehow |
| 06:51.14 | cr2 | so it depends on the capabilities of the controller in thje panel itself |
| 06:51.15 | cmonex | this has 800x480 hardware pixels. |
| 06:51.24 | cr2 | which is controlled over spi i think. |
| 06:51.24 | cmonex | let me explain again ... |
| 06:51.29 | cr2 | ok |
| 06:51.31 | cmonex | as i said above: the lcd is 800x480, but current code leaves black borders at the right and left |
| 06:51.38 | cmonex | so only uses 640x480 |
| 06:51.45 | cr2 | ok |
| 06:51.47 | cmonex | 80 pixel black at left, 80 at right |
| 06:52.19 | cr2 | i mean that it can be done in hardware |
| 06:52.25 | cmonex | so now, if i play with these values like HCYCLE, etc... then i get 800x480 activated, however image is corrupt, so far anyway. I see a small change in the right value causes big problems. so not easy to find right ones |
| 06:52.25 | cr2 | by sending the spi commands |
| 06:54.05 | cmonex | argh |
| 06:54.09 | cmonex | what do you call spi command? |
| 06:54.24 | maejrep | cmonex: did you see the discussion tmzt and i had last night after you left? |
| 06:54.30 | cmonex | nope, maejrep |
| 06:54.38 | cmonex | dcc-chat it over or pastebin.com it |
| 06:54.44 | cr2 | the controller on the panel can support multiple resolutions, and multiple color depths |
| 06:54.49 | cmonex | cr2, thats cool. |
| 06:54.50 | maejrep | the diagram of clock timings explains what the values represent |
| 06:54.59 | cmonex | current code sets 65K colours, and i dont care about that part |
| 06:55.03 | cmonex | (i think it can do more) |
| 06:55.12 | cmonex | well maejrep if you could pastebin the convo |
| 06:55.19 | maejrep | and that was why I initially talked about xorg modelines, because the modeline takes all those parts into consideration to give you the resolution you want |
| 06:55.50 | cr2 | so you can send an spi command "switch to qvga" on a vga panel, for example |
| 06:56.03 | cmonex | it doesnt send such a command |
| 06:56.05 | cr2 | it all depends on the controller capabilities |
| 06:56.08 | cmonex | in the current spl |
| 06:56.13 | maejrep | cmonex: http://www.privatepaste.com/be0SUtCJt9 |
| 06:56.16 | maejrep | pdf is on 4th line |
| 06:56.24 | cr2 | then you can change the timing as much as you lkike, but you can't have vga... |
| 06:56.38 | cmonex | <maejrep> so my linking to an xorg modeline generator was pretty much accurate ;) |
| 06:56.40 | cmonex | eh what was the link? |
| 06:56.52 | cmonex | cr2: why are you not reading me. |
| 06:56.55 | maejrep | http://xtiming.sourceforge.net/cgi-bin/xtiming.pl |
| 06:56.55 | cmonex | I have vga |
| 06:57.02 | cmonex | I want wvga which the panel can and will do |
| 06:57.30 | cmonex | maejrep, wish i knew pixel clock value. |
| 06:57.34 | cr2 | cmonex: i'm reading :) but are you sure that the panel is in wvga mode ? |
| 06:57.44 | cmonex | cr2: dunno what you mean |
| 06:58.00 | cmonex | what i got so far is 800x480 screen but no prope image |
| 06:58.02 | cmonex | proper* |
| 06:58.07 | cmonex | with patches |
| 06:58.35 | cr2 | the timing / pixclock may depend on the mode |
| 06:59.07 | cmonex | so this is why it didnt give proper not garbled image eh? |
| 06:59.40 | cr2 | maybe |
| 06:59.50 | cr2 | how can one know without the docs ? |
| 07:01.45 | cmonex | do you have docs for android code ? |
| 07:01.56 | cmonex | thats good enough to me |
| 07:02.03 | cr2 | no |
| 07:03.56 | cmonex | too bad |
| 07:03.59 | cmonex | do they exist publicly ? |
| 07:04.59 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 07:05.02 | Untouchab1e | Good morning :) |
| 07:06.50 | cmonex | hi |
| 07:07.02 | Untouchab1e | How's things? |
| 07:13.33 | *** join/#htc-linux kiozen (n=oeichler@p5492239F.dip0.t-ipconnect.de) |
| 07:14.10 | *** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
| 07:17.16 | *** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 07:22.26 | *** join/#htc-linux ewasx (n=Armin@armin-dev.ict.tno.nl) |
| 07:25.37 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-210-229.bak.res.rr.com) |
| 07:33.38 | *** join/#htc-linux timebomb (n=tb@e176116067.adsl.alicedsl.de) |
| 07:39.27 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 07:40.21 | *** join/#htc-linux kiozen (n=oeichler@p5492239F.dip0.t-ipconnect.de) |
| 07:42.38 | *** join/#htc-linux opennandra (n=opennand@80.122.179.98) |
| 07:45.27 | opennandra | good morinig |
| 07:47.30 | Untouchab1e | Good morning |
| 07:49.26 | opennandra | I'm trying to run kernel on htc oxygen (omap850) |
| 07:49.38 | opennandra | I get branch from linwizard |
| 07:49.53 | opennandra | and try to add board and lcd specific stuff |
| 07:50.06 | opennandra | it's necessary to add something else? |
| 08:02.13 | tmzt | opennandra: you want to ask in #linwizard |
| 08:02.27 | tmzt | have you dumped omapfb timings? |
| 08:02.32 | opennandra | yes |
| 08:02.55 | opennandra | but still with no success |
| 08:03.11 | opennandra | what I see is only some colours on display :) |
| 08:03.19 | opennandra | no readable text |
| 08:03.40 | tmzt | cmonex: I see what cr2 is saying, if it's not in wvga that would explain vista corruption wouldn't it? |
| 08:05.32 | tmzt | by the way, the spi we are talking about is not from msm cpu, it's from the toshiba chip |
| 08:05.51 | tmzt | or microp (atmel) we don't know which on your hardware I think |
| 08:06.08 | tmzt | sorry, shift probably has no microp |
| 08:06.59 | tmzt | when you say you know where it sets the resolution, you are talking about the BITMAP0 and these other paramters from last night? |
| 08:08.46 | tmzt | not sure pixel clocks matters much since the other values are relative to it, on pxa it's usually a set value and not hw specific |
| 08:08.55 | *** join/#htc-linux grojules (n=5b974d4e@lon92-8-88-165-13-120.fbx.proxad.net) |
| 08:09.15 | tmzt | have you looked at p12 of that pdf? |
| 08:09.54 | tmzt | you can answer tomorrow if want, I will read the log |
| 08:38.39 | *** join/#htc-linux ionstorm (n=ion@ip68-227-227-148.ph.ph.cox.net) |
| 08:47.52 | NetRipper | maejrep, it was fyi ;) i did it all by myself ;) |
| 08:48.18 | NetRipper | but i got stuck on the input devices that werent handled by android |
| 08:48.49 | NetRipper | but balsat may have a point.. as it does seem x=0 y=0 is reported instead of the actual position |
| 08:49.04 | tmzt | PSPdemon: yes, that is mostly in #linwizard |
| 08:51.33 | tmzt | NetRipper: the power thing? |
| 08:51.57 | tmzt | anyone see that in android git? this make no sense |
| 08:52.03 | tmzt | s/make/makes/ |
| 08:52.19 | Untouchab1e | Good morning Maejrep! |
| 08:52.41 | NetRipper | tmzt, im having trouble finding the 'android power management' kernel module |
| 08:52.41 | NetRipper | ;) |
| 08:53.01 | tmzt | I think its driver/android/pm.c |
| 08:54.04 | NetRipper | there is no drivers/android in .27 |
| 08:55.14 | Untouchab1e | Ooh! are we working on power management now? |
| 08:55.21 | NetRipper | no |
| 08:55.24 | Untouchab1e | hehe |
| 08:55.35 | NetRipper | android is not working properly on .27 |
| 08:55.45 | Untouchab1e | oh, thought we got it booted and running? |
| 08:55.47 | NetRipper | fixed that graphics issue i mentioned before |
| 08:55.55 | Untouchab1e | nice! |
| 08:56.04 | NetRipper | there's a difference between booting and running, and working properly |
| 08:56.04 | NetRipper | ;) |
| 08:56.20 | Untouchab1e | true, true |
| 08:56.36 | tmzt | on raph100? |
| 08:56.40 | tmzt | what graphics issue? |
| 08:56.58 | Untouchab1e | what about the WiFi driver? Last time I heard, (which wasnt yesterday, as I took my birthday off), you were getitng close? |
| 08:58.31 | tmzt | maejrep was I think |
| 08:58.43 | tmzt | all down to userspace maybe |
| 08:59.50 | NetRipper | tmzt, on .27 the msm_fb would timeout during pan updates |
| 09:00.03 | NetRipper | not in console, but when starting any grahpical environment |
| 09:00.13 | NetRipper | android/x |
| 09:00.44 | tmzt | so they changed the panning or we just didn't update the driver to work with the yoffset method? |
| 09:01.14 | NetRipper | i checked the android git, but there are no changes to the msmfb that fix this problem |
| 09:01.23 | NetRipper | so i guess they're not facing the same issue.. |
| 09:01.36 | tmzt | what was the fix? |
| 09:01.39 | NetRipper | see git |
| 09:01.45 | NetRipper | just resetting a state |
| 09:02.03 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commitdiff;h=e0a4e761225b85486b8630d6646561529e65627f |
| 09:02.12 | NetRipper | first 5 lines |
| 09:02.26 | tmzt | ah |
| 09:02.42 | NetRipper | it's hard to imagine this driver does work for android |
| 09:02.44 | NetRipper | or in g1 |
| 09:03.21 | tmzt | how different is trout msmfb? |
| 09:03.27 | NetRipper | this is the trout msmfb |
| 09:03.40 | tmzt | upstream android 2.6.27 |
| 09:03.42 | NetRipper | yes |
| 09:04.10 | NetRipper | difference between our msmfb and the latest msmfb is that they applied a vsync fix... i tried that but it didn't fix this issue ;) |
| 09:04.47 | tmzt | does this work with android then? |
| 09:04.52 | NetRipper | yes |
| 09:05.17 | NetRipper | but next problem is that android doesn't read the touchscreen properly anymore |
| 09:05.34 | NetRipper | hence the PM |
| 09:05.39 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-205-227.web.vodafone.de) |
| 09:05.41 | NetRipper | but i have PM enabled in the kernel |
| 09:05.41 | tmzt | why is it setting msmfb->sleeping to FULL_UPDATE_DONE before the work is executed? |
| 09:05.47 | tmzt | cr2: hey |
| 09:06.12 | NetRipper | tmzt, because the full update is actually done when that function is entered.. it's the callback function after the dma is finished |
| 09:06.18 | NetRipper | the work does not do the full update |
| 09:06.33 | tmzt | ok |
| 09:08.57 | tmzt | there's no point in the #if defined( if you get the size from msmfb is there? |
| 09:09.01 | tmzt | (your url) |
| 09:09.15 | tmzt | and what does #if defined mean anyway?? |
| 09:09.16 | NetRipper | the hack shouldn't be there at all |
| 09:09.26 | NetRipper | defined() is a macro |
| 09:09.34 | tmzt | ok |
| 09:09.52 | tmzt | so you use if when doing || && or whatever |
| 09:09.57 | tmzt | makes sense |
| 09:10.05 | NetRipper | #if defined() vs #ifdef is #ifdef only checks for one define... #if can have a proper logirithmic |
| 09:10.21 | NetRipper | indeed |
| 09:11.11 | NetRipper | the hack is still there because it's needed for X to work |
| 09:11.15 | cr2 | tmzt: lol. i'm sitting in a project meeting now :) |
| 09:11.21 | tmzt | ok, sorry |
| 09:11.24 | NetRipper | hi cr2 ;) |
| 09:11.31 | NetRipper | greetings to them |
| 09:11.31 | NetRipper | ;) |
| 09:11.33 | cr2 | hi NetRipper |
| 09:11.48 | cr2 | umts is evil :) |
| 09:11.57 | NetRipper | or a relieve |
| 09:12.47 | cr2 | NetRipper: can we optimize the ram layout ? |
| 09:13.13 | NetRipper | you mean using the trout defines? |
| 09:14.16 | cr2 | no |
| 09:14.44 | cr2 | using lower sdram bank only |
| 09:15.00 | cr2 | as it now, but with a better layout |
| 09:15.05 | NetRipper | aha |
| 09:16.16 | cr2 | NetRipper: and remove the TROUT* from board-htcraphael.h |
| 09:16.21 | NetRipper | yes |
| 09:16.24 | NetRipper | still do that |
| 09:16.26 | NetRipper | will* |
| 09:16.33 | cr2 | ok |
| 09:16.49 | NetRipper | but you also suggested to take the other defines from board-trout.h |
| 09:16.58 | NetRipper | i thought that's what you meant by ram layout |
| 09:17.11 | cr2 | this is too uncertain |
| 09:17.25 | *** join/#htc-linux timebomb (n=tb@e176116067.adsl.alicedsl.de) |
| 09:17.37 | cr2 | we need a reliable way to autodetect the sram size |
| 09:17.44 | cr2 | first |
| 09:17.58 | cr2 | otherwise you will simply crash and burn |
| 09:18.19 | cr2 | NetRipper: i have found the 115200 clock timing for BT |
| 09:18.28 | cr2 | need to look for the 4Mbit though. |
| 09:18.31 | NetRipper | ok |
| 09:18.42 | cr2 | but we may try to enable the serial_hs |
| 09:20.53 | *** join/#htc-linux daspsycho_work (n=TimJorda@213.155.79.202) |
| 09:24.38 | *** join/#htc-linux [1]Untouchab1e (n=Untoucha@82.147.51.146) |
| 09:25.22 | NetRipper | cr2, didn't you already try that? |
| 09:30.17 | NetRipper | cr2, so, how do we optimize memory layout? |
| 09:37.45 | *** join/#htc-linux dcordes-x1 (n=drcordes@ip-77-25-18-255.web.vodafone.de) |
| 09:38.06 | dcordes-x1 | hi |
| 09:39.07 | NetRipper | hi |
| 09:39.10 | NetRipper | x1 ;) |
| 09:40.01 | NetRipper | back to work, late |
| 09:48.39 | cr2 | NetRipper: try to extend the 76MB value first |
| 09:54.22 | *** join/#htc-linux [1]Untouchab1e (n=Untoucha@82.147.51.146) |
| 10:02.49 | NetRipper | cr2, extend, to what? you want to see how far we can go? |
| 10:03.25 | NetRipper | offsets for MDP/ADSP are variable and will move too |
| 10:04.14 | NetRipper | what do EBI and MDP mean? |
| 10:04.28 | NetRipper | are these all virtual addresses? |
| 10:04.34 | NetRipper | iomaps |
| 10:04.47 | NetRipper | if not EBI_BASE is the first memory bank |
| 10:05.16 | NetRipper | enlarging it make it closer to smem |
| 10:25.39 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 10:26.44 | cr2 | EBI1 and SMI is fixed, you can't change them |
| 10:26.58 | cr2 | thy belong to msm*io.h |
| 10:27.42 | cr2 | MDP is the preallocaqtedarea the display processor |
| 10:28.07 | cr2 | smem is in SRAM |
| 10:28.11 | cr2 | aka SMI |
| 10:29.37 | NetRipper | ok |
| 10:29.40 | *** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215) |
| 10:29.48 | NetRipper | i cant increase the LINUX_SIZE |
| 10:30.14 | NetRipper | it'll change the offsets for MDP/ADSP/GPU1/FB |
| 10:31.48 | NetRipper | (and they cant overlap) |
| 10:32.03 | NetRipper | when i use the trout value for LINUX_SIZE |
| 10:32.08 | NetRipper | it boots, but i get a white screen |
| 10:32.12 | NetRipper | i.e. fb doesn't work anymore |
| 10:33.29 | NetRipper | didn't crash though, navi lights were still responsive ;) |
| 10:41.05 | cr2 | you should not push the LINUX_SIZE too high |
| 10:41.29 | cr2 | because the other preallocated areas can't go above 128M in your case |
| 10:44.40 | *** join/#htc-linux Mahr (n=Mahr@user228.85-195-57.netatonce.net) |
| 10:45.34 | Mahr | Hey, I have a HTC Touch Diamond (Swedish 3g, The operator is 3) and I was wondering if it's safe to try out android 1.0 on it using the Raphael Linux howto? |
| 10:45.52 | Mahr | This one: wiki.xda-developers.com |
| 10:53.52 | *** join/#htc-linux MethoS- (n=lem@host-091-096-212-155.ewe-ip-backbone.de) |
| 10:56.31 | NetRipper | right |
| 11:02.50 | NetRipper | cr2, we'll also need a way to detect whether or not there's a second memory bank |
| 11:08.44 | *** join/#htc-linux azenned (n=azenned@41.224.152.156) |
| 11:38.22 | *** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215) |
| 11:47.54 | *** join/#htc-linux ChanServ (ChanServ@services.) |
| 11:47.54 | *** mode/#htc-linux [+o ChanServ] by irc.freenode.net |
| 12:05.51 | *** join/#htc-linux bs2 (n=kra@87.72.13.87) |
| 12:10.15 | *** join/#htc-linux metter (n=metter@1-173.203-62.cust.bluewin.ch) |
| 12:10.28 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-111-32.web.vodafone.de) |
| 12:12.56 | cr2 | NetRipper: yes, but it's an easier task |
| 12:17.03 | *** join/#htc-linux timebomb (n=tb@p5B3E6B69.dip.t-dialin.net) |
| 12:22.53 | *** join/#htc-linux timebomb (n=tb@p5B3E70DF.dip.t-dialin.net) |
| 12:35.45 | azenned | hi, |
| 12:36.16 | miknix | azenned, http://wiki.xda-developers.com/index.php?pagename=HTC_Pharos |
| 12:36.46 | azenned | yes , i read it. |
| 12:36.56 | miknix | http://wiki.xda-developers.com/index.php?pagename=PHAROS%20Dump%20Process |
| 12:37.22 | azenned | what about spi interface? |
| 12:37.39 | miknix | you should create a page about it |
| 12:38.06 | azenned | create a page ?!! |
| 12:38.10 | miknix | its a wiki |
| 12:38.36 | miknix | I have to go now |
| 12:39.04 | azenned | please , what about the spi |
| 12:39.40 | NetRipper | cr2, for kaiser they havent bridged the memory gap either yet |
| 12:39.56 | NetRipper | somehow they enable the second memory bank, but don't use it |
| 12:41.48 | miknix | azenned, addlist traces p2v(0xfffc1000) 0 16 |
| 12:42.12 | miknix | 0xfffc1000 is the base address |
| 12:42.23 | miknix | sorry, I have to go |
| 12:42.31 | azenned | thanks |
| 12:48.39 | azenned | can some one help me to find toochscreen driver to my htc pharos P3470 |
| 12:49.54 | *** join/#htc-linux MethoS-- (n=lem@host-091-096-215-093.ewe-ip-backbone.de) |
| 12:59.02 | azenned | any ideas about HTC pharos toochscreen? |
| 12:59.24 | *** join/#htc-linux goxboxlive1 (n=goxboxli@mail2.hjellnesconsult.no) |
| 13:01.19 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
| 13:06.58 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 13:07.00 | Untouchab1e | Hi all |
| 13:07.25 | azenned | hi |
| 13:09.24 | Untouchab1e | Hows it going? |
| 13:17.17 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-042.ewe-ip-backbone.de) |
| 13:55.36 | *** join/#htc-linux opennandra (n=opennand@80.122.179.98) |
| 13:58.50 | cr2 | NetRipper: they create an artificial hole in the first bank to take care of ram corruption |
| 14:18.24 | *** join/#htc-linux wmu (n=wmu@88.104.92-79.rev.gaoland.net) |
| 14:18.30 | wmu | hello |
| 14:20.49 | wmu | i try android with my kaiser but i don't was operator phone |
| 14:20.57 | *** part/#htc-linux daspsycho_work (n=TimJorda@213.155.79.202) |
| 14:21.52 | wmu | i try any more versions of android 1.31, 1.23 and 2.1 but i boot with haret is ok but not connect to my operator mobile |
| 14:22.13 | wmu | i try that with any version of radio and nothing |
| 14:37.30 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-111-32.web.vodafone.de) |
| 14:44.51 | *** join/#htc-linux myxor (n=myxor@pdbn-4d089f90.pool.mediaWays.net) |
| 14:48.02 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 14:57.04 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-036.ewe-ip-backbone.de) |
| 15:07.31 | *** join/#htc-linux MethoS- (n=lem@host-091-097-244-036.ewe-ip-backbone.de) |
| 15:24.12 | *** part/#htc-linux azenned (n=azenned@41.224.152.156) |
| 15:25.38 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-11f7e2968bf115ae) |
| 15:36.57 | *** join/#htc-linux ykut_johny (n=ykut_joh@op.niser.org.my) |
| 15:55.32 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 16:04.43 | *** join/#htc-linux zenned (n=chatzill@41.224.152.156) |
| 16:09.35 | *** join/#htc-linux zycho_ (n=zycho@a89-182-14-89.net-htp.de) |
| 16:11.48 | AstainHellbring | morning |
| 16:17.14 | *** join/#htc-linux exco (n=exco@e181104221.adsl.alicedsl.de) |
| 16:17.15 | *** part/#htc-linux exco (n=exco@e181104221.adsl.alicedsl.de) |
| 16:17.17 | *** join/#htc-linux exco (n=exco@e181104221.adsl.alicedsl.de) |
| 16:39.51 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
| 17:07.53 | *** join/#htc-linux goxboxlive (n=goxboxli@185.84-48-126.nextgentel.com) |
| 17:22.33 | *** join/#htc-linux AstainHellbring (n=AstainHe@206.71.78.158) |
| 17:23.11 | *** join/#htc-linux AstainZZZZZZ (n=AstainHe@unaffiliated/astainhellbring) |
| 17:26.33 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
| 17:28.24 | *** join/#htc-linux zenned_ (n=chatzill@41.224.222.47) |
| 17:35.44 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 17:42.55 | *** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215) |
| 17:51.24 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
| 17:56.03 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
| 18:16.23 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
| 18:30.54 | *** join/#htc-linux miknix_ghost (n=miknix@bl9-97-140.dsl.telepac.pt) |
| 18:43.34 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
| 18:46.13 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 18:46.16 | Untouchab1e | Good evening |
| 18:53.53 | *** join/#htc-linux zenned (n=chatzill@41.224.99.25) |
| 19:19.00 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c2f1.pool.einsundeins.de) |
| 19:26.08 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
| 19:36.19 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 19:46.27 | *** join/#htc-linux TheOther (n=nahh@108.84-49-166.nextgentel.com) |
| 19:50.35 | Balsat | Evening... Any news on the PM (ts) error? |
| 20:01.12 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-103-42.web.vodafone.de) |
| 20:05.30 | *** join/#htc-linux MethoS-- (n=lem@dyndsl-085-016-166-051.ewe-ip-backbone.de) |
| 20:10.55 | *** join/#htc-linux hd|3 (i=5d687528@gateway/web/ajax/mibbit.com/x-51cda6530e47debf) |
| 20:12.14 | j0b0 | balsat what is the pm(ts) error? |
| 20:15.55 | Balsat | The Touch screen driver returns x=0, y=0 because of a missing Power management driver (according to the people on google) |
| 20:18.36 | *** join/#htc-linux Xime (n=xime@bankize.net) |
| 20:19.02 | j0b0 | hmm.. is it in the touchscreen driver or in the input sub system |
| 20:23.14 | Balsat | The vkeyb is working, so it must be the sub system |
| 20:23.35 | j0b0 | ..is what i was thinking |
| 20:26.42 | cr2 | Balsat: lol. |
| 20:29.18 | j0b0 | also, the leds on the navi light up as expected but when i press a button they go weird |
| 20:29.20 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-161-152.ewe-ip-backbone.de) |
| 20:29.30 | j0b0 | merely touching does not report any events |
| 20:30.56 | cr2 | j0b0: ts_test ? or the 'od -x /dev/input/eventX' ? |
| 20:31.55 | j0b0 | i mean touching the navi. the driver lights up the leds where you touch it but doesnt post events until you press it |
| 20:31.57 | *** join/#htc-linux opennandra (n=opennand@afrodita.advanet.sk) |
| 20:32.29 | opennandra | what happened with #htcwizard channel? Anybody know? |
| 20:33.34 | j0b0 | which is the same situation as the vkeyb working (lighting up the red keys and being draggable) but not the ts |
| 20:33.55 | j0b0 | so what we read from the hardware and post to the kernel is correct, but what comes out the other end (sorry) is not |
| 20:34.48 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 20:41.41 | *** join/#htc-linux Tinyboom (n=nahh@108.84-49-166.nextgentel.com) |
| 20:52.37 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 20:53.47 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 20:55.54 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
| 21:04.33 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-161-152.ewe-ip-backbone.de) |
| 21:06.27 | cmonex | [09:01:41] <tmzt> cmonex: I see what cr2 is saying, if it's not in wvga that would explain vista corruption wouldn't it?รป |
| 21:06.32 | cmonex | tmzt: nope. |
| 21:06.39 | cmonex | when I lowered VCYCLE by a bit |
| 21:06.45 | cmonex | the corruption was fixed, it was no more. :) |
| 21:06.54 | cmonex | [09:04:59] <tmzt> when you say you know where it sets the resolution, you are talking about the BITMAP0 and these other paramters from last night? |
| 21:06.54 | cmonex | [09:06:47] <tmzt> not sure pixel clocks matters much since the other values are relative to it, on pxa it's usually a set value and not hw specific |
| 21:07.21 | cmonex | BITMAP0, H/V-CYCLE, H/V-SW, H/V-DE_START, H/V-DE_SIZE |
| 21:13.45 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 21:13.48 | *** join/#htc-linux MethoS-- (n=lem@host-091-096-209-077.ewe-ip-backbone.de) |
| 21:15.20 | *** join/#htc-linux cmonexaway (n=xy6091@ognf7eohno.adsl.datanet.hu) |
| 21:20.27 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 21:24.12 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c2f1.pool.einsundeins.de) |
| 21:28.28 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c2f1.pool.einsundeins.de) |
| 21:51.55 | *** join/#htc-linux dcordes (n=dcordes_@f049173208.adsl.alicedsl.de) |
| 21:54.54 | *** join/#htc-linux DJWillis (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
| 21:59.36 | cr2 | NetRipper: the htc spec and service manual say raph has 32MB sram |
| 22:05.18 | dcordes | " |
| 22:07.46 | cr2 | dcordes: http://forum.xda-developers.com/showthread.php?t=452077 |
| 22:09.26 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 22:12.21 | dcordes | cr2, should I try it on the kovsky? |
| 22:14.07 | dcordes | cr2, what is the tv out? is it wired to the usb or is it the extra pins? |
| 22:17.29 | *** join/#htc-linux MrFeetio (n=MrFeetio@pool-98-117-23-186.hrbgpa.fios.verizon.net) |
| 22:18.08 | cr2 | it's on the extra pins |
| 22:18.18 | dcordes | :-( |
| 22:23.31 | *** join/#htc-linux acsviluppo (n=acsvilup@151.67.30.84) |
| 22:27.04 | *** join/#htc-linux diggle (n=diggle@host81-158-29-169.range81-158.btcentralplus.com) |
| 22:34.22 | *** join/#htc-linux smile30 (n=ruisilva@88.210.115.127.rev.optimus.pt) |
| 22:36.41 | smile30 | join #htc-linux |
| 22:39.00 | cmonex | dcordes what do you want to try on kovsky? |
| 22:39.33 | cmonex | that usb on raphael is neat, if it can do 1) usb sync 2) usb host 3) serial 4) tvout 5) headset.. |
| 22:39.42 | cmonex | by the way xperia usb is different, right? |
| 22:39.59 | dcordes | cmonex, yea afaik I doesn't have the extra (extusb) pins |
| 22:40.06 | cmonex | clearly |
| 22:40.08 | cmonex | the raphael sync cable will not fit it |
| 22:40.20 | cmonex | though that may be unrelated :) |
| 22:40.23 | cmonex | hmm, though, |
| 22:40.32 | cmonex | i would like serial working with it... |
| 22:40.44 | cmonex | because then you can unbrick it if you killed SPL |
| 22:40.48 | dcordes | what about the headset remote control? |
| 22:41.01 | cmonex | for raphael its possible to build serial cable that plugs to the usb port and then access radio bootloader without spl |
| 22:41.22 | dcordes | yes dream_kill mentioned that |
| 22:41.27 | cmonex | neat eh |
| 22:41.33 | cr2 | cmonex: is the pinout known ? and the voltage levels |
| 22:41.46 | cmonex | yes see revskills.de forum |
| 22:41.52 | cr2 | ok |
| 22:41.56 | cmonex | i will ask viper if he has tried building it yet :) |
| 22:42.02 | cmonex | also, how do you know dreamkill built it :D |
| 22:42.04 | cr2 | i guess you can access uart1 as on g1 |
| 22:42.06 | cmonex | know = think |
| 22:42.11 | cr2 | hehe |
| 22:42.16 | cmonex | he built it for raphael and it worked fine |
| 22:44.14 | dcordes | cmonex, I probably confused it with kais |
| 22:45.04 | dcordes | cmonex, do you have the cheapo plastic xperia? |
| 22:45.38 | cmonex | dcordes i have no idea what you mean :) |
| 22:45.54 | cmonex | didnt know there was a plastic version :) |
| 22:47.00 | cr2 | http://forum.revskills.de/download/file.php?id=78 |
| 22:47.11 | cr2 | looks good. 3.3v uart probably |
| 22:47.39 | cmonex | dcordes ? |
| 22:48.14 | dcordes | cmonex, every version has plastic parts |
| 22:48.34 | cmonex | [07:59:46] <cmonex> do you have docs for android code ? |
| 22:48.34 | cmonex | [07:59:56] <cmonex> thats good enough to me |
| 22:48.34 | cmonex | [08:00:04] <cr2> no |
| 22:48.35 | cmonex | [08:01:56] <cmonex> too bad |
| 22:48.35 | cmonex | [08:02:00] <cmonex> do they exist publicly ? |
| 22:48.41 | cr2 | hehe. ok, so it's probably the alt=4, but needs to be checked. |
| 22:48.50 | cr2 | cmonex: afaik no. |
| 22:48.51 | cmonex | dcordes: so? what did you mean by your question....? |
| 22:48.55 | cmonex | cr2 thx |
| 22:50.10 | dcordes | cmonex, http://forum.xda-developers.com/showthread.php?t=447211 |
| 22:50.49 | cmonex | hm nope i dont have that issue with either of my xperias |
| 22:51.23 | cmonex | also i dont have the paint peeling off even though they're black xperias :) |
| 22:51.29 | cmonex | the trick is simple |
| 22:51.30 | dcordes | probably because you have them at home for cracking spls etc |
| 22:51.36 | cmonex | dont carry it together with your keys |
| 22:51.39 | dcordes | I used it for one week as my day to day phone then it cracked. |
| 22:51.42 | cmonex | no, i use one of them as main phone |
| 22:51.49 | cmonex | been using it since late december |
| 22:51.49 | cmonex | :) |
| 22:52.35 | dcordes | well lucky. you picked one with the good plastic I suppose |
| 22:55.55 | dcordes | cmonex, you think the two missing data pins are on the audio jack? |
| 22:56.09 | dcordes | used for the remote |
| 22:57.47 | cmonex | i picked TWO |
| 22:57.48 | cmonex | hehe |
| 22:57.55 | cmonex | one of them is a prototype from january 2008 :) |
| 22:58.03 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-167-175.ewe-ip-backbone.de) |
| 22:58.07 | cmonex | maybe the same one I saw in barcelona at 3gsm :) |
| 22:58.23 | cmonex | dunno about audio..what data pins are you asking about? |
| 23:06.05 | dcordes | cmonex, th ones that on raphael diamond etc have the serial video and whatnot |
| 23:06.40 | *** join/#htc-linux MrFeetio- (n=MrFeetio@pool-98-117-23-186.hrbgpa.fios.verizon.net) |
| 23:07.03 | *** join/#htc-linux MethoS- (n=lem@dyndsl-085-016-167-175.ewe-ip-backbone.de) |
| 23:09.57 | cr2 | dcordes: rs232,audio,video,usb host/client |
| 23:10.54 | cmonex | dcordes: yeahm, dunno about it |
| 23:11.14 | cr2 | there is some wizardrx going on there, like on g1 because of the pin mux |
| 23:11.17 | cr2 | http://forum.xda-developers.com/attachment.php?attachmentid=111350&stc=1&d=1220703129 |
| 23:13.23 | *** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au) |
| 23:15.31 | dcordes | cr2, kovsky can at least provide what A-E, 1, 2, 5, 6 in that pinout provides |
| 23:15.43 | dcordes | because it has the normal usb and a headset connector |
| 23:15.51 | dcordes | I could imagine it's the same internal wiring |
| 23:18.27 | *** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com) |
| 23:19.02 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 23:21.59 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 23:28.24 | *** part/#htc-linux acsviluppo (n=acsvilup@151.67.30.84) |
| 23:29.49 | cr2 | dcordes: "Touch driver stores touch screen calibration data to MFG persistant partition now and re-loads it on a cold boot." |
| 23:30.39 | dream_kill | hi guys |
| 23:30.55 | dcordes | cr2, what's MFG again? if we can do it we can get rid of the calibration on each boot? |
| 23:30.57 | dcordes | hi DracoDan |
| 23:31.00 | dcordes | dream_kill, |
| 23:31.32 | dream_kill | MFG is a hidden partition in nand |
| 23:31.53 | dream_kill | the HTC store in it some nvram stuff needed for SPL |
| 23:32.18 | dream_kill | for example if the phone should allways boot in spl |
| 23:32.30 | dream_kill | if is a cold boot...etc |
| 23:32.42 | dream_kill | but 80% of the space there seems unused :D |
| 23:32.56 | cr2 | dream_kill: all htc docs say that raph has 32MB smem |
| 23:33.17 | cr2 | while g1 has 64 ;) |
| 23:33.26 | dream_kill | nice |
| 23:33.48 | cr2 | ans some spls have a detection code for 32 vs 64 |
| 23:34.01 | cr2 | but they only check some 0x1f* location |
| 23:34.24 | dream_kill | aha |
| 23:34.51 | dream_kill | cmonex did u build the cable yet :P ? |
| 23:35.24 | dream_kill | or u have trouble getting a 11 pins miniusb :P ? |
| 23:35.52 | dream_kill | told u to use the raph sync cable as it has all 11 pins :D |
| 23:35.57 | dream_kill | just need to cut it open |
| 23:36.07 | dream_kill | and solder the serial lines :D |
| 23:43.59 | NetRipper | cr2, will you document that 32 vs 64 detection? |
| 23:48.14 | *** join/#htc-linux Pure4Real (n=pure4rea@89-97-140-219.ip17.fastwebnet.it) |
| 23:48.28 | *** join/#htc-linux dzo (n=dzo@121-98-128-127.bitstream.orcon.net.nz) |
| 23:48.44 | NetRipper | im off, good night |
| 23:51.49 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
| 23:59.23 | *** join/#htc-linux gw280_ (n=george@195.10.223.142) |