00:25.20 | *** join/#htc-linux ttols (n=ttols@222.117.234.186) |
01:07.40 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
01:10.26 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
01:34.07 | *** join/#htc-linux ALoGeNo (n=alogeno@unaffiliated/alogeno) |
01:51.31 | *** join/#htc-linux ALoGeNo (n=alogeno@unaffiliated/alogeno) |
02:00.47 | *** join/#htc-linux x29a_ (n=x29a@unaffiliated/x29a) |
02:01.44 | *** join/#htc-linux jeremychang (n=jeremych@61-30-10-70.static.tfn.net.tw) |
02:31.38 | *** join/#htc-linux enjalot (n=enjalot@wg-d232025.dsl.fsu.edu) |
02:42.48 | *** join/#htc-linux AstainHellbring (n=AstainHe@174-23-35-109.slkc.qwest.net) |
03:05.14 | *** join/#htc-linux Pandemic187 (n=Bob@134.48.136.235) |
03:05.24 | Pandemic187 | anyone familiar with transferring files via bluetooth? |
03:05.39 | tmzt | with? |
03:05.49 | AstainHellbring | hi |
03:06.02 | tmzt | hello |
03:06.04 | Pandemic187 | what? |
03:06.13 | Pandemic187 | which device? |
03:06.20 | tmzt | from? to? with what software, etc |
03:06.27 | Pandemic187 | to? |
03:06.37 | tmzt | to what device |
03:06.39 | Pandemic187 | oh |
03:06.51 | Pandemic187 | i thought that was some abbreviation |
03:07.02 | Pandemic187 | from my laptop (windows 7) to my kaiser |
03:07.36 | |Jason8| | Pandemic187: sync with activesync |
03:07.39 | |Jason8| | then you can just click and drag |
03:07.58 | Pandemic187 | yeah, but my USB port is broken so i can't. |
03:08.08 | |Jason8| | sync with activesync via bluetooth ;) |
03:08.35 | Pandemic187 | how will that help with file transfer? |
03:11.23 | tmzt | you probably wanted #xda-devs or #ppcgeek |
03:11.32 | tmzt | and yeah, you can browse over activesync/wmdc |
03:12.50 | Pandemic187 | yeah, i was trying to find a more appropriate channel but i didn't know where to look. |
03:13.10 | Pandemic187 | #ppcgeek? |
03:13.13 | Pandemic187 | on this server? |
03:13.29 | Pandemic187 | oh, also, i don't have active sync because i'm on win7. |
03:13.47 | Pandemic187 | oh, yeah, wmdc. |
05:02.29 | *** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no) |
05:13.39 | *** join/#htc-linux mickey|ICE672 (n=M@80.187.210.104) |
05:19.17 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
05:57.20 | *** join/#htc-linux droid0011 (n=g1@p4FDCDF3A.dip.t-dialin.net) |
06:21.40 | *** join/#htc-linux Pandemic187 (n=Bob@134.48.161.210) |
06:39.03 | *** join/#htc-linux mickey|train (n=M@80.187.210.104) |
06:53.32 | *** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz) |
06:57.50 | *** join/#htc-linux JoshuaL (n=JoshuaL@cable-92-43.zeelandnet.nl) |
07:00.30 | *** join/#htc-linux RobRB (i=7d25788a@gateway/web/freenode/x-shfbvcvhbjbeyfnc) |
07:06.54 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
07:10.06 | *** join/#htc-linux docc (n=docc@static.88-198-83-83.clients.your-server.de) |
07:29.59 | *** join/#htc-linux cr2 (n=cr2@ip-109-84-148-219.web.vodafone.de) |
07:30.20 | cr2 | NetRipper: ping |
07:34.46 | BHSPitMonkey | Host unreachable error. |
07:35.34 | *** join/#htc-linux Pandemic187 (n=Bob@134.48.161.210) |
07:36.35 | *** join/#htc-linux kiozen (n=oeichler@p54920F68.dip0.t-ipconnect.de) |
07:44.31 | RobRB | Hey guys, I am currently taking apart a shattered Blackstone that I got for free |
07:45.31 | RobRB | From my experience so far, I want to warn people, I don't think it can be done non-destructively |
07:48.54 | *** join/#htc-linux cr2_ (n=cr2@ip-109-85-95-179.web.vodafone.de) |
07:50.11 | BHSPitMonkey | heh |
07:58.30 | *** join/#htc-linux RobRB (i=7d258042@gateway/web/freenode/x-ibmdmerimeupguej) |
07:59.11 | RobRB | Basically, I'm trying to learn more about the screen |
08:00.19 | RobRB | This HD was destroyed already by its original owner, so I'm losing nothing by opening it |
08:04.45 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
08:16.55 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
08:26.53 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
08:31.40 | *** join/#htc-linux RobRB (i=7d25702f@gateway/web/freenode/x-ztxkqskwlsojtqss) |
08:32.25 | *** join/#htc-linux ycy0 (n=humhum@ANantes-158-1-99-60.w86-199.abo.wanadoo.fr) |
08:33.02 | *** join/#htc-linux hurdman (n=humhum@ANantes-158-1-99-60.w86-199.abo.wanadoo.fr) |
09:02.41 | RobRB | Has anyone written journels about their experience figuring out the interfaces on these devices? I mean is there something for new entrants to follow to get an idea how to approach their device? |
09:17.13 | *** join/#htc-linux aavan (n=aavan@91.183.57.198) |
09:19.06 | aavan | hi everybody |
09:35.05 | RobRB | Hi |
09:35.53 | *** join/#htc-linux balans (n=Administ@212-123-149-239.ip.telfort.nl) |
09:50.46 | *** join/#htc-linux kvaster (n=kvaster@93.84.112.80) |
10:37.46 | *** join/#htc-linux Captnoord (n=Captnoor@145.74.217.223) |
10:38.36 | *** join/#htc-linux kam187 (n=kam187@87-194-204-58.bethere.co.uk) |
10:40.02 | *** join/#htc-linux MethoS- (n=clemens@134.102.106.250) |
10:57.57 | *** join/#htc-linux balans (n=Administ@212.123.149.239) |
11:02.38 | *** join/#htc-linux stamppot (i=d4cb1b12@gateway/web/freenode/x-tekkfznsdhdshbnp) |
11:24.23 | *** join/#htc-linux MiT-MiTiK (n=MiT@194.230.146.22) |
11:25.01 | MiT-MiTiK | !seen tuxhero |
11:26.32 | tmzt | try ~ |
11:26.57 | tmzt | RobRB: irclog.netripper.com |
11:27.04 | MiT-MiTiK | ~seen tuxhero |
11:27.07 | apt | tuxhero <n=tuxhero@122.169.149.130> was last seen on IRC in channel #htc-linux, 16d 16h 39m 7s ago, saying: 'phh, does diamond LCD and Panel Working correctly?'. |
11:27.08 | tmzt | RobRB: what device? |
11:27.10 | MiT-MiTiK | like this ? ghghhg |
11:31.29 | *** join/#htc-linux leobaillard (n=leobaill@leobaillard.org) |
11:32.44 | MiT-MiTiK | ~seen *!*@122.169.149.130 |
11:32.45 | apt | i haven't seen '*!*@122.169.149.130', MiT-MiTiK |
11:33.28 | RobRB | tmzt: Blackstone |
11:34.07 | tmzt | a lot has been done on blak |
11:34.13 | Captnoord | ~seen cr2 |
11:34.14 | apt | cr2 <n=cr2@ip-109-84-148-219.web.vodafone.de> was last seen on IRC in channel #htc-linux, 4h 3m 54s ago, saying: 'NetRipper: ping'. |
11:34.59 | tmzt | looking for tp2 stuff? |
11:35.03 | tmzt | rhod/topa |
11:35.13 | RobRB | And thanks, I've been reading hte irc logs, I was just talking about a more human-readable descriptive journey through the process of discovering a devices GPIO map, then how that is applied to an otherwise rather mature code in the kernel drivers |
11:35.45 | tmzt | what code? |
11:35.50 | RobRB | tmzt: I've noticed that a lot has been done on Blackstone.. so I'm trying to walk myself through some of that work |
11:35.52 | tmzt | gpios are in the wiki |
11:36.19 | RobRB | tmzt: well, right now I'm teaching myself how to do this, using the wiki's, arm docs, etc as guides |
11:36.35 | RobRB | tmzt: Many of them are, not all. |
11:36.40 | tmzt | learn by doing |
11:36.45 | tmzt | ask for help |
11:36.54 | RobRB | tmzt: seems that topaz is there but blackstone's gpio's aren't. |
11:37.23 | tmzt | there are some good discussions in the lo9gs |
11:37.39 | tmzt | yeah, they are very similar to raph100 |
11:38.33 | RobRB | tmzt: I just meant that as an effort to build the wiki, it would be beneficial to write howto's for probing and discovering GPIOs.. or do those lists fall out of the sky? |
11:38.36 | RobRB | :) |
11:39.13 | tmzt | no |
11:39.20 | tmzt | they happen over time |
11:39.26 | RobRB | It seems like there's about 6 months of primer learning that goes into being able to contribute. :) |
11:39.28 | tmzt | mostly tracing in haret |
11:39.40 | tmzt | a new port? |
11:40.03 | tmzt | adding something to blak shouldn't be too difficult |
11:40.33 | RobRB | Yeah, say for example. I'd love to read the steps netripper has gone through from the point of first starting a port to his Leo |
11:41.21 | tmzt | ask him to record those |
11:41.28 | RobRB | :) |
11:41.39 | tmzt | seems he's working on haret right now |
11:41.51 | RobRB | the IRC logs are great, but an index to them, would be awesomly helpful |
11:41.57 | tmzt | next would be codeaurora kernel for q8650 |
11:42.11 | tmzt | site:irclog.netripper.com |
11:43.00 | RobRB | ah, right |
11:43.40 | *** join/#htc-linux DarkMasterHalo (n=DarkMast@modemcable187.118-80-70.mc.videotron.ca) |
11:45.05 | RobRB | tmzt: that's very useful, but only on the condition that someone knows what they are looking for. Hence my pleasure at seeing that there is some getting started documentation underway on the wiki.. but unfortunately its only just been started. |
11:48.40 | tmzt | ask dcordes about an account |
11:48.58 | tmzt | I don't know how else to help you |
11:49.08 | RobRB | :) |
11:49.16 | tmzt | there isn't really a set way to do a new port |
11:49.18 | RobRB | I wasn't really looking for personal help |
11:49.30 | tmzt | except use haret |
11:50.03 | tmzt | dump the ce drivers etc. |
11:50.04 | RobRB | I was making a suggestion that some of the veterans of doing it, document what they've done |
11:50.04 | RobRB | not for me, but for the overall evolution of the process |
11:51.27 | RobRB | my experience is that even the best coders are often weakest at documenting their process, and this has chilling effects on the overall process |
11:59.37 | RobRB | tmzt: thanks for your helpfulness. I'm going to continue studying now. I'm taking a break from the ARM docs to get further along in the HaRET docs. multi-tasking... |
12:03.31 | *** join/#htc-linux x29a_ (n=x29a@unaffiliated/x29a) |
12:04.10 | *** part/#htc-linux RobRB (i=7d25702f@gateway/web/freenode/x-ztxkqskwlsojtqss) |
12:24.26 | Captnoord | lol |
12:24.36 | Captnoord | and again somebody who points coders to the document part |
12:24.37 | Captnoord | lol |
12:29.42 | *** join/#htc-linux azer1 (n=niko@62.72.107.138) |
12:33.11 | *** join/#htc-linux YourDNS (i=7a370f0b@gateway/web/freenode/x-btegzgfvmmbsxifs) |
12:34.13 | *** part/#htc-linux YourDNS (i=7a370f0b@gateway/web/freenode/x-btegzgfvmmbsxifs) |
12:37.57 | *** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) |
13:00.45 | *** join/#htc-linux nantes_geek (n=humhum@ANantes-158-1-156-244.w90-59.abo.wanadoo.fr) |
13:14.03 | *** join/#htc-linux Miek (n=mike@unaffiliated/mikechml) |
13:38.22 | *** join/#htc-linux epsy (i=nobody@dedib.ath.cx) |
14:25.47 | tpr_m900 | hmmm... what the first thing to do with haret ? when machine is not known... |
14:26.08 | tpr_m900 | watch gpios doesnt works |
14:26.12 | tpr_m900 | Minimal virtual address: 00010000, maximal virtual address: 7FFFFFFF |
14:26.12 | tpr_m900 | Detected machine Default/generic (Plat='PocketPC' OEM='M900V030') |
14:26.13 | tpr_m900 | CPU is ARM ARM arch unknown(15) stepping 6 running in system mode |
14:28.27 | Captnoord | tpr_m900: is compile haret with your machine support |
14:28.35 | Captnoord | NetRipper: know info about that I guess..... |
14:28.45 | Captnoord | so does cr2 |
14:28.51 | Captnoord | and someother guys here |
14:29.05 | Captnoord | sometimes you need to add support for your device |
14:31.30 | tpr_m900 | ok tx |
14:31.38 | tpr_m900 | i can do that |
14:34.14 | *** join/#htc-linux itchy8me (n=itchy8me@ip80-116-211-87.adsl2.static.versatel.nl) |
14:39.07 | NetRipper | tpr_m900, what cpu is in that device? |
14:39.52 | tpr_m900 | just began this page: |
14:39.53 | tpr_m900 | http://wiki.xda-developers.com/index.php?pagename=Acer_M900 |
14:40.03 | tpr_m900 | samsung |
14:40.53 | tpr_m900 | like samsung omnia 2 |
14:41.15 | NetRipper | eh? i thought omnia 2 had a much faster cpu |
14:41.43 | NetRipper | think im confused with another device |
14:41.49 | tpr_m900 | yes, mine is 533 |
14:41.54 | tpr_m900 | omnia 2 is 800Mhz |
14:41.56 | NetRipper | ah ok |
14:42.04 | tpr_m900 | but same cpu |
14:42.10 | tpr_m900 | some, maybe.... |
14:42.13 | tpr_m900 | so, maybe |
14:42.18 | NetRipper | does "wirq 1" work? |
14:42.20 | NetRipper | in ahret |
14:42.23 | tpr_m900 | hang up |
14:42.23 | NetRipper | without crashing |
14:42.35 | tpr_m900 | wirq 1, ive a line... hold on |
14:42.53 | tpr_m900 | HaRET(1)# wirq 1 |
14:42.53 | tpr_m900 | irq:800493e8@A03043F8=8102a0ec abort:80082ee0@A03043F0=8102a110 prefetch:80048f58@A03043EC=8102a13c data=80fe9000 sizes=c:000014e4,t:000454e4 |
14:42.53 | tpr_m900 | Beginning memory tracing. |
14:42.53 | tpr_m900 | MMU table merg |
14:43.06 | tpr_m900 | nothing more |
14:43.11 | NetRipper | it crashed there? |
14:43.15 | tpr_m900 | yes |
14:43.16 | NetRipper | ok |
14:44.35 | tpr_m900 | ok, installed cegcc... |
14:49.37 | NetRipper | there's already a git with a kernel that supports your cpu |
14:49.42 | NetRipper | you can get a lot of info from that |
14:49.45 | tpr_m900 | :) |
14:49.47 | NetRipper | http://github.com/leemgs/samsung-s3c6410-android.1.0/ |
14:49.50 | tpr_m900 | =) |
14:50.51 | tpr_m900 | yes, thanks for that |
14:51.02 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
14:51.29 | NetRipper | thank google for that;) |
14:56.15 | tpr_m900 | there is an android device based on this chip |
14:56.19 | tpr_m900 | the Samsung Moment |
14:56.31 | tpr_m900 | maybe i can find kernel tree |
14:56.40 | NetRipper | ah |
14:58.12 | NetRipper | the thing that's making haret crash now is because it's detecting the wrong ARM version |
14:58.54 | NetRipper | i can make a small modification so that it's detected as a s3c2442 chip.. then wirq may work |
14:59.33 | tpr_m900 | :) |
14:59.45 | tpr_m900 | i'm compiling it... seems to work |
14:59.48 | tpr_m900 | no |
15:00.07 | tpr_m900 | <PROTECTED> |
15:00.07 | tpr_m900 | <PROTECTED> |
15:00.26 | tpr_m900 | i use mingce 0.59.1 |
15:00.38 | NetRipper | probably too new |
15:00.41 | NetRipper | i had the same error |
15:01.26 | tpr_m900 | if you can tell me where to subst the chip... |
15:01.39 | tpr_m900 | k, will get the svn rev known to work |
15:02.00 | NetRipper | im using mingw32ce 0.51 |
15:03.21 | tpr_m900 | ok, will grab this one too :p |
15:04.00 | tpr_m900 | if i find it |
15:04.46 | NetRipper | and if you want to do the code changes yourself, you'll need to: |
15:05.43 | NetRipper | generate a new include/mach-types.h with a new mach name for your device |
15:05.48 | NetRipper | such as SAMSUNG_M900 |
15:06.02 | NetRipper | (think its in docs/ dir where it says how to) |
15:06.33 | NetRipper | normally you request a mach type at the official arm website, but for a quick n dirty hack you can add one yourself |
15:06.36 | NetRipper | :) |
15:07.08 | NetRipper | then under src/mach/machlist.txt you add the following line: |
15:07.11 | NetRipper | M900, S3c2442 ,M900V030, SAMSUNG_M900 |
15:07.17 | tpr_m900 | ok |
15:07.20 | NetRipper | (within the Platform=PocketPC section |
15:07.58 | NetRipper | S3c2442 has an existing MachineS3c2442 class which is then used for your device |
15:08.39 | NetRipper | irq and io addresses may still be wrong though |
15:08.51 | NetRipper | it sets some defaults |
15:11.49 | tpr_m900 | there is also CONFIG_MACH_S3C6400 |
15:11.53 | tpr_m900 | in mach-types |
15:11.56 | NetRipper | ah |
15:11.59 | NetRipper | then use it |
15:12.52 | tpr_m900 | in machlist ? |
15:13.05 | NetRipper | yes instead of the SAMSUNG_M900 |
15:13.20 | NetRipper | and the M900 at the beginning you can also change to S3C6400 if you want |
15:13.57 | NetRipper | though generally device names are used instead of chipset names but it's easier to test if it'll work ;) |
15:14.13 | tpr_m900 | not the S3C2442 ? |
15:14.41 | NetRipper | no if you look in the same machlist.txt you'll see the S3c2442 for HTCHERMES but also for HTC_TRINITY |
15:14.55 | tpr_m900 | oh hmm :) |
15:15.03 | NetRipper | but you can fix that up later |
15:15.12 | NetRipper | for now it's a test if it'll work at all;) |
15:16.15 | NetRipper | you can see how it inits in src/mach/arch-s3.cpp |
15:16.32 | NetRipper | you can see there' a list of gpio's and irqs predefined, but those may only be valid for the s3c2442 series |
15:16.39 | tpr_m900 | so, line is : S3C6400, S3c2442 ,M900V030, S3C6400 |
15:16.45 | NetRipper | yep |
15:16.59 | NetRipper | the M900V030 is the OEM string you pasted earlier |
15:17.25 | *** join/#htc-linux JoshuaL (n=JoshuaL@cable-92-43.zeelandnet.nl) |
15:17.56 | tpr_m900 | yes, seen that |
15:18.14 | tpr_m900 | dunno why 030, it has hw rev 1.00 |
15:18.33 | NetRipper | it's probably the same as htc has 100/300/etc |
15:18.47 | NetRipper | raph100, raph300, raph500, raph800 |
15:18.49 | tpr_m900 | argh, need to resize my /var lvm... hmm |
15:20.12 | tpr_m900 | and /var is busy arf |
15:24.40 | *** join/#htc-linux MethoS- (n=clemens@134.102.106.250) |
15:34.03 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
15:54.20 | *** join/#htc-linux balans (n=Administ@212.123.149.239) |
16:14.54 | *** join/#htc-linux epsy (i=nobody@dedib.ath.cx) |
16:31.12 | *** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes) |
16:38.37 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
16:40.48 | *** join/#htc-linux docc (n=docc@static.88-198-83-83.clients.your-server.de) |
17:02.41 | *** part/#htc-linux sdt555 (n=titus@147.145.40.44) |
17:07.21 | *** join/#htc-linux kvaster (n=kvaster@live.bn.by) |
17:09.24 | *** join/#htc-linux gnutoo (n=gnutoo@host26-10-dynamic.54-79-r.retail.telecomitalia.it) |
17:12.41 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
17:25.04 | *** join/#htc-linux kiozen (n=kiozen@rgnb-5d87c531.pool.mediaWays.net) |
17:35.35 | *** join/#htc-linux kvaster_ (n=kvaster@live.bn.by) |
17:37.24 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
17:37.42 | *** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes) |
17:37.57 | *** join/#htc-linux MiT-MiTiK (n=MiT@194.230.146.22) |
17:39.31 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
17:41.40 | dcordes | tpr_m900, hi. it's better to use http://htc-linux.org/wiki for documenting M900 |
17:44.26 | dcordes | NetRipper, added leo link on frontpage |
17:53.45 | *** join/#htc-linux [1]Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
17:59.15 | *** join/#htc-linux epsy (i=nobody@dedib.ath.cx) |
18:00.43 | NetRipper | dcordes, ah, thx, noticed i couldnt do it |
18:01.00 | tpr_m900 | ok, repaired my vmware, was hard :p |
18:01.24 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
18:10.03 | *** join/#htc-linux cmonex (n=xy6091@py81tzy417.adsl.datanet.hu) |
18:13.20 | dcordes | http://www.forbes.com/2009/11/12/qualcomm-lenovo-mobile-technology-personal-smartbook.html |
18:14.15 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
18:16.40 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
18:24.55 | tpr_m900 | ok compiled haret |
18:25.12 | tpr_m900 | Found machine s3c6400 |
18:26.30 | tpr_m900 | Detected machine S3C6400/s3c2442 (Plat='PocketPC' OEM='M900V030') |
18:26.30 | tpr_m900 | CPU is ARM ARM arch unknown(15) stepping 6 running in system mode |
18:27.21 | tpr_m900 | ok watch gpios 1 give me a list, but all is 0 |
18:28.29 | dcordes | tpr_m900, hey again. did you see my message "it's better to use http://htc-linux.org/wiki for documenting M900" ? |
18:28.48 | *** join/#htc-linux JuNu_KN (n=chatzill@kons-5f71068f.pool.mediaWays.net) |
18:28.50 | tpr_m900 | oh |
18:28.51 | dcordes | NetRipper, yea it's setup so only the admin can edit |
18:29.16 | tpr_m900 | than xda wiki ? |
18:29.39 | dcordes | tpr_m900, because all the other machines are documented at htc-linux too. xda wiki is outdated when it comes to the porting relevant info |
18:29.49 | dcordes | yep |
18:30.06 | *** join/#htc-linux pH5 (n=ph5@e178213142.adsl.alicedsl.de) |
18:30.21 | tpr_m900 | ok |
18:30.24 | tpr_m900 | i will |
18:30.31 | tpr_m900 | first, i need to setup haret :) |
18:30.57 | dcordes | heh alright |
18:31.13 | tpr_m900 | ok, same as before, wirq 1 lock the phone |
18:31.44 | dcordes | pH5, hej man |
18:36.09 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
18:38.58 | *** join/#htc-linux kvaster (n=kvaster@live.bn.by) |
18:52.50 | *** join/#htc-linux epsy (i=nobody@dedib.ath.cx) |
18:53.00 | *** join/#htc-linux |Epsy| (i=nobody@dedib.ath.cx) |
18:53.48 | *** join/#htc-linux enjalot (n=enjalot@wg-d232032.dsl.fsu.edu) |
18:53.51 | tpr_m900_kaiser | grr |
18:53.54 | tpr_m900_kaiser | ok :) |
19:02.16 | tpr_m900_kaiser | ok, compiling my first samsung kernel :) |
19:04.57 | tpr_m900_kaiser | ive found gpio bank definition in kernel sources : |
19:04.59 | tpr_m900_kaiser | http://github.com/leemgs/samsung-s3c6410-android.1.0/blob/master/include/asm-arm/arch-s3c2410/regs-gpio.h#L1278 |
19:05.05 | *** join/#htc-linux leaigor (n=laigor@188.134.16.241) |
19:05.17 | tpr_m900_kaiser | there are many banks (A to N) |
19:05.58 | *** join/#htc-linux furtardo (n=mks@nat/yahoo/x-ydgejfhmbjvloryl) |
19:05.59 | pH5 | hi |
19:07.13 | tpr_m900_kaiser | hello |
19:09.39 | *** join/#htc-linux Traveler (n=traveler@68-114-124-39.dhcp.slid.la.charter.com) |
19:11.52 | *** join/#htc-linux toi (n=toi@d54C2A96D.access.telenet.be) |
19:20.24 | *** join/#htc-linux Hydrokracker (n=hydrokra@68-114-124-39.dhcp.slid.la.charter.com) |
19:20.45 | Hydrokracker | Thanks for the email earlier cmonex. |
19:20.59 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
19:23.58 | *** join/#htc-linux xxx (i=59738023@gateway/web/freenode/x-lumjxfgpbxgeeopm) |
19:28.35 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
19:34.58 | *** join/#htc-linux JoshuaL (n=JoshuaL@cable-92-43.zeelandnet.nl) |
19:47.37 | *** join/#htc-linux gnutoo (n=gnutoo@host26-10-dynamic.54-79-r.retail.telecomitalia.it) |
19:55.38 | *** join/#htc-linux diogene31 (n=diogene3@mur31-2-82-243-122-54.fbx.proxad.net) |
19:57.23 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
20:06.50 | *** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz) |
20:15.53 | *** join/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
20:16.49 | yoyey | hi all, |
20:17.27 | phh | hi yoyey |
20:17.32 | phh | yoyey: any success ? |
20:17.59 | yoyey | phh=> yep with donut raphael image |
20:18.01 | yoyey | it works |
20:18.06 | phh | awesome |
20:18.49 | yoyey | but in sensors.c you don't need a ioctl to get the i2c address |
20:18.58 | phh | you have a better way ... ? |
20:19.13 | phh | well some /sys things right |
20:19.15 | yoyey | just look => cat /sys/class/input/event2/device/phys |
20:19.23 | phh | but anyway eviogetphys should be implemented |
20:19.30 | phh | and it's easier to use than reading links |
20:20.15 | phh | s/links/file/ |
20:20.52 | phh | on one hand you have a one line ioctl, on the other hand, 5 lines to create pathname+open+read+close a file |
20:21.36 | yoyey | of course |
20:21.46 | phh | yoyey: anyway, are there some features working on raph/diam that aren't for blackstone ? |
20:22.42 | yoyey | I just test 3G, and accelerometer => to make it work I must chmod -R 777 /sys/class/I2c-adapter/I2c-0 |
20:22.55 | phh | 3G works ? |
20:23.00 | yoyey | ye |
20:23.02 | yoyey | yes |
20:23.05 | phh | huhu |
20:23.08 | phh | that was unexpected :D |
20:24.37 | *** join/#htc-linux onen|openBmap (n=quassel@vbo91-1-89-87-201-85.dsl.club-internet.fr) |
20:24.58 | phh | yoyey: what do you think about trying bluetooth ? |
20:25.23 | yoyey | I modified the file board-htcblackstone.c because is not I2C_BOARD_INFO("kionix-ksd9", 0x19), but kionix-kxsd9 |
20:25.44 | phh | yes I commited this patch into gitorious |
20:26.56 | yoyey | I yes but in the path there is a mistake ksd9 instead of kxsd9 |
20:27.19 | phh | oh ok |
20:27.32 | yoyey | I have a question why don't you use the linuxtogo git ? |
20:27.44 | phh | some network problem somewhere |
20:27.48 | phh | i can't commit on it |
20:27.56 | yoyey | ok |
20:29.03 | phh | yoyey: can you try bluetooth ? |
20:29.06 | phh | i think it might work as is |
20:29.22 | yoyey | Ok I'll test |
20:32.32 | yoyey | for bluetooth I need to compile the rfkill module ? |
20:32.44 | phh | it's already in the defconfig |
20:32.46 | *** join/#htc-linux dzo_ (n=dzo@mail.marginz.co.nz) |
20:32.58 | phh | if you used the blackstone defconfig, it should work really as is. |
20:33.09 | phh | no modification or anyway |
20:33.13 | phh | s/anyway/anything/ |
20:34.12 | phh | oh it's even the say amss |
20:34.18 | phh | we could do binary compatible builds \o/ |
20:35.49 | tpr_m900_kaiser | is there a way to use same frame buffer as haret in kernel ? |
20:36.14 | tpr_m900_kaiser | i've compiled a s3c6410 kernel, which seems to boot... |
20:36.21 | tpr_m900_kaiser | but lcd is off |
20:40.41 | yoyey | yep bluetooth works but no sound in headset Is this normal ? |
20:41.00 | phh | music's playing at ~ 3x real time ? |
20:41.35 | *** join/#htc-linux Pandemic187 (n=Bob@nmd.sbx02268.milwawi.wayport.net) |
20:41.45 | phh | anyway if scan works, other problems are purely android related |
20:41.54 | yoyey | ok |
20:42.21 | phh | i've the same problem, most of the time my headset doesn't work, but once every ten tries it does work. |
20:44.22 | phh | anyway, purely software problem and a fix for diam will fix it for everyone |
20:45.23 | yoyey | In diam, gsensor works witout chmod 777 in /sys/class ? |
20:45.32 | phh | yoyey: the chmod is done in /init.donut.rc |
20:45.39 | phh | but it's only for 0-0018 |
20:46.40 | yoyey | ok I modify this in my rootfs |
20:47.11 | phh | i'm trying to unify kernel building, you'll have some time today to do some tests ? |
20:47.22 | yoyey | Yes of course, |
20:50.30 | tpr_m900_kaiser | Minimal virtual address: 0x10000, maximal virtual address: 0x7fffffff - what should i set as RAMADDR, how can i know that ? |
20:51.11 | phh | no 0x0 ? no fun. |
20:52.32 | *** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz) |
20:53.18 | tpr_m900_kaiser | ok, i ll keep kaiser settings... same ram so.. |
20:53.29 | phh | yoyey: try http://husson.hd.free.fr/zImage |
20:53.40 | phh | if i did it correctly this zImage should work for blackstone+diam+raph :D |
20:54.28 | *** join/#htc-linux [1]Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
20:56.18 | tpr_m900_kaiser | PDUMP 0x0 seems to point to Bootloader |
20:56.42 | tpr_m900_kaiser | PDUMP 0 1000 : BOOTER_M900_03_LB_01_12 |
20:56.43 | phh | on MSM 0x0 it's what is called at ARM11 startup, so it seems logical |
20:56.55 | tpr_m900_kaiser | nice to know :) |
20:57.16 | tpr_m900_kaiser | but RAMADDR is the place where to put the kernel ? |
20:58.15 | tpr_m900_kaiser | 20000000 has only 000 seems free |
21:01.20 | phh | grr, not working on diamond |
21:03.11 | tpr_m900_kaiser | is there an haret physical mem search ? |
21:03.16 | tpr_m900_kaiser | command |
21:06.39 | yoyey | phh the zImage don't boot |
21:06.45 | phh | whitescreen ? |
21:06.50 | *** join/#htc-linux marex (n=marex@85-132-216-250-eth3-gwfm10-user.802.cz) |
21:07.00 | phh | reboot ? |
21:07.06 | yoyey | nothing happen haret freeze |
21:07.22 | phh | no vibrate ? |
21:07.28 | yoyey | and I must reboot and no vibrate |
21:07.34 | phh | argh |
21:08.35 | tpr_m900_kaiser | weird, the PDUMP grab me same things every 0x4000 |
21:09.01 | tpr_m900_kaiser | PDUMP 0x0000 0x1000 = PDUMP 0x4000 0x1000 = PDUMP 0x8000 0x1000 |
21:16.47 | phh | grr what am i doing wrong ... |
21:17.30 | yoyey | What defconfig are you using ? |
21:17.32 | phh | oh. some ifdef BLACKSTONE ... |
21:17.41 | phh | my "diamraph" one |
21:17.48 | *** join/#htc-linux dzo (n=dzo@mail.marginz.co.nz) |
21:19.19 | tpr_m900_kaiser | is there somewhere a "HOWTO start porting new device" for haret ? |
21:22.19 | phh | yoyey: can you start my zImage, then in haretconsole do pwf dm 0x0e0000 0x020000 |
21:22.21 | phh | and pastebin dm |
21:22.29 | dcordes | tpr_m900_kaiser, did you check wiki? |
21:22.39 | dcordes | tpr_m900_kaiser, it has the relevant links |
21:23.23 | tpr_m900_kaiser | some |
21:23.28 | tpr_m900_kaiser | i've read the haret page |
21:23.35 | tpr_m900_kaiser | not all the wiki |
21:23.39 | tpr_m900_kaiser | wikis |
21:25.28 | dcordes | http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation this one? |
21:26.12 | tpr_m900_kaiser | yes this one |
21:26.30 | tpr_m900_kaiser | but maybe not the full page |
21:26.37 | tpr_m900_kaiser | almost |
21:29.33 | yoyey | phh: I must connect to haret console before booting ? |
21:29.55 | phh | yoyey: no, this haretconsole command is after reboot |
21:30.03 | tpr_m900_kaiser | .... |
21:30.17 | tpr_m900_kaiser | it's possible to use haretconsole while booting ? |
21:30.32 | phh | no. |
21:30.42 | tpr_m900_kaiser | yea... would be too easy ;) |
21:30.47 | phh | :p |
21:31.07 | tpr_m900_kaiser | ok, i will tell him the morse code to leds ;) |
21:31.35 | phh | lol |
21:31.59 | tpr_m900_kaiser | phh, you told me its possible to dump the tty... |
21:32.08 | phh | the ram console. |
21:32.13 | tpr_m900_kaiser | yea right |
21:32.26 | phh | as RAM isn't cleared while rebooting ... |
21:32.39 | tpr_m900_kaiser | could you give me a sample command to do that... |
21:32.40 | dcordes | http://headfuzz.co.uk/?q=taxonomy/term/2 <- morse ;) |
21:33.10 | phh | tpr_m900_kaiser: depends on the board configuration, but for black/raph/kovsky/others it's pwf dm 0x0e0000 0x020000 |
21:33.12 | tpr_m900_kaiser | lol :) could be my kaiser :p |
21:33.33 | dcordes | good old kaiser.. rock solid device. |
21:33.42 | tpr_m900_kaiser | pwf, so Physical wf |
21:34.05 | tpr_m900_kaiser | pwrite file |
21:34.06 | tpr_m900_kaiser | hmm |
21:34.22 | tpr_m900_kaiser | but the PDUMP give me always same first blocks |
21:34.37 | phh | don't know what is this for other systems than MSM |
21:35.00 | phh | check kernel source |
21:35.02 | phh | code |
21:35.08 | yoyey | phh, the zImage boot but I don't have touchscreen |
21:35.09 | tpr_m900_kaiser | the problem is with haret |
21:35.12 | dcordes | tpr_m900_kaiser, you booting msm kernel on m900? |
21:35.19 | tpr_m900_kaiser | :) no |
21:35.21 | phh | yoyey: oh cool |
21:35.40 | tpr_m900_kaiser | i'm booting a 2.6.24 kernel |
21:35.53 | tpr_m900_kaiser | http://github.com/leemgs/samsung-s3c6410-android.1.0/blob/master/include/asm-arm/arch-s3c2410/regs-gpio.h#L1278 |
21:35.54 | phh | yoyey: that problem is easy to fix :p |
21:36.18 | tpr_m900_kaiser | but s3c framebuffer doesnt handle my LCD panel (almost) |
21:36.18 | dcordes | tpr_m900_kaiser, for which device is this? |
21:36.36 | dcordes | some samsung eval board? |
21:36.41 | tpr_m900_kaiser | a development platform yes |
21:36.53 | phh | yoyey: download it again from the same url, touchscreen should work. |
21:37.43 | yoyey | after few seconds screen poweroff and I can't power on... |
21:37.53 | yoyey | I'll try you new zImage |
21:37.57 | tpr_m900_kaiser | CONFIG_MACH_SMDK6410 |
21:38.07 | phh | yoyey: oh you have no "power" key ? |
21:39.43 | tpr_m900_kaiser | dcordes: lcd is almost same, same resolution (800x480) but landscape one |
21:40.31 | tpr_m900_kaiser | LTE480WV |
21:41.05 | yoyey | just add {KEY_POWER, 83, 1, "Power button"}, |
21:41.05 | yoyey | <PROTECTED> |
21:41.21 | yoyey | and i'll try |
21:42.55 | phh | KEY_POWER ? i'd say KEY_HOME mmm |
21:42.59 | phh | zImage updated |
21:44.31 | dcordes | tpr_m900_kaiser, This model is composed of a TFT-LCD module, a driver circuit |
21:44.31 | dcordes | and a back-light unit. |
21:44.49 | dcordes | is "driver circruit" mddi ? |
21:45.40 | phh | grr, so many ifdef things for blackstone |
21:46.42 | dcordes | I mean is it the equivalent to the mddi in msm devices? |
21:47.01 | tpr_m900_kaiser | i cant tell, there is several frame buffer drivers in this kernel tree |
21:47.17 | tpr_m900_kaiser | i'm trying with default fbcon |
21:47.43 | dcordes | tpr_m900_kaiser, CONFIG_MACH_SMDK6410 doesn't select one? |
21:48.14 | tpr_m900_kaiser | yes, the S3C6410 advanced one |
21:48.20 | *** join/#htc-linux cr2 (n=cr2@ip-109-84-13-100.web.vodafone.de) |
21:48.25 | tpr_m900_kaiser | 8 to 32bit |
21:50.25 | tpr_m900_kaiser | hmm |
21:50.31 | tpr_m900_kaiser | maybe i can find info in wince |
21:50.45 | tpr_m900_kaiser | registry... |
21:56.19 | yoyey | phh=> touchscreen ok lcd on/off ok with HOME BTN but btn volum up down doesn't work |
21:56.32 | phh | yoyey: worked before ? |
21:56.57 | phh | anyway, i'm currently trying to get it working on my diam again first :D |
21:56.58 | yoyey | with my old zImage yep (linuxtogo) |
21:57.09 | NetRipper | hi cr2 |
21:57.15 | NetRipper | you read my messages in irclog? :) |
21:57.23 | phh | yoyey: hum ok |
21:57.27 | phh | NetRipper: he does |
21:57.44 | NetRipper | phh, i know, usually |
21:58.27 | phh | yoyey: i can't see any difference which would explain this volume up/down thing :/ |
21:59.14 | phh | yoyey: when you say "doesn't work", it means it isn't detected by android right ? |
21:59.20 | dcordes | cr2, hey there |
21:59.23 | NetRipper | Kevin2, i requested to join your project yesterday, could you take a look? :) |
21:59.38 | yoyey | I'm looking on my defconfig |
21:59.42 | phh | yoyey: maybe try chmod a+rw /dev/input/* |
22:00.16 | dcordes | tpr_m900_kaiser, you got a full dump of the wince filesystem? |
22:00.17 | phh | (do killall system_server after the chmod) |
22:01.35 | cr2 | NetRipper: probably partly |
22:01.56 | cr2 | NetRipper: there is source for NBMerge.exe ?? |
22:02.15 | NetRipper | cr2, i don't know? don't know the tool even :) |
22:02.32 | NetRipper | cr2, i got haret to not crash when wirq |
22:03.02 | NetRipper | cr2, so i wanted to ask you if you could find out the physical gpio addresses for each bank, so that i can see if i can find the gpio for the LED again |
22:04.30 | tpr_m900_kaiser | dcordes: yes |
22:04.41 | tpr_m900_kaiser | its available |
22:04.49 | tpr_m900_kaiser | but yes i have if you want |
22:05.33 | tpr_m900_kaiser | i've the m900 kitchen |
22:06.01 | tpr_m900_kaiser | but, its not easy to flash... the tools are buggy |
22:06.13 | yoyey | phh this is my /dev/input |
22:06.15 | dcordes | tpr_m900_kaiser, don't know if I would be of any help. just trying to make sure you have the tools you need. |
22:06.16 | yoyey | # cat /sys/class/input/event0//device/name |
22:06.16 | yoyey | MSM touchscreen |
22:06.16 | yoyey | # cat /sys/class/input/event1//device/name |
22:06.16 | yoyey | MSM Blackstone pad |
22:06.16 | yoyey | # cat /sys/class/input/event2//device/name |
22:06.16 | yoyey | kionix-kxsd9 |
22:06.18 | yoyey | # |
22:06.29 | phh | yoyey: uh ?!? |
22:06.37 | phh | no gpio thing ? |
22:06.40 | dcordes | tpr_m900_kaiser, do you also have the bootloader dumped? |
22:06.42 | yoyey | yep |
22:06.45 | tpr_m900_kaiser | i flashed with a lite rom (which doesnt include oem cabs in extrom) |
22:06.51 | tpr_m900_kaiser | yes |
22:07.12 | dcordes | tpr_m900_kaiser, is there spl etc like on msm? |
22:07.37 | tpr_m900_kaiser | there 2 special boot modes |
22:07.47 | tpr_m900_kaiser | diagnostic and rom downloader (SD or USB) |
22:08.13 | tpr_m900_kaiser | boot.dat, ipl.dat, knight.dat (diag) and usbdl.dat |
22:08.33 | dcordes | those are the raw binaries? |
22:08.42 | tpr_m900_kaiser | yes i think |
22:09.03 | tpr_m900_kaiser | boot.dat is 16K, ipl is 128K knight 284K and usbdl is 106K |
22:09.13 | tpr_m900_kaiser | but yea :) will take a look with IDA |
22:09.41 | yoyey | phh, In misc device we need to activate gpio button |
22:09.55 | tpr_m900_kaiser | yea, its raw... saw same data with PDUMP |
22:09.55 | phh | it is ... |
22:11.01 | tpr_m900_kaiser | only access to boot.dat with PDUMP |
22:11.02 | cr2 | NetRipper: use the uboot patch ? |
22:11.13 | NetRipper | cr2, for what? |
22:11.14 | phh | yoyey: but no event3 at all ? |
22:11.24 | phh | on my device it goes up to event4 ... |
22:11.33 | NetRipper | cr2, and where to find? |
22:11.33 | cr2 | NetRipper: i can check it with wince, but i doubt that we will learn something new compared to uboot. |
22:11.41 | AstainHellbring | hiya cr2 hows it going? |
22:12.10 | NetRipper | cr2, uboot patch contains gpio addresses? |
22:12.17 | cr2 | <PROTECTED> |
22:12.20 | NetRipper | cr2, i guess i can find them in the codeaurora tree as well actually |
22:12.23 | NetRipper | ah |
22:12.23 | NetRipper | k |
22:12.49 | phh | yoyey: isn't it "keyboard gpio" instead of "misc gpio" ? |
22:12.59 | phh | let's try. |
22:13.02 | yoyey | ok |
22:13.15 | cr2 | NetRipper: QSD8x50_reg.h |
22:13.32 | NetRipper | cr2, do you know if the leo would most resemble the "SURF", the "FFA" or the "COMET" boards in the aurora tree? or can i throw them away and start a new board completely? :) |
22:14.23 | cr2 | AstainHellbring: SURF and FFA share the same file, and the config seems to be more extensive than COMET |
22:14.51 | NetRipper | ok |
22:14.52 | cr2 | you mostly need to edit it, remove the unnecessary parts and add the gpios |
22:15.12 | cr2 | AstainHellbring: nothing new yet. |
22:15.17 | NetRipper | man that's a lot of #define's |
22:15.36 | cr2 | AstainHellbring: if we will make BT work, if it possible to ssh over BT ? |
22:15.47 | cr2 | NetRipper: the whole cpu :) |
22:16.01 | cr2 | i wish we had such file for 7201A |
22:16.10 | tpr_m900_kaiser | hmmm, yea ida can dissassemble... but not enough familiar with arm asm to understant what it make |
22:16.13 | NetRipper | cr2, hehe so seems best to go with the codeaurora tree then |
22:16.37 | cr2 | NetRipper: compile SURF+FFA config first |
22:16.41 | NetRipper | tpr_m900_kaiser, i found a nice plugin that partially translates it to C code, makes it quite a bi tmore understandable (though its far from perfect) |
22:16.51 | cr2 | you need some recent compiler i guess |
22:16.57 | tpr_m900_kaiser | for ida ? |
22:17.15 | NetRipper | cr2, i did, and tried to boot, but hung somewhere.. which is why i want to find the gpio for LED.. as it may help pinpoint where it hangs |
22:17.23 | tmzt | 2009q1 should have cortex |
22:17.25 | NetRipper | tpr_m900_kaiser, yes for ida |
22:17.30 | cr2 | NetRipper: use vibra :) |
22:17.35 | NetRipper | cr2, is it easier? |
22:17.44 | yoyey | phh, the diamond board use the "buttons" module but blackstone board use "gpio_keys module" |
22:17.46 | NetRipper | cr2, but then a whole lot needs to be initialized already |
22:17.50 | phh | yoyey: ok |
22:17.54 | phh | yoyey: love that :p |
22:17.56 | cr2 | NetRipper: hm. you need to patch the smem addresses first, for DEX to work |
22:18.09 | yoyey | maybe we can change the module to use the same |
22:18.22 | cr2 | NetRipper: you have the flash led on leo too ? :) |
22:18.40 | phh | yoyey: i think every board will eventually be unified |
22:18.54 | NetRipper | cr2, yes, wouldnt have bought it otherwise;) |
22:19.05 | NetRipper | cr2, dual led even |
22:19.06 | cr2 | NetRipper: hm. trace the gpio ? |
22:19.21 | NetRipper | cr2, yes which is why i asked for the gpio addresses, but i guess i can find it in the reg.h |
22:19.23 | cr2 | i looked, but didn't find it. |
22:19.45 | NetRipper | already updated TorchButton with support for leo :P |
22:19.46 | cr2 | NetRipper: i doubt they are different from 7201 |
22:20.01 | NetRipper | cr2, the IRQ addresses differed quite a bit |
22:20.05 | NetRipper | so i suppose gpio might as well |
22:20.08 | cr2 | just more banks. |
22:20.15 | cr2 | irq is a different story. |
22:20.31 | tmzt | phh: blak and raph how? |
22:20.41 | phh | tmzt: they aren't that different .. |
22:20.41 | NetRipper | <PROTECTED> |
22:20.41 | NetRipper | <PROTECTED> |
22:20.49 | NetRipper | that's raphael |
22:20.55 | NetRipper | oh not even, that's vogue |
22:21.01 | phh | tmzt: some well placed if instead of ifdef should be enough |
22:21.06 | NetRipper | <PROTECTED> |
22:21.06 | NetRipper | <PROTECTED> |
22:21.07 | NetRipper | that's leo |
22:21.09 | phh | yoyey: ne try ? :) |
22:21.12 | phh | new* |
22:21.18 | yoyey | ok |
22:21.23 | NetRipper | 0xac instead of 0xc :) |
22:21.28 | cr2 | NetRipper: the smem has some shift too |
22:21.34 | NetRipper | ok |
22:21.43 | cr2 | but the rest is the same i think |
22:22.06 | NetRipper | ok |
22:22.13 | tmzt | tpr_m900_kaiser: probablly need both lcdc configuration and some display init or just use a vfb type thing with existing address can't remember the name though |
22:22.17 | NetRipper | i cant work on it right now but i'll check it later on |
22:22.18 | cr2 | NetRipper: this time we need to address the proc_comm properly :) |
22:22.56 | NetRipper | cr2, how does "proper" differ from last time? we modified it 10x :P |
22:23.37 | dcordes | wow hd2 is real sexy |
22:23.41 | cr2 | NetRipper: #include "wince*" was ugly |
22:24.05 | cr2 | NetRipper: just to write the new handler to "native" proc_comm codes. |
22:24.33 | cr2 | now we know most everything of the proc_comm operation, unlike last year. |
22:25.00 | NetRipper | cr2, last time i got lost working with proc_comm and others ended up doing it :) |
22:25.14 | NetRipper | so i dont know how it was done previously |
22:25.34 | dcordes | it even has the compass |
22:25.57 | NetRipper | but i'll take a look and see ;) maybe you can write some of the ideas you have about how proc_comm should be implemented in the wiki page? |
22:26.05 | phh | compass and capactitive panel are the only things i'd like to see on my diamond actually |
22:26.07 | cr2 | dcordes: yes. the same as on g2 |
22:26.12 | NetRipper | you clearly have it better in your mind than i do |
22:26.22 | dcordes | perfect |
22:26.27 | NetRipper | phh, no you dont |
22:26.39 | cr2 | +#define NAND_DEVn_CFG0__ECC_PARITY_SIZE_BYTES___M 0x00780000 |
22:26.40 | NetRipper | phh, well in my personal opinion, capacitive aint "it" :) |
22:26.46 | phh | NetRipper: hu ? why ? |
22:26.49 | phh | like stylus ? :) |
22:26.56 | cr2 | phh: capacitive panel works already ? |
22:27.03 | NetRipper | not neccesarily, but dislike the precision of capacitive |
22:27.08 | phh | cr2: don't think so |
22:27.23 | phh | NetRipper: oh.. never tried capacitive actually |
22:27.31 | cr2 | phh: it is. the leds do weird thing based on this data |
22:27.34 | NetRipper | and sometimes seems to misinterpret... i.e. i try to touch a button, and it registers a weird move as if i dragged from top to bottom |
22:27.46 | NetRipper | phh, may just be me, havent seen others complain yet;) |
22:28.19 | NetRipper | another collegue of mine gets his phone this weekend so im going to compare my experience with his device... maybe it's just my device and i need to send it in ;) |
22:28.20 | dcordes | I like the touchscreen in kovsky a lot |
22:28.20 | phh | NetRipper: i think i have never touched a capacitive panel, but theorically it should be way better than resistive :p |
22:28.36 | NetRipper | phh, well it's more sensitive alright :) you dont have to "press" the screen |
22:28.37 | NetRipper | just slide over it |
22:28.39 | NetRipper | that's nice |
22:28.50 | phh | (and multitouch.) |
22:28.53 | NetRipper | yes |
22:28.59 | NetRipper | although resisive can be multitouch as well |
22:29.08 | phh | yes right |
22:29.10 | NetRipper | but you'd have to press with two fingers,while dragging |
22:29.15 | NetRipper | and thats not handy |
22:29.15 | NetRipper | :) |
22:29.43 | cr2 | NetRipper: you see the irqs in haret now ? |
22:29.56 | NetRipper | cr2, yes, but getting a lot of spam |
22:30.02 | dcordes | cr2, what about the patch? should I try to fiddle in the broken parts? |
22:30.04 | cr2 | and decodes the names ? |
22:30.07 | NetRipper | dont have haret in front of me |
22:30.13 | NetRipper | cr2, no havent done haretconsole yet |
22:30.18 | cr2 | dcordes: which one ? |
22:30.26 | cr2 | NetRipper: ok |
22:30.51 | cr2 | dcordes: which parts are broken ? |
22:30.52 | dcordes | cr2, the last one you gave me. against the not uptodate tree |
22:31.34 | dcordes | reapplying to check |
22:32.55 | yoyey | phh can't boot with the last zImage |
22:34.07 | AstainHellbring | sorry cr2 stepped away yah if bt works and we can connect it to btpan then yes we can ssh over bt |
22:36.38 | tpr_m900_kaiser | tmzt: yes tx, the standard framebuffer could be enough... the haret fb messages with 4x6 font is one centimeter large x 3mm :) i've more than enough place to see kernel messages... |
22:37.07 | dcordes | cr2, arch/arm/mach-msm/qdsp5/adsp_6120.c |
22:37.30 | tpr_m900_kaiser | i just need to know how to use that... like dzo did with the uncompressing kernel stuff... |
22:39.21 | phh | yoyey: please try again, works for me this time :D |
22:39.37 | phh | pretty sure it will do for you too |
22:41.26 | *** join/#htc-linux IR7612 (n=ircap@84.78.175.196) |
22:44.24 | *** join/#htc-linux cr2 (n=cr2@109.84.13.100) |
22:44.33 | dcordes | cr2, arch/arm/mach-msm/qdsp5/adsp_6120.c |
22:44.50 | dcordes | cr2, and it tries to remove arch/arm/mach-msm/qdsp5/adsp_6120.h which is gone already |
22:45.17 | dcordes | I just tried to build without the adsp hunks but it fails on smd.c |
22:45.44 | yoyey | phh, boot ok but no button doesn't work |
22:46.03 | phh | yoyey: \o/ |
22:46.18 | yoyey | no /dev/input/ |
22:46.26 | phh | yes i forgot to build it again |
22:46.36 | phh | http://phhusson.free.fr/zImage |
22:46.39 | yoyey | ;-) |
22:46.53 | phh | i was trying to fix FB and bam. |
22:47.24 | NetRipper | PB? |
22:47.28 | NetRipper | platform builder? |
22:48.06 | phh | *F*B |
22:48.09 | phh | framebuffer |
22:49.06 | *** join/#htc-linux [1]Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
22:49.25 | tpr_m900_kaiser | but, look like its CE related... |
22:49.32 | tpr_m900_kaiser | the haret thing... |
22:50.23 | phh | yoyey: if you want to build your own kernel i pushed my patch on gitorious |
22:50.47 | yoyey | excellent... |
22:50.56 | yoyey | thanks |
22:51.35 | phh | we will be able to do a single release for diamond+blackstone+raphael, was worth the work :p |
22:52.00 | yoyey | yes audio volume works |
22:52.04 | phh | cool |
22:53.56 | yoyey | The power off/on button works on diamon ? |
22:54.09 | phh | it does power on not power off |
22:54.13 | phh | but it is declared as "home" button |
22:54.16 | phh | not "power" button |
22:54.22 | yoyey | ok |
22:55.05 | tpr_m900_kaiser | sorry for that : "Sous quel système fonctionne votre téléviseur ? S'il est récent et de marque Samsung, il fonctionne sous... Linux. Et certains utilisateurs ont donc décidé de profiter de ce système pour améliorer les fonctions des téléviseurs. Il existe maintenant un firmware alternatif, SamyGo, qui permet de débloquer certaines fonctions et en ajoute d'autres." |
22:55.29 | tpr_m900_kaiser | samsung tv have a linux kernel too ;:p |
22:55.35 | phh | we really need to unify those things ... we aren't even using the same gpio driver across boards ... |
22:55.48 | phh | tpr_m900_kaiser: i new that they gave the source code with my TV :p |
22:55.56 | phh | but didn't know there were alternatives firmwares mmm |
22:56.07 | phh | might be interesting :) |
22:56.11 | tpr_m900_kaiser | :) |
22:56.59 | phh | mythtv without a big and noisy computer on my 52" plasma |
22:57.00 | phh | <3 |
22:57.50 | dcordes | phh, nice 52" plasma |
22:58.01 | phh | yes :p |
22:59.03 | tpr_m900_kaiser | only have a 42" lg tv, and a 24" MVA screen |
22:59.36 | tpr_m900_kaiser | and now a WVGA 260dpi phone :) |
23:00.46 | phh | :) |
23:00.52 | phh | i'd like 260dpi on a 40" screen :D |
23:01.02 | phh | scummvm for samsung TV ! |
23:01.04 | phh | omg |
23:01.06 | tpr_m900_kaiser | wow WXXXVGA ;p |
23:01.30 | phh | tpr_m900_kaiser: the problem will be to find a correct graphic card handling that :p |
23:01.43 | tpr_m900_kaiser | sure... but maybe not |
23:02.07 | tpr_m900_kaiser | with the new systems to have 4 screens or more on 1 card |
23:02.27 | tpr_m900_kaiser | dont remember the name |
23:02.54 | tpr_m900_kaiser | part of DisplayPort system |
23:03.48 | tpr_m900_kaiser | http://www.pcinpact.com/actu/news/51584-matrox-serie-m-multiecran-displayport-gxms.htm (french) |
23:04.49 | *** join/#htc-linux okias (i=ejabberd@62.109.141.134) |
23:05.08 | okias | Hello |
23:05.24 | dcordes | hi okias |
23:05.35 | okias | dcordes: hi, how are you? :-) |
23:05.56 | dcordes | okias, I'm fine, you? long time no see |
23:06.27 | okias | fine, now I got HTC Dream and iPaq H3800 |
23:07.15 | okias | so I decided play with h3800... now I got lcd and backlight working (trying ressurect 2.4 code) |
23:07.45 | dcordes | nice |
23:09.44 | tpr_m900_kaiser | there is something like JTAG behind my m900 battery... |
23:10.06 | okias | I don't know how exactly explain it, but now I worndering, if light sensor from h3800 giving some information to system or only regulating backlight without giving information about light status |
23:10.13 | okias | *wondering |
23:10.51 | tpr_m900_kaiser | 2x7 double DIN |
23:11.02 | tmzt | phh: can you help with mddi bus problem? |
23:11.20 | phh | tmzt: i don't think so but what's the problem ? |
23:11.22 | tmzt | if you got that working we could use your new boards on 31 |
23:12.05 | phh | ho |
23:12.05 | dcordes | cr2, still there? |
23:12.09 | phh | i'll give it a try tomorrow |
23:13.05 | tmzt | gitorious.org/~tmzt |
23:13.16 | yoyey | phh, a last patch to make gsensor working well on blackstone |
23:13.21 | dcordes | okias, I think the first thing. it's giving info to system and some driver uses it to regulate backlight. just my guess |
23:13.29 | tmzt | I'm working on a new bus driver for mddi that's not pushed yet |
23:13.37 | yoyey | how can I send you this patch ? |
23:13.46 | phh | yoyey: phhusson@free.fr |
23:13.53 | yoyey | ok |
23:14.08 | tmzt | light sensor? |
23:14.13 | tmzt | it should be adc |
23:19.07 | phh | time to sleep. |
23:20.17 | *** part/#htc-linux yoyey (n=yoann@lns-bzn-49f-81-56-185-87.adsl.proxad.net) |
23:20.39 | okias | dcordes: hmm, I think so, but light sensor on h3800 looks like he modifying brightness self, without help of OS.. |
23:25.22 | dcordes | okias, why do you think that? |
23:25.39 | *** join/#htc-linux gnutoo (n=gnutoo@host26-10-dynamic.54-79-r.retail.telecomitalia.it) |
23:29.25 | okias | dcordes: I just can't find in code any value which it can give to brightness... I'm going sleep, work wait :-D Good night |
23:29.48 | dcordes | good night |
23:30.02 | *** part/#htc-linux okias (i=ejabberd@62.109.141.134) |
23:30.49 | *** join/#htc-linux gnutoo_ (n=gnutoo@host26-10-dynamic.54-79-r.retail.telecomitalia.it) |
23:32.19 | tpr_m900_kaiser | hmm, almost loose my time today... ready to modify haret... |
23:38.03 | *** join/#htc-linux leobaillard (n=leobaill@leobaillard.org) |
23:39.08 | tmzt | pxa pwm? |
23:39.11 | tmzt | or egpio |
23:42.45 | tpr_m900_kaiser | :) found a recent samsung kernel :) nice |
23:42.50 | tpr_m900_kaiser | git://git.kernel.org/pub/scm/linux/kernel/git/kki_ap/linux-2.6-samsung.git |
23:43.05 | tpr_m900_kaiser | 2.6.28 to 2.6.31 |