| 00:00.11 | druidu | that's so really cool :) |
| 00:00.11 | tmzt | kcore |
| 00:00.23 | dzo | druidu: are those latest diamond patches yours? |
| 00:00.27 | druidu | yes |
| 00:01.00 | dzo | cool, it didn;t boot for me at first, my diamond only has 1 bank of ram. |
| 00:01.04 | druidu | I updated to latest upstream stuff on both .27 branch and tweaked the config |
| 00:01.20 | druidu | then a little mod on the vibrator driver to make it work in android :) |
| 00:01.24 | dzo | i put a kernel param in for the no of banks. |
| 00:01.31 | druidu | that's good |
| 00:01.53 | dzo | you don't use the extra 32M of stacked ram? |
| 00:02.06 | druidu | what? |
| 00:02.18 | druidu | I'm really not sure if the stuff with the memory banks is ok |
| 00:02.33 | druidu | plus, i have mem=76MB in default.txt so it won't use more than that anyway... |
| 00:02.52 | dzo | on my device there's another 32M at 0x02000000 |
| 00:03.06 | druidu | how can we reliably auto detected this stuff? |
| 00:03.32 | druidu | I mean, I'm looking at board-htcdiamond vs board-htcraphael and they're *identical* except raphael has the keypad |
| 00:03.36 | dzo | ok, do all diamonds have 128M+64M |
| 00:03.55 | druidu | with a few autodetection routines, or kernel params, we could make just one board file for all these phones |
| 00:04.07 | druidu | pdadb.net might help here |
| 00:04.14 | cr2 | druidu: it's in MFG area in NAND |
| 00:04.17 | druidu | mine has 192 |
| 00:04.38 | druidu | MFG area can be read directly (map it somehow) ? |
| 00:04.51 | dzo | druidu: yes 128M at 0x10000000 and 64M at 0x0 |
| 00:05.15 | dzo | with part of each used by amss. |
| 00:05.42 | tmzt | where's the video? |
| 00:05.43 | druidu | problem is I'm not sure the linux kernel knows about these "arrangements" so it can use the maximum ram that is |
| 00:05.54 | druidu | and so that we can trask the mem=76 MB from the default.txt file |
| 00:06.04 | druidu | s/trask/trash/g |
| 00:06.43 | dzo | should be OK without that now. |
| 00:07.13 | dzo | do you mind if i enable adb too? |
| 00:08.01 | tmzt | can you get adb and ether to work, or support switching between them? |
| 00:08.30 | druidu | dunno, if it works it would be great :) |
| 00:11.27 | *** join/#htc-linux apt (i=ibot@rikers.org) |
| 00:11.27 | *** topic/#htc-linux is Welcome to htc-linux | Logs: http://apt.rikers.org/%23htc-linux | Livelogs: http://irclog.netripper.com/?chan=htc-linux | Wiki: http://htc-linux.org/wiki | Original project page: http://wiki.xda-developers.com/index.php?pagename=Xanadux | Please use device codenames. For aliases, see: http://wiki.xda-developers.com | Join #android for android centered discussion. |
| 00:13.02 | *** join/#htc-linux jyoshm (n=jmissao@unaffiliated/sundial) |
| 00:15.00 | dzo | ok, i just pushed another patch to allow the vogue userspace to work. |
| 00:16.26 | dzo | druidu: does the panel turn on correctly for you? |
| 00:16.26 | druidu | cr2: or the good ol' cat > :) |
| 00:16.44 | druidu | turn on? it never turns off, if it turns off it won't turn back on |
| 00:18.09 | dzo | druidu: ok, is data smd7? |
| 00:18.23 | tmzt | yeah, on gsm |
| 00:18.28 | dzo | is it ppp or qmi? |
| 00:18.34 | tmzt | ppp |
| 00:18.43 | tmzt | we don't have rmnet working if it's even in the amss |
| 00:18.44 | cr2 | dzo: you have gsm diam ? |
| 00:18.56 | cr2 | dzo: data is ppp, also on cdma. |
| 00:19.21 | dzo | yes, gsm, but it's a crappy chinese version without wcdma and wifi. was cheap though! |
| 00:19.45 | cr2 | dzo: the smd_private.h is not 100% right, but all important things are the same |
| 00:20.11 | cr2 | dzo: smd7 is gprs, smd27 is gps nmea |
| 00:20.33 | druidu | gsm diam here |
| 00:20.37 | dzo | ok, looks like the slow clock sync isn't working, when it idles it crashes. |
| 00:21.18 | druidu | what crashes? |
| 00:21.52 | druidu | mine crashes occasionally too, I"d love to find out why |
| 00:22.00 | dzo | lots of errors about scheduling in idle and late clock sync and then kernel crash. |
| 00:22.19 | dzo | it's the clock sync on idle. |
| 00:22.39 | tmzt | clock sync? |
| 00:22.47 | tmzt | rtc or something else? |
| 00:23.11 | druidu | I also get some i2c errors, msm_i2c msm_i2c.0: Warning bus was busy (3), lots of them with different numbers |
| 00:23.21 | druidu | these come after starting to boot android |
| 00:23.30 | dzo | it switches off the gp timer during idle and has to sync it ith a9 arterwards, easy to fix, just don't switch off the gp timer. |
| 00:26.25 | dzo | ok, i pushed a change that should fix it. |
| 00:27.18 | tmzt | what branch are you working on? |
| 00:27.28 | tmzt | is the kovs stuff fixed now?? |
| 00:27.49 | cr2 | i think it's better to replace the disabled 4X prescaler for BT, with 4X multiplier... |
| 00:28.12 | dzo | htc-msm-2.6.27 |
| 00:31.17 | druidu | dzo: I'm gonna undo the makefile change in your patch |
| 00:31.30 | druidu | I use env vars for ARCH and CROSS_COMPILE and mine is different :) |
| 00:32.09 | tmzt | oh, I just use that on the command line :) |
| 00:32.12 | dzo | oh, sorry about that, i forgot to take those out. |
| 00:32.30 | druidu | no problem |
| 00:32.36 | druidu | you might wanna add Makefile to .gitignore |
| 00:32.59 | druidu | or just set them up in an env var and do like: ". envvars" when you start working |
| 00:33.33 | druidu | pushed |
| 00:38.31 | *** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34) |
| 00:38.52 | dcordes | somebody gonna join htc-linux congress at my place |
| 00:38.53 | dcordes | ? |
| 00:40.39 | druidu | lol, like in Koeln? :) |
| 00:40.49 | dcordes | no at my place in Ratingen |
| 00:41.20 | druidu | well, I'm far away from that too :P |
| 00:43.06 | druidu | do we have like a page summarizing differences between AMSS versions & stuff? |
| 00:44.01 | cr2 | druidu: 52xx, 6150 and g1 versions ? |
| 00:44.21 | druidu | yeah |
| 00:44.55 | druidu | I'm speculating that, for example, we could activate the vibrator via RPC too |
| 00:51.25 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 00:52.25 | druidu | cr2: btw, I was mistaken about the shutdown stuff |
| 00:52.29 | druidu | it actually works as expected |
| 00:52.57 | druidu | the blinking lights were actually because it was charging, duh! that's why the reset didn't work, it was shut down |
| 00:54.16 | cr2 | ok |
| 00:54.32 | druidu | anyway, I'm thinking... let's figure things out on the 2.6.27 image and once we have things clear we could refactor all the changes directly on the 2.6.29 code and do them properly, and try to group similar devices on same boards |
| 00:54.39 | druidu | with as much autodetection as possible |
| 00:55.49 | druidu | it would be cool to package it up into a linload version and boot many devices with no configuration |
| 00:58.13 | druidu | who was write access to the wiki homepage? |
| 00:59.57 | cr2 | which wiki ? |
| 01:01.46 | druidu | htc-linux.org/wiki |
| 01:02.05 | druidu | wrote a tutorial and figured it could be useful to have a link somewhere |
| 01:02.10 | dcordes | druidu, I have access what do you need changed? |
| 01:02.14 | druidu | http://www.htc-linux.org/wiki/index.php?title=How_to_Extract_an_OS_Image |
| 01:02.19 | dcordes | ok |
| 01:02.23 | druidu | thanks |
| 01:02.47 | cr2 | we can't do it with 100% free software |
| 01:02.56 | tmzt | dcordes: how is the autobuilder stuff coming, I know we don't really have the resources for that |
| 01:03.30 | druidu | for raphael and diamond we'll make it somehow I hope... |
| 01:04.03 | druidu | question: resistive touchscreens can report pressure and touch area size? |
| 01:04.33 | cr2 | j0b0 did something about pressure |
| 01:04.43 | druidu | where? |
| 01:04.57 | druidu | I am sure I ran some build which had a much better touchscreen driver, somehow |
| 01:04.58 | dcordes | tmzt, ellis said he can provide good machine |
| 01:05.04 | druidu | it reported the size of the touched area |
| 01:05.23 | druidu | don't really know exactly what image I used... |
| 01:05.28 | tmzt | dzo: do you have any infrastructure/scripts like that? |
| 01:05.36 | tmzt | how do you build android anyway? |
| 01:05.57 | tmzt | also, not sure if you are familiar with wing-linux, but it's an android port for omap devices |
| 01:06.21 | tmzt | using oe to bootstrap the standard android build tools |
| 01:06.23 | druidu | tmzt: you download repo |
| 01:06.27 | druidu | it's a tool they made |
| 01:06.33 | tmzt | yeah, I know |
| 01:06.35 | druidu | and you sync the entire android repository |
| 01:06.36 | tmzt | was asking dzo |
| 01:06.41 | druidu | ok :) |
| 01:06.52 | dcordes | druidu, I added a link to the main page |
| 01:06.58 | druidu | nice |
| 01:07.16 | dzo | scripts for what? i have haret parsing scripts for 7x00. |
| 01:07.41 | druidu | http://www.htc-linux.org/wiki/index.php?title=How_to_Extract_an_OS_Image |
| 01:07.43 | tmzt | was talking about an autobuilder setup |
| 01:07.46 | druidu | ops wrong paste again |
| 01:07.48 | tmzt | not sure what you might be using |
| 01:07.50 | druidu | (04:02:56) tmzt: dcordes: how is the autobuilder stuff coming, I know we don't really have the resources for that |
| 01:07.56 | druidu | like autobuild kernel images from git? |
| 01:07.57 | tmzt | but we can just focus on kernel if that makes more sense |
| 01:08.04 | dcordes | tmzt, yea |
| 01:09.05 | dzo | no, just set up a cron job to git pull and build every night perhaps. |
| 01:09.54 | tmzt | we need to make sure all the devices are buildable from one tree at some point |
| 01:10.14 | tmzt | I would include non-A in that but I don't know what differences remain between htc-msm-2.6.27 and htc-vogue |
| 01:11.05 | dzo | not a good idea to include non-A, it's too different i think. |
| 01:11.10 | cr2 | tmzt: it's a different cpu, so there are many differences |
| 01:11.39 | cr2 | and different amss ;) |
| 01:12.39 | tmzt | yes, I don't mean that |
| 01:12.48 | tmzt | I mean the different approaches in things like clocks |
| 01:13.53 | druidu | we should be able to compile with everything activated |
| 01:14.15 | druidu | so if they are similar, write one driver that selects proper way at runtime (maybe with function pointers) |
| 01:14.17 | cr2 | the non-A clocks can be cleaned up, so it matches the A |
| 01:14.50 | druidu | if they are different, write different drivers that can function independent of each other and disable themselves if they don't detect the hardware |
| 01:14.50 | tmzt | yeah, we definately needs a msm_ops and msm_amss_ops etc. |
| 01:15.01 | cr2 | the clock-wince missed 2 other clock classes: 1bit and rpc calls |
| 01:15.17 | druidu | android git has devices.c and devices_htc.c |
| 01:15.22 | druidu | this is a good step forward |
| 01:15.36 | druidu | drivers are much better structured in newest tree |
| 01:15.44 | cr2 | rpc calls may be avoided, but it's easier to do this way |
| 01:15.46 | tmzt | well, we shouldn't disable anything because that breaks cross device compatibility |
| 01:15.53 | cr2 | drui |
| 01:16.00 | tmzt | anyway, there's only ARCH_MSM still, unless that changes it should all be buildable |
| 01:16.12 | cr2 | druidu: still they miss VREGs in pdev |
| 01:16.29 | *** join/#htc-linux rafyvitto (n=rafyvitt@24.54.253.34) |
| 01:16.33 | druidu | maybe g1 doesn't have it |
| 01:16.46 | tmzt | 1bit clocks? |
| 01:16.47 | druidu | we can patch their files, that wouldn't be a problem |
| 01:16.52 | cr2 | g1 has them hardcoded |
| 01:17.03 | cr2 | like certain gpios |
| 01:20.29 | druidu | what exactly are VREGs? |
| 01:21.14 | druidu | damn, an acronym page would be pure gold for a n00b to mobile hacking:) |
| 01:22.26 | dzo | voltage regulator, provides power to part of the device. |
| 01:23.02 | druidu | and VREGs are on the PMIC chip right? |
| 01:23.14 | cr2 | yes |
| 01:23.35 | druidu | does haret have cmd line options? like listen on port? |
| 01:23.52 | *** join/#htc-linux eway (n=ellis@94.30.45.128) |
| 01:23.57 | cr2 | yes |
| 01:24.04 | druidu | can't find it anywhere... |
| 01:24.05 | dzo | no, would be useful, i just put listen into startup.txt |
| 01:24.08 | cr2 | type 'help' |
| 01:24.59 | druidu | I want to run it from cmdline, like with synce-prun |
| 01:25.13 | druidu | help only lists actual commands when in the console |
| 01:25.45 | dzo | cr2: does the panel power on/off correctly on raph? |
| 01:26.41 | cr2 | no |
| 01:26.50 | cr2 | but it's documented |
| 01:26.52 | druidu | same in diamond |
| 01:27.08 | druidu | what's the mddi client? |
| 01:27.08 | dzo | ok, i'll take a look later. |
| 01:27.28 | dzo | mobile display digital interface, a serial interface for the panel. |
| 01:27.50 | druidu | no, i know that, what brand |
| 01:27.53 | druidu | the one used in raph/diam |
| 01:28.01 | cr2 | dzo: there is a wiki page about it |
| 01:28.03 | dzo | mine is sharp. |
| 01:28.08 | druidu | epson / toshiba / n35399 |
| 01:28.10 | druidu | not the panel |
| 01:28.12 | dcordes | eway, hi |
| 01:28.46 | dzo | oh, the bridge, toshiba i think. |
| 01:28.46 | cr2 | the gsm diam/raph has toshiba mddi client, like g1 |
| 01:29.06 | cr2 | so the panel is detected by toshiba gpios |
| 01:29.17 | druidu | so we only need to worry about the powerup sequence, the panel specific stuff |
| 01:29.27 | cr2 | yes. |
| 01:29.47 | dzo | yes, it'll be a proc_comm for vreg and some gpios. |
| 01:29.53 | cr2 | the vregs, gpios and (for some panels) the SPI init |
| 01:30.40 | tmzt | we need that for xip boot as well |
| 01:30.44 | dzo | is spi, used for backlight? i see spi writes when device is plugged in? |
| 01:30.44 | tmzt | rafyvitto: you here? |
| 01:31.00 | rafyvitto | hiya |
| 01:31.05 | cr2 | spi is used for panel init |
| 01:31.17 | cr2 | thr spi controller is on toshiba mddi |
| 01:31.27 | tmzt | rafyvitto: find anything else about that bootloader? |
| 01:31.29 | cr2 | it also has 2 pwm controllers, and i2c controller |
| 01:31.45 | tmzt | what does, the client chip? |
| 01:32.01 | rafyvitto | i havent research on it yet >< |
| 01:32.08 | dzo | what exactly is SPI? |
| 01:32.30 | druidu | SPI is a low-level hardware protocol |
| 01:32.35 | cr2 | serial protocol, like i2c |
| 01:32.37 | druidu | communication between chips |
| 01:32.44 | rafyvitto | but i will probably tomorrow see if i can find the source, or atleast contact the main dev |
| 01:32.54 | cr2 | 'motorola spi' |
| 01:33.15 | tmzt | dzo: it's a non-multiplex serial protocol, it uses cs to activate the chip rather than the address |
| 01:33.22 | druidu | we access spi via proc comm or rpc or what? |
| 01:33.42 | druidu | maybe gpios to select the chip |
| 01:33.46 | dzo | spi goes through the mddi interface. |
| 01:34.07 | cr2 | druidu: you send the commands over mddi |
| 01:34.30 | cr2 | druidu: look in the wiki. raphaelMDDI i think |
| 01:34.43 | druidu | PMDH (MDDI1) init: |
| 01:34.47 | druidu | PMDH? |
| 01:35.28 | cr2 | Primary MDDI host |
| 01:35.57 | cr2 | http://htc-linux.org/wiki/index.php?title=RaphaelLCD |
| 01:40.12 | dzo | gpu works now, just needed imem clock. |
| 01:40.18 | tmzt | on diam? |
| 01:40.26 | dzo | yes |
| 01:40.45 | cr2 | dzo: the clock-wince needs to be patched, |
| 01:40.58 | cr2 | dzo: for camera you'll need rpc clock calls |
| 01:41.11 | dzo | yes, same on vogue. |
| 01:41.12 | tmzt | camera is on mddi as host |
| 01:41.16 | cr2 | they are all in wiki too |
| 01:42.00 | dzo | adsp does the cam interface for you. i2c to control the shutter, focus etc. |
| 01:43.08 | druidu | btw, found a driver for the small vga camera |
| 01:44.11 | druidu | found it in a patch for davinci linux |
| 01:46.12 | cr2 | ov6680 ? |
| 01:47.35 | druidu | nope, MT9T113 |
| 01:47.37 | druidu | i2c |
| 01:47.44 | druidu | isn't that the one? |
| 01:55.14 | cr2 | on raph? yes |
| 01:56.22 | *** join/#htc-linux rafyvitto7 (i=rafyvitt@24.54.253.34) |
| 01:56.40 | eway | hi dcordes |
| 01:57.08 | eway | hi all |
| 02:01.46 | rafyvitto7 | tmzt you there? |
| 02:01.53 | tmzt | yeah |
| 02:02.08 | rafyvitto7 | ok i did i little bit of diggin >< |
| 02:02.12 | rafyvitto7 | its all in chinese |
| 02:02.17 | rafyvitto7 | but i translate it |
| 02:02.23 | rafyvitto7 | http://translate.google.com/translate?hl=en&sl=zh-CN&tl=en&u=http%3A%2F%2Fbaike.c114.net%2Fview.asp%3Fid%3D15291-EFBE7F60 |
| 02:02.31 | rafyvitto7 | check that website |
| 02:02.44 | rafyvitto7 | its a google translation so its not the best |
| 02:02.46 | rafyvitto7 | lol |
| 02:02.51 | tmzt | dzo: this is a bootloader for linux/ce on omap devices using a modified spl |
| 02:03.42 | rafyvitto7 | its explain at the bottom of the page but its a shitty translation |
| 02:03.50 | rafyvitto7 | atleast i think it is |
| 02:04.48 | tmzt | yeah, I'm looking for more details, how the asm was done, etc. |
| 02:05.16 | rafyvitto7 | our best shot is contacting yifengling0 hes the one who made it happen |
| 02:05.40 | rafyvitto7 | i did a search on google, hes nick appears on several chinease forums |
| 02:07.35 | tmzt | 1, through the list, ld, and call commands, you can load the card in any one bin file, in fact you could compile your own program to load a. |
| 02:07.38 | tmzt | 2ï¼ç¨callå½ä»¤å¯ä»¥è°ç¨splçå½æ°ï¼ ç»å 个å°å大家ç©ç©ã 2, with the call command to call the spl functions, to a few addresses you play. |
| 02:07.41 | tmzt | 1ï¼ FUNCPTR SetFrontlight = (FUNCPTR)0x8C01B0C4; ä¿®æ¹èå
ã 1) FUNCPTR SetFrontlight = (FUNCPTR) 0x8C01B0C4; modify the backlight. SetFrontlight(1)å¯ä»¥å
³éä¸ä¸ªç¯ï¼å®ç°åèå
ã SetFrontlight (1) you can turn off a lamp, to achieve half-backlight. |
| 02:07.46 | tmzt | å½ä»¤å¦ä¸æ ¼å¼å¦ä¸ï¼ call 1 8c01b0c4 1 Command follows the following format: call 1 8c01b0c4 1 |
| 02:08.31 | rafyvitto7 | so the method is explain afterall? |
| 02:08.49 | tmzt | no |
| 02:08.57 | tmzt | just a feature |
| 02:09.11 | rafyvitto7 | ic |
| 02:09.11 | tmzt | I can't read the forum |
| 02:09.11 | rafyvitto7 | im trying to find hes msn |
| 02:10.14 | rafyvitto7 | if he has one that is |
| 02:10.32 | tmzt | I guess linux is after imgfs he means |
| 02:11.22 | rafyvitto7 | Give you some techniques to use console. 547d4ee46267884c4e0d5bf9ff0c4f1a67095e2e52a94fe1606fff0c4e0d8fc789817528597dconsole970089814e004e9b7a0b5e8f529f5e95ff0c547554753002 Command execution does not, there will be help, but a good console to use some of the procedures required skills, Hehe. |
| 02:11.39 | rafyvitto7 | bleh it wont fit here |
| 02:12.12 | rafyvitto7 | wait its the same thing you copy pasted nvm |
| 02:12.59 | tmzt | yeah |
| 02:13.00 | tmzt | I think |
| 02:13.17 | rafyvitto7 | there seems to be a document for download i think its something abotu the bootloader, not sure yet |
| 02:13.24 | rafyvitto7 | about* |
| 02:14.12 | rafyvitto7 | http://vivien.chappelier.free.fr/typhoon/doc.html thats the documents, its knone |
| 02:14.27 | *** join/#htc-linux Daemon_ (n=DaemonES@195.238.92.163) |
| 02:14.29 | tmzt | it's about flash on the htc typhoon |
| 02:14.42 | rafyvitto7 | yeh not what were looking for |
| 02:14.54 | tmzt | if lcd init works we should be able to use an xip bootloader though |
| 02:15.01 | tmzt | this is a different approach |
| 02:17.23 | rafyvitto7 | http://www.mediafire.com/?xewlyyaeu3f thats the link for the pack |
| 02:17.33 | rafyvitto7 | guess thats were the bootloader is idk |
| 02:17.59 | rafyvitto7 | lots of .bin files in it |
| 02:18.28 | rafyvitto7 | you should have a look at it |
| 02:20.56 | tmzt | yeah, ok |
| 02:30.53 | druidu | dzo: cool, ram console worked :D |
| 02:36.03 | *** join/#htc-linux eway (n=ellis@94.30.45.128) [NETSPLIT VICTIM] |
| 02:36.03 | *** join/#htc-linux darkstar62 (n=darkstar@97-126-104-157.tukw.qwest.net) [NETSPLIT VICTIM] |
| 02:36.03 | *** join/#htc-linux infernix (i=nix@unaffiliated/infernix) |
| 02:42.00 | druidu | dzo: did you test adb? works? |
| 02:43.03 | dzo | yes, it does work, but i added a kernel param to enable ether or adb. i haven't tested ether and adb together. |
| 02:44.38 | *** join/#htc-linux Amaranth (n=travis@ubuntu/member/Amaranth) |
| 02:51.31 | dcordes | bbl |
| 03:01.38 | druidu | dzo: do you plug in the usb cable after booting is done? |
| 03:02.10 | tmzt | darkstar62: you try that bootloader? |
| 03:02.31 | darkstar62 | whitesharks? |
| 03:02.47 | tmzt | ? |
| 03:02.51 | darkstar62 | no, I haven't tried any bootloader yet (besides haret) |
| 03:03.03 | darkstar62 | whiteshark was making a new one that was going to support menus |
| 03:03.07 | tmzt | the on rafyvitto found |
| 03:03.15 | tmzt | oh, like eol? |
| 03:03.18 | darkstar62 | yeah |
| 03:03.23 | tmzt | this flashes to nand, not sd |
| 03:03.27 | darkstar62 | not familiar with the one you're talking about |
| 03:03.44 | tmzt | it's linked on xda |
| 03:03.45 | darkstar62 | reads back |
| 03:03.55 | tmzt | but I don't have theu url here |
| 03:05.10 | darkstar62 | huh, fascinating |
| 03:05.50 | rafyvitto7 | tmzt did you downloaded the pack? |
| 03:05.55 | tmzt | not yet |
| 03:05.58 | darkstar62 | so in theory, if we have a working mtd driver in Linux, we could use that and create our own custom flash image to flash linux directly to the device |
| 03:06.04 | tmzt | yes |
| 03:06.14 | tmzt | and it seems it works for someone |
| 03:06.16 | tmzt | well |
| 03:06.20 | tmzt | maybe they use sd |
| 03:06.26 | tmzt | for the fs |
| 03:06.55 | darkstar62 | it's a shame we don't have easy access to jtag...we could put redboot on there and be done with it |
| 03:08.01 | darkstar62 | still, that's a really cool find |
| 03:15.37 | eway | cant remember where i came accross it but i did find some trueffs dev stuff for the doc stuff somwhere |
| 03:22.20 | *** join/#htc-linux toi (n=toi@d515304E5.static.telenet.be) |
| 03:28.11 | *** join/#htc-linux stickboy (n=anonymou@128.153.211.10) |
| 03:50.25 | *** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey) |
| 04:09.01 | *** join/#htc-linux Shinto (n=John@f049114213.adsl.alicedsl.de) |
| 04:09.45 | *** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no) |
| 04:22.58 | *** join/#htc-linux droid0011 (n=g1@p4FDCFD1A.dip.t-dialin.net) |
| 05:03.06 | *** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk) |
| 05:08.49 | *** join/#htc-linux mrmoku|away (n=mrmoku@ppp-62-216-212-159.dynamic.mnet-online.de) |
| 05:55.57 | *** join/#htc-linux x29a (n=x29a@unaffiliated/x29a) |
| 06:06.29 | *** join/#htc-linux kiozen (n=oeichler@p549214DD.dip0.t-ipconnect.de) |
| 06:35.39 | *** join/#htc-linux Daemon_ (n=DaemonES@195.238.92.163) |
| 06:49.05 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
| 07:05.42 | *** join/#htc-linux furtardo (n=mks@nat/yahoo/x-naxpaovmwjpaouzc) |
| 07:09.20 | *** join/#htc-linux FR^2 (n=frzwo@2001:41d0:1:ed2f:0:0:0:cafe) |
| 07:11.43 | *** join/#htc-linux Ximon (i=simomn@pub99-11.pub.luth.se) |
| 07:34.01 | *** join/#htc-linux c4software (n=vbrossea@217.112.64.97) |
| 07:38.57 | *** join/#htc-linux goffy (i=simomn@pub99-11.pub.luth.se) |
| 07:50.10 | *** join/#htc-linux c4software1 (n=vbrossea@217.112.64.97) |
| 07:52.47 | *** join/#htc-linux c4software (n=vbrossea@217.112.64.97) |
| 08:00.40 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B035231.dip.t-dialin.net) |
| 08:00.43 | *** join/#htc-linux ellisway (n=ellis@genkt-048-026.t-mobile.co.uk) |
| 08:02.09 | *** join/#htc-linux stefan_schmidt_ (n=stefan@p5B035231.dip.t-dialin.net) |
| 08:02.17 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B035231.dip.t-dialin.net) |
| 08:34.53 | *** join/#htc-linux ArteK (n=Artur@81.15.241.96) |
| 08:52.07 | *** part/#htc-linux ArteK (n=Artur@81.15.241.96) |
| 09:10.07 | *** join/#htc-linux eway (n=ellis@94.30.45.128) |
| 09:18.44 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 09:21.20 | *** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix) |
| 09:27.12 | x29a | any xda mini dev around that could hint me to a good starting point for installing linux? |
| 09:30.49 | *** join/#htc-linux FireDevil123 (n=a@punephenix.net4india.com) |
| 09:30.52 | *** part/#htc-linux FireDevil123 (n=a@punephenix.net4india.com) |
| 09:34.57 | x29a | ok, think im on it |
| 09:42.52 | *** join/#htc-linux dcordes (n=luke-g@unaffiliated/dcordes) |
| 09:47.17 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 09:55.47 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 10:04.09 | *** join/#htc-linux Moku (n=John@g227162181.adsl.alicedsl.de) |
| 10:11.20 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 10:11.38 | *** join/#htc-linux Captnoord (n=Captnoor@145.74.183.115) |
| 10:16.15 | *** join/#htc-linux goffy (i=simomn@pub99-11.pub.luth.se) |
| 10:16.16 | *** join/#htc-linux Ximon (i=simomn@pub99-11.pub.luth.se) |
| 10:22.19 | FR^2 | x29a: I'm interested - what are you doing? |
| 10:24.27 | x29a | FR^2: actually just testing through alle the images with linload/haret |
| 10:24.42 | x29a | i want to write programs which use infrared and bluetooth (in the end) |
| 10:24.53 | FR^2 | hmmhmm |
| 10:25.42 | *** join/#htc-linux Ximon (i=simomn@pub99-11.pub.luth.se) |
| 10:25.55 | x29a | FR^2: and you? |
| 10:26.40 | FR^2 | I've got a htc wings 220 (HTC s730) which is not supported yet (no wonder with those hundrets of htc phones alone) |
| 10:29.03 | *** join/#htc-linux SOG (n=SOG@n219079206252.netvigator.com) |
| 10:29.44 | *** join/#htc-linux ptitjes (n=didier@93.2.7.143) |
| 10:49.48 | *** join/#htc-linux chab7 (n=chab7@fibhost-67-206-132.fibernet.hu) |
| 11:02.00 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
| 11:20.11 | x29a | hm, openmoko image works, but slow, other images either dont react to touchscreen or just present a boot without anything, i think i need to connect it via usb to get a remote shell? |
| 11:31.25 | *** join/#htc-linux Zinbolic (n=zinbolic@84.238.80.215) |
| 11:33.08 | *** part/#htc-linux druidu (n=druidu@78.97.155.94) |
| 11:33.49 | x29a | oi nice, bricked |
| 11:34.02 | x29a | i pulled out the batterie while linux was running, now its not booting at all |
| 11:34.22 | FR^2 | uh-oh |
| 11:35.37 | Captnoord | hmmm quite smart.... |
| 11:36.36 | x29a | i kind of had no choice |
| 11:36.51 | x29a | when i plug in the recharger the led turns red |
| 11:37.17 | *** join/#htc-linux MethoS- (n=clemens@host-091-097-241-089.ewe-ip-backbone.de) |
| 11:38.39 | x29a | Captnoord: any ideas? |
| 11:49.22 | *** join/#htc-linux druidu (n=druidu@78.97.155.94) |
| 11:49.37 | druidu | dzo: you should really try the export ARCH="arm" stuff :P |
| 11:55.59 | x29a | i wonder what that little lever at the back beside the batterie does |
| 12:00.56 | *** join/#htc-linux mrb__ (n=mrb@160.89-10-30.nextgentel.com) |
| 12:01.36 | dzo | druidu: Yes, i just noticed that, i have Makefile in .gitignore but that didn't seem to work. I fixed it now. Anyway audio works for me now. |
| 12:02.07 | druidu | gonna try it now |
| 12:02.26 | druidu | btw, how can I send module params? in the kernel cmdline? |
| 12:02.30 | druidu | like set adb=0 |
| 12:02.35 | dzo | may not work if your rom uses a different id |
| 12:02.42 | x29a | hu, works again it seems |
| 12:02.54 | dzo | board-htcdiamond.adb=0 |
| 12:03.07 | druidu | damn, I tried just adb=0, duh :) |
| 12:03.25 | dzo | or perhaps board_htcdiamond.adb=0, i think it converts - to _ |
| 12:06.41 | dzo | I just put an android initrd and rootfs that works for diamond on code.google.com/p/vogue-android, use them with the ion system image. |
| 12:08.17 | druidu | ion system image? |
| 12:09.11 | druidu | ok, found the cause of my crash (thanks to the ram console) |
| 12:09.12 | dzo | system-2009-08-08, on the same site. |
| 12:09.17 | druidu | [ 60.688873] ARM9 has CRASHED |
| 12:09.17 | druidu | [ 60.688964] smem: DIAG '' |
| 12:09.17 | druidu | [ 72.895568] msm_proc_comm_wince: DEX cmd timed out. status=0x0, A2Mcntr=9, M2Acntr=8 |
| 12:09.17 | druidu | [ 72.895599] BUG: scheduling while atomic: app_process/116/0x00010003 |
| 12:10.24 | dzo | which proc_comm was it doing? |
| 12:10.28 | druidu | the msleep in htcraphael_reset() triggers the BUG() |
| 12:10.57 | druidu | dunno... I have a stack dump |
| 12:11.01 | dzo | change it to mdelay then. |
| 12:12.19 | druidu | static irqreturn_t smsm_irq_handler(int irq, void *data) |
| 12:12.28 | druidu | this is where handle_modem_crash() is called |
| 12:12.43 | druidu | <PROTECTED> |
| 12:12.44 | druidu | <PROTECTED> |
| 12:13.01 | druidu | it's useless, handle_modem_crash is supposed to reset the device anyway |
| 12:13.19 | druidu | maybe the msleep was actually on purpose, so it generated the stack trace |
| 12:14.37 | druidu | anyway, I'm not sure I can find out what proc_comm caused this... it's the random crash when starting up android I was telling you about |
| 12:14.49 | dzo | if audio doesn't work for you, look at where it fails and it will say something like: no local endpoint for X, that is the id to put into adsp.c |
| 12:15.05 | druidu | I'll try audio now, this is unrelated :) |
| 12:15.13 | druidu | actually |
| 12:15.18 | druidu | isn't this the proc comm: DEX cmd timed out. status=0x0, A2Mcntr=9, M2Acntr=8 ? |
| 12:16.10 | dzo | yes, but it doesn't say what it was trying to do just the counters. |
| 12:17.08 | dzo | the proc_comm probably caused the a9 to crash. |
| 12:18.16 | dzo | anyway, it's getting late here, good night. |
| 12:19.35 | druidu | msm_snd this device plays audio? |
| 12:19.40 | druidu | or msm_pcm_out ? |
| 12:19.58 | druidu | ah, ok, 'night |
| 12:21.18 | druidu | [ 181.258270] audmgr_rpc_thread() start |
| 12:21.18 | druidu | [ 181.259643] [RPC] READ on ept c2ccca40 |
| 12:21.18 | druidu | [ 182.656494] audio_disable() |
| 12:30.16 | *** join/#htc-linux ximon (i=simomn@pub99-11.pub.luth.se) |
| 12:34.33 | *** join/#htc-linux shoragan (n=shoragan@debian/developer/shoragan) |
| 12:36.17 | dzo | druidu: i'm still here, msm_pcm_out plays sound but you need the android userspace for it to work. |
| 12:37.27 | druidu | tried to send garbage to it but didn't make a sound |
| 12:37.39 | druidu | tried to play an mp3 in android but nu reaction from the devices |
| 12:37.54 | dzo | it won't it needs an ioctl to enable it. |
| 12:39.50 | dzo | easiest way to test is to use android. |
| 12:41.16 | druidu | I did... the playwav is not in my android image, but tried with the media player app |
| 12:41.19 | druidu | shouldn't that work? |
| 12:42.29 | *** join/#htc-linux ximon (i=simomn@pub99-11.pub.luth.se) |
| 12:42.35 | dzo | yes, using my rootfs it will, if it's an sdk based system, it won't work. |
| 12:44.12 | dzo | audio routing works for phone calls now too. |
| 12:52.30 | druidu | btw, how do you make adb work under ubuntu? |
| 12:52.50 | druidu | tried adding this to /etc/udev/rules.d/51-android.rules: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" |
| 12:53.14 | druidu | doesn't seem to work |
| 12:53.34 | druidu | lsusb shows it correctly: Bus 002 Device 054: ID 0bb4:0c02 High Tech Computer Corp. |
| 12:54.31 | dzo | that's exactly what i have for udev rules, did you reload udev? |
| 12:54.59 | druidu | nope :D |
| 12:55.30 | dzo | sudo service udev restart |
| 12:55.59 | druidu | done that, same... no action... where should the device appear? |
| 12:57.07 | druidu | shouldn't there be a NAME="xxx" in the rules file too? |
| 12:57.24 | druidu | I mean, symlink |
| 12:58.09 | dzo | that worked for me. |
| 12:58.37 | dzo | what does dmesg say when you plug it in? |
| 12:59.22 | druidu | [61217.321221] udev: starting version 141 |
| 12:59.22 | druidu | [61226.758262] usb 2-1: USB disconnect, address 54 |
| 12:59.22 | druidu | [61228.524065] usb 2-1: new high speed USB device using ehci_hcd and address 55 |
| 12:59.22 | druidu | [61228.667590] usb 2-1: configuration #1 chosen from 1 choice |
| 12:59.34 | druidu | this is when I restarted udev, unplugged it then replugged it in |
| 12:59.50 | druidu | `adb devices` doesn't see anything |
| 13:01.52 | dzo | exactly what mine does. is this booting without adb=0? |
| 13:05.09 | druidu | yep, otherwise I'd have ethernet |
| 13:05.13 | druidu | ok so the udev rule worked |
| 13:05.16 | druidu | crw-rw-rw- 1 root root 189, 182 2009-09-01 15:55 /dev/bus/usb/002/055 |
| 13:05.23 | druidu | the device is chmoded 0666 |
| 13:06.02 | druidu | strace actually shows the adb daemon reading from the right file |
| 13:06.19 | dzo | how old is your adb? |
| 13:06.40 | druidu | just got the latest sdk |
| 13:06.47 | druidu | 1.5r3 |
| 13:06.57 | dzo | that should be ok then. |
| 13:07.02 | druidu | hd /dev/bus/usb/002/001 |
| 13:07.02 | druidu | 00000000 12 01 00 02 09 00 00 40 6b 1d 02 00 06 02 03 02 |.......@k.......| |
| 13:07.02 | druidu | 00000010 01 01 09 02 19 00 01 01 00 e0 00 09 04 00 00 01 |................| |
| 13:07.02 | druidu | 00000020 09 00 00 00 07 05 81 03 04 00 0c |...........| |
| 13:07.08 | druidu | sorry wrong paste |
| 13:07.17 | druidu | # hd /dev/bus/usb/002/055 |
| 13:07.17 | druidu | 00000000 12 01 02 01 00 00 00 40 b4 0b 02 0c 00 01 03 02 |.......@........| |
| 13:07.18 | druidu | 00000010 00 01 09 02 20 00 01 01 00 80 80 09 04 00 00 02 |.... ...........| |
| 13:07.18 | druidu | 00000020 02 00 00 00 07 05 01 02 00 02 00 07 05 81 02 00 |................| |
| 13:07.18 | druidu | 00000030 02 00 |..| |
| 13:07.43 | druidu | so this is the usb device for android adb... I suppose the adb daemon reads this and looks for a pattern, which is not there |
| 13:08.02 | druidu | 055 is the id of the device (lsusb confirms it) |
| 13:08.37 | druidu | lol |
| 13:08.42 | druidu | neevermind... persist.service.adb.enable=0 |
| 13:08.46 | druidu | in default.prop |
| 13:09.01 | dzo | ok.. that would do it. |
| 13:10.03 | dzo | i think we should use the vogue userspace, people have been working on it for a long time. |
| 13:10.14 | dzo | (for android that is) |
| 13:10.51 | dzo | and there are lots of choices, ion, cupcake, hero, themed, rogers.... |
| 13:14.29 | druidu | weeee, works |
| 13:17.51 | dzo | ok, i've really got to go to sleep now, bye. |
| 13:19.40 | druidu | thanks again, bye |
| 13:21.46 | *** join/#htc-linux MethoS- (n=clemens@dyndsl-085-016-165-099.ewe-ip-backbone.de) |
| 13:28.41 | *** join/#htc-linux stefan_schmidt_ (n=stefan@p5B03408B.dip.t-dialin.net) |
| 13:30.36 | *** join/#htc-linux cmw (n=jlika@static-173-68-151-26.nycmny.fios.verizon.net) |
| 13:30.46 | *** join/#htc-linux dcordes_ (n=luke-g@unaffiliated/dcordes) |
| 13:31.54 | *** join/#htc-linux zz_rosseaux (i=znc@84.19.167.129) |
| 13:39.22 | j0b0 | 03:04:03<druidu> question: resistive touchscreens can report pressure and touch area size? |
| 13:39.24 | j0b0 | druidu, this (over 2 months old) post explains the 'touched area size' detection in the ts driver a bit and it links to a diff --> http://forum.xda-developers.com/showthread.php?p=3788860 |
| 13:40.13 | j0b0 | it was later confirmed that it works for all raph/diam 100/500/800 |
| 13:47.07 | druidu | uuu, nice! |
| 13:47.25 | druidu | j0b0: I'm sure I came across a kernel image that implemented this :) |
| 13:47.56 | Daemon_ | BTW |
| 13:47.58 | druidu | so what about pressure, any ideas on that? |
| 13:48.13 | Daemon_ | Watch videos from Stantum, they used resistive ts |
| 13:48.23 | j0b0 | druidu, maybe it was the image that that same post links to also |
| 13:48.50 | j0b0 | im not even sure whether i measure size only or both size and pressure |
| 13:49.11 | druidu | I wonder why nobody merged you patch, this is great :) |
| 13:49.47 | Daemon_ | Stantum uses information about touch size to implement pressure detection with resistive technology |
| 13:50.12 | druidu | interesting |
| 13:53.06 | Daemon_ | And they use information about state of each dot in the ts matrix to implement multitouch. But I doubt, that such hack will not be available for us, because MSM7200 ts controller... |
| 13:54.40 | druidu | weeeee, that's great! |
| 13:55.51 | j0b0 | altho it seems a bit unlikely that the 'proper way' to get this info would be so complex. why not have a couple of registers that just hold values for size and pressure |
| 13:59.02 | cmw | anyone here worked with a locosto based gprs chipset? i'm having some strange issue getting it to attach to the network. I issue CFUN=1 and the radio starts then %NRG but it just keeps searching forever |
| 13:59.34 | *** join/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 14:00.29 | druidu | ok, so we can only use what msm7200 ts controller gives us... do we have any detailed info on that? maybe there are some more registers that give other info |
| 14:01.29 | *** join/#htc-linux ximon (i=simomn@pub99-11.pub.luth.se) |
| 14:04.07 | *** part/#htc-linux sdt555 (n=titus@147.145.40.44) |
| 14:05.41 | j0b0 | druidu, afaik all info on the touchscreen was gathered by just watching smem |
| 14:10.34 | druidu | ok, I look on the stantum website and there's no way we can implement stuff like in those videos, we'd need a different ts controller |
| 14:19.44 | Daemon_ | The only way how to get info - dump the range when TS registers placed on each finger press, and try to find some patters |
| 14:21.06 | druidu | anybody know if there's a limit on the number of loop devices? |
| 14:21.23 | druidu | like those used by losetup |
| 14:22.02 | druidu | loop0 and loop1 work, I get no such device when trying to use loop3 (but losetup doesn't fail for loop3) |
| 14:32.42 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
| 14:37.01 | *** join/#htc-linux xperia (n=chatzill@80-218-228-251.dclient.hispeed.ch) |
| 14:47.20 | *** join/#htc-linux Captnoord (n=Captnoor@145.74.201.104) |
| 14:51.18 | *** join/#htc-linux x29a (n=x29a@unaffiliated/x29a) |
| 15:00.35 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
| 15:10.47 | *** join/#htc-linux stickboy (n=anonymou@128.153.181.182) |
| 15:19.45 | *** join/#htc-linux Gnutoo (n=gnutoo@ABordeaux-152-1-40-189.w83-193.abo.wanadoo.fr) |
| 15:24.33 | *** join/#htc-linux kiozen (n=kiozen@rgnb-5d87c1d0.pool.mediaWays.net) |
| 15:30.23 | *** join/#htc-linux darkstar62_ (n=darkstar@m660e36d0.tmodns.net) |
| 15:42.03 | x29a | can anybody help me with linux on htc magician/xda mini. i got different kernels/rootfs running, but either they have no touchscreen, or xserver crashes, so id like to get a remote shell via usb somehow, how would i do that? |
| 15:46.50 | Gnutoo | can you run code on the device? |
| 15:46.55 | Gnutoo | I bet yes |
| 15:46.59 | Gnutoo | in the init script |
| 15:47.03 | Gnutoo | so: |
| 15:47.16 | Gnutoo | cross-compile netcat |
| 15:47.22 | Gnutoo | and get a shell via netcat |
| 15:47.33 | Gnutoo | but this assume that you've got usbnet working |
| 15:47.39 | Gnutoo | but not dropbear |
| 15:47.47 | Gnutoo | (else you would use dropbear) |
| 15:47.56 | Gnutoo | that's what I did with angstrom |
| 15:48.06 | *** join/#htc-linux stickboy (n=anonymou@128.153.144.209) |
| 15:48.09 | Gnutoo | it was a problem with udev or mdev I don't remember |
| 16:07.31 | *** join/#htc-linux rafyvitto (i=rafyvitt@24.54.253.34) |
| 16:07.52 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
| 16:08.16 | rafyvitto | hello guys |
| 16:19.08 | *** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net) |
| 16:25.15 | *** join/#htc-linux MethoS-- (n=clemens@host-091-097-249-083.ewe-ip-backbone.de) |
| 16:37.06 | *** join/#htc-linux toi (n=toi@d54C2AAB7.access.telenet.be) |
| 16:52.11 | druidu | j0b0: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=54bd488059a97175604e2c391969261db2de1d3e |
| 16:52.23 | druidu | any other patches you want to share? :) |
| 16:52.47 | druidu | actually, I remember the battery driver on that image was also a bit different, android actually showed the charging icon |
| 17:03.57 | *** join/#htc-linux idkfa (n=sergey@87.228.4.172) |
| 17:05.02 | *** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net) |
| 17:06.46 | *** join/#htc-linux Shinto (n=John@f049087001.adsl.alicedsl.de) |
| 17:14.21 | *** join/#htc-linux stickboy (n=anonymou@128.153.182.51) |
| 17:17.59 | Daemon_ | So, in Dream and Magic used the same Synaptics RMI TS controller |
| 17:18.41 | Daemon_ | Very interesting to find datasheet |
| 17:25.43 | *** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl) |
| 17:26.55 | *** join/#htc-linux idkfa (n=sergey@87.228.4.172) |
| 17:27.47 | *** join/#htc-linux mickey|sofa (n=M@e180177121.adsl.alicedsl.de) |
| 17:50.54 | j0b0 | thanks druidu. the last patch i made for the battery driver is this: http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-86bfe43-raph100-batt-jobo-090528.txt it is a modification to maejreps driver he wrote for raph800. i dont know how well that ever worked. with this patch you should get sane values for raph100. i can probably produce a patch that does diamond as well. |
| 17:54.39 | *** join/#htc-linux MethoS_ (n=clemens@host-091-097-247-180.ewe-ip-backbone.de) |
| 17:56.26 | druidu | actually I found it already, gonna put the same stuff in board diamong and if it works push it to git |
| 17:56.58 | druidu | :) |
| 17:59.47 | j0b0 | itd be nice to test it on raph/diam 800 as well. |
| 18:01.07 | druidu | only have a diam100, with the patch up other people can test it anyway |
| 18:01.19 | druidu | have you tried dzo's latest image? |
| 18:02.09 | druidu | http://forum.xda-developers.com/showthread.php?p=4437045#post4445175 |
| 18:02.23 | j0b0 | i havent. what does it have over git head |
| 18:05.14 | j0b0 | what is that zimage built from? is it based on htc-msm-2.6.27 ? |
| 18:05.41 | j0b0 | if so it should work for raphael as well |
| 18:07.48 | druidu | it's pretty much the git head, configured a bit different from the default (no msm_vkeyb, no htc_fb_console, cramfs support...) |
| 18:08.11 | druidu | the android image also tries to init something that crashes my phone, probably gprs or smth |
| 18:08.28 | druidu | ah, it also has the sound patches, but they are in git now |
| 18:09.42 | druidu | field size & smem offets should be same as for raphael right? (2 for gsm, 4 for cdma) |
| 18:10.07 | j0b0 | yes |
| 18:11.24 | j0b0 | so would it make sense to patch htcraphael_android_defconfig |
| 18:12.06 | *** join/#htc-linux MethoS- (n=clemens@host-091-097-246-224.ewe-ip-backbone.de) |
| 18:12.38 | druidu | dunno, it's a bit behind htcraphael_defconfig |
| 18:13.18 | mickey|sofa | unfortunately androidisms have crept into htcraphael_defconfig and much was broken by the last commit to it |
| 18:13.18 | druidu | I'm really thinking of rewriting the whole board stuff and try to put all the similar boards into one file |
| 18:13.29 | druidu | your mdp packing patch is also very nice for this |
| 18:13.53 | j0b0 | one board file for raph/diam/blak? |
| 18:14.49 | druidu | yep |
| 18:15.23 | druidu | black seems similar to raphael, not sure, but as for diam and raphael they are different in only *one* driver -- raphael has a keyboard |
| 18:15.44 | druidu | rest is identical (well, plus the fixup part with the memory banks) |
| 18:15.59 | druidu | btw, any idea on how to detect what devices are on the i2c bus? |
| 18:16.04 | *** join/#htc-linux FR^2 (n=frquadra@frquadrat.de) |
| 18:16.17 | druidu | should be possible right? I mean, get the addresses of all the devices on the i2c bus |
| 18:16.25 | j0b0 | raph/diam 500 are interesting as it has soe stuff from 100 and some fro 800 |
| 18:17.29 | j0b0 | i dont know. i only know how to see the id in haret :/ |
| 18:18.10 | j0b0 | i imagine there could be some kind of 'who is there' message that would have all devices report their IDs? |
| 18:20.17 | *** join/#htc-linux pH5 (n=ph5@e178221161.adsl.alicedsl.de) |
| 18:21.16 | druidu | id as in i2c id? |
| 18:21.25 | *** join/#htc-linux marex (n=marex@thor.hackndev.com) |
| 18:21.31 | druidu | even bruteforce would do, just try all 255 addresses |
| 18:22.02 | druidu | i want this just for testing, don't care if it's under linux or wince, I wanna see all the devices that are there |
| 18:22.03 | *** join/#htc-linux Bally3 (n=Bally3@cpc1-blac6-0-0-cust618.manc.cable.ntl.com) |
| 18:23.15 | *** join/#htc-linux rafyvitto (i=rafyvitt@24.54.253.34) |
| 18:26.45 | *** join/#htc-linux toi (n=toi@d54C2AAB7.access.telenet.be) |
| 18:28.17 | rafyvitto | ok got the new dzo zimage running on my raph110 |
| 18:29.02 | *** join/#htc-linux idkfa (n=sergey@87.228.4.172) |
| 18:29.24 | *** join/#htc-linux MethoS-- (n=clemens@host-091-096-211-098.ewe-ip-backbone.de) |
| 18:29.50 | *** join/#htc-linux stickboy (n=anonymou@128.153.182.51) |
| 18:36.30 | *** join/#htc-linux darkstar62_ (n=darkstar@m660e36d0.tmodns.net) |
| 18:37.14 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 18:46.04 | *** join/#htc-linux ellisway (n=ellis@94.30.45.128) |
| 18:46.47 | *** join/#htc-linux darkstar62 (n=darkstar@97-126-104-157.tukw.qwest.net) |
| 18:50.28 | *** join/#htc-linux leaigor (n=laigor@188.134.36.14) |
| 18:51.29 | *** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it) |
| 18:53.28 | *** join/#htc-linux MethoS_ (n=clemens@host-091-097-242-130.ewe-ip-backbone.de) |
| 19:00.32 | *** join/#htc-linux Marajin (n=marajin@87-194-102-189.bethere.co.uk) |
| 19:03.27 | *** join/#htc-linux djatel (n=djatel@87.69.209.207) |
| 19:13.09 | *** join/#htc-linux MethoS- (n=clemens@host-091-097-247-122.ewe-ip-backbone.de) |
| 19:23.21 | *** join/#htc-linux MethoS-- (n=clemens@host-091-097-244-046.ewe-ip-backbone.de) |
| 19:28.41 | *** join/#htc-linux MethoS_ (n=clemens@host-091-097-246-105.ewe-ip-backbone.de) |
| 19:37.03 | *** join/#htc-linux Mark_ILB (n=Mark_ILB@adsl-67-38-81-158.dsl.sfldmi.ameritech.net) |
| 19:37.42 | Mark_ILB | hello |
| 19:43.07 | *** join/#htc-linux MethoS-- (n=clemens@host-091-096-214-098.ewe-ip-backbone.de) |
| 19:46.47 | *** join/#htc-linux rafyvitto (n=rafyvitt@199.1.152.227) |
| 19:47.31 | *** join/#htc-linux rafyvitto (n=rafyvitt@199.1.152.227) |
| 19:49.58 | *** join/#htc-linux sd00 (n=smac@82-39-194-231.cable.ubr02.jarr.blueyonder.co.uk) |
| 19:56.54 | *** join/#htc-linux MethoS_ (n=clemens@host-091-097-242-190.ewe-ip-backbone.de) |
| 20:00.23 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
| 20:03.39 | *** join/#htc-linux MethoS- (n=clemens@host-091-096-208-252.ewe-ip-backbone.de) |
| 20:09.07 | *** join/#htc-linux stickboy (n=anonymou@128.153.211.18) |
| 20:22.55 | *** join/#htc-linux MethoS-- (n=clemens@host-091-096-215-118.ewe-ip-backbone.de) |
| 20:23.17 | *** join/#htc-linux luc_ (n=luc@89-115-128-35.cl.ipv4ilink.net) |
| 20:28.43 | *** join/#htc-linux sd00 (n=smac@82-39-194-231.cable.ubr02.jarr.blueyonder.co.uk) |
| 20:33.28 | *** join/#htc-linux MethoS_ (n=clemens@host-091-096-208-109.ewe-ip-backbone.de) |
| 20:37.36 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-93-241.web.vodafone.de) |
| 20:38.13 | cr2 | hi |
| 20:40.50 | cr2 | BabelO: pin |
| 20:41.03 | BabelO | hi cr2 |
| 20:41.09 | BabelO | g |
| 20:41.36 | cr2 | BabelO: http://meduse.acri.fr |
| 20:42.26 | BabelO | cr2: nooo :) |
| 20:42.28 | BabelO | not here |
| 20:44.39 | cr2 | just fyi :) |
| 20:48.42 | cr2 | druidu: smd ch 0 is AT |
| 20:49.23 | cr2 | druidu: and GPRS works as expected. pppd on /dev/smd7, just connect first on /dev/smd0 |
| 20:55.14 | *** join/#htc-linux Bally3 (n=Bally3@cpc1-blac6-0-0-cust827.manc.cable.ntl.com) |
| 20:57.30 | cr2 | hey Bally3. already compiled linux for hermes ? |
| 21:00.33 | xperia | cr2: just extracted the xip from my rom but cant find the kernel. do you knwo where the kernel could be loacted |
| 21:00.52 | Bally3 | me? nope.. still playing with it.. I only learned how to compule kernels the other day :) |
| 21:01.10 | cr2 | xperia: you can get it from ram |
| 21:07.29 | druidu | cr2: so then why does it crash? |
| 21:08.21 | cr2 | android can't send DEX call by itself |
| 21:08.34 | cr2 | does the sound work for you ? |
| 21:08.48 | druidu | the image crashes for me... |
| 21:09.00 | druidu | I'm recompiling the whole android platform now, I'll get the playwav file from there |
| 21:09.21 | cr2 | the only unimplemented part is IIR and such things, and they need a DEX call too. it's strange that sound didn't work for me. |
| 21:09.32 | cmw | anyone here ever used TI's Riviera Tracer? |
| 21:10.11 | cr2 | druidu: it uses some binary library. time to look at it closer. |
| 21:11.02 | cr2 | druidu: is the static ioremap already in action for board_*init ? |
| 21:12.43 | druidu | what static ioremap? |
| 21:13.13 | cr2 | virtual addresses for IO mmapped areas |
| 21:13.40 | druidu | it's the standard one in include/mach/msm_iomap.h |
| 21:13.41 | cr2 | i'd like to dump a lot of info from smem and other registers. |
| 21:13.52 | cr2 | yes. when is it enabled ? |
| 21:14.04 | cr2 | i guess very early |
| 21:15.22 | druidu | msm_map_common_io() |
| 21:15.24 | druidu | in io.c |
| 21:16.15 | cr2 | #define MSM_CLK_CTL_BASE IOMEM(0xE0005000) |
| 21:16.18 | cr2 | ok |
| 21:17.34 | druidu | you can do the dumping in the halibut_map_io() function if you want to do it before the ios are mapped |
| 21:17.39 | cr2 | druidu: i'm in hotel now :) can you add some printks of readl(MSM_CLK_CTL_BASE+0xXXX) to board_ init ? |
| 21:18.01 | druidu | ok |
| 21:18.10 | druidu | after remap right? |
| 21:18.34 | cr2 | at a stage when readl will work |
| 21:18.40 | cr2 | board_init is ok |
| 21:18.46 | cr2 | http://htc-linux.org/wiki/index.php?title=MSM_CLK |
| 21:19.00 | cr2 | the PLL* L,M,N values |
| 21:19.17 | cr2 | 9 numbers in total |
| 21:20.04 | cr2 | i'll fix the s* names in wiki now. |
| 21:20.32 | cr2 | "s?" are some other unknown settings. |
| 21:21.56 | *** join/#htc-linux rafyvitto (i=rafyvitt@24.54.253.34) |
| 21:22.13 | cr2 | +0x304 PLL0_L_VAL |
| 21:22.29 | cr2 | +0x308 PLL0_M_VAL |
| 21:22.47 | cr2 | +0x30c PLL0_N_VA |
| 21:23.03 | cr2 | +0x320 PLL1_L_VAL |
| 21:23.16 | cr2 | +0x324 PLL1_M_VAL |
| 21:23.29 | cr2 | +0x328 PLL1_N_VAL |
| 21:23.43 | cr2 | +0x33c PLL2_L_VAL |
| 21:23.53 | cr2 | +0x340 PLL2_M_VAL |
| 21:24.04 | cr2 | +0x344 PLL2_N_VAL |
| 21:24.49 | cr2 | i want these values to be present in all our dmesg, so we can see the settings for all our 7x0xA phones |
| 21:25.34 | cr2 | readl(MSM_CLK_CTL_BASE+0xXXX) |
| 21:29.26 | *** join/#htc-linux marcin88 (n=marcin@chello089078160132.chello.pl) |
| 21:32.49 | xperia | cr2: i have a question to you. how is it possible when somebody goes in the tricolour spl screen that the version of microp chips are printed even when the kernel is not loaded? |
| 21:33.15 | xperia | how can spl know the versions number of microp |
| 21:37.27 | druidu | xperia: XIP - Execute In Place means that the kernel DLLs are flashed to nvram and they don't have to be loaded -- they're already there |
| 21:39.09 | druidu | unlike our current setup for linux in which the kernel is compressed, loaded in ram by haret then it's executed (it's like a self-extracting kernel image, unpacks itself in ram and executes itself) |
| 21:45.12 | *** join/#htc-linux sd00 (n=smac@82-39-194-231.cable.ubr02.jarr.blueyonder.co.uk) |
| 21:47.05 | xperia | druidu: thanks for the explaintation. then it looks like that everything speaks that the logis must be in this dll. hmmm |
| 22:23.58 | *** join/#htc-linux stickboy (n=anonymou@128.153.181.104) |
| 22:25.15 | *** join/#htc-linux varius (n=vrs@84-75-52-218.dclient.hispeed.ch) |
| 22:31.50 | *** join/#htc-linux Darwin2 (n=cmeresse@62-2-167-20.static.cablecom.ch) |
| 22:32.16 | Darwin2 | Hello |
| 22:36.35 | *** part/#htc-linux Darwin2 (n=cmeresse@62-2-167-20.static.cablecom.ch) |
| 22:39.40 | *** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821) |
| 22:40.55 | druidu | cr2: got the values :) |
| 22:40.56 | druidu | [ 1.516876] PLL0 @ e0005300: MODE=00000007 L=0000000c M=00000004 N=00000005 |
| 22:40.56 | druidu | [ 1.516967] PLL1 @ e000531c: MODE=00000007 L=00000028 M=00000000 N=00000001 |
| 22:40.56 | druidu | [ 1.517028] PLL2 @ e0005338: MODE=00000007 L=00000037 M=00000000 N=00000001 |
| 22:41.49 | druidu | I know what PLL stands for, but where do they come in? |
| 23:03.20 | *** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-58-38.dynamic.mnet-online.de) |
| 23:11.43 | cr2 | druidu: acpuclock.[ch] |
| 23:12.03 | cr2 | druidu: and clock-wince.c |
| 23:12.05 | cr2 | g |
| 23:12.09 | cr2 | ood night |
| 23:13.24 | *** join/#htc-linux marcin88 (n=marcin@chello089078160132.chello.pl) |
| 23:18.29 | *** part/#htc-linux sd00 (n=smac@82-39-194-231.cable.ubr02.jarr.blueyonder.co.uk) |
| 23:22.06 | druidu | 'night |