IRC log for #htc-linux on 20081224

00:02.35*** join/#htc-linux LunohoD__ (n=alex@e180069210.adsl.alicedsl.de)
00:02.43Untouchablehi
00:03.09*** join/#htc-linux dream_kill (n=nospam@212.116.219.82)
00:05.34*** join/#htc-linux Kensan_ (n=ken@gw.ptr-80-238-206-39.customer.ch.netstream.com)
00:06.44*** join/#htc-linux dream_kill (n=nospam@92.56.48.66)
00:30.04*** part/#htc-linux balsat (n=kll@87.72.13.87)
00:30.59*** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231)
00:34.59tekkdronedcordes: initial shot with tihtc shows it's attempting channel 0x24, an unknown channel
00:35.24tekkdronehappens to be hex for '$', first character of incoming unsolicited csq's
00:36.23tekkdroneafter looking it over I see ldisc type 17 is defined in the 2.6.25 kernel already, USB CAN devices or some such, I'll let you know what turns up
00:38.21tekkdrone(that was the htc apache btw)
01:25.55*** join/#htc-linux chavonbravo (n=cb@221.225.8.67.cfl.res.rr.com)
01:49.40*** part/#htc-linux drasar (n=maik@77.93.211.13-msol.msol.cz)
02:11.33*** join/#htc-linux dream_kill (n=nospam@92.56.48.66)
02:15.13*** join/#htc-linux exco (n=exco@e181098016.adsl.alicedsl.de)
02:24.43*** part/#htc-linux exco (n=exco@e181098016.adsl.alicedsl.de)
02:30.23maejreptmzt_, anything new?
02:51.14*** join/#htc-linux br1ck_ (n=br1ck@xdslce104.osnanet.de)
03:00.18*** join/#htc-linux ionstorm (n=kyle@ip68-228-225-247.ph.ph.cox.net)
03:21.27*** join/#htc-linux ionstorm (n=kyle@ip68-228-225-247.ph.ph.cox.net)
04:48.40*** join/#htc-linux woodson (n=CDP@c-76-101-90-149.hsd1.fl.comcast.net)
04:50.00*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
04:55.10maejreppdump 0xa86000a0 0x08  <-- should tell me what a0 and a4 vals are currently being used by windows, right?
05:20.14*** join/#htc-linux techknow (i=TechKnow@c-98-226-124-63.hsd1.in.comcast.net)
05:20.32techknowHTC as in running linux on a HTC device?
05:20.42tcccpo.O
05:20.47tcccpWell...yes?
05:21.34techknowCool
05:21.48techknowI'm getting a tytn II tommorrow
05:22.07techknowas looking into cooked roms and the like hen seen  a android port
05:22.11techknowthen8
05:22.17tcccpI have an HP iPaq hw6915
05:22.34tcccpAnd I lost the 2G memory card to continue with "Debian ARM" on this device
05:23.25techknowhmm debian on the device
05:23.30tcccpaye
05:23.33tcccpworks...somehow
05:23.40tcccpThe keyboard is a real pain
05:23.51techknowgot a gui? I hard that ubuntu is releasing a os for mobile devices such as the nokia N810 which can also run android
05:24.02tcccpnot yet
05:24.04techknowhow i miss my n810
05:24.15tcccpX/GUI is my next point...as soon as I have found the memory card again
05:24.26tcccpBut...asterisk with console dial is better than WinCE ;)
05:28.04techknow:)
05:28.24tcccpI need to tweak a bit with the kernel also
05:28.54techknowim waiting for more apps for android b4 i make the leap
05:29.15techknowim a palm fan well used to be and wince can support palm with a proggy
05:30.23techknown810 did not have good pim features
05:41.39*** join/#htc-linux divinebovine (n=rtaylor@S01060016b6b53675.vf.shawcable.net)
06:00.31*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
06:16.51*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
06:17.33AstainHellbringevening
06:32.57*** join/#htc-linux Othello (i=Othello@gateway/tor/x-f9ea7198ba430c0c)
06:34.24tekkdrone'lo Astain
06:34.59AstainHellbringsup tekkdrone
06:35.31tekkdronehackin' away to christmas music :)
06:38.28AstainHellbringnice
06:44.24AstainHellbringtrying to get osx installed on a buddy's laptop but its being a bitch
06:48.16tekkdroneI haven't kept up with that, is osx86 still the way to go?
06:48.53AstainHellbringbasically
06:58.28*** join/#htc-linux pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be)
07:22.21*** join/#htc-linux rmoravcik (n=rmoravci@adsl-dyn39.78-98-100.t-com.sk)
07:28.58BHSPitLappyosx86 is the blanket term for that whole scene
07:29.10BHSPitLappythe hard part is determining which distro is best
07:30.01techknowwhich in any case would be installinig windows xp and skinning it like macOSX
07:30.40BHSPitLappyha
07:31.33techknow:P
08:32.28*** join/#htc-linux Magorium (i=Othello@gateway/tor/x-146bd6dc7e5c538d)
08:40.37*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net)
08:48.21*** join/#htc-linux divinebovine (n=rtaylor@S01060016b6b53675.vf.shawcable.net)
08:57.44*** join/#htc-linux DasFx (n=John@dasfx-lptp.euronet.nl)
09:17.18*** join/#htc-linux balsat (n=kll@87.72.13.87)
09:44.30*** join/#htc-linux nebi_ (n=nebi@c-d0ed70d5.02-145-7570701.cust.bredbandsbolaget.se)
09:51.57*** join/#htc-linux pishuri (n=pishuri@194.230.146.146)
10:00.57*** join/#htc-linux timebomb (n=tb@e176119123.adsl.alicedsl.de)
10:05.38*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d812.pool.einsundeins.de)
10:12.54*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
10:17.30*** join/#htc-linux xutywx (n=xutywx@195.205.38.92)
10:18.17xutywxHello everyone! MerryChristmass ;)
10:32.10*** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com)
10:34.32*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d812.pool.einsundeins.de)
11:11.19*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net)
11:19.48rolkHappy holidays to you to xutywx.
11:29.58*** join/#htc-linux drasar (n=maik@77.93.211.13-msol.msol.cz)
11:30.33*** part/#htc-linux drasar (n=maik@77.93.211.13-msol.msol.cz)
11:46.21*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
11:50.10*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
13:02.01*** join/#htc-linux pishuri (n=pishuri@194.230.146.253)
13:08.13*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
13:14.05*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
13:44.56balsatHo ho merry Christmas
13:51.16*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfde70.pool.einsundeins.de)
14:17.43*** join/#htc-linux toer_ (i=tore@179.81-166-86.customer.lyse.net)
14:22.24*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
14:27.02*** join/#htc-linux pishuri_ (n=pishuri@194.230.146.226)
15:03.43*** join/#htc-linux pishuri__ (n=pishuri@194.230.146.206)
15:28.50*** join/#htc-linux TripleQ (n=joost@ip49-198-173-82.adsl2.static.versatel.nl)
15:34.18*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
15:54.45*** join/#htc-linux sleepr (n=sleepr@c-9ddce355.03-113-73766c10.cust.bredbandsbolaget.se)
16:20.56*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
16:22.45*** join/#htc-linux TripleDES (n=sergio@80.27.101.78)
16:40.45*** join/#htc-linux TripleDE1 (n=sergio@80.27.102.15)
16:41.15*** join/#htc-linux pishuri (n=pishuri@194.230.146.31)
16:41.38*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfd9f8.pool.einsundeins.de)
17:10.49*** join/#htc-linux dante_ (n=dante@94.162.70.8)
17:17.29*** join/#htc-linux Othello (i=Othello@gateway/tor/x-4e00f56dfba6c49c)
17:29.15*** join/#htc-linux WyrM (n=wyrm@20158142097.user.veloxzone.com.br)
17:35.59*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
17:42.12errf323nnnnnnnpp
17:51.56czarnasMerry Christmas :)
18:02.04*** join/#htc-linux BabelO (n=fcr@jau19-1-88-168-5-124.fbx.proxad.net)
18:06.20*** part/#htc-linux WyrM (n=wyrm@20158142097.user.veloxzone.com.br)
18:21.21*** join/#htc-linux xero (n=weechat@216.31.94.52)
18:28.13*** join/#htc-linux xutywx (n=xutywx@195.205.38.92)
18:45.35*** join/#htc-linux rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl)
18:59.07*** join/#htc-linux TrinityDied (i=TrinityD@212-198-148-149.rev.numericable.fr)
19:44.32*** join/#htc-linux lupine_88 (n=lupine_8@212.183.134.67)
19:44.44lupine_88ello ello
19:44.56lupine_88i have my htc phone!
19:45.27lupine_88went for the htc touch pro in the end - better keyboard by such a wide margin
20:05.59*** join/#htc-linux radem205 (n=aaa@e144118.upc-e.chello.nl)
20:27.11rogro82anyone in here?
20:27.19xutywxme ;)
20:27.25rogro82hiya :)
20:27.31rogro82quiet
20:38.37lupine_85alllo :)
20:38.58lupine_85christmas eve, quiet? who'd a thought
20:40.14lupine_85== lupine_88 incidentally
20:40.19xutywxsilent night...
20:42.09lupine_85Not here it wasn't#
20:42.16lupine_85I set off the evil house alarm
20:42.19lupine_85LOUD
20:57.43*** join/#htc-linux timebomb (n=tb@e176125147.adsl.alicedsl.de)
21:03.02lupine_85ho hum, activesync is vaguely confuzzling
21:08.55rogro82anyone working on android?
21:10.02lupine_85probably soon :D
21:10.09lupine_85need to get up to speed first, mind
21:12.22rogro82dcordes you in here?
21:21.34*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
21:26.28*** join/#htc-linux thejigsaw (n=thejigsa@77.29.74.94)
21:39.35rogro82hiya rold
21:39.37rogro82rolk
21:40.02rogro82did you manage to check my changes?
21:42.48*** join/#htc-linux br1ck (n=br1ck@xdslce104.osnanet.de)
21:47.20dcordes_ho ho ho
21:47.50dcordes_rogro82: I spent a few hours with your kaiser>htc-vogue kernel source yesterday. I was unable to reconstruct the SD stability you experienced.
21:48.05dcordes_s/kaiser/polaris/
21:50.07rogro82weird
21:50.25rogro82did you replace the mmc code with the one i used?
21:51.32rogro82i had a copy of a clean 2.6.25 kernel... patched it with the 3 diff files and then started to make the changes dzo made and it worked like a charm
21:52.05dcordes_no I used your complete kernel zip as a basis. I only did cosmetic changes and modified the framebuffer code to work with kaiser.
21:52.28dcordes_did not touch msm_sdcc at all
21:52.42rogro82did it boot at all?
21:52.57dcordes_after I removed the on screen keyboard
21:53.06dcordes_well after that, fb worked. it boots all the time
21:53.37dcordes_I noticed some variations in how early sd choked
21:54.02dcordes_depending on SD vs SDHC and the CMDLINE parameters (fmax)
21:54.04rogro82k.. were you able to unzip the data.gz/system.gz automaticaly or did you had to do it by hand?
21:54.31rogro82lemme look at mine
21:54.34dcordes_I also tried the dzo android zip. no, the kernel died with sd errors before it accomplished to extract.
21:55.03dcordes_I checked afterwards and the (gunzipped) data file was around 40 megs
21:55.13dcordes_should be ~60 iirc
21:55.20rogro82it should be 64 orso
21:55.35rogro82both
21:57.04rogro82my command line is pretty basic: set cmdline "ppp.username=internet ppp.password=internet msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"
21:57.56dcordes_this is the fmax value dzo suggests in the default.txt. I used that value too
21:58.06rogro82what config did you use? the android_defconfig?
21:58.34rogro82its the same as on dzo's site
21:58.35dcordes_do you get some debug  printks about sd before the sd driver finished initializing? (before it shows the blocks)
21:58.52dcordes_I did use .config from your zipfile. only removed power management.
21:59.20rogro82one sec ill try to make my device extract them once again
21:59.29dcordes_did you only try it once?
21:59.38rogro82no multiple times
22:00.21dcordes_ok intersteing. what sd paritioning and size?
22:00.28dcordes_and sd type
22:01.23rogro82scandisk one full partition of 6gb if im correct
22:01.45dcordes_fat32 ?
22:02.01rogro82yup
22:02.19dcordes_I tried with 4gb class 4 sdhc. full size used by one fat32
22:02.55rogro82ill check it with gparted
22:03.49rolkdcordes,rogro82: I did the same as you dcordes.
22:03.52rogro82ill backup my data.img first
22:04.02rogro82and?
22:04.24rolkI checked from the kernel.zip rogro82 posted. Made a clean build from it using the android_defconfig file.
22:04.36rolkIt did not boot successfully.
22:04.38dcordes_I did use the .config
22:04.54rolkIt got stuck in haret ('booting linux').
22:05.41dcordes_rolk: you must set htcvogue machine type in default
22:05.41rogro82rolk look over in the polaris forum on xda... i posted a zip file on page 14 with all files
22:05.54rogro821663 isnt it?
22:05.54dcordes_else it won't boot
22:05.57rolkI checked the differences in that kernel source with those in the latest linuxtogo.
22:06.02dcordes_set MTYPE 1667
22:06.14rogro82thats what i meant :P
22:06.51dcordes_I only compared with pristine htc-vogue
22:07.06rolkTo try to understand what might cause the instability, and why the vogue/dzo source is more stable.
22:07.08*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
22:07.42rolkThere are some clues.
22:08.18rolkThere is quite some stuff that deals with card detection and initialisation, delays added to the code that deals with that.
22:08.20dcordes_I didn't try cause I wouldn't understand it anyway
22:08.26rogro82i can recreate the needed changes against a clean commit in a few hours... ill do that tomorrow
22:08.33rolkI don't think it is in that.
22:08.37dcordes_that's intersting
22:08.59rolkI've merged the szsoftware+dwaradzyn patches in the latest commit of the ltg branch.
22:09.08dcordes_I had to add quite some rootdelay or dzo init script wouldn't see the card at all
22:09.20rolkAnd have a working kernel from that.
22:09.25dcordes_rolk: which ltg branch?
22:09.55rolkandroid-msm-htc-2.6.25, with latest patches for the diamond and raphael.
22:10.33dcordes_htc-msm-2.6.25 has the diamond and raphael code
22:11.01rolkThe situation isn't all that pretty. It seems that diamond and raphael are on the same footing with G1, using most of that code as is (based on the same MSM7201A?).
22:11.23dcordes_22:33 < rolk> There are some clues.
22:11.29dcordes_soory mid mouse
22:11.38rolkThe kaiser/polaris/vogue stuff is like an ugly add-on.
22:12.06rolkI also checked the diff git-g1-18-11-08.diff, which is to introduce the kaiser stuff, properly.
22:12.21rolkIt's not working for me, yet.
22:13.07rolkI'm wondering, the CONFIG_MSM7X00 flag, does that basically cover all MSM7200 devices like polaris, kaiser, but not the MSM7201A ones?
22:13.42dcordes_yea barry said g1 patch it's an approach to really merge it with the new code
22:13.58rolkI re-instated a delay in the irq handler.
22:14.05rolkudelay(200)
22:14.23rolkThere was a udelay(5) in my current code.
22:14.32dcordes_I didn't read much in the g1-diff. only tried to make framebuffer work (because I suspect that's the reason for not booting)
22:15.30rolkI repeated my test with a 20MB file copying between two ext2 partitions on the SD card.
22:15.49rolkI didn't get the timeout errors I usually get.
22:16.22rogro82my biggest problem in resetting during kernel is the smd.... if i switch it to the vogue one it will boot 100% if i use the old kaiser one it will hang 8/10 times or so
22:16.22rolkThe vogue/dzo code has some strange deviations from the code I currently use.
22:17.55rolkIt requests the SD interrupt line in a different mode from the code I now have. Edge-triggered versus level, I believe.
22:18.08rogro82ok im extracting both gz files again... and without a problem
22:18.44rogro82boots straight after extracting the files
22:19.03rolkrogro82: what config file did you use with the kernel you posted? Is that the android-defconfig file?
22:19.11rogro82yes
22:19.18rogro82to keep it the same as dzo
22:19.32rolkOk.
22:19.58rolkSo, the reason why it did not boot for me would be the machine number in the haret script?
22:20.04rogro82yes
22:20.32rogro82heres my default.txt
22:20.34rogro82set MTYPE 1667
22:20.38rolkInteresting to see that the code actually 'works' with the interrupt requested in different modes.
22:20.40rogro82set RAMSIZE 0x07800000
22:20.47rogro82set KERNEL zImage
22:20.53rogro82set initrd initrd.gz
22:21.00rogro82set cmdline "ppp.username=internet ppp.password=internet msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"
22:21.08rogro82boot
22:21.11rogro82thats it
22:21.34rolkAllright.
22:21.45rolkI'll try that again.
22:22.43rogro82what are you getting when you try to boot your original code?
22:22.55rogro82does it halt? or resets?
22:23.23rolkOriginal code? Which? The one based on your kernel.zip?
22:23.41rogro82no the kaiser/polaris one...
22:23.59rolkWell, it works fine with the angstrom initrd.
22:24.00rogro82the latest merged g1 commit
22:24.29rogro82and using android? does it boot at all?
22:24.39rolkI'm checking that now.
22:24.40lupine_85dcordes_: I have my HTC! :) - a touch pro rather than an xperia though.
22:25.12rolkI'm waiting for the system.gz to e copied to my SD card.
22:25.21rogro82ZZZzzzzz :D
22:26.17rolkIt has to move from internal storage to sd card (file transfers from PC to HTC are via bluetooth, and it stuffs incoming files in 'My Documents').
22:28.50rolkDoesn't work.
22:29.11rogro82its pretty easy to merge in the changes dzo made into the last commit of android-msm-htc-2.6.25 ( incl. the 3 patches of szsoftware ). Did it this morning against a copy of it and it took me about an hour or so to only replace the needed parts
22:29.20rogro82:-S
22:29.27rolkWhen extracting system.gz it still comes with data timeouts.
22:29.33rogro82weird
22:29.48rolkNah. This is common.
22:29.57rolkIts not your kernel.
22:29.59rogro82i just did it.... no problem
22:30.01*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfd983.pool.einsundeins.de)
22:30.07rogro82both files
22:30.32rogro82is it a pure kaiser problem or did it affect polaris in the past?
22:30.39rolkSo, can you identify dzo's changes?
22:30.43rogro82yes
22:30.57rolkI've never had proper SD card support on polaris.
22:31.19rolkI'll try to boot the stuff you posted on xda forum.
22:31.22rogro82my was always real bad even in winmo... but out of a sudden all is good :S
22:31.50rogro82k
22:32.40rogro82it has the files already extracted... the gz files are removed after unpacking... So this was the fastest way to create it :)
22:33.20rolkIts downloading now.
22:37.24*** join/#htc-linux br1ck (n=br1ck@xdslce104.osnanet.de)
22:40.01rolkWith those values above in haret script, and with your kernel sources build with the android_defconfig, I get a kind of endless listing of printk's.
22:43.37rolkIs it extracting the system.gz / data.gz files while it is printing that stuff?
22:48.02dcordes_lupine_85: I think it's the device of better quality
22:49.16rogro82rolk its mdp messages?
22:49.40rogro82those are from the video driver i copied of dzo
22:50.02*** join/#htc-linux nebi_ (n=nebi@c-c8e470d5.02-145-7570701.cust.bredbandsbolaget.se)
22:50.24dcordes_rolk: I got that printk spam when initializing sd
22:50.27dcordes_on the kais
22:50.38dcordes_sd printks
22:50.42rogro82yes it has to do with mddi
22:50.59rogro82oh the sd printks
22:51.21rogro82i think rolk is mentioning the mddi ones.... mdp_to_mda or so
22:51.56rogro82the vogue code has a lot more kernel messages
22:53.00rogro82rolk did it extract the files?
22:57.30*** join/#htc-linux br1ck (n=br1ck@xdslce104.osnanet.de)
23:03.29*** join/#htc-linux _kensou_ (n=kpi@men75-3-82-224-236-214.fbx.proxad.net)
23:05.50rogro82rolk: you still awake?
23:05.56rolkYes.
23:06.00rolkAnd yes.
23:06.02rogro82:)
23:06.05rogro82did it work?
23:06.18rolkI just have booted the stuff you posted.
23:06.30rolkNice.
23:06.33rolkNice!
23:06.43rogro82finally 1.0? :)
23:07.08rolkWell, I'm currently more intrigued by the SD card stuff..
23:07.25rogro82it extracts.... thats a big difference
23:07.56rolkThe zImage from that package, that's build from the kernel tree you posted?
23:08.02rogro82yes
23:08.57rolkWith that android_defconfig file? Allright. I need to retrace my steps once more, rebuild it from scratch and try the resulting zImage i.s.o the one from the package.
23:08.57rogro82problem is the kernel tree i posted is a trial and error one... so too much was changed
23:09.18rolkI understand.
23:09.31rolkMost of us are in trial and error mode.
23:09.37rogro82i made a clean one this morning...
23:09.51rolkYou started from which commit?
23:09.52rogro82but still against a copy
23:10.15rogro82the latest android c0..... merge g1 stuff
23:10.44rogro82added the szsoftware patches and then started to merge
23:10.52rogro82it can be done in about an hour or so
23:10.56rolkThat;s where I started from.
23:11.17rolkI have szsoftware patched on that c0... commit, and dwaradzyn's full keyboarfd patch.
23:11.44rogro82k.. use my android_defconfig ill walk u through it
23:12.07rolkBut you mentioned dzo patches....
23:12.10rolkWhich are those?
23:12.40rogro82i didnt get any patches from dzo i got one of his commits... and then merged the code
23:12.57rolkOk.
23:13.04rolkWhat was that commit?
23:13.47rogro82Merge with vogue tree - a30413e460ea8d462bd1cec65577ab84eb5e3e80
23:13.59rogro82that was his starting point
23:14.14rogro82so its best to start with that and get it on the same level
23:14.25rogro82else youll end up in circles
23:14.44rolkThat a3 commit, is that on the htc-vogue branch on ltg?
23:14.49rogro82yes
23:16.01rogro82i have 3 kernels.... one that i work on... one patched with szsoftware and that one... and then merge them by hand
23:16.29lupine_85dcordes_: aye, after comparing its keyboard to the xperia one, it was just...
23:16.31lupine_85yeah
23:16.45rogro82just copy your patched one... get the vogue one... mine and i can talk you through it
23:16.51lupine_85so all I need to do now is get linux running on it :D
23:17.40rogro82linux is almost sleeping... no running in here
23:17.42rogro82:)
23:17.50lupine_85:p
23:18.03lupine_85too much effort to do it tonight
23:18.11rolkI have two kernel trees now: ltg/android-msm-htc-2.6.25+raphael/diamond patches+szsoftware patches for kaiser polaris support + full keyboard patch from dwaradzyn, and the clean htc-vogue branch.
23:18.31lupine_85not that I expect it to be a one-day operation
23:18.54rogro82copy the ltg/android one... and extract the one i made so you can take files from it
23:18.57rogro82if needed
23:19.15rolkI also have that...
23:19.38rogro82copy the android_defconfig to your working copy...
23:19.58rogro82use that one and compile and tell me your first error
23:19.59NetRipperso, christmas eve, and you guys are playing with linux
23:20.15rolkok.
23:20.42lupine_85NetRipper: I just came back from a lovely day spent with my partner
23:20.45lupine_85:p
23:21.05rogro82also use my board as your board... so you wont get too much specific errors
23:21.19lupine_85we went out together and got my phone. it was very romantic
23:21.21NetRipperlupine_85, ah ok, so you're still human
23:21.22NetRipper:P
23:21.25NetRipperhaha
23:21.29lupine_85very much so :D
23:21.57NetRipper;)
23:22.10rolkUh. my board = your board?
23:22.32rogro82the vogue one from my zip file... its a stripped down polaris one
23:23.04rogro82also copy the vogue-ts included and backup your old one if you want to use it later on
23:23.19rolkYou mean the htcvogue-board.c?
23:23.29rogro82yup from my kernel
23:23.37lupine_85oh, <3 logfiles
23:23.44lupine_85has found where all the space on his / has gone
23:23.44lupine_85-rw-------  1 lupine lupine 7.5G 2008-12-24 23:23 .xsession-errors
23:24.14rolkYou simply plugged a stripped polaris board file in htcvogue-board.c becaise of machine type issues?
23:24.31rogro82yup polaris didnt have any mach type
23:24.45rolkIt does now.
23:24.46rogro82and i started on the vogue tree....
23:24.58rogro82i started the other way around
23:25.46rogro82i merged in the polaris stuff into the vogue tree.... and this morning i merged in the vogue stuff in to the msm-htc-android tree
23:26.03rolkHow much effort would it be to do it 'cleanly'? I'd rather try to change whatever is needed to get the SD card working properly in the existing polaris files.
23:26.28rolkOtherwise you end up with 'vogue' files that cannot be pushed back to ltg.
23:27.00rogro82im getting a new commit as we speak... so ill know in a few....
23:28.46rogro82if you rename your drivers/mmc to drivers/mmc(original)... copy the vogue one and compile
23:29.24rogro82problem with the vogue code is that the rpc is completely different
23:29.41rogro82so you cant just use one piece of it
23:30.18rogro82his msm_rpc_write/read etc has only 2 parameters instead of the original 3...
23:30.18rolkVogue is also MSM7200 based, right?
23:30.22rogro82yes
23:31.08rolkSomehow we need to end up with a code base that shares as much as possible between the MSM7200 and MSM7201A architectures.
23:31.10rogro82he uses his own vogue_rpc code instead of the smd_rpcrouter...
23:31.28rogro82yes ive never a mess as big as this one :P
23:31.42rolkAnd then in MSM7200, there's the different machines (Kaiser, Polaris, Vogue, others?)
23:32.07rolkAnd from what I gather, MSM7200 and MSM7201A are more different than the same.
23:32.08rogro82yeah and then there is msm7200a..
23:33.03rogro82i think its better to split files then to use configs....
23:33.04rolkYou said the rpc code for Vogue is different.
23:33.10rogro82yes
23:33.20rolkDifferent from Kaiser/Polaris.
23:33.31rogro82it works but is completely different from the original smd_rpcrouter code
23:33.51rolkDoes that code have anything to do with the MMC interface? I think no?
23:34.15rolkBtw, I agree it is better to split files than to use configs.
23:34.19rogro82msm_rpc_read/msm_rpc_write etc are differnt.... but still its working on polaris
23:34.55rogro82havent really looked into the difference but the main problem is he is using 2 parameters instead of 3... so all new code needs to be ported.
23:35.04rogro82also had to do this to the adsp code
23:35.49rolkTo summarize:
23:36.10rolkwith your approach, you have a 'vogue' build that works on polaris.
23:36.25rolkWhether that works on kaiser is to be confirmed.
23:36.48rolkDoes that build still work on Vogue? (Seems unreal)
23:36.52rogro82i guess so... polaris and kaiser are pretty much the same
23:37.24rogro82no... only a few vogue files were used... all the rest is polaris/kaiser
23:37.27dcordes_lupine_85: that's really romantic
23:37.37lupine_85dcordes_: oh, absolutely
23:37.46lupine_85though not as romantic as the lunch then cinema then dinner
23:37.53rogro82like i said this morning i build it the other way around...
23:38.18rolkI understand that.
23:38.50rogro82my biggest concern is the rpc code and the still not working smd ( old kaiser smd freezes a lot )
23:39.33dcordes_lupine_85: :) you got gsm or cdma raph?
23:39.41lupine_85erm, GSM I think
23:39.44lupine_85(live in the UK)
23:39.51rogro82DZO is always 2 steps ahead... so i think its best to take his route on some parts
23:40.17dcordes_rogro82: did you also pull in the kaiser proc_comm?
23:41.09rogro82yes... but it cant be used of the vogue-rpc... im not using the proc_comm code
23:41.12lupine_85wonders if WM 6.1 is also known by a year? - e.g. 2002, 2003, etc
23:41.13rogro82only header
23:41.20lupine_85or are they different versions altogether?
23:41.30lupine_85is wanting pocket PuTTY :)
23:42.21rogro82rolk you want me to put together a merge log? so you can backtrack all things ive done? i can do that tomorrow if you like
23:42.34rogro82i can also make suggestions and why things were replaced
23:42.42rolkYes, that would be good.
23:43.23rogro82it shouldnt take too much time... but there are some decissions to be made... like the rpc/mmc code
23:43.25rolkIt's late (you're Dutch too, aren't you) here, and with X-mas tomorrow, I'm off to sleep soon.
23:43.40rogro82yes im dutch too :)
23:43.45rolkI'll try to be back tomorrow evening.
23:43.59rolkDepends on the family.
23:44.01lupine_85hummm, 2003 version "seems to work"
23:44.11rogro82k... ill try to have a manual finished by then and a diff file
23:44.28rolkWould be great (dank je)
23:44.39rogro82your welcome ( graag gedaan :) )
23:45.10lupine_85woo again!
23:45.18rogro82k im off also... see you all later
23:45.22rolkBye all, good night. And rogro82: congratulations on this result. We're progressing...
23:45.39rogro82bye bye
23:48.16lupine_85so much easier with the right phone :D
23:52.30*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)

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