IRC log for #htc-linux on 20100104

00:06.18ToAsTcfhhow exactly do i see what apps are using what ports?
00:06.43tmzton?
00:26.39kupoToAsTcfh: which os?
00:27.13Markinusphh: I'm thinking about the backlight driver, what du you mean, I think we should integrate this in the microp-klt driver ( there is a registered "lcd-backlight" device ) ?
00:35.46tmztwhich backlight driver?
00:35.51tmztit should already be in there anyway
00:35.58tmzthmm, mickey|zzZZzz wanted that
00:38.26*** join/#htc-linux we350z (n=bkusnir@adsl-99-8-225-30.dsl.pltn13.sbcglobal.net)
00:39.30Markinusfor topaz
00:39.55tmztright, but why is it not in the driver already?
00:40.29Markinusdo you mean in the -panel.c file?
00:40.36tmztno
00:40.41tmztin the microp-klt
00:40.54tmztjust export a function and write a backlight driver
00:40.59tmztwhat's lcd-backlight though?
00:41.08Markinusthere is nothing with disebling of the vregs . .
00:41.47Markinusthe display is going dark, but backlight is still on
00:44.41Markinusokay . . . I llok on it . .
00:44.44Markinuslook
00:45.18tmztthe backlight is handled by microp
00:45.30rzk__hm... what standard utilities i can remove from initrd.gz ?
00:45.31tmztwe don't have a vreg driver using microp yet, though we probably should
00:45.58rzk__i still cannot resize everything to be in 3MB
00:46.12tmztfor nand?
00:46.16*** join/#htc-linux YellowGTO|Nix_ (n=quassel@c-71-226-239-246.hsd1.pa.comcast.net)
00:46.42rzk__yes
00:47.57we350zhi - excuse my noobiness but Ii was referred here by friend on xda-developers (phhusson) who has started working on porting android to the CDMA version of HTC Panther (Palm Treo Pro 850e).  He has compiled a kernel and image that uses GSM radio drivers and I want to fork it for CDMA version.  I am new to compiling kernels for mobile devices.  The bootloader is already unlocked via CFay's HardSPL unlocker.  Just need some help
00:50.03we350z**he has started work on GSM version
00:52.18we350zhmm sorry i see the wiki has good howto info i'll start there
00:54.47rzk__tmzt: is there some man or howto for building initrd?
00:55.21rzk__noob in init ramdisk's
00:56.20rzk__i think dzo deleted e2fcsk and dosfcsk in initrd, or moved somewhere, coz there is nothing to delete in it, exclude that.
00:56.35rzk__otherwise it will be above 3mb
01:12.44*** join/#htc-linux luminoso_ (n=lumos@av-217-129-128-10.netvisao.pt)
01:19.09*** join/#htc-linux ccube (n=ccube@95-90-193-96-dynip.superkabel.de)
01:26.14MatBeeph, it's both
01:26.26MatBeephh, its both cdma and gsm
01:26.43MatBee7501A is cdma, 7201(a?) is gsm
01:42.19tmztyes
01:42.26tmztMatBee: which chip? 7600a?
01:42.53tmztwe350z: that's phh
01:43.28tmztwe350z: I don't know what kind of changes it will need in kernel, but for android you will need a ril that works with cdma
01:43.38tmztwe350z: what chip does it use?
01:44.54makkonentreo pro cdma uses a 7501a
01:45.53tmztok
01:45.56makkonenI'm pretty sure there's preliminary support in the main htc_msm_android line. hasn't MatBee been talking to phh about getting treo pro working?
01:46.08tmzttry booting with raph800 mtype and see if htcfb works
01:46.17makkonenI don't think there's a booting kernel yet.
01:47.18makkonenhuh
02:05.13*** join/#htc-linux toi (n=toi@d54C2A96D.access.telenet.be)
02:09.54*** join/#htc-linux x29a_ (n=x29a@unaffiliated/x29a)
02:31.34*** join/#htc-linux jeremychang (n=jeremych@61-30-10-70.static.tfn.net.tw)
02:34.55*** join/#htc-linux makkonen (n=makkonen@cpe-72-224-203-91.maine.res.rr.com)
02:35.46*** join/#htc-linux Zack84a (n=zack84a@r74-192-19-93.bcstcmta01.clsttx.tl.dh.suddenlink.net)
02:39.35makkonenanyone know what's going on with this coming up all the time:
02:39.35makkonenmsm_proc_comm_wince: DEX cmd timed out. status=0x0, A2Mcntr=15, M2Acntr=6
03:04.23madCoder-cmd timed out means it didn't receive a response from the modem
03:04.37madCoder-which appears correct, based on a2m counter being 15, and m2a being 6
03:14.05makkonenwhat are a2m and m2a counters?
03:14.15makkonenand... I guess that also makes sense, since it's getting no service.
03:16.44makkonenpretty sure other people are getting working modem under eclair on raph800, so maybe I've just got the wrong eclair files. <crosses fingers>
03:28.41makkonenyup. different build, all working. Of course, then it crashes.
03:33.27madCoder-a2m = app-to-modem, m2a = (yup) modem-to-app :)
03:33.44madCoder-app being the ARM11 cpu, modem being the ARM9
03:34.34ToAsTcfhmadCoder: hey man any progress?
03:35.49madCoder-haven't looked
03:36.00madCoder-been working on work stuff
03:36.09madCoder-the downside to taking a 2-week vacation :/
03:36.17makkonenmadcoder-: thanks. good to know, though apparently that's not my problem anymore.
03:36.38ToAsTcfhyeah i got busted on my build so im just working on voicemail and other stuff till i can figure it out
03:36.41*** join/#htc-linux aker (n=quassel@219.142.122.100)
03:37.57ToAsTcfhi cant make the liboem for some reason. quiet said he changed the settings in the android.mk when he did 1.6. and well hes got camera
03:38.01makkonentoastcfh: What are you trying to get your hero to do?
03:38.19ToAsTcfhwork on 2.1
03:38.37ToAsTcfhthe hardware and  stuff
03:38.45makkonennods
03:38.54ToAsTcfhall thats left is camera and multi touch
03:38.54makkonendidn't realize there wasn't a working port out yet.
03:39.04*** join/#htc-linux luminoso_ (n=lumos@av-217-129-128-10.netvisao.pt)
03:39.08makkonenmmm, multitouch.
03:39.20makkonensuch an attractive feature that I don't actually care about at all when I use it.
03:39.44ToAsTcfhwell me either. but itcomes last to camera
03:40.28ToAsTcfhit wotuld be nice to have though
03:41.10ToAsTcfhive almost got sprints pain in the ass visual voice mail workin
03:41.36ToAsTcfhit atleast connects through tcp and see it needs to update
03:42.20ToAsTcfhit took me hours to find out it was a binary file holding it down
03:42.43makkonensprint has visual voicemail?
03:42.56ToAsTcfhyeah it comes with the hero
03:43.01makkonenI just moved to google voice. so deleriously happy about that.
03:43.07ToAsTcfhbut its a bitch
03:43.24ToAsTcfhto get working i mean
03:43.27ToAsTcfhlol
03:43.30makkonenI hate sprint's voicemail... actually, I just hate voicemail. at least google voice lets me barely use it.
03:44.19ToAsTcfhyeah visual voicemail is nice though i like it. idont hve to sit through the please push 7  shit
03:44.30MatBeeoh i hate that shit too
03:44.34makkonenhate that.
03:44.40MatBeethe whole world hates it
03:44.48ToAsTcfhi can see them all and delet what i dont need
03:44.55MatBeewho would have thought that new devices should use data rather than analog?
03:44.57MatBeelol
03:45.10ToAsTcfhlol
03:45.33makkonenyeah. I can log into the google voice site and do that, or just wait till I get home and listen on the computer.
03:45.43*** join/#htc-linux randomblame (n=kevin@c-71-59-184-96.hsd1.wa.comcast.net)
03:45.45MatBeeand the annoying voicemail icon
03:46.00ToAsTcfhlol
03:46.02MatBeebrawrrr
03:46.09randomblameis the .27 kernel now compiled with 2008-q3 also?
03:46.09makkonenhate that icon so much.
03:46.28makkonenI think I use 2009-q3, but in general people use 2008-q3
03:47.16randomblameit was compiling fine under 2008-q1 then I tried compiling the .32 kernel and needed q3 and when I wen't back to .27 it's giving me errors.....
03:47.27randomblameI be confuzzeled
03:47.28ToAsTcfhmaDcoader: well if u get a chance to look at the lib camera source that would be great
03:47.36makkonenthough now, with the voicemail icon, I have a mortscript to enable the icon (when I get a text from google voice), and another to zero my voicemail count. so I have notification, but I can turn it off when I get pissed at it.
03:47.38makkonensorry for the winmo talk
03:47.53MatBeelol
03:47.59ToAsTcfhmaCoder
03:48.02MatBeeim in canada, so i get no google voice
03:48.10makkonenbummer
03:48.11MatBeei can sign up, just not use it
03:48.14MatBeelol
03:48.28makkonenI thought they rolled out to canada.
03:48.39makkonenthey rolled out free calling from GV to canada, but I guess not the other way around.
03:49.14MatBeeyeah
03:49.27MatBeegrandcentral worked in canada
03:50.26makkonenit's the chief reason I want to move to android. perfectly integrated Google Voice calling and SMS.
03:50.38makkonennow that I don't have to use sprint's voicemail, I guess I don't really care that much.
03:52.30MatBeei suppose ill have to move to the us of a
03:53.33makkoneneh. I'd suggest against jumping aboard this particular dying empire.
03:54.14MatBeelol
03:54.33randomblamemeh next year the dems will lose all their seats
03:54.44MatBeejust no more bush's please
03:55.04MatBeeus north of the border would like something respectful below us
03:55.21madCoder-ToAsTcfh: maDcoader?
03:55.27randomblamethats nice for you :D
03:55.50MatBeeatleast the usa is getting healthcare
03:55.52MatBeeits about time
03:55.59randomblameno it will be repealed
03:56.13madCoder-ToAsTcfh: fyi, I have a highlight on my nick...  but to trigger it, you have to spell my nick right.
03:56.14MatBeewould be a dumb move
03:56.17madCoder-;)
03:56.22ToAsTcfhloll sorry i misspelled twice
03:56.26randomblameno a dumb move was letting it get this far
03:56.27ToAsTcfhmy bad
03:56.30makkonenma decoder. like ma bell.
03:56.35randomblamesocialism doesn't work
03:56.40MatBeeyes it does
03:56.43MatBeelol
03:57.02madCoder-ToAsTcfh: you said quietblongs got the camera working in 1.6?
03:57.03MatBeelets look at every major country in the world, they all have healthcare, except for the usa
03:57.09makkonenoh no, what have I done? from winmo talk to... politics talk.
03:57.14MatBeewoopsie ;D
03:57.15madCoder-so does that just mean that the lib*camera interface has changed in 2.x?
03:57.21randomblameyeah lets stop spamming the channel
03:57.35ToAsTcfhyes but ills end u what his instuctions were
03:58.22madCoder-I haven't even looked at the source for liboem or libqcamera yet
03:58.49ToAsTcfhmadCoder: The option is to link or load liboemcamera. I set it to "load" for 1.6
03:59.06ToAsTcfhthats what he told me and thats what i found
03:59.25ToAsTcfhlook in libcamera and ull find the source
03:59.43madCoder-where did you find libqcamera source ?
03:59.52madCoder-hardware/msm7k/libcamera ?
04:00.31madCoder-DLOPEN_LIBQCAMERA:=1
04:00.44ToAsTcfhyes
04:01.38madCoder-can't tell what this code generates
04:01.48madCoder-the dlopen() call opens liboemcamera.so, not libqcamera.so
04:01.54madCoder-so maybe this source builds libqcamera ?
04:02.02ToAsTcfhit mentoions libq liboem and some others
04:02.21madCoder-actually this code builds libcamera.so
04:02.41ToAsTcfhhe set the .mk to load liboem
04:02.42madCoder-QualcommCameraHardware.cpp:            libqcamera = ::dlopen("liboemcamera.so", RTLD_NOW);
04:02.54madCoder-which is already is by default
04:03.02ToAsTcfhshit yeah
04:03.05madCoder-dlopen means load dynamically
04:03.07ToAsTcfhthat sux
04:03.32ToAsTcfhwell maybe itll build it to work with liboem better
04:03.36madCoder-you mentioned something about camera_cb
04:04.07ToAsTcfhyeah i used the one from the hero source but i dont think it matters
04:04.14makkonenkernel BUG at drivers/char/tty_ldisc.c:199!
04:04.15makkonensdifc
04:04.17makkonenweird
04:04.34ToAsTcfhu can compare them but i didnt see much at a glance
04:05.07ToAsTcfhg1 uses our camera thoufgh so if needed we can go that route
04:05.40ToAsTcfhgiven the correct files are in our sourc
04:05.42ToAsTcfhe
04:06.13ToAsTcfhi didnt look to see if they had it in there source to build lib oem
04:06.26ToAsTcfhcould it be apache?
04:07.19madCoder-if there's a 2.1 build of dream that works with camera, then we could just use that library, without having to build it
04:07.27madCoder-(is there?)
04:08.03madCoder-ToAsTcfh: type "which m"
04:08.10madCoder-where is it in the sdk
04:08.18ToAsTcfhidk
04:08.37ToAsTcfhum i can get a 2.0 g1 rom maybe
04:09.39madCoder-only if camera works in it
04:11.04ToAsTcfhok but they are using a really moded kernel. i think .31
04:11.10madCoder-cyanogen's rom has libcamera.so, libcameraservice.so, and libqcamera.so
04:11.23madCoder-that should be fine
04:11.47madCoder-as long as camera works, with a somewhat-vanilla 2.x build, the libraries are probably mostly compatible
04:13.03ToAsTcfhno 2.0 roms for g1 with camera
04:13.07ToAsTcfhdamn
04:13.25madCoder-cyanogen's mod has all the "QualcommCameraHardware" code in libcamera.so
04:13.40madCoder-not libqcamera, or liboemcamera
04:13.44ToAsTcfhbut its not working
04:13.57madCoder-cyanogen does work, but it's just a heavily modified 1.6
04:14.08madCoder-and I'm talking about on my sapphire, not dream
04:14.21madCoder-but they should be close enough
04:14.42ToAsTcfhyeah alot of the cameras are the same as ours
04:14.45madCoder-I'll see if libqcamera has all the dlsyms that libcamera is looking for
04:14.56ToAsTcfhstring it
04:15.09madCoder-there are better ways ;)
04:17.19*** part/#htc-linux DarkMasterHalo (n=DarkMast@modemcable187.118-80-70.mc.videotron.ca)
04:17.37randomblameshibby timer is fixed
04:17.40madCoder-<PROTECTED>
04:17.56madCoder-looks like libqcamera.so on sapphire build is the same sensor
04:20.58randomblamewoah
04:21.14ToAsTcfhwoot
04:21.30randomblamekernel just went all the freakin way and then it rebooted my phone back to winmo?
04:22.19ToAsTcfhmadCoder: have u had any issues with the new 2.1 rom?
04:22.30ToAsTcfhbesides being loaded down
04:23.03ToAsTcfhor did u ditch it
04:23.11madCoder-no, still running it
04:23.21madCoder-it works great, minus camera
04:23.24ToAsTcfhit pretty stable
04:23.31madCoder-and vvm
04:23.48madCoder-but better than aosp, where vvm was causing the voicemail indicator to show up all the time
04:24.18ToAsTcfhim fixin it now
04:25.09ToAsTcfhive got it to get through tcp and get to the site. now its just varifying isse
04:25.47ToAsTcfhso its getting there ive been on it all day
04:25.57ToAsTcfhon and off of course
04:26.51ToAsTcfhbinary stopping it from getting through port now i just gotta get the rest of it right
04:27.51madCoder-heh, so sapphire has msm_camera enabled in its kernel
04:28.01madCoder-that's why its libqcamera works
04:28.04ToAsTcfhdamn
04:28.09madCoder-we need a new kernel with msm_camera enabled
04:28.27madCoder-if htc would just release the damn source (even without .29 updates), we could get camera working
04:28.29madCoder-guaranteed
04:28.42ToAsTcfhwell its working in 1.6
04:29.04madCoder-whose rom?
04:31.05ToAsTcfhquiets
04:31.18madCoder-oh, probably using the 1.5 libqcamera.so
04:31.24ToAsTcfhno
04:31.29madCoder-$ strings ../system/lib/libqcamera.so | grep /dev
04:31.31ToAsTcfhmayybe
04:31.39madCoder-there is no mention of /dev/msm_camera in the stock libqcamera
04:32.16madCoder-but in the 2.1 liboemcamera.so, *and* in cyanogen's sapphire libqcamera.so, they all mention /dev/msm_camera
04:32.21madCoder-which is not enabled in our kernel
04:32.41madCoder-which means we might be able to use the 1.5 libqcamera...  but I get the feeling someone's already tried that
04:33.06ToAsTcfhhe may have idk
04:33.48ToAsTcfhtry compiling with it see what happens
04:34.08*** join/#htc-linux randomblame (n=kevin@c-71-59-184-96.hsd1.wa.comcast.net)
04:34.25randomblameany idea why the kernel would reboot to windows?
04:34.58madCoder-randomblame: kernel panic, with auto-reboot enabled
04:35.11randomblamebah gotta disable that
04:35.26madCoder-there's a cmdline option, that'll let you at least specify the delay
04:35.40madCoder-don't recall offhand, but it might be in your haret config, commented out?
04:35.55madCoder-something like panic_delay=999, or to that effect
04:35.57randomblameit's not in the defconfig somewhere?
04:36.20madCoder-you could recompile the kernel, sure, but its honestly easier to just increase the delay
04:36.44randomblamelol this is a new device I am recompiling the kernel every 5 minutes
04:36.52randomblameso I'm turnin the shit off for good
04:37.06makkonenwhy bother? what can you do with a panicked device? reboot and check ramconsole.
04:37.24randomblameI can see the last message for easier debugging
04:37.51makkonenoh
04:38.03makkonenthe important bits usually scroll off the screen for me, so it's no use anyway.
04:38.30makkonen(I'm just totally pumped about having ramconsole back)
04:38.34randomblamewell the frame buffer is properly implemented ova here
04:38.43makkonenrandomblame: what device?
04:38.46randomblameI'm totally pumped about having a working system timer
04:38.53randomblamethe LG Incite
04:39.04madCoder-ToAsTcfh: trying stock 1.5 lib*cam* libraries :/
04:43.07ToAsTcfhwoot balls to the wall
04:44.55madCoder-libcamera.so from 1.5 can't be loaded because of memory offset differences
04:45.31ToAsTcfhcant that be built
04:46.15madCoder-i thought you said you couldn't build it
04:46.31madCoder-01-03 23:45:31.300 V/QualcommCameraHardware(   77): loading liboemcamera at 0xb0013ea0
04:46.31madCoder-01-03 23:45:31.410 I/DEBUG   (   74): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04:46.31madCoder-01-03 23:45:31.410 I/DEBUG   (   74): Build fingerprint: 'sprint/htc_heroc/heroc/heroc:1.5/1.29.651.1/69164:user/release-keys'
04:46.31madCoder-01-03 23:45:31.410 I/DEBUG   (   74): pid: 77, tid: 96  >>> /system/bin/mediaserver <<<
04:46.31madCoder-01-03 23:45:31.410 I/DEBUG   (   74): signal 11 (SIGSEGV), fault addr 00000000
04:47.12ToAsTcfhhmm i gotta fix that
04:48.37ToAsTcfhmy build is messed up some how. i just havent tried settin up a new build yet
04:49.17ToAsTcfhwonder whats up with the fingerprint
04:49.59madCoder-fingerprint should be fine
04:50.06madCoder-it's just the start of the crash output
04:50.18madCoder-like a kernel panic prints debug data to the screen
04:50.25madCoder-this prints the same data when a system library crashes
04:50.53ToAsTcfh<PROTECTED>
04:51.06ToAsTcfhidk though market is a pain
04:51.10madCoder-what?
04:51.17madCoder-i don't think you're following
04:51.21madCoder-ignore the keys/fingerprint
04:51.33ToAsTcfhi know
04:52.20ToAsTcfhso its the same shit pretty much
04:52.31ToAsTcfhcameera and all
04:52.34madCoder-it crashes o.0
04:52.35*** join/#htc-linux babijoee (n=joee@110.33.179.112)
04:54.09*** join/#htc-linux joee_ (n=joee@110.33.179.112)
04:54.31ToAsTcfhwell what source we have is all we have. if building it with different options doesnt work then were screwed
04:54.39ToAsTcfhlibcamera
04:56.32ToAsTcfhtry building with the option set to load ;iboem
04:56.41ToAsTcfhliboem
04:56.51ToAsTcfhinstead of link
04:57.15ToAsTcfhit may change something maybe not
04:58.02ToAsTcfhit may just print out an error that says get a new kernel
05:00.18ToAsTcfhthe sad part is why can we build liboem?
05:00.31ToAsTcfhwhy can we build them all
05:00.43ToAsTcfhanyway we need
05:01.33ToAsTcfhand u said v4l2 is a no go, not a chance in hell kinda thing right?
05:02.33madCoder-heh and nexus one's lib*cam* crashes over and over
05:05.20ToAsTcfhtry espresso
05:05.25ToAsTcfhits a hero
05:06.03madCoder-not sure if I have that dump
05:06.09ToAsTcfhi trie dthe kerne l it was no deviceshowin flop
05:06.21madCoder-say again?
05:06.52madCoder-espresso isn't a full dump
05:06.59madCoder-at least what I have of it
05:07.03ToAsTcfhi have a full dump
05:07.10madCoder-link?
05:08.05madCoder-yeah you only sent me userdata.img i think
05:08.46randomblamemy defconfig is set to only use the htc_fb_console during boot, yet the kernel is still trying to do the handover wtf
05:09.01ToAsTcfhhttp://www.androidspin.com/2009/12/28/full-htc-espresso-dump-with-radio-recovery-and-boot/
05:09.04madCoder-you're misunderstanding
05:09.26*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
05:09.26ToAsTcfhits a full dump
05:09.27madCoder-when it says "use fb console only during boot", that means do not continue to use the fb console *after* boot is ready
05:09.46ToAsTcfhnot much of use though. its un finished
05:09.53madCoder-if you want the fb console to be used even after the system is ready, and you want it to NOT do the handover, you need to disable that option
05:10.30ToAsTcfhmadCoder: i gotta get some sleep hit me up with the results
05:10.31randomblamegaw
05:10.43randomblamethats some bad wording
05:10.46ToAsTcfhemail preffered
05:10.51ToAsTcfhttyl
05:11.47madCoder-randomblame: and in that case, you probably want to enable the delay
05:12.09ToAsTcfhalso my guess is that the espresso is pimping a .29 kernel
05:12.09madCoder-otherwise it'll just all go by too fast, and you'll never be able to read what it says except for the last screenful
05:12.13randomblameyeah the delay is enabled
05:12.22madCoder-ToAsTcfh: repeat what you said about the espresso kernel?
05:12.28randomblameok I'm trying again
05:12.29madCoder-whatever you said got lost in translation
05:12.40ToAsTcfhi believe its got a .29 kernel
05:12.45madCoder-no earlier
05:12.49madCoder-<ToAsTcfh> i trie dthe kerne l it was no deviceshowin flop
05:12.51madCoder-translate plz
05:13.02ToAsTcfhoh th kernel wouldnt even init
05:13.10ToAsTcfhlol
05:13.20ToAsTcfhi talk to much shit
05:13.53ToAsTcfhit wouldnt even show up as a device
05:14.27madCoder-ok, espresso dump does have camera libs
05:14.38madCoder-and its msm7k
05:14.46madCoder-so that should be closer
05:14.55ToAsTcfhyes it is
05:14.58madCoder-as for the kernel -- it wouldn't work, because this is from a GSM espresso
05:15.08ToAsTcfhbut prolly msm_camera
05:15.12madCoder-right
05:15.13madCoder-i agree
05:15.16ToAsTcfhright
05:15.19madCoder-which isn't gonna get us anywhere
05:15.30madCoder-we need to be able to compile a kernel in order to get msm_camera
05:15.40ToAsTcfhyup were fuct
05:15.41madCoder-hmm, wait
05:15.51madCoder-espresso has a libreference-cdma-sms.so
05:16.03ToAsTcfhwhat
05:16.10ToAsTcfhwcdma prolly
05:16.20ToAsTcfhits tmobile
05:16.27madCoder-which is GSM, not WCDMA
05:16.31madCoder-AT&T is WCDMA
05:16.42ToAsTcfhoh
05:16.45ToAsTcfhok
05:17.07madCoder-meh, flan dump has the same so file
05:18.16ToAsTcfhwell all the roms have cdma and gsm stuff in them
05:18.36ToAsTcfhevery dumop has sprint shit in the framework
05:18.52madCoder-yeah, espresso's libcamera also requires /dev/msm_camera
05:19.01ToAsTcfhfigures
05:19.05ToAsTcfh.29
05:19.12madCoder-doesn't need .29
05:19.16ToAsTcfhwhat about v4l2
05:19.17madCoder-we just need kernel source, to enable msm_camera
05:19.25madCoder-msm_camera requires v4l2, yes
05:19.34madCoder-we can add that into the 2.6.27 kernel that we have
05:19.37madCoder-but we need the source code first
05:19.50randomblameok that is working again
05:19.51madCoder-which means that the GSM builds can actually get camera working for their ROMs
05:20.01randomblamenow I gotta find the reason the timer is broken again
05:20.03randomblamegrr
05:20.03madCoder-they just need to build the kernel with msm_camera support
05:20.12ToAsTcfhcould we try with hero source and just rob the files we need
05:20.21madCoder-I've tried it
05:20.24madCoder-there's more involved than that
05:20.44madCoder-we need to modify the gsm hero files, and we don't know what needs modifying
05:20.58madCoder-would help a lot if we could get console working
05:21.22ToAsTcfhphh said we could build a v4l2 driver and load it wihout it being in the kernel
05:21.28madCoder-I'm not even gonna try debugging it until I can see what I'm doing, and having no console makes that near impossible
05:21.35madCoder-and he's right
05:21.52madCoder-but the code for msm_camera requires symbols that are in built-in modules of the kernel, and are not exported
05:22.08ToAsTcfhi see
05:22.12madCoder-so the camera modules end up trying to access a function in built-in.o, when those functions aren't exposed
05:22.26madCoder-I got it to build
05:22.34ToAsTcfhwhat
05:22.42ToAsTcfhliboem
05:22.45madCoder-$ adb shell ls /system/lib/modules
05:22.45madCoder-wlan.ko
05:22.45madCoder-videodev.ko
05:22.45madCoder-v4l2-int-device.ko
05:22.45madCoder-v4l2-common.ko
05:22.45madCoder-v4l1-compat.ko
05:22.47madCoder-msm_v4l2.ko
05:22.49madCoder-msm_camera_probe.ko
05:22.51madCoder-msm_camera.ko
05:23.04madCoder-but all the msm* modules can't be inserted because of missing symbols
05:23.28madCoder-the only way to build them was to modify the kernel source and add EXPORT_SYMBOL(..) after the functions msm_camera needed, then it would build and link
05:23.51madCoder-but it linked against built-in.o that I built, with EXPORT_SYMBOL() all over the place... and because of that, it doesn't work with the kernel in the phone
05:24.50ToAsTcfhdamn so until we get source were doomed on camera
05:25.04ToAsTcfhno options left
05:25.56madCoder-unless i can find out how to debug the kernel
05:26.14ToAsTcfhor get a panel or console
05:27.05madCoder-right...  i don't know if I can setup the serial console, but net console might be possible, if it can enable the network usbfn
05:27.41madCoder-i wonder what I can do to make it not display the boot splash
05:28.13ToAsTcfhoh to make it like haret
05:29.16madCoder-hmm, do you know if fastboot will show the boot lines via console?
05:29.36ToAsTcfhno i dont ive never used it
05:29.52ToAsTcfhzinx may know
05:30.16ToAsTcfh#android-root
05:31.33ToAsTcfhlol i gotta get some sleep.but i think u got something going.  ttyl let me know what u find
05:32.14*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
05:34.18madCoder-Qualcomm CDMA Technologies MSM
05:34.27madCoder-in the espresso radio
05:34.33ToAsTcfhwoot
05:34.45ToAsTcfhsteel the ril
05:34.51ToAsTcfhthat us
05:35.18ToAsTcfhi heard it was a hero with a keyboard
05:36.11ToAsTcfhpull the echo out of xbin and try that ril
05:36.23ToAsTcfhecho3
05:37.03ToAsTcfhthats what enables the cdma data
05:37.38ToAsTcfhmight be a lucky break
05:38.09ToAsTcfhsince our ril is hacked
05:39.10madCoder-hmm, looks like libhtc_ril.so might be cdma
05:39.24ToAsTcfhstrings and grep are the best huh?
05:39.45ToAsTcfhtmobile stuff in ect
05:39.48ToAsTcfhetc
05:40.06ToAsTcfhbut ur right
05:40.26madCoder-pdadb doesn't have any info on espresso
05:40.36ToAsTcfhill try the ril stuff tomorrow
05:41.02ToAsTcfhphh found an mtype
05:43.03ToAsTcfhi wonder if u could compile a saphire kernel for the heroc
05:43.43ToAsTcfhbut use our modules and stuff. it might acually init
05:44.36madCoder-doubt it, different hardware
05:44.42madCoder-sapphire is gsm
05:52.39*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
06:01.41randomblamebah
06:06.38randomblamethe kernel gets as far as unpacking initrd.gz
06:06.41randomblamethen dies
06:41.42randomblamemsm_proc_comm_wince: DEX cmd Timed out.
06:41.46randomblameany ideas?
06:43.06madCoder-which command is it timing out on
06:43.56randomblamethe damned thing scrolls so fast I don't know
06:44.05randomblameeven with the delay
06:44.11randomblamelemmie run it again
06:45.29randomblamealso have an irritating bug where htc_fb works perfectly 1/2 times
06:45.44randomblameonly displays part of the screen sometimes
06:46.20randomblamethere it goes
06:47.02randomblamedoesn't seem to like the htc raphael wifi or sd interfaces
06:47.21randomblamea2mcntr=2 m2acntr=0
06:47.43randomblameit happens just after the raph sd interface starts
06:48.14randomblameand then it loops again disabling those it looks like and unpacks the inirt  thenh says smem:diag'modcm 00000
06:48.25randomblameflashes quickly something and reboots
06:48.33randomblamecan't ever read what it flashes
06:49.32randomblamemy 5 month old son is in my lap and squirming around
06:49.41randomblamemakes this difficult haha
07:01.12*** join/#htc-linux GregLem (n=greg@lal69-5-88-171-98-250.fbx.proxad.net)
07:18.43*** join/#htc-linux Pandemic187 (n=Pandemic@c-76-125-12-222.hsd1.il.comcast.net)
07:19.19Pandemic187hey guys. i'm apologize as i know this is an off-topic question, but does anyone know if there is a way to tell what class a micro SD card is?
07:27.10randomblameshould say on it or on the packaging it came in either way that class spec is not a good way to determine speed
07:30.58Pandemic187really? i did see some forum posts saying that but i wasn't sure it was relevant to what i'm doing.
07:32.00randomblamewhat are you doing?
07:32.17Pandemic187running android from my micro sd card.
07:33.33randomblamemeh it involves a lot of reading which shouldn't be an issue for most cards
07:33.49Pandemic187i see
07:34.31randomblameis it being slow or something?
07:35.14Pandemic187not really, but i have 2 micro SD cards and if one would be faster than the other.
07:35.29Pandemic187err, i was wondering. can't type today.
07:37.21randomblamemeh test it out on the other, if you can't tell the difference between them then it doesn't really matter right
07:38.39jumoitdo you guys here know that if these is a support for htc sense ui within cyanogen? (hopefully, this is not off-topic!!)
07:39.11Pandemic187yeah, probably not.
07:39.33Pandemic187did you look on xda-developers, jumoit?
07:40.37jumoitim looking for the information on xda-developers. but never found out nothing around that!!
07:40.55Pandemic187what about cyanogen's site?
07:41.48jumoitchecking!!
07:42.37jumoitit seems that cyanogen never include any stuff on htc sense at http://www.cyanogenmod.com/changelog, right?
07:43.53jumoitif possible, please point me to the sources available!!
07:47.27*** join/#htc-linux itchy8me (n=quassel@ip80-116-211-87.adsl2.static.versatel.nl)
07:49.13randomblamehmm I think I've found where my kernel panics
07:49.25randomblamesmd core init
07:49.25randomblamearm9 has crashed
07:49.25randomblamesmem:diag 'modcm 00000
07:49.28randomblameany thoughts
07:51.40jumoitrandomblame: which handset are you currently playing with?
07:51.47randomblamelg incite
07:52.29jumoitrandomblame: what chipsets within lg incite is used?
07:52.43randomblamemsm 7201a
07:53.21randomblamethat dialog comes from smd.c line 88ish
07:54.30randomblame2.6.27 kernel
07:59.00*** join/#htc-linux kvaster (n=kvaster@93.84.112.80)
08:00.26randomblameno idea jumoit?
08:01.12randomblameit's also showing the wrong value for bogomips
08:04.11jumoitnothing. effectively, for the time being, i wanna have thorough understanding of htc sense ui with android!!
08:05.19*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d903.pool.mediaWays.net)
08:07.00*** part/#htc-linux jumoit (n=samuel@121.77.87.145)
08:38.11*** join/#htc-linux |Jason8| (i=JayAte@server2.tiltshellz.org)
08:40.31*** join/#htc-linux |Jason8| (i=JayAte@server2.tiltshellz.org)
08:51.09*** join/#htc-linux cefn (n=cefn@host81-151-123-198.range81-151.btcentralplus.com)
08:51.28*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
09:29.31*** join/#htc-linux Zack84a (n=zack84a@r74-192-19-93.bcstcmta01.clsttx.tl.dh.suddenlink.net)
09:39.47*** join/#htc-linux mickey|office (n=Mickey@dialbs-092-079-168-007.static.arcor-ip.net)
09:40.49*** join/#htc-linux gsommer (n=gsommer@194.192.93.101)
09:40.52tmztrand: don't expect any of that to work
09:41.01tmztour amss code is for wince amss
09:41.24tmztthat inludes msm clocks, timers, smd, proc comm (no vibrate right)?
09:41.30tmztwince meaning htc actually
09:41.38tmztlg could be very different
09:42.15tmztjum: #android-root and #cyanogenmod
09:54.03*** join/#htc-linux Markinus (n=Miranda@gtng-4db04f42.pool.mediaWays.net)
10:00.54*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d903.pool.mediaWays.net)
10:14.37*** join/#htc-linux Fjodor (n=sune@0x5551eec2.adsl.cybercity.dk)
10:18.35*** join/#htc-linux toi (n=toi@d54C2A96D.access.telenet.be)
10:26.11*** join/#htc-linux c2d (n=quassel@port-92-200-45-52.dynamic.qsc.de)
10:48.11*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-169-34.dynamic.mnet-online.de)
10:51.04*** join/#htc-linux toi (n=toi@d54C2A96D.access.telenet.be)
11:02.57*** join/#htc-linux babijoee (n=joee@110.33.179.112)
11:08.31*** join/#htc-linux Billyonthemounta (n=Miranda@stiitcsc412.epfl.ch)
11:18.25*** join/#htc-linux mickey|office (n=Mickey@dialbs-092-079-168-007.static.arcor-ip.net)
11:30.25*** join/#htc-linux LittleJ (n=linuz@82.78.185.26)

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