00:03.23 | tmzt_ | NetRipper: is CMDA 18bpp or not? |
00:10.32 | *** join/#htc-linux TheOther (n=nahh@178.80-202-153.nextgentel.com) |
00:18.09 | *** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com) |
00:23.06 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) |
00:51.04 | *** join/#htc-linux era| (n=im@pool-70-16-74-15.port.east.verizon.net) |
01:03.07 | *** part/#htc-linux snadge (n=snadge@starbug.ugh.net.au) |
01:11.57 | *** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231) |
01:15.36 | *** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |
01:38.38 | *** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |
02:13.28 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-e0537e9b7e39656b) |
02:55.13 | *** join/#htc-linux br1ck_ (n=br1ck@xdslcd208.osnanet.de) |
03:14.42 | *** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |
03:21.05 | *** join/#htc-linux tekkdrone_ (n=tekkdron@72.183.115.231) |
03:33.11 | *** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net) |
03:45.26 | *** join/#htc-linux Tinyboom (n=nahh@178.80-202-153.nextgentel.com) |
03:50.50 | *** join/#htc-linux lavender1t (n=jerrey@c-24-17-204-47.hsd1.wa.comcast.net) |
03:55.03 | *** join/#htc-linux Castr0 (n=castr0@96.246.168.228) |
04:23.06 | parmaster | tekkdrone are you able to bring up a csd or evdo connection? |
04:23.40 | tekkdrone | actually, but accident, I believe I just did |
04:23.45 | tekkdrone | by accident* |
04:23.51 | parmaster | nice |
04:23.54 | tekkdrone | then it died, and came back, then died again |
04:23.56 | tekkdrone | lol |
04:23.58 | parmaster | do you have a link to the images you're using? |
04:24.22 | tekkdrone | not the most current ones no, I was hoping to post the latest tomorrow at chillaxin.net |
04:24.28 | parmaster | what phone application are you using with it |
04:24.31 | tekkdrone | (personal blog, no spam) |
04:25.04 | tekkdrone | none yet, I'm still workiong out the details, tmz just slipped me the pxa ohci code last week |
04:25.15 | tekkdrone | and of course, there's no smd0 or smd1 on here so... |
04:26.02 | parmaster | cool i've never seen cdma AT setup |
04:26.07 | tekkdrone | I had my apache sitting on the lock screen and I was messing with dzo's ril code and some manual at commands, suddenly my lock screen said Android instead of no service, and the 3G icon came up, then jumped up 2 bars |
04:26.09 | parmaster | what commands do you send to the modem |
04:26.36 | tekkdrone | standard fare, AT+HTC_DUN=0, etc |
04:26.44 | parmaster | oh ok |
04:26.53 | tekkdrone | i'm talking to ti via ttyS0 |
04:26.56 | tekkdrone | to it* |
04:27.21 | parmaster | was there some automatic line discrimination done through setthci |
04:27.25 | parmaster | or whatever |
04:27.42 | tekkdrone | I have absolutely no idea, ppp is new territory for me |
04:28.02 | parmaster | no i mean jsut to be able to talk to /dev/ttyS0 |
04:28.10 | tekkdrone | oh yes, it's a FFUART |
04:28.14 | parmaster | ok |
04:28.37 | tekkdrone | i can microcom in and watch CSQ signal strenth scroll by |
04:28.50 | tekkdrone | strength* sorry new keyboard |
04:28.59 | parmaster | you could also cu in |
04:29.14 | parmaster | just copy armv5te cu package to it |
04:29.28 | parmaster | then chmod uucp.uucp /dev/ttyS0 |
04:29.34 | tekkdrone | what's cu? |
04:29.37 | parmaster | execute cu on it -s 115200 |
04:30.06 | parmaster | then after cu is connected to it set the perms back to normal and run whatever else against it you want |
04:30.16 | parmaster | and you'll see the commands it send and the response |
04:30.19 | tekkdrone | capture utility? |
04:30.23 | tekkdrone | ahh gotcha |
04:30.29 | parmaster | no its the call unix command |
04:30.31 | parmaster | oldschool |
04:30.58 | tekkdrone | right on |
04:31.43 | tekkdrone | question, what handles power switching on peripherals, pda-power? |
04:31.44 | parmaster | how do you dial via the cdma modem though |
04:32.37 | tekkdrone | well so far I've only done so accidentally, using dzo's scripts and libreference, and I have a device called smd1 with the major and minors of ttyUSB0, which is my qualcomm on ohci |
04:33.06 | tekkdrone | smd0 is setup the same way, but with ttyS0's device node numbers |
04:33.15 | parmaster | nice |
04:33.22 | tekkdrone | it's dirty but it was only intended as a test |
04:34.02 | tekkdrone | I really don't know a damn thing about cellular ppp |
04:34.40 | parmaster | when you qualcom on ohci.. which chipset are you talking about 6800 or something? |
04:34.51 | tekkdrone | 6500 I believe |
04:35.00 | parmaster | oops yep thats what i meant |
04:35.34 | parmaster | cool so who hooked u up with it? |
04:35.35 | parmaster | tmzt? |
04:36.10 | tekkdrone | yeah he had a couple of golden lines with addresses for ohci |
04:36.18 | parmaster | kick ass... |
04:36.28 | parmaster | now i look forward to some real progress |
04:36.33 | tekkdrone | after that it was a matter of adding it to init and checking the generic OHCI in the kernel config |
04:36.48 | tekkdrone | I was shocked to see usb 1-1: Product: Qualcomm CDMA Technologies MSM |
04:36.48 | tekkdrone | usb 1-1: Manufacturer: Qualcomm, Incorporated |
04:36.48 | tekkdrone | <PROTECTED> |
04:37.04 | parmaster | yeah he was saying he thought it was through usb |
04:37.19 | tekkdrone | aye there's some stuff about it in o'connors notes too |
04:37.33 | parmaster | ok cool |
04:37.51 | tekkdrone | well, pretty much that sentence you just said is in his notes |
04:37.52 | tekkdrone | lol |
04:38.03 | parmaster | ;-) |
04:38.03 | tekkdrone | and that's it |
04:41.29 | tekkdrone | best thing was getting udc and the adb gadget driver working last night, no more typing on the tiny keyboard, yay. |
04:41.53 | tekkdrone | it's dirty though, but from what I've read, with the pxa27x dirty is standard fare |
04:48.19 | parmaster | i've got an apache laying around somewhere let me know if you want me to play around with it too when you get more settled with it |
04:49.21 | tekkdrone | thanks :) |
04:51.10 | parmaster | i even still have it active through sprint |
04:52.20 | tekkdrone | heh, don't wanna pay the contract termination fee? |
04:53.04 | parmaster | well its got an old number in silicon valley attached to it tha everyone knows... so i keep it on for that reason |
04:53.39 | tekkdrone | ahhh mine's in another area code, same reason |
04:55.24 | parmaster | are any of the other devices working on it? |
04:55.54 | parmaster | bluetooth? |
05:01.12 | tekkdrone | not yet |
05:01.54 | tekkdrone | I don't think that was even working previously on the old hh kernel |
05:01.56 | tekkdrone | >_< |
05:02.07 | parmaster | yeah in fact i'm sure it wasn't |
05:07.21 | tmzt_ | hi, parmaster |
05:10.00 | parmaster | hi tmzt :) |
05:14.03 | *** join/#htc-linux holycow (n=rtaylor@S01060016b6b53675.vf.shawcable.net) |
05:17.50 | tmzt_ | what's going on? |
05:22.56 | parmaster | not much, glad to see stuff coming along retroactively |
05:24.15 | tmzt_ | tekkdrone: you see CSQ unsolicited messages on which ttyS0/ttyUSB0 ? |
05:34.07 | *** join/#htc-linux tekkdrone_ (n=tekkdron@72.183.115.231) |
05:34.20 | tekkdrone_ | argh |
05:42.29 | tmzt_ | tekkdrone: you see CSQ unsolicited messages on which ttyS0/ttyUSB0 ? |
05:42.46 | tekkdrone | ttyS0 |
05:43.31 | tmzt_ | interesting, that may be primarily the voice at channel |
05:43.45 | tmzt_ | have you been able to connect to EVDO? |
05:43.54 | tekkdrone | I think I have, but only by mistake |
05:44.13 | parmaster | are you sure those CSQ messages aren't towers? |
05:44.42 | tekkdrone | I was fiddling around and my lock screen suddenly showed "Android" isntead of no service, my 3g icon appeared, and I had an active signal bar, then it dc'd |
05:45.00 | tekkdrone | first I'd seen of it |
05:45.56 | tekkdrone | as far as I know, it's just my signal strenth indicator (the HTC_CSQ(x,x) messages) |
05:47.11 | parmaster | do you see tower numbers in there? |
05:47.18 | tekkdrone | no |
05:47.37 | tekkdrone | just two integers |
05:47.43 | parmaster | how big are they |
05:47.48 | parmaster | like, show me a pair |
05:47.55 | tekkdrone | 3,3 4,4 |
05:47.56 | tekkdrone | etc |
05:48.03 | parmaster | oh ok.. yeah... def not then |
05:48.28 | tmzt_ | tekkdrone: does usb0 also respond to at commands? |
05:48.47 | tekkdrone | I haven't attempted as I have no idea what speed to terminal in at |
05:49.10 | tmzt_ | 115200 should work, but usb doesn't really have baud rate |
05:49.29 | tekkdrone | aye, does it not matter being that it's usbserial? |
05:49.38 | tekkdrone | (ttyUSB0) |
05:49.40 | tmzt_ | right |
05:49.45 | tekkdrone | ah cool |
05:57.09 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
06:36.53 | parmaster | actually on usb you might want to try 19200 |
06:38.22 | parmaster | 230k, all that |
06:41.12 | parmaster | 300,600,1200,1800,2400,4000,4800,7200,9600,14400,16000,19200,28800,38400,51200,56000,57600,64000,76800,115200,128000,153600,230400,250000,256000,460800,500000,576000,921600 |
06:41.19 | parmaster | it's certaint to be one of those :) |
06:42.37 | parmaster | UART baud rates |
06:44.23 | *** join/#htc-linux data|2 (n=datachao@189.27.166.151.adsl.gvt.net.br) |
06:44.28 | parmaster | you request a baud rate and its gonna translate into one of those anyway. |
06:49.56 | parmaster | an application can just request any baud rate and it will actually give whichever of those rates in that list is closest to the one requested. |
06:50.34 | tekkdrone | fair enough, so far I'm not seeing any responses or unsolicited messages |
06:55.41 | parmaster | theres a usb to uart bridge controller there.. so i guess you could try all of rates |
06:55.49 | parmaster | up to you what you want to do |
06:56.49 | *** join/#htc-linux kiozen (n=oeichler@p5492A3DF.dip0.t-ipconnect.de) |
06:57.00 | tmzt_ | parmaster: usb to uart where? |
06:57.14 | parmaster | has to be |
06:57.31 | tmzt_ | you mean in the msm chip? |
06:57.47 | parmaster | if you are conencting via usb to a uart |
06:58.06 | *** join/#htc-linux lpotter (n=ljp@CPE-124-191-144-181.vic.bigpond.net.au) |
06:58.14 | parmaster | it would be 'part of the usb' |
06:58.29 | tmzt_ | the usb is connected to the msm chip, which has a device controller like the pxa |
06:58.52 | parmaster | then consider its 'part of the usb' |
07:01.07 | parmaster | just brute force all of the speeds look for data then done ;) |
07:02.17 | *** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
07:02.26 | tmzt_ | tekkdrone: do you have minicom? |
07:18.04 | *** join/#htc-linux kkaze_wor (n=kaze@ABordeaux-152-1-21-24.w82-125.abo.wanadoo.fr) |
07:18.21 | *** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231) |
07:27.38 | parmaster | thats everything up to about a megabit |
07:29.10 | parmaster | The FFUART supports modem-control capability. The maximum baud rate is 921,600 bps. |
07:29.32 | parmaster | so those 32 baud rates cover everything. |
07:30.09 | parmaster | thats straight from the PXA27x developers manual. |
07:30.20 | tekkdrone | aye, I can terminal to the ffuart |
07:30.28 | tmzt_ | ok, you mean the ttyS0 then, I was referring to the ttyUSB0 |
07:30.46 | tekkdrone | yes, ttyUSB0 is an ohci device |
07:31.00 | tmzt_ | tekkdrone: can you connect to the usb and see if it responds to AT commands? |
07:31.08 | tekkdrone | I attempted, got nothing |
07:31.09 | tmzt_ | tekkdrone: ohci is the host controller |
07:31.23 | parmaster | Because 921,600 bps is not a common standard baud rate programs like stty do not typically support it. A quick work around to this problem is to use a simple C program to set the baud rate manually using the termOptions struct in Linux. |
07:31.34 | tmzt_ | ok, can you try dialing ATD#777 on the S0 then |
07:31.50 | parmaster | C program is available at: |
07:31.53 | parmaster | http://embedded.seattle.intel-research.net/wiki/index.php?title=Using_other_UARTs_in_Linux |
07:31.53 | tekkdrone | yes, lemme reboot the phone and start fresh with dzo's scripts disabled |
07:32.19 | tmzt_ | if dzo scripts work, you should be ok then |
07:32.34 | tmzt_ | do any of the phone functions work? |
07:33.11 | tekkdrone | I haven't tried a call, I've yet to add in sound |
07:34.03 | tmzt_ | not the sound, just if you can make a call/receive a call in android |
07:34.39 | tekkdrone | i've yet to try, as far as android's concerned I'm not registered on a network |
07:34.44 | parmaster | what version of android are you trying 0.8? |
07:34.50 | tekkdrone | 1 |
07:34.53 | parmaster | k |
07:35.13 | tmzt_ | try dzo libreference_ril from vogue linux or dcordes bootkit |
07:35.45 | tekkdrone | I have it, is the one one from the files on his site up to date? |
07:35.45 | tmzt_ | well, dcordes for 0.8 |
07:36.20 | tmzt_ | linuxtogo.org/~lgorris/ |
07:39.01 | *** join/#htc-linux rob_w (n=bob@p549BE4F9.dip.t-dialin.net) |
07:40.59 | parmaster | hi rob_w |
07:47.32 | rob_w | hi |
07:53.54 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
07:58.37 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
08:00.08 | *** join/#htc-linux marmotta (n=skodde@e178062242.adsl.alicedsl.de) |
08:08.31 | *** join/#htc-linux tekkdrone_ (n=tekkdron@72.183.115.231) |
08:21.25 | *** join/#htc-linux holycow (n=rtaylor@S01060016b6b53675.vf.shawcable.net) |
08:37.16 | *** join/#htc-linux kilian_ (n=kilian@92.66.94.81) |
08:39.32 | *** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
09:08.16 | *** join/#htc-linux pishuri (n=pishuri@194.230.146.235) |
09:24.57 | NetRipper | tmzt_, the forum post meant android, but confused it with x11 ;) |
09:26.00 | NetRipper | tmzt_, and i think cmda is also 16bpp but a different rgb spacing somehow.. i dont know the detials about that |
09:26.51 | NetRipper | jobo posted something in the form of rrrbbgggGGggg or something lol |
09:26.54 | NetRipper | dont know how that works |
09:27.18 | NetRipper | i am anxious to see lavender.t's diff though |
09:27.27 | NetRipper | as he had some results with mmc on diamond |
09:37.25 | tmzt_ | hi, NetRipper |
09:40.09 | tmzt_ | I guess it means the colors are in planes |
09:41.05 | tmzt_ | cr2 found what should be the lcd controller on raph |
09:45.11 | tmzt_ | 4:4:4 ? what is that for |
09:45.55 | tmzt_ | maejrep: you here? |
09:52.13 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
10:02.19 | *** join/#htc-linux Magister7 (n=Magister@vicont.in.ua) |
10:06.24 | tmzt_ | NetRipper: the "stuck" cursor problem has been seen on the kaiser by dcordes since early summer, we think it's caused by the screen not updating and someone has added an update thread to the ts driver |
10:07.00 | NetRipper | tmzt_, yes, and i heard it worked for kaiser |
10:07.03 | NetRipper | uh |
10:07.05 | NetRipper | polaris |
10:07.11 | NetRipper | so probably kaiser as well |
10:07.12 | tmzt_ | ok, good |
10:08.03 | tmzt_ | did you see the message from cr2 about the lcd controller s1dxxxx chip? |
10:08.19 | tmzt_ | is this the mddi client or is that the lcd itself? |
10:12.55 | NetRipper | no i didnt see any messages from cr2 |
10:13.11 | NetRipper | and i dont know whether it is the mddi client or lcd |
10:13.16 | NetRipper | i'd think mddi |
10:13.45 | *** join/#htc-linux br1ck (n=br1ck@xdslcd208.osnanet.de) |
10:13.59 | NetRipper | or, isn't mddi built into the msm chip? |
10:14.13 | tmzt_ | S1D13774_DB |
10:14.33 | tmzt_ | I think mddi is a bus |
10:14.45 | NetRipper | http://www.spezial.com/commercio/dateien/produktbeitraege/S1D13774_DB.pdf |
10:14.50 | NetRipper | lcd controller |
10:15.01 | NetRipper | S1D13774 WVGA LCD Controller |
10:15.06 | tmzt_ | that says it's an mddi client, or it's listed as a supported connection of something |
10:15.47 | NetRipper | MDDI, 18-bit Indirect, or I2C Host Interface |
10:15.51 | NetRipper | is one of its features |
10:17.13 | tmzt_ | http://www.qctconnect.com/products/mddi.html |
10:17.45 | NetRipper | yes, that's just the standard |
10:19.46 | NetRipper | hm, that lcd controller has tv out support |
10:23.45 | tmzt_ | right |
10:24.19 | tmzt_ | anything that can be read from windows to find the display configuration, like on pxa and omap? |
10:29.56 | *** join/#htc-linux br1ck (n=br1ck@xdslcd208.osnanet.de) |
10:31.58 | NetRipper | you can read the framebuffer data, then try to let photoshop interpret it |
10:32.20 | NetRipper | (or gimp) |
10:32.27 | tmzt_ | well I mean color depth or pixel format |
10:32.29 | NetRipper | (or imagemagick convert) |
10:32.54 | *** join/#htc-linux stefan_schmidt (n=stefan@c120.apm.etc.tu-bs.de) |
10:32.56 | tmzt_ | mddi registers or anything else that might be helpful |
10:32.59 | NetRipper | well photoshop would have to detect the format |
10:33.33 | NetRipper | but i dont know how about other things |
10:33.56 | tmzt_ | basically taking registers from the kernel headers and dumping them with haret |
10:34.41 | tmzt_ | anyway, do you know why the htc console is still needed? |
10:37.08 | Magister7 | hello to all |
10:38.05 | Magister7 | tmzt_: can you tell me how to dump mddi registers with haret? as far a I understand, that will help me to implement panel on/off, right? |
10:38.33 | tmzt_ | pd for physical address |
10:38.39 | tmzt_ | pd <phys> <size> |
10:38.50 | tmzt_ | pwf <filename> <phys> <size> |
10:39.01 | tmzt_ | the order could be wrong on the second one |
10:40.26 | tmzt_ | Magister7: what device do you have? |
10:40.36 | Magister7 | Titan |
10:41.29 | tmzt_ | the linux headers should have the physical addresses for mddi |
10:41.38 | tmzt_ | don't know if that helps with suspend |
10:42.32 | Magister7 | well... I tried to dump (address from Memory map on xda wiki), and if then I am doing power off (the code taken from Vogue), and power on (the same code, but writing dumped data) - backlight comes, but there is no any picture. |
10:42.51 | Magister7 | is it possible to trace what WinCE does during panel on/off? |
10:43.34 | tmzt_ | read ApachePhoneTrace and HaRET on handhelds.org wiki |
10:43.49 | tmzt_ | not everything applies to msm but should be similar |
10:44.26 | tmzt_ | you probably need to init the lcd to power it back on |
10:44.38 | tmzt_ | more than just writing registers |
10:45.13 | Magister7 | maybe... but how to do that? |
10:45.40 | Magister7 | and looks like it's true, because backlight comes |
10:47.44 | tmzt_ | backlight turns on but not the lcd? |
10:47.52 | Magister7 | нÑÑ |
10:47.58 | Magister7 | sorry.. yes |
10:48.54 | tmzt_ | does it work on vogue? |
10:49.06 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-9ed792b3b309a1a7) |
10:49.26 | Magister7 | yes, dzo got it fully working on vogue |
10:49.54 | tmzt_ | see what his does for init if it does |
10:50.10 | *** join/#htc-linux beabras (n=bb@213.226.165.195) |
10:50.14 | tmzt_ | I guess the lcd's are different on vogue/titan? I thought hw was similar |
10:52.15 | Magister7 | the hardware is very similar, the same kernel will run on both titan and vogue (display, pm, leds, charging, battery meter, sound, etc). but looks like lcd is somewhat different.... |
10:54.28 | Magister7 | the code from dzo: |
10:54.28 | Magister7 | <PROTECTED> |
10:54.28 | Magister7 | <PROTECTED> |
10:54.28 | Magister7 | <PROTECTED> |
10:54.28 | Magister7 | <PROTECTED> |
10:54.29 | Magister7 | <PROTECTED> |
10:54.31 | Magister7 | <PROTECTED> |
10:54.33 | Magister7 | <PROTECTED> |
10:54.35 | Magister7 | <PROTECTED> |
10:54.37 | Magister7 | <PROTECTED> |
10:54.39 | Magister7 | <PROTECTED> |
10:54.41 | Magister7 | <PROTECTED> |
10:54.43 | Magister7 | <PROTECTED> |
10:54.45 | Magister7 | <PROTECTED> |
10:54.47 | Magister7 | <PROTECTED> |
10:54.49 | Magister7 | <PROTECTED> |
10:54.51 | Magister7 | <PROTECTED> |
10:54.53 | Magister7 | <PROTECTED> |
10:54.55 | Magister7 | <PROTECTED> |
10:54.57 | Magister7 | <PROTECTED> |
10:54.59 | Magister7 | <PROTECTED> |
10:55.58 | tmzt_ | maejrep: If you can find how to dump the registers set in the jobo patches on cdma raph with haret |
10:56.15 | tmzt_ | Magister7: ok, the titan panel is in there? |
10:56.55 | Magister7 | regs_on_xxx is a an array of {register, value, delay} items |
10:57.40 | Magister7 | write_mddi_regs calls mddi_remote_write(panel->mddi, regs->val, regs->reg); and then mdelay(regs->time); for each array item |
10:58.14 | Magister7 | how can I find which panel is on Titan? |
10:58.29 | tmzt_ | ok, you have your own regs made for titan? |
10:59.08 | beabras | Hello, anybody here working on Kaiser/Tytn II + Android? |
10:59.25 | tmzt_ | dcordes is working on kaiser |
11:00.46 | tmzt_ | I don't know if 1.0 is working, but you can try the initrd from vogue thread on xda-devs |
11:00.59 | tmzt_ | http://forum.xda-developers.com/showthread.php?t=382265&page=240 |
11:03.05 | Magister7 | tried to dump them with haret (traced, but it says that tracing of that area is not well suported) |
11:03.11 | Magister7 | and tried to do: |
11:03.11 | Magister7 | <PROTECTED> |
11:03.11 | Magister7 | <PROTECTED> |
11:03.11 | Magister7 | <PROTECTED> |
11:03.12 | Magister7 | <PROTECTED> |
11:03.32 | Magister7 | but got different values, and none of them worked |
11:06.45 | *** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl) |
11:07.08 | tmzt_ | try dump mmu 2 <phys> |
11:07.21 | tmzt_ | and trace the virtual addresses (the 1MB ones) |
11:11.15 | tmzt_ | Magister7: on the devices lcd init has been found, the primary method is the bootloader |
11:11.18 | tmzt_ | spl |
11:11.37 | *** join/#htc-linux Loki657 (n=Loki657@82.147.51.146) |
11:11.40 | Loki657 | hi all! |
11:11.51 | tmzt_ | hi |
11:11.53 | Magister7 | tmzt_: what does it mean? |
11:12.07 | Loki657 | Anyone here working on Android for the Diamond and/or Touch Pro? |
11:12.11 | tmzt_ | Magister7: I mean someone would have to look at the spl on titan |
11:12.55 | tmzt_ | Loki657: do you have gsm or cdma? |
11:13.02 | Loki657 | gsm |
11:13.15 | Loki657 | got a RAPH100 myself |
11:13.30 | Magister7 | hm... looks like that I should be that "someone"... |
11:15.22 | tmzt_ | Loki657: for android information: http://forum.xda-developers.com/showthread.php?t=402002&page=104 |
11:15.27 | Loki657 | Yeah, I know |
11:15.34 | Loki657 | ive been following the development quite closely |
11:15.42 | Loki657 | I was just wondering if anyone in here is working on it |
11:15.57 | tmzt_ | NetRipper is working on raph100 |
11:16.16 | Loki657 | Ah |
11:16.19 | Loki657 | il give him a shout then |
11:16.51 | tmzt_ | what are you looking for? |
11:16.56 | Loki657 | Just a way to help |
11:17.07 | Loki657 | I am interessted in your opinion though.. How likely is it that we will see Android fully working? The Vouge has come very far, but still isnt 100% working |
11:17.35 | tmzt_ | raph is closer to g1 than vogue |
11:17.37 | Loki657 | and I spoke with a market director with HTC a week ago, and he told me that they wont be offering Android to WinMo devices from HTC |
11:17.57 | Loki657 | I know, but Android 1.0 is running quite good on the vouge |
11:18.16 | *** join/#htc-linux miknix (n=miknix@193.137.97.156) |
11:18.27 | tmzt_ | raph should support h3wd driver and libhgl so android will run as fast as on g1, hopefully |
11:19.04 | tmzt_ | the biggest differences are probably in the amss (radio) and what commands it supports on the shared memory channels |
11:19.17 | tmzt_ | as well as different lcd which is being worked on |
11:19.53 | Loki657 | I have no conserns regarding performance, I am just curious as to the likelyhood of Android fully working on it.. Considering how far they have come with the HTC Vogue, although some significant features still arent in |
11:20.25 | Loki657 | http://www.engadget.com/2008/12/10/video-android-rocking-on-the-htc-touch/ |
11:20.31 | Loki657 | if you havent seen it already |
11:20.43 | tmzt_ | I believe the vogue support is based on the sdk image and drivers |
11:21.00 | tmzt_ | for msm_fb at least |
11:21.26 | Loki657 | yeah |
11:21.48 | Loki657 | but still.. what do you think? Will we get Android running perfectly? |
11:22.17 | tmzt_ | not sure what you are asking then |
11:22.39 | br1ck | it doesnt even need to run perfectly, it would still be better than winmo |
11:23.14 | Loki657 | just curious as to the likelyhood of Android running on, lets say the Raph or any other phone than the G1, just as well as on the G1 (all features, functionality, etc) |
11:23.15 | br1ck | sorry for the drop-in, i am only lurking around |
11:23.35 | tmzt_ | hi br1ck |
11:23.40 | Loki657 | Android has a nicer UI than WinMo, but WinMo is still ahead when it comes to functionality ;) |
11:24.03 | Magister7 | tmzt_: is there a source of Olipro SPL? |
11:24.09 | tmzt_ | someone was concerned about the app store and not having any applications |
11:24.21 | tmzt_ | Magister7: ask him |
11:24.25 | Loki657 | with the Vogue, you can manually install apps though.. Just not through the App store.. |
11:24.33 | tmzt_ | Magister7: I think they modify the hex though |
11:24.39 | tmzt_ | Magister7: I think they modify the asm though |
11:25.04 | Magister7 | tmzt_: hm.. maybe. will try to ask.. |
11:25.30 | tmzt_ | he's usually in #hpcdev or #xda-dev |
11:25.34 | Loki657 | Was thinking about getting the G1, but then I realized that Android would be the only reason doing so.. The hardware on it sucks.. So having Android on my Touch Pro would make it perfect :) |
11:25.44 | beabras | I have not been ivolved in development or porting so far, so I would like to understand porting problem in high-level: what are main problems in making run Android on Kaiser(or other HTC devices): writing drivers, getting spec's for chips to be able to write drivers or some other problems? |
11:26.09 | tmzt_ | Loki657: there may be no reason the g1 or dev phone image wouldn't work if the drivers were written |
11:26.29 | Loki657 | aha, thanks |
11:26.48 | Loki657 | now, to my follow up.. How can I help? I Have some contacts in Google which could be able to help out.. |
11:28.11 | Loki657 | I could also support through donations.. |
11:28.23 | tmzt_ | basically, google release source for the msm7201a last fall |
11:29.17 | tmzt_ | this supports most of the hardware inside the system-on-chip package, but much of the functionality of the msm chips is implemented in the AMSS software running on the arm9 core |
11:29.48 | tmzt_ | this implements phone, gps, connection to the dsp for video, gps decorr., etc. |
11:29.51 | Loki657 | right.. |
11:30.07 | tmzt_ | also, the clocks some power functions and other things needed |
11:30.28 | tmzt_ | the protocol for controlling these things is different (and undocumented) on the windows-based HTC devices |
11:30.32 | Loki657 | so, bottom line is.. what can Google o? :) |
11:30.39 | Loki657 | do* |
11:31.40 | tmzt_ | google developers have answered some questions here and in #android, have documented the source well and provided a usable git history (not complete though) |
11:31.57 | Loki657 | so there isnt much more they can do then? :) |
11:34.10 | tmzt_ | for raphael? what do you mean |
11:36.53 | Loki657 | for anything |
11:36.54 | Loki657 | hehe |
11:39.37 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
11:42.34 | Loki657 | I just want to help out.. heh |
11:49.11 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
11:49.29 | Loki657 | oh well, just let me know |
11:55.49 | parmaster | this is #htc-linux ;) |
11:58.48 | Loki657 | yup |
12:21.24 | *** part/#htc-linux Magister7 (n=Magister@vicont.in.ua) |
12:31.29 | *** join/#htc-linux datachaos (n=datachao@c915521c.virtua.com.br) |
13:01.09 | NetRipper | Loki657, /query is less secure, but more common than /dcc chat ;) |
13:02.25 | Loki657 | ah, hi Netripper |
13:07.54 | parmaster | hahahaha |
13:07.57 | parmaster | http://forum.xda-developers.com/showthread.php?t=382265 |
13:08.04 | parmaster | that link made it into information week. |
13:08.26 | parmaster | http://www.informationweek.com/blog/main/archives/2008/12/android_goes_bo.html |
13:11.41 | NetRipper | hi loki |
13:13.23 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
13:13.29 | NetRipper | "android goes borg", how lame ;) |
13:16.44 | *** join/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig) |
13:17.01 | *** part/#htc-linux LanceHaig (i=c2d8ed19@foresight/member/lhaig) |
13:20.06 | parmaster | NetRipper: :-) |
13:30.06 | *** join/#htc-linux metter (n=metter@32-149.62-81.cust.bluewin.ch) |
13:45.38 | *** join/#htc-linux pishuri (n=pishuri@users3.ilo.org) |
14:10.39 | *** join/#htc-linux Uncle_CM (i=Uncle@gateway/tor/x-026c3ee7e3c3733c) |
14:13.17 | maejrep | tmzt_, i'll see what i can do, will probably have to be later tonight |
14:13.30 | maejrep | do you need a before/after the patch? |
14:22.27 | *** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231) |
14:40.50 | *** join/#htc-linux lpotter (n=ljp@CPE-124-191-144-181.vic.bigpond.net.au) |
14:44.47 | *** join/#htc-linux surgex (i=surge@pool-98-118-165-224.bflony.fios.verizon.net) |
15:20.35 | *** join/#htc-linux mooky (n=suzannet@berger.projecthugo.co.uk) |
15:20.39 | *** join/#htc-linux dcordes (n=dcordes@ip-90-186-233-225.web.vodafone.de) |
15:20.54 | dcordes | NetRipper, others: hi |
15:21.08 | dcordes | NetRipper: which thread should I check? |
15:33.43 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
15:51.02 | *** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com) |
16:31.31 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
16:48.27 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87db08.pool.einsundeins.de) |
17:07.36 | *** join/#htc-linux LunohoD_ (n=alex@e180079225.adsl.alicedsl.de) |
17:10.46 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
17:18.41 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
17:54.49 | *** join/#htc-linux pishuri (n=pishuri@194.230.146.4) |
18:02.10 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
18:03.28 | dcordes | beabras sorry been busy |
18:03.41 | dcordes | I'll be back later |
18:12.08 | *** join/#htc-linux KungFunk (n=cow@c-ecd572d5.014-46-73746f28.cust.bredbandsbolaget.se) |
18:17.05 | *** join/#htc-linux Xime (n=xime@dag94-3-82-233-170-230.fbx.proxad.net) |
18:22.12 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
18:52.49 | *** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231) |
19:00.26 | *** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com) |
19:03.37 | tekkdrone | fuckin A google.com just loaded |
19:03.43 | tekkdrone | hot damn |
19:08.36 | Bally3 | on what?? |
19:09.32 | tekkdrone | apache |
19:10.00 | Bally3 | aah |
19:10.03 | tekkdrone | android release, htc apache, pxa27x, cdma |
19:10.19 | tekkdrone | using dzo's libreference and a ton of dicking around |
19:10.59 | Bally3 | did you get his libreference then? would appreciate if you could point me to it |
19:11.18 | tekkdrone | I didn't get his source, just the one on his websute |
19:11.21 | tekkdrone | website* |
19:11.39 | Bally3 | aah ok |
19:12.17 | tekkdrone | lol damn, I loaded google, then my 'G' gprs icon appeared and I lost my interface in ifconfig |
19:12.26 | tekkdrone | soooo much to figure out |
19:13.15 | Bally3 | yeah.. an i bet you doing it alone too :( |
19:13.23 | Bally3 | always seems to be the problem |
19:13.57 | tekkdrone | aye but parmaster offered up a dusting-off of his Apache :) |
19:14.08 | tekkdrone | so maybe not? :) |
19:14.29 | Bally3 | thats ok then ;) |
19:14.49 | Bally3 | bbl.. food time |
19:28.13 | *** join/#htc-linux WatskeBart (n=23059234@a80-101-189-242.adsl.xs4all.nl) |
19:28.35 | *** join/#htc-linux sni1 (n=igor@92.124.50.54) |
19:28.51 | *** part/#htc-linux sni1 (n=igor@92.124.50.54) |
19:28.53 | *** join/#htc-linux sni1 (n=igor@92.124.50.54) |
19:37.58 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
19:39.10 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
19:42.26 | *** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes) |
19:42.59 | *** join/#htc-linux OpnSrc1 (i=harisha1@gateway/tor/x-ef07717d22374990) |
19:43.48 | dcordes | hi all |
19:50.00 | imfloflo | hi dcordes |
19:50.12 | dcordes | hello my friend |
19:51.05 | dcordes | so on the raph100 the X problems are not present |
19:51.41 | imfloflo | so you can start an X interface on the raph100 |
19:51.47 | WatskeBart | hi all |
19:52.33 | dcordes | haha De Jeugd van Tegenwoordig or what? |
19:52.44 | WatskeBart | haha someting like that |
19:53.02 | dcordes | so what's happening? |
19:53.06 | WatskeBart | ppl started calling me like that |
19:53.14 | WatskeBart | so made the nick |
19:53.23 | dcordes | I had that song somewhere |
19:53.27 | *** join/#htc-linux thejigsaw (n=thejigsa@77.29.71.126) |
19:54.30 | thejigsaw | anyone from the polaris developement team |
19:54.30 | thejigsaw | <PROTECTED> |
19:54.30 | WatskeBart | funny song thats for sure |
19:55.13 | WatskeBart | i was observing and hoping i might learn something more on linux for the RAPH100 |
19:55.59 | WatskeBart | is there a way to go back from GUI to the console in Android v0.8? |
19:56.17 | Bally3 | wassup jigsaw? |
19:58.06 | thejigsaw | yo Bally3 |
19:58.12 | *** join/#htc-linux Shinto (n=John@g227175084.adsl.alicedsl.de) |
19:58.19 | thejigsaw | i wanna help and contribute to the team |
19:58.33 | Bally3 | go... got hear |
19:58.47 | Bally3 | damn ir kbd |
19:58.47 | thejigsaw | i heard that you need people |
19:58.53 | Bally3 | yes.. |
19:58.55 | thejigsaw | i am not very good at kernels |
19:58.56 | Bally3 | one mo.. |
19:59.16 | thejigsaw | but i have very good expirience in c#, vb. |
19:59.24 | thejigsaw | so i can learn and if i would be of help |
19:59.28 | thejigsaw | i could do something |
19:59.41 | dcordes | WatskeBart, things like that are easily achieved in the angstrom distro images. I just learned Xserver works well on the raphael and friends. |
20:00.10 | dcordes | don't know about android. you might use remote host over usbnet |
20:00.17 | dcordes | telnet in |
20:02.19 | WatskeBart | thanx for the tip |
20:02.32 | WatskeBart | will use the angstrom distro from the wiki |
20:03.44 | OpnSrc1 | hello all |
20:03.50 | OpnSrc1 | hi decordes, |
20:05.22 | OpnSrc1 | I've built a zImage with the full keyboard patch. How to activate KB on Kaise and Poalris ? I've both devices.. |
20:05.44 | OpnSrc1 | thanks, in advance.. |
20:08.32 | dcordes | the ts driver used on pola (vogue-ts.c) has the keyboard activated with cam button |
20:15.02 | *** join/#htc-linux chab7 (n=kvirc@212.92.4.114) |
20:17.19 | dcordes | imfloflo, sorry, overseen that. yes it works without refresh hacks: http://forum.xda-developers.com/showpost.php?p=3042196&postcount=1102 |
20:17.25 | *** join/#htc-linux MThomas (n=mthomas@adsl-155-143-171.bhm.bellsouth.net) |
20:19.23 | dcordes | ~seen Magister7 |
20:19.26 | apt | magister7 <n=Magister@vicont.in.ua> was last seen on IRC in channel #htc-linux, 8h 54m 22s ago, saying: 'tmzt_: hm.. maybe. will try to ask..'. |
20:19.33 | dcordes | hm missed him again |
20:20.01 | imfloflo | dcordes great job |
20:20.28 | dcordes | well it works out of the box so to say. jobo tested it. |
20:22.31 | *** join/#htc-linux TrinityDied (n=TrinityD@212-198-144-81.rev.numericable.fr) |
20:22.35 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfea82.pool.einsundeins.de) |
20:37.28 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
20:45.07 | wasabi | any of you played with the G1 hardware yet? I assume so. |
20:45.47 | *** join/#htc-linux lavender-t (n=jerrey@c-24-17-204-47.hsd1.wa.comcast.net) |
20:46.25 | beabras | bye |
20:48.46 | WatskeBart | adieu |
20:51.05 | dcordes | wasabi, infernix has one |
20:51.12 | infernix | yup |
20:51.22 | infernix | its nice |
20:51.22 | wasabi | yeah. i ordered a dev phone friday |
20:51.22 | dcordes | wasabi, what's up with it? |
20:51.25 | wasabi | i patiantly await. |
20:51.36 | wasabi | just wondering if anybody has got it dual booting a normal distro, etc. |
20:51.38 | infernix | wrote a backup script so far |
20:51.43 | infernix | so i can experiment |
20:51.50 | infernix | but yes, saurik has, somewhat |
20:52.10 | infernix | basically debian in a chroot |
20:52.19 | dcordes | uuh chroot |
20:52.40 | infernix | problem is, android doesnt use /etc/passwd |
20:52.46 | infernix | so need a libnss_android for that |
20:53.16 | infernix | anyway see here http://www.telesphoreo.org/pipermail/g1-hackers/2008-November/000032.html |
20:53.38 | wasabi | Chroot ain't really what I mean. |
20:53.42 | dcordes | wasabi, do you have documentation about using/configuring g1 dev edition bootloader? |
20:53.45 | infernix | we can also basically turn any G1 into a dev phone as long as you have root |
20:53.48 | wasabi | I want to get a second / on maybe a SD |
20:53.56 | infernix | wasabi: yeah thats the next step |
20:53.58 | wasabi | And get a boot loader set up so I can switch between them. |
20:54.09 | wasabi | No, I don't. |
20:54.14 | infernix | but there is no grub so something has to be made that can switch |
20:54.26 | infernix | and using the g1 bootloader is simple |
20:54.34 | infernix | you have fastboot protocol to write flash partitions |
20:54.35 | wasabi | fastboot or something? |
20:54.52 | infernix | you can write without having to boot a kernel |
20:54.55 | infernix | so you can do whatever |
20:55.02 | dcordes | wasabi, why would that be a problem on the developer phone- having mutiple rootfilesystems to chose from. am I wrong when I assume the bootloader is comparable to uboot and such? |
20:55.15 | infernix | bootloader is in SPL, e.g its HTC code |
20:55.17 | wasabi | I have no idea. that's what I'm here asking. |
20:55.20 | infernix | it fires off whatever is in boot.img |
20:55.25 | infernix | which is a kernel+initrd right now |
20:55.31 | wasabi | Ahh. |
20:55.37 | wasabi | So we need a second loader in there? |
20:55.43 | infernix | so for being able to switch, either make some script in boot.img that does something for you |
20:55.45 | dcordes | wasabi, is there no public documentation on the dev phone from google side? |
20:55.50 | infernix | or compile a kernel with kexec |
20:55.58 | infernix | and just start another kernel from android os itself |
20:56.06 | *** join/#htc-linux Bally3_ (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com) |
20:56.09 | dcordes | kexec sounds best |
20:56.20 | dcordes | so you have a static whatsoever.img |
20:56.45 | dcordes | and have the kernel images / filesystem wherever your .img kernel can acccess |
20:57.22 | wasabi | Well, I'd like to keep teh built in kernel as hands off as possible... so i can reflash it all the time, etc. |
20:57.24 | dcordes | we could test it on the non dev phones already |
20:57.29 | infernix | look here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images |
20:57.31 | wasabi | I'm looking into flashboot now |
20:57.38 | dcordes | wasabi, what I said |
20:57.39 | infernix | misc is not used in userspace |
20:57.47 | wasabi | It is supposed to be my primary phone. ;0 |
20:57.49 | infernix | recovery is bootable with a key combo on the phone |
20:58.06 | infernix | so recovery is basically rescue mode, independent from boot/system |
20:58.11 | wasabi | ahh |
20:58.29 | infernix | cache is where OTA updates are stored, no other use is known (least not to me) |
20:58.39 | wasabi | dev phone won't use ota updates no doubt |
20:58.52 | infernix | system is your OS, gets mounted at /system, and userdata is /data which is where android stores apps |
20:59.12 | infernix | in recovery mode you can reset, which just formats data |
20:59.16 | wasabi | so there's a set of rescue keys that will determine whether to boot off of boot or recovery? |
20:59.21 | infernix | sort of like a hard reset in WM HTC phones |
20:59.33 | infernix | wasabi: no you boot recovery by holding home+power |
20:59.40 | infernix | and spl/bootloader with camera+power |
20:59.41 | wasabi | 'rescue keys' |
21:00.06 | infernix | i'm not following |
21:00.11 | infernix | there's no keys involved in booting |
21:00.17 | wasabi | dude. home/power are keys |
21:00.24 | infernix | oh heh |
21:00.27 | wasabi | so you answered my question yes |
21:00.27 | infernix | i was thinking RSA keys |
21:00.29 | wasabi | heh |
21:00.31 | wasabi | oh |
21:01.20 | wasabi | have you been into the hardware yet? curious what hte framebuffer is |
21:01.30 | wasabi | and if you can talk to the gsm unit in any meaningful way from code |
21:01.43 | infernix | so what ive done so far is a way to dump data from all relevant mtd partitions (boot recovery system data) and convert them back into flashable images for fastboot |
21:01.49 | wasabi | openmoko for instance had teh gsm unit exposed over a little text based thing. |
21:01.56 | wasabi | which made it very easy to dial, etc. |
21:01.58 | infernix | theres a few proprietary libs |
21:02.18 | wasabi | Actually, it was a normal line based modem thing. ATDT to dial. |
21:02.27 | wasabi | And you could open two channels because there were two device files. |
21:02.29 | infernix | ~/src/android/mydroid/vendor/htc/dream$ ls proprietary/ |
21:02.29 | infernix | akmd AudioFilter.csv AudioPara4.csv Fw1251r1c.bin gps.conf libaudioeq.so libhtc_ril.so libqcamera.so tiwlan.ini |
21:02.35 | wasabi | So run ppp on one, and initiate a voice dial on another. |
21:02.46 | *** join/#htc-linux br1ck (n=br1ck@xdslcd208.osnanet.de) |
21:02.52 | infernix | i am guessing htc_ril is where the communication is at |
21:02.56 | wasabi | hmm |
21:03.00 | infernix | either way its done in shared mem |
21:03.08 | infernix | afaik |
21:03.18 | wasabi | well that'll be itneresting. |
21:03.18 | infernix | but i havent explored fully yet |
21:03.33 | wasabi | know what the framebuffer is? |
21:04.04 | infernix | not sure what you mean, the driver for it? |
21:04.13 | wasabi | yeah |
21:04.29 | infernix | i can pastebin dmesg for you |
21:04.49 | dcordes | wasabi, "curious what hte framebuffer is" X should work on the trout. "if you can talk to the gsm unit in any meaningful way from code" AT command channel is /dev/smd0. Just like the moko text thing. |
21:05.05 | wasabi | trout? huh? |
21:05.11 | dcordes | g1 is trout in the kernel |
21:05.21 | wasabi | nice. |
21:05.34 | wasabi | So it does have a text based command channel? |
21:05.39 | dcordes | they like fish. the evaluation board they used is halibut |
21:05.42 | dcordes | yes |
21:05.42 | wasabi | See. that is highly interesting. That sounds fun. |
21:05.53 | dcordes | but there's a show stopper |
21:05.58 | wasabi | ? |
21:06.23 | dcordes | the data connections are a bit complicated on the trout |
21:06.59 | dcordes | infernix, what about pppd. does that work on the trout? |
21:07.10 | wasabi | is there only one control channel? |
21:07.15 | infernix | afaik they don't use pppd |
21:07.15 | dcordes | for AT yes |
21:07.19 | wasabi | Hmm. |
21:07.27 | infernix | but again i havent investigated |
21:07.27 | dcordes | infernix, I know the stock images don't use it |
21:07.31 | infernix | ask #android |
21:07.46 | dcordes | did |
21:08.02 | wasabi | I can't imagine it not being done through PPP. Since all ISP data connections use PPP. |
21:08.08 | wasabi | That I'm aware of. |
21:08.13 | dcordes | wasabi, but AT does not everything. there are other mecahnisms to control modem. I think audio settings are done using the msm proc_comm |
21:08.30 | infernix | just browse the source if you want to find out |
21:08.58 | *** join/#htc-linux metter_ (n=metter@32-149.62-81.cust.bluewin.ch) |
21:09.00 | wasabi | This sierra aircard I have here is also interesting. You get 3 control channels. One you can use to initiate a voice dial. The other a data dial and then PPP, and the other will notify you on network status changes. |
21:09.29 | wasabi | and txt messages |
21:09.37 | dcordes | infernix, as you know in the kais smd code we got the normal ppp channel. on the g1 there is rmnet |
21:09.54 | wasabi | Anyways, my main point of interest is getting a real distro on it, X, and maemo. |
21:09.55 | dcordes | and I wonder how difficult it will be to use it with common tools |
21:10.02 | wasabi | And then playing with writing a telepathy backend for the voice. |
21:10.25 | dcordes | wasabi, sounds interesting. I will try helping out where I can. |
21:10.38 | infernix | wasabi: you can start wrapping it around your brain with a sweatband |
21:10.43 | wasabi | hehe |
21:10.44 | dcordes | wasabi, I'm currently trying to get the openmoko phone api working with msm72* modems. |
21:13.39 | infernix | wasabi: dmesg http://pastebin.com/d3c731f1f |
21:13.51 | wasabi | hope mine gets here asap. |
21:14.55 | wasabi | cool thx |
21:14.56 | dcordes | infernix, I think there is no point looking at the sources since the rmnet library is not in there |
21:15.11 | infernix | dcordes: well the source must talk to the library |
21:15.19 | infernix | i think that would be a good starting point |
21:15.37 | infernix | my guess is it's easier to do that than to reverse engineer the lib |
21:15.45 | infernix | but IANAC so YMMV |
21:16.17 | dcordes | http://git.android.com/?p=kernel.git;a=blob;f=drivers/net/msm_rmnet.c;h=36911a4e5163031edf747a7fe1fd8c8db25ebae3;hb=6cd5a6fc5ea47dec067ff3d11521b924a9e4dd90 |
21:21.37 | *** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes) |
21:28.46 | tmzt_ | you will probably have to use ppp on the windows HTC devices, at least until they start using rmnet/qmi in the AMSS |
21:29.26 | tmzt_ | voice is probably an audio routing problem, needing the correct proc_comm commands |
21:30.03 | tmzt_ | I would like to see Telepathy wrapping fso api's for a combined chat/voice calling program, but fso is not Telepathy now |
21:31.49 | dcordes | tmzt_, can rmnet data flow be used with normal linux distro? |
21:32.11 | tmzt_ | it's just an ethernet device, but the AMSS has to support it |
21:32.16 | tmzt_ | netdev |
21:34.23 | dcordes | great so it's actually much better than the ppp stuff |
21:34.35 | tmzt_ | less overhead |
21:34.43 | tmzt_ | what device are you trying this on? |
21:34.47 | dcordes | g1 still uses the normal AT dialing? |
21:34.59 | tmzt_ | for data? |
21:35.08 | tmzt_ | I think it uses qmi to start the connection |
21:35.15 | dcordes | wasabi, has been wondering about normal linux userspace stuff on the g1 developer device he will receive. |
21:35.49 | tmzt_ | I think replacing the recovery partition is the way to do it, but replacing the primary partition should work too |
21:36.03 | tmzt_ | the bootload can be configured to use any cmdline, just like haret |
21:37.04 | tmzt_ | <PROTECTED> |
21:37.32 | tmzt_ | I wonder if the bootloader allows nbh flashing though, something suggested it might not if the fastboot is corrupt and the eng bootloader is used |
21:37.42 | dcordes | they use qmi to start the connection... what is qmi? |
21:37.47 | tmzt_ | this would make supporting the dev phones harder than it probably should be |
21:38.04 | tmzt_ | look in the kernel, it's a basic ascii protocol from what I can see |
21:38.52 | dcordes | are there other modem operations outsourced from smd0 ? |
21:40.15 | tmzt_ | I thought you had singleline partly working on there? |
21:40.31 | tmzt_ | what are you asking? |
21:41.45 | dcordes | I am wondering in how far controling the modem with g1 amss is differnt from contorling the modem with the old amss |
21:43.54 | tmzt_ | I don't know of any differences other than trout using qmi to start a rmnet connection, I assume that dialing ***1 (gprs command) works with ppp on smd1 |
21:44.04 | tmzt_ | (don't know the gprs command, but that's what I mean) |
21:44.49 | dcordes | so you think you can use both, rmnet and the old style connection? |
21:45.09 | tmzt_ | yes |
21:45.28 | *** join/#htc-linux thejigsaw (n=root@77.29.71.126) |
21:46.07 | *** part/#htc-linux thejigsaw (n=root@77.29.71.126) |
21:46.20 | dcordes | ok |
21:47.02 | dcordes | bbl |
21:55.48 | Loki657 | Anyone working on the Raph here atm? |
21:58.11 | tmzt_ | hi again Loki657, doesn't look like it right now |
21:58.20 | tmzt_ | wasabi: are you still here? |
21:59.15 | wasabi | Yeah |
21:59.53 | tmzt_ | the kernel source has the qmi and rmnet, I think you just need to bring up the interface and negotiate the ip address somehow |
22:00.17 | tmzt_ | how is X working? |
22:01.17 | *** join/#htc-linux thejigsaw (n=root@77.29.71.126) |
22:01.38 | Bally3_ | hi jigsaw.. got guests so i'll be on later |
22:01.54 | Bally3_ | did you have a read on the logs? |
22:03.00 | thejigsaw | yeap |
22:03.04 | thejigsaw | i am setting up the ubuntu now' |
22:04.34 | *** join/#htc-linux br1ck (n=br1ck@xdslcd208.osnanet.de) |
22:13.23 | *** join/#htc-linux datachaos (n=datachao@189.27.183.68.adsl.gvt.net.br) |
22:43.28 | tmzt_ | NetRipper: you probably don't need a board for DIAM, just is_mach_diam100() | is_mach_diam800() and a seperate MTYPE |
22:44.01 | tmzt_ | you don't want to use #ifdef because it should be possible to build both in the same kernel |
22:44.07 | NetRipper | tmzt_, well not specifically diam100/diam800 but more like is_mach_diamond and is_mach_raphael |
22:44.11 | NetRipper | yes |
22:44.21 | NetRipper | doesn't each mtype have its own boardfile? |
22:44.29 | NetRipper | or can you give one boardfile multiple mtypes |
22:44.37 | tmzt_ | I think we will need seperate MTYPEs for cmda/gsm unless, based on what swetland said |
22:44.59 | tmzt_ | yes, just include it multiple times in the Makefile, look at mach-pxa ezx.c for an example |
22:45.50 | tmzt_ | sorry, I think you need a CONFIG_* something and have both select it in the Kconfig |
22:46.11 | *** join/#htc-linux br1ck (n=br1ck@xdslcd208.osnanet.de) |
22:46.27 | NetRipper | tmzt_, ok i'll check it out |
22:46.32 | NetRipper | but we'll get 4 mtypes then |
22:46.38 | NetRipper | raph100/raph800/diam100/diam800 |
22:46.47 | NetRipper | (need diff between raph/diam for gpio differences) |
22:46.57 | Loki657 | whats the difference between the raph100 and raph800? (GSM and CDMA?) |
22:47.10 | tmzt_ | there is already a CONFIG_AMSS for g1, we might need one for the windows HTCs version |
22:47.23 | NetRipper | modem and panel, and possibly more |
22:47.31 | tmzt_ | it seems there are more differences than we expected |
22:48.26 | tmzt_ | if we can get vreg and clk apis implemented, it might be posible to have most differences be on the AMSS option |
22:48.52 | tmzt_ | anyway, have you found anything on SDCC clocks? |
22:50.16 | NetRipper | i'm going to check out lavender.t's patch tomorrow |
22:50.20 | NetRipper | just give it a shot at raphael |
22:50.24 | NetRipper | to see what it does |
22:50.32 | NetRipper | hoping it wont fry my device |
22:50.33 | NetRipper | ;) |
22:50.37 | tmzt_ | lavender-t: you here? |
22:50.43 | NetRipper | he posted his diff on forum |
22:50.52 | NetRipper | he made progress, it detects the size and the sd card |
22:50.55 | tmzt_ | with the clock-7x00 ? |
22:50.59 | NetRipper | but actual data transfer was not yet possible |
22:51.02 | NetRipper | yes |
22:51.10 | tmzt_ | oh, it detects the card? |
22:51.11 | NetRipper | yes |
22:51.26 | tmzt_ | which device does he have? |
22:51.33 | NetRipper | http://forum.xda-developers.com/showpost.php?p=3043596&postcount=1105 |
22:51.33 | NetRipper | diamond |
22:51.35 | NetRipper | so |
22:51.37 | NetRipper | it detects movinand |
22:51.39 | NetRipper | not card |
22:51.42 | NetRipper | (sorry for confusion) |
22:51.56 | tmzt_ | oh, that might be a different clock |
22:52.30 | tmzt_ | would the ether function work on g1 with a modified kernel? |
22:52.30 | *** part/#htc-linux thejigsaw (n=root@77.29.71.126) |
22:52.52 | NetRipper | it should |
22:53.05 | NetRipper | you have to enable ether on two places inthe kernel though |
22:53.16 | NetRipper | both as config option, and you have to add it in board file |
22:53.32 | tmzt_ | ok, do you have a patch for this (just the driver)? |
22:53.48 | NetRipper | the ether.c? you can get that from any git |
22:53.58 | NetRipper | i dont have a diff |
22:53.59 | tmzt_ | the android function version? |
22:54.21 | NetRipper | it's included in the android git |
22:54.24 | NetRipper | just not enabled |
22:54.43 | tmzt_ | oh, who was trying to convert that to NetChips/RNDIS? |
22:54.44 | NetRipper | you may need to change the product/vendor id |
22:54.50 | NetRipper | well |
22:54.56 | NetRipper | we did that for raph/diam |
22:55.02 | NetRipper | lavender-t did that as well i think |
22:55.18 | NetRipper | yes he did |
22:55.29 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=df6bc3917c80b8e4e6d718d58e4ca227259a8408 |
22:55.32 | tmzt_ | so it should work on g1, just not on polaris/vogue ? |
22:55.32 | NetRipper | that's the patch |
22:55.32 | NetRipper | it's minor |
22:55.51 | NetRipper | it doesn't work on polaris/vogue because usb driver doesn't work there |
22:55.56 | NetRipper | usb driver does work on g1 |
22:55.56 | NetRipper | ;) |
22:56.17 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=6dd4ca4878b7c2d8cacf09632fdc446851d4232b apply that patch as well, fixes a typo |
22:56.42 | NetRipper | brb 10 min |
22:56.42 | tmzt_ | is that usbnet then? |
22:56.47 | NetRipper | cdc_ether |
22:56.55 | NetRipper | it'll create a usb0 on your pc |
22:57.01 | NetRipper | and usb1 |
22:57.10 | NetRipper | then usb1 is the functional one |
22:57.29 | NetRipper | you need a 2.6.25+ kernel on your pc side though |
23:02.39 | *** join/#htc-linux thejigsaw1 (n=root@77.29.66.163) |
23:07.25 | *** join/#htc-linux marked (n=mafia@host86-130-120-23.range86-130.btcentralplus.com) |
23:18.57 | NetRipper | right |
23:19.02 | NetRipper | off to bed |
23:19.04 | NetRipper | good night |
23:28.28 | *** join/#htc-linux lpotter_ (n=ljp@CPE-124-191-144-181.vic.bigpond.net.au) |
23:30.26 | Loki657 | night |