00:07.05 | *** join/#htc-linux mcbridematt (~matt@comalies.bionicmessage.net) |
00:12.15 | *** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey) |
00:15.08 | *** join/#htc-linux shu8i (~shu8i@78.104.102.92) |
00:15.39 | *** part/#htc-linux shu8i (~shu8i@78.104.102.92) |
00:17.48 | *** join/#htc-linux msd18 (~kvirc@adsl-69-232-73-146.dsl.sndg02.pacbell.net) |
00:18.02 | msd18 | any one active |
00:18.58 | msd18 | ello anyone there |
00:23.07 | *** join/#htc-linux Kawaiius (~yadayada@pool-72-84-157-214.slsbmd.east.verizon.net) |
00:23.08 | msd18 | has anyone been able 2 boot andriod on a leo fully with a screen and all cuse mine boots but no screen |
00:24.35 | msd18 | can anyone answer me? |
00:24.45 | ender_x|2 | I havent. |
00:25.08 | msd18 | do u get to the end of the console boot? |
00:25.18 | ender_x|2 | no I don't have a leo. |
00:25.28 | msd18 | o :( |
00:27.28 | msd18 | it just shows a black screen |
00:28.35 | *** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk) |
00:28.47 | msd18 | grrrr dam leo -.- |
00:29.33 | msd18 | where is netripper when u need him -.- |
00:38.45 | *** join/#htc-linux mastermerlin (~Adium@pD957C0CC.dip.t-dialin.net) |
00:40.06 | msd18 | hey |
00:40.53 | msd18 | can anyone tell me if initrd is required for andriod on leo or no cuse i keep getting a black screen after the console |
00:43.08 | *** join/#htc-linux Tukon (~JoeN@67.104.19.195) |
00:43.39 | msd18 | can anyone tell me if initrd is required for andriod on leo or no cuse i keep getting a black screen after the console |
00:50.29 | msd18 | brb |
00:57.35 | *** join/#htc-linux Kawaiius (~yadayada@pool-71-255-183-147.slsbmd.east.verizon.net) |
01:08.34 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
01:20.18 | *** join/#htc-linux thedicemaster2 (~thedicema@e200071.upc-e.chello.nl) |
01:23.52 | *** join/#htc-linux mastermerlin (~Adium@pD957C06B.dip.t-dialin.net) |
01:43.12 | msd18 | has anyone gotta andriod 2 boot up on leo |
02:02.23 | *** join/#htc-linux stunt1n (~fuck@c-24-23-42-1.hsd1.ca.comcast.net) |
02:20.31 | spetrillo_away | is set as away : Reason(zzzzzzzzzzzzzzzzzzzz) |
02:28.28 | *** join/#htc-linux xawen (~Admin@pool-96-244-250-218.bltmmd.fios.verizon.net) |
02:33.40 | *** join/#htc-linux rafyvitto (~rafyvitto@76-195-45-44.lightspeed.wlfrct.sbcglobal.net) |
02:36.47 | *** join/#htc-linux Zoolooc_ (~fredsibar@p54955CE8.dip.t-dialin.net) |
02:57.21 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:10.56 | *** join/#htc-linux makkonen (~makkonen@cpe-66-69-229-9.austin.res.rr.com) |
03:16.13 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:16.51 | *** join/#htc-linux |msd18| (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:17.44 | *** join/#htc-linux |msd18| (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:19.24 | *** join/#htc-linux _msd18_ (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:23.27 | *** join/#htc-linux |msd18| (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:28.42 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
03:36.40 | *** join/#htc-linux po6ot (~18162abf@gateway/web/freenode/x-ycxdsvzcaviebdiw) |
03:40.22 | po6ot | hey, this is possibly not the right spot at all to ask, but does anyone have any ideas for why adb wouldn't work on a topaz with windows 7? I get nothing with 'adb devices'. (no connected devices) |
03:40.57 | |Jason8| | po6ot: I do believe that USB drivers are incomplete for the HTC WinMo phones |
03:40.59 | stinebd | i can't offer any advice, but i do hear a lot about windows 7 having problems with that |
03:41.24 | |Jason8| | If you boot with the USB cable plugged in, it might work |
03:41.47 | stinebd | maybe missing usb IDs in the driver? |
03:41.47 | po6ot | well, I'd try a different os if that would help... does xdandroid support this at all? |
03:41.58 | |Jason8| | I did it with my Fuze |
03:42.05 | |Jason8| | but it was a pain in the ass to get working. |
03:42.12 | po6ot | yeah, it's a pure |
03:42.13 | |Jason8| | You have to boot with the USB cable plugged in for sure. |
03:42.27 | |Jason8| | (that won't work if you're in mass storage mode btw) |
03:42.44 | stinebd | yeah, boot android with the phone usb in activesync mode |
03:42.50 | po6ot | mass storage mode in windows mobile? |
03:42.53 | po6ot | ah, I get it |
03:42.58 | po6ot | okay, cool. I'll try that |
03:43.04 | po6ot | I am in mass storage mode |
03:43.08 | stinebd | i think it won't let you see the sd card with it in UMS mode anyway |
03:44.12 | po6ot | yep. windows doesn't see it at all. |
04:00.29 | *** join/#htc-linux po6ot (~18162abf@gateway/web/freenode/x-ldkwhoimbksufcrp) |
04:01.18 | po6ot | activesync + a reboot did the trick, by the way. many thanks :) |
04:02.31 | |Jason8| | no problem. Glad to hear it's working. :D |
04:03.38 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
04:23.39 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
04:32.38 | *** join/#htc-linux mickeyl (~mickey@80.81.242.146) |
04:35.03 | *** join/#htc-linux makkonen (~makkonen@cpe-66-69-229-9.austin.res.rr.com) |
04:40.24 | *** join/#htc-linux unitypunk (~unitypunk@76-14-141-97.rk.wavecable.com) |
04:44.24 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
04:44.49 | msd18 | hey guys |
04:45.28 | msd18 | can anyone explain 2 me y after the andriod console runs and boots it gives me a black screen and halts on leo |
04:47.56 | |Jason8| | because you broke it |
04:48.07 | |Jason8| | Are you using the right startup config? |
04:56.11 | msd18 | ya i should be |
04:56.45 | *** join/#htc-linux swc|666 (~infidel20@unaffiliated/swc666/x-4934821) |
04:56.46 | msd18 | im using the kernel from http://www.netripper.com/leo/ |
05:06.30 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
05:14.10 | *** join/#htc-linux MacDrunk (~marper@201.164.154.197) |
05:26.18 | *** join/#htc-linux MacDrunk (~marper@201.164.154.197) |
05:27.57 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
05:33.58 | *** join/#htc-linux flaep (~flaep@188.109.103.155) |
05:47.50 | *** join/#htc-linux Schuft (~qqqqq@c114-76-172-82.blktn4.nsw.optusnet.com.au) |
05:48.39 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
06:10.23 | *** join/#htc-linux finalbeta_ (~finalbeta@ip-83-134-158-79.dsl.scarlet.be) |
06:11.14 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
06:12.14 | *** join/#htc-linux Specialist (~tg@62-12-248-138.pool.cyberlink.ch) |
06:16.15 | *** join/#htc-linux RaptorX (~devilcuba@cpe-24-160-123-231.tampabay.res.rr.com) |
06:20.43 | *** join/#htc-linux Kasjopaja (~Tina@p57BC048E.dip0.t-ipconnect.de) |
06:26.31 | DomZ | msd18 : I think that the only guys that can help you on leo are : dcordes, Kensan, netripper and LeTama, they are the most active users on this device here, all others are either working on another device or (like me) readers (without skills in linux kernel ...) |
06:27.10 | msd18 | ok well its becoming a pain and ya |
06:29.11 | DomZ | I understand but must of them are in west europe and it is very early |
06:29.50 | msd18 | ya i know |
06:30.03 | msd18 | its like i got it 2 load the kernel but now its a black screen |
06:31.05 | DomZ | from what I know, it's the actual state, all guys have a black screen when booting on leo |
06:32.21 | msd18 | does it stay black? |
06:32.30 | DomZ | I mean "when booting on android on leo" |
06:32.31 | msd18 | or does it finaly load |
06:32.32 | DomZ | yeap |
06:32.39 | DomZ | stay black |
06:32.54 | msd18 | what is causing it |
06:33.07 | DomZ | no driver for the touch screen |
06:33.33 | *** join/#htc-linux dzo__ (~dzo@mail.marginz.co.nz) |
06:33.47 | msd18 | hmmm dam |
06:33.58 | msd18 | thats what i was guessing |
06:34.48 | DomZ | you need to wait some progress from the leo team, may be you can help too ;) |
06:40.09 | msd18 | ya maybe |
06:40.51 | msd18 | what about a generic driver for leo? |
06:40.53 | msd18 | would that work |
06:41.00 | msd18 | so at least we can see an img |
06:42.59 | DomZ | *To write a driver for the leo touchscreen we are looking for a datasheet. Name is "Elan B81_". <<<=== any help still welcome |
06:43.41 | DomZ | http://forum.xda-developers.com/showthread.php?t=651632 |
06:51.50 | *** join/#htc-linux miknix (~miknix@gentoo/developer/miknix) |
06:55.48 | msd18 | so y cant we get elan b81 |
06:56.16 | *** join/#htc-linux dekar_ (~dekar@f051119241.adsl.alicedsl.de) |
07:04.37 | MacDrunk | htc hd2 can run android |
07:05.17 | *** join/#htc-linux fleixius (~fleixius@c-68-48-154-122.hsd1.md.comcast.net) |
07:05.29 | fleixius | man the htc desire's are EXPENSIVE. |
07:09.38 | *** join/#htc-linux mayohead (~ethan@c-71-59-131-74.hsd1.wa.comcast.net) |
07:14.52 | *** join/#htc-linux mayohead (~ethan@c-71-59-131-74.hsd1.wa.comcast.net) |
07:15.30 | *** join/#htc-linux BabelO (~fcr@unaffiliated/babelo) |
07:16.24 | *** join/#htc-linux Specialist (~tg@62-12-248-138.pool.cyberlink.ch) |
07:20.33 | *** join/#htc-linux Termana (~bradley@123-3-190-93.static.dsl.dodo.com.au) |
07:22.24 | msd18 | ya |
07:24.31 | *** join/#htc-linux mayohead (~ethan@c-71-59-131-74.hsd1.wa.comcast.net) |
07:28.39 | *** join/#htc-linux madCoder- (~madcoder@c-68-42-30-56.hsd1.pa.comcast.net) |
07:31.36 | *** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk) |
07:32.31 | *** join/#htc-linux kiozen (~oeichler@rgnb-5d87d8b2.pool.mediaWays.net) |
07:35.20 | *** join/#htc-linux akoma1s (~quassel@ppp-94-68-116-82.home.otenet.gr) |
07:37.18 | *** join/#htc-linux akoma1s (~quassel@ppp-94-68-116-82.home.otenet.gr) |
07:37.48 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
07:40.39 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
07:51.18 | *** join/#htc-linux akoma1s (~quassel@ppp-94-68-116-82.home.otenet.gr) |
07:52.54 | *** join/#htc-linux hd2` (~nah@cpe-24-165-10-245.san.res.rr.com) |
07:58.13 | *** join/#htc-linux pigeon (~pigeon@eth5284.nsw.adsl.internode.on.net) |
08:01.50 | *** join/#htc-linux DaveWM (~dave@173-19-136-12.client.mchsi.com) |
08:13.33 | *** join/#htc-linux mayohead (~ethan@c-71-59-131-74.hsd1.wa.comcast.net) |
08:22.00 | *** join/#htc-linux kvaster (~kvaster@93.84.112.80) |
08:29.43 | *** join/#htc-linux kalemas (~kalemas@ns2.openhardware.ru) |
08:33.03 | *** join/#htc-linux GNUtoo (~GNUtoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
08:34.54 | tmzt | DomZ: doesn't google already have elan drivers? |
08:42.28 | *** join/#htc-linux GNUtoo (~GNUtoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
08:57.27 | *** join/#htc-linux kiozen (~oeichler@rgnb-5d87d8b2.pool.mediaWays.net) |
08:59.38 | NetRipper | msd18, you should at least get console output |
08:59.42 | NetRipper | boot console |
08:59.53 | msd18 | where |
09:00.01 | msd18 | and how do i implement it |
09:01.01 | Kensan | NetRipper: hi |
09:01.11 | NetRipper | hi Kensan |
09:01.22 | NetRipper | implement? |
09:01.33 | NetRipper | the current kernel in ltg git already has a boot console |
09:01.34 | NetRipper | for hd2 |
09:01.57 | Kensan | NetRipper: Did Markinus get msm_fb working on the Leo? |
09:01.57 | NetRipper | the htcleo_defconfig already has this enabled |
09:02.31 | NetRipper | dont recall exactly who made it work, but both the htc_fb_console and the msm_fb are working |
09:03.10 | NetRipper | htc_fb_console is the early console and msm_fb is what it switches over to during boot |
09:03.54 | Kensan | NetRipper: yes, I also got it to run on the nexus |
09:04.12 | NetRipper | good :) |
09:04.13 | Kensan | NetRipper: but there's a bug with "scheduling while atomic" |
09:04.21 | NetRipper | the panic? |
09:04.29 | NetRipper | that sounds familiar yes, i had that panic as well |
09:04.42 | Kensan | NetRipper: it's commented in the source. |
09:05.08 | Kensan | NetRipper: and that it would need further investigation. |
09:05.16 | Kensan | NetRipper: did anybody investigate this further? |
09:05.31 | NetRipper | i disabled something in the mdp to make it work anyway, however the downside is that you get these 'dma busy' messages in the console |
09:06.41 | Kensan | NetRipper: yes, request_vsync is set to 0. |
09:06.56 | Kensan | NetRipper: it say in the code |
09:07.06 | NetRipper | yes |
09:07.09 | Kensan | Temporarily disable vsync to prevent a scheduler bug, need |
09:07.11 | msd18 | hey net |
09:07.16 | Kensan | <PROTECTED> |
09:07.35 | NetRipper | Kensan, yes correct, i added that |
09:07.54 | Kensan | NetRipper: ok, but you did not investigate it further then right? |
09:08.03 | NetRipper | during the vsync interrupt handler some things happened |
09:08.04 | NetRipper | no i havent |
09:08.23 | msd18 | m,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,hey net,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, |
09:08.25 | msd18 | hey net |
09:08.27 | NetRipper | thought other things were more important |
09:08.33 | NetRipper | msd18, i read you the first time |
09:08.39 | tmzt | NetRipper: does the panic occur without mdp? |
09:08.46 | msd18 | do i have 2 add anything to make the new boot console load |
09:08.49 | tmzt | or can you just not tell |
09:08.52 | NetRipper | tmzt, the panic is caused by mdp, so no :P |
09:09.01 | Kensan | it's during initialization |
09:09.03 | NetRipper | tmzt, it's the vsync interrupt that causes the panic |
09:09.05 | tmzt | okay, sounds like the stuff I was doing with leviathan |
09:09.22 | Kensan | I have a picture of the panic somewhere *heh* |
09:09.36 | msd18 | hmm |
09:09.46 | NetRipper | during vsync it does a do_work or schedule_work or something and that causes the panic... but i think it shouldnt |
09:09.48 | msd18 | does leo have an interface yet working? |
09:10.09 | NetRipper | msd18, what kernel git tree and what defconfig are you using? |
09:10.32 | msd18 | im using Image from netriper.net/leo |
09:10.46 | msd18 | unless there is one thats more complete |
09:10.46 | NetRipper | i have no clue if that is working |
09:10.53 | NetRipper | building yoru own. |
09:10.57 | tmzt | NetRipper: do you have the code that loads mdp components apart from probing the bus |
09:10.59 | NetRipper | don't just take images from anywhere :P |
09:10.59 | Kensan | NetRipper: it does a lcdc_wait_vsync(fb_panel); |
09:11.05 | tmzt | in the upstream kernel |
09:11.10 | Kensan | NetRipper: which in turn does ret = wait_event_timeout(lcdc->vsync_waitq, lcdc->got_vsync, HZ / 2); |
09:11.42 | NetRipper | Kensan, i've looked it through but i don't see the reason why the kernel would panic, unless there's something wrong in a lower level piece of code |
09:12.29 | Kensan | NetRipper: so request_vsync should be fine even from interrupt context right? |
09:12.33 | NetRipper | tmzt, i'm just using the google msm_fb code.. and i slightly modified it |
09:12.44 | NetRipper | Kensan, well, the same code is working for nexus one, so i'd say yes :) |
09:12.54 | msd18 | net thw boot console loads but i get a completely black screen is this a missing driver in the kern or just no interface 2 display |
09:13.06 | Kensan | NetRipper: well it's not actually, I had to do the same change to get the 2.6.32 kernel up on my nexus. |
09:13.44 | NetRipper | msd18, that you get a black screen is already nice ;) but i have no clue what that Image you found on my website does, it may be broken, it may destroy your device, i have no idea :) |
09:13.55 | Kensan | NetRipper: I am basing off the htc-msm-2.6.32 branch from the mobile-linux repos. |
09:13.58 | NetRipper | Kensan, hm |
09:14.17 | msd18 | http://www.netripper.com/leo/20100310_package/ |
09:14.48 | NetRipper | Kensan, you could check the newer kernel branches by google to see if they made any changes |
09:14.52 | NetRipper | regarding vsync |
09:15.03 | NetRipper | Kensan, maybe it is a problem in the interrupt handler then yes |
09:15.08 | tmzt | what timer code are we using? |
09:15.33 | Kensan | NetRipper: I checked there but maybe there's something in the experimental branches |
09:15.41 | Kensan | NetRipper: trees I mean... |
09:15.46 | Kensan | NetRipper: man I need to wake up. |
09:16.39 | NetRipper | tmzt, for leo we disabled GP timer in favor of the DG timer (which is high res), as the GP timer was causing issues and wants to sync with the ARM9 core which doesn't work ootb for us as we have a wince radio |
09:17.07 | NetRipper | normally the GP timer is used and DG is only used in high res situations |
09:18.13 | NetRipper | msd18, that package is pretty old.. im not sure what state it is in |
09:18.13 | tmzt | irqs come from arm9 right? |
09:18.20 | tmzt | even irqs like vsync |
09:18.22 | NetRipper | tmzt, no |
09:18.34 | msd18 | what package do u recoment net? |
09:18.35 | tmzt | no? what's the replacement for vic |
09:18.36 | NetRipper | we directly access the ARM11 irq |
09:18.43 | tmzt | sorry, I don't know cortex/qsd yet |
09:18.47 | NetRipper | msd18, none, i've never published anything publically, only for test |
09:18.49 | tmzt | google does it the same way? |
09:18.54 | NetRipper | tmzt, yes |
09:19.29 | msd18 | ok net but for what build do u recoment me 2 use to at least get an interface 2 work with |
09:19.31 | tmzt | maybe we should try the chrome version |
09:19.42 | tmzt | seems to have better locking for dri |
09:19.42 | NetRipper | msd18, i'd say build a versin of your own |
09:20.00 | NetRipper | msd18, if you have patience i'll put a version that boots the kernel in a day or so |
09:20.15 | NetRipper | but it will fail nontheless.. |
09:20.19 | Kensan | NetRipper: nothing in the "official" 2.6.32 tree, just two commits which touch the bcm43 driver albeit the latter reverts the former *hehe* |
09:20.46 | NetRipper | msd18, as it will panic.. kernel development is NOT complete, lots need to be done before android can be booted.. |
09:20.47 | tmzt | what kernel version are you using |
09:20.54 | NetRipper | 2.6.32 |
09:21.01 | tmzt | is there a reason |
09:21.09 | NetRipper | we cloned nexus tree |
09:21.12 | NetRipper | which is 2.6.32 |
09:21.29 | msd18 | welnet whats the dif in nexus and hd2 hardware? |
09:21.47 | NetRipper | msd18, there are some similarities, but there's actually quite a lot of differences |
09:22.32 | NetRipper | i think this info is available in the hd2 linux thread on xda |
09:22.47 | msd18 | well i got incrediblec_cc1c2268 source |
09:22.49 | NetRipper | msd18, http://htc-linux.org/wiki/index.php?title=Leo also has a lot of info |
09:22.59 | tmzt | msd18: you're working on cdma? |
09:23.33 | msd18 | not really |
09:23.49 | msd18 | i wanna start dev on leo as well but i need at least a work interface for leo |
09:27.25 | *** join/#htc-linux LeTama (~IceChat7@vau06-1-82-228-252-90.fbx.proxad.net) |
09:28.50 | LeTama | hello guys |
09:29.08 | msd18 | hi |
09:29.23 | msd18 | LeTama |
09:29.33 | msd18 | do u know of a working build that shows a gui for leo |
09:29.36 | Kensan | LeTama: hi |
09:30.00 | Kensan | NetRipper, tmzt: Seems like codeaurora's Chromium repos has some changes to msm_fb |
09:30.10 | LeTama | msd18: your expectations are far too high, we would be happy to run executables without crashing |
09:30.47 | LeTama | msd18: right now, everything crashes semi-randomly |
09:30.50 | msd18 | yes i understand that but i would like a build that gives me an interface so i can start development and know its working |
09:31.13 | LeTama | msd18: it's not possible |
09:31.32 | msd18 | so we do not have an interface after boot yet? |
09:31.39 | tmzt | msd18: the panic is in the fraembuffer driver |
09:31.41 | tmzt | no graphics |
09:31.58 | msd18 | cuse im getting just a black screen after boot |
09:33.04 | Kensan | ah this is a mess |
09:33.29 | Kensan | the android tree has a different history than the chromium tree |
09:35.59 | Kensan | In the middle commits like "Update to latest MSM framebuffer driver." |
09:36.34 | msd18 | what tree is this? |
09:38.39 | Kensan | https://www.codeaurora.org/gitweb/quic/chrome/?p=kernel.git;a=summary |
09:45.34 | msd18 | gwt guya |
09:46.23 | msd18 | \hey guys how do i copy http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32 using git |
09:51.32 | Kensan | msd18: git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git |
09:51.43 | Kensan | msd18: git checkout htc-msm-2.6.32 |
09:53.26 | msd18 | ok |
09:53.36 | msd18 | thanks |
10:01.00 | *** join/#htc-linux shu8i (~shu8i@78.104.102.92) |
10:05.21 | *** join/#htc-linux Vito_| (~Sysel@gw.loccal.net) |
10:09.37 | msd18 | hey kensan |
10:09.47 | msd18 | question |
10:09.53 | msd18 | so how exactly does this copy work |
10:09.59 | msd18 | ive never used git b4 |
10:11.49 | Kensan | msd18: did you do the git clone? |
10:12.35 | Kensan | msd18: http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html |
10:13.01 | *** part/#htc-linux kalemas (~kalemas@ns2.openhardware.ru) |
10:15.02 | *** join/#htc-linux kalemas (~kalemas@ns2.openhardware.ru) |
10:15.29 | msd18 | ya its copying now |
10:15.43 | msd18 | 15% donw |
10:15.46 | msd18 | done |
10:16.16 | Kensan | msd18: now you need to switch to that branch |
10:16.41 | msd18 | its still download the kernel.git |
10:16.50 | Kensan | msd18: git checkout -b htc-msm-2.6.32 origin/htc-msm-2.6.32 |
10:16.52 | Kensan | msd18: ok |
10:17.01 | msd18 | from git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git |
10:17.30 | Kensan | msd18: this command will create a local branch called htc-msm-2.6.32 |
10:17.36 | msd18 | k |
10:18.05 | Kensan | msd18: it's a good idea to read through a git tutorial so you get the basic commands and know what they do. |
10:18.07 | msd18 | the kernel has 2 be compiled under linux right? |
10:18.22 | msd18 | the source of the kernel i mean |
10:18.43 | Kensan | msd18: you could also crosscompile on a different os but that makes things just unnecessarily complicated |
10:18.59 | msd18 | ya true |
10:19.01 | Kensan | msd18: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide |
10:19.38 | Kensan | msd18: you will need a crosscompilation toolchain so you can build the kernel for ARM |
10:20.12 | msd18 | and how would i do that |
10:20.30 | msd18 | im a c programmer |
10:20.40 | msd18 | so im still kinda a baby at the rest of the shit |
10:25.57 | msd18 | git://android.git.kernel.org/platform/prebuilt.git |
10:26.18 | msd18 | is that a good cross compilation toolchain |
10:28.08 | *** join/#htc-linux T-Junk (elite@h29239.upc-h.chello.nl) |
10:28.39 | Kensan | msd18: look at the wiki page I posted the link to. |
10:28.53 | msd18 | k |
10:33.13 | Kensan | NetRipper: A quick an dirty compile with the msm driver from the chromium repo comes up without the panic. |
10:34.09 | NetRipper | Kensan, nice, also without the dma busy messages? |
10:34.43 | Kensan | NetRipper: let me post the dmesg |
10:34.59 | NetRipper | msd18, also look here http://forum.xda-developers.com/showthread.php?t=631216 but note that this is for an older git tree so you'd have to replace some things (use common sence) |
10:35.02 | NetRipper | Kensan, ok |
10:35.50 | Kensan | NetRipper: http://pastebin.org/302577 |
10:36.17 | Kensan | NetRipper: but it's really just a quick and dirty copy&compile. I just wanted to see if that codebase could actually be used. |
10:36.45 | NetRipper | wow you're using a huge command line :P |
10:37.08 | Kensan | NetRipper: actually I just fed it "fastboot -c "console=tty0 no_console_suspend=1 rootdelay=5 fbcon=rotate:1" boot zImage-chromium-fb" |
10:37.18 | Kensan | NetRipper: the rest seems to come from the bootloader |
10:37.26 | NetRipper | oh right you're on the nexus right |
10:37.32 | NetRipper | not hd2 |
10:37.41 | Kensan | NetRipper: that's why it boots into Android :) |
10:37.55 | NetRipper | yea just forgot :) |
10:37.58 | Kensan | NetRipper: but I don't know yet how to *not* make it boot android. |
10:38.44 | Kensan | NetRipper: there's some intermittent blanking in Android but I seems to look better than what we currently have. |
10:39.53 | Kensan | NetRipper: there's still some locking issues but I think we also have them in our current tree. |
10:39.58 | msd18 | hey net |
10:40.17 | NetRipper | dmesg looks fine |
10:40.52 | msd18 | are u guys using a pc based emu for hd2 and debugging |
10:40.58 | NetRipper | no |
10:41.07 | msd18 | lol |
10:42.28 | msd18 | are u guys taking bits and pieces from other andriods 2 make leo's? |
10:43.20 | NetRipper | it's a cobination of using stuff that is available, writing new stuff, reverse-engineering windows mobile code, using the brain... |
10:43.32 | Kensan | msd18: the kernel is based on the one from Nexus since the hardware is similar. |
10:43.36 | *** part/#htc-linux shu8i (~shu8i@78.104.102.92) |
10:43.51 | msd18 | ok |
10:44.27 | Kensan | NetRipper: yeah, dmesg looks surprisingly good. Boots up on first try... something must be lurking in the dark to hit me when I least expect it. |
10:44.36 | Kensan | looks around for murphy... |
10:44.41 | NetRipper | Kensan, that's the fun about this :D |
10:45.05 | NetRipper | it's no fun if it works without any work :P |
10:45.56 | Kensan | NetRipper: well that's what I am saying. From experience this should never have worked on the first try... |
10:46.02 | Kensan | hm |
10:46.11 | Kensan | <PROTECTED> |
10:46.32 | Kensan | maybe it mucked with my nand |
10:46.34 | Kensan | heh |
10:46.42 | NetRipper | well |
10:46.52 | msd18 | do we have a proper initrd for leo? |
10:46.59 | NetRipper | <5>[ 4.114379] Creating 6 MTD partitions on "msm_nand": |
10:47.01 | NetRipper | that does look scary |
10:47.10 | NetRipper | msd18, no, we have several, none "proper" |
10:47.23 | Kensan | well but properly porting msm_fb from the chromium tree looks painfull. |
10:47.33 | msd18 | is it possible thats where the fault might lay? |
10:47.43 | Kensan | that tree is for some magical ST1.5 device... whatever that is. |
10:47.51 | msd18 | if im not mistaken initrd contains alot of instructions |
10:47.56 | NetRipper | msd18, there is no "the fault", it's not one problem that needs solving and fix everything ;) |
10:48.19 | msd18 | ya i know that |
10:48.29 | msd18 | but when u run an app it seg faults |
10:48.41 | NetRipper | yep, that's a problem |
10:48.49 | msd18 | would that lay within initrd since that contains the basic instructions besides the kern |
10:49.18 | NetRipper | my best guess is the kernel still. |
10:49.18 | msd18 | like i know the kern has alot of glitchs but the initrd plays an important role as well with the os |
10:49.41 | Kensan | NetRipper: hm stock android boots fine but there might be some data corruption... |
10:49.53 | NetRipper | dcordes proved that the initrd can be made to work with the kernel by compiling it from scratch |
10:50.01 | NetRipper | but it'd be favorable if we could use existing initrds |
10:50.08 | NetRipper | so we have to do something with the kernel probably |
10:50.34 | msd18 | hmmm does the media player for andriod kernel work fine? |
10:50.59 | NetRipper | errrr androi ddoesn't work, why would the media player work? :) |
10:51.09 | NetRipper | or do you mean dcordes mediaplayer? |
10:51.32 | msd18 | ya the test media player |
10:51.44 | NetRipper | that has nothing to do with android |
10:51.57 | NetRipper | and yes, obviously that works ;) |
10:52.02 | msd18 | it still has a kernel |
10:52.11 | msd18 | so that means it must be able 2 load the app |
10:52.14 | NetRipper | yes, the exact same kernel as we have |
10:52.16 | NetRipper | arf.. |
10:52.26 | msd18 | so y not look at that since it can load the app |
10:52.30 | NetRipper | wait |
10:52.33 | NetRipper | you're not getting it |
10:52.41 | NetRipper | we _are_ using that kernel |
10:52.49 | pitillo | NetRipper: was the initrd built from scratch built with the same toolchain like the initrd's which are built atm? |
10:53.11 | NetRipper | it's just that that initrd is built from nothing using the same toolchain as dcordes used to build the kernel, a 4.4.4 toolchain |
10:53.14 | msd18 | ya i know ur using that kernel so y cant u load an app now by then u can? |
10:53.20 | NetRipper | because of that, it works |
10:53.27 | NetRipper | only because the initrd is built to fit the kernel... |
10:53.51 | NetRipper | we can load an app if we apply the same principle, but that would mean we cannot re-use any existing initrd |
10:53.58 | NetRipper | while they should all be valid |
10:54.42 | NetRipper | pitillo, i don't quite understand the question.. but on that mediaplayer, kernel + initrd is built with same toolchain, same build flags |
10:54.42 | msd18 | so u try and work it out the hard way instead of making a initrd that fits this kern |
10:55.03 | NetRipper | msd18, the fact that we can't use existing initrds, indicates a problem |
10:55.17 | pitillo | NetRipper: I think you just answered my question answering msd18, thank you |
10:55.21 | NetRipper | in the kernel, or with compiling the the kernel |
10:55.30 | NetRipper | pitillo, y/w |
10:55.43 | msd18 | true but if that media player built loads and app then the exising dev on it shoulf as well |
10:55.48 | msd18 | am i right? |
10:56.29 | NetRipper | i dont understand your sentence |
10:57.04 | msd18 | ok the media player kernel and build works u say ur using that kernel then y isnt it loading any app's now and y would it be seg faulting |
10:57.23 | msd18 | concidering that kernel works then u shouldnt be seg faulting since it played an app |
10:57.49 | NetRipper | because we're trying to run normal initrds, and not initrds that we have specifically built |
10:58.10 | msd18 | so y not build a initrd specificaly for it |
10:58.16 | NetRipper | be my guest |
10:58.32 | *** join/#htc-linux bradley_ (~bradley@123-3-144-217.static.dsl.dodo.com.au) |
10:58.46 | msd18 | wouldnt that be alot easyer then fuckin in the kernel |
10:59.06 | msd18 | cuse in the end the initrd will need 2 be modded anywyas |
10:59.10 | NetRipper | in the long run you'll run into other problems.. you wouldn't be able to use any existing application compiled for (for example) the nexusone |
10:59.22 | NetRipper | besides the java obviously |
10:59.41 | msd18 | true but as with any linux os |
10:59.46 | NetRipper | likely firmware for i.e. wifi will probably cause problems as well |
10:59.49 | msd18 | u cant run slax packages on red hat |
11:00.11 | pitillo | easier or not, the point must be to look for the problem, which isn't found and seems developers are researchin (delimiting) |
11:00.14 | NetRipper | msd18, be my guest, but it's not the approach i'm taking yet |
11:00.45 | msd18 | ok where is dcords? |
11:00.57 | NetRipper | not here currently |
11:01.02 | msd18 | i wanna see if i can get the source for the media player final build |
11:01.11 | NetRipper | that's angstrom |
11:01.15 | msd18 | ya |
11:01.20 | NetRipper | www.openembedded.org |
11:01.26 | NetRipper | code is committed in there |
11:01.30 | NetRipper | and it uses our kernel |
11:01.57 | pitillo | which defconfig are you using (sorry if this is a trivial question) |
11:02.23 | NetRipper | htcleo_defconfig |
11:02.43 | pitillo | thank you NetRipper |
11:08.33 | pitillo | another question, the nexusone uses msm_defconfig? |
11:08.49 | NetRipper | no nexusone uses mahimahi_defconfig |
11:08.55 | NetRipper | mahimahi is codename for nexusone |
11:09.12 | pitillo | ah ok, thank you again NetRipper |
11:13.14 | msd18 | hey net is the git repo on linuxtogo uptodate |
11:19.28 | Kensan | pitillo: do you want to build for nexus one? |
11:20.55 | pitillo | Kensan: no, sorry for the noise, I have been reading both, nexus and leo configs |
11:21.36 | Kensan | pitillo: ok. I have a config which works for nexus with the mobile-linux/htc-msm-2.6.32 tree |
11:22.02 | pitillo | I'm reeeeeeally far from the knowledge in this channel |
11:22.16 | NetRipper | msd18, it's the repo we work on, so yes |
11:22.26 | Kensan | pitillo: well, then there's an opportunity to learn ;) |
11:22.33 | NetRipper | msd18, the msm-qsd-2.6.32 |
11:22.37 | NetRipper | uh |
11:22.40 | NetRipper | htc-msm-2.6.32 i think |
11:23.07 | pitillo | Kensan: true, I'm trying to read and understand things bit by bit |
11:23.08 | msd18 | ok well all i got is kernel source aftrer downloading the git file |
11:23.16 | Kensan | pitillo: cool. |
11:23.20 | NetRipper | msd18, yep |
11:23.39 | NetRipper | there are no binaries in git |
11:24.11 | msd18 | ya i know but i didnt use the checkout command says the git repo didnt exist i looked in the folder and i saw the source |
11:28.03 | Kensan | pitillo: what device do you have? |
11:28.40 | Kensan | NetRipper: I "tweeted" about the msmfb chromium thing, let's see if dcordes picks up on it :) |
11:29.20 | msd18 | hey net did u make a break thu using chromium lol |
11:29.52 | pitillo | Kensan: I have an htc-touch (running linwizard/wing-linux omap kernel) and a ipaq hw6915 (htc-sable, with I'm not able to boot linux on it) |
11:30.43 | pitillo | I haven't low-level knowledge and this is what I'm trying to improve (here there is a lot of knowledge in all levels...) |
11:31.06 | Kensan | NetRipper: it would be nice to properly use clock-wince when building for leo only. |
11:33.42 | msd18 | hey net |
11:33.56 | msd18 | lets port linux andriod to the iphone rofl |
11:34.23 | NetRipper | didnt someone already boot android on iphone or was that fake? |
11:34.30 | msd18 | idk o.0 |
11:35.05 | Kensan | NetRipper: I think there was a tarball with some code floating around so it seems to be not fake. |
11:35.20 | Kensan | NetRipper: but I don't care about iP* devices so I would not know. |
11:35.32 | NetRipper | http://tweakers.net/nieuws/67456/ontwikkelaar-publiceert-methode-voor-android-op-de-iphone.html |
11:35.32 | msd18 | lol |
11:35.35 | NetRipper | :) |
11:35.42 | NetRipper | english source: http://www.pcworld.com/article/196595/how_to_install_android_on_your_iphone.html |
11:35.49 | msd18 | o.0 |
11:37.10 | Kensan | LeTama: wrt. your latest findings and mail to the ML: the push instruction is related to stack handling. |
11:37.28 | Kensan | LeTama: maybe we have stack corruption which causes the segfaults? |
12:08.03 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
12:24.57 | *** join/#htc-linux mickeyl (~mickey@openmoko/coreteam/mickey) |
12:26.49 | LeTama | Kensan, well, in fact the crash is not always with stack instructions |
12:28.05 | LeTama | I wrote some basic tests check stack with my init C app, it was doing fine |
12:28.47 | LeTama | it seems more related to context switch during syscalls or execs |
12:29.29 | LeTama | looking at some traces I had, it may also be related to compiler again |
12:30.43 | LeTama | I have to check back again, but the same kernel compiled with two different toolchains and same binaries gives different results |
12:35.12 | thedicemaster | ooh nice, for how long has wired headset support through extUSB been working? |
12:35.38 | thedicemaster | properly i mean(not through forced settings) |
12:37.56 | *** join/#htc-linux dcordes (~dccordes@unaffiliated/dcordes) |
12:40.31 | NetRipper | LeTama, you mentioned a while back you had usbnet working, did you commit that? |
12:41.18 | NetRipper | ah you have it in the mailing list |
12:46.11 | LeTama | netripper, no I didn't commit as it was not android net support |
12:46.27 | dcordes | hi NetRipper, LeTama others |
12:46.35 | LeTama | hi dcordes! |
12:47.27 | dcordes | I've been thinking about the usbnet as well. we should add that in htc-msm-2.6.32 |
12:49.19 | dcordes | LeTama, nobody said htc-msm-2.6.32 is for the sole purpose of running android. do you have commit access? |
12:50.25 | dcordes | Kensan, hi. did you get anywhere with the fb during boot problem? |
12:52.23 | LeTama | dcordes, ok :) |
12:53.10 | LeTama | I don't have commit access I guess |
12:53.18 | LeTama | And I won't be able to push it right now, I have too many changes around the place |
12:55.43 | *** join/#htc-linux madCoder- (~madcoder@c-68-42-30-56.hsd1.pa.comcast.net) |
12:55.46 | Kensan | dcordes: hi there |
12:55.56 | Kensan | dcordes: read my twitter message? |
12:56.24 | dcordes | Kensan, about the codeaurora msm_fb ? |
12:56.40 | Kensan | dcordes: yes |
12:57.08 | Kensan | LeTama: I see... it is very well possible that compilers emmit different code for the same source. |
12:57.23 | NetRipper | hi dcordes |
12:57.55 | Kensan | dcordes: I did some minor adjustments to the htc-msm-2.6.32 tree and it boots fine on my nexus |
12:58.14 | NetRipper | Kensan, with vsync? |
12:58.15 | Kensan | dcordes: with the same limitations as leo -> scheduling while atomic issue |
12:58.19 | NetRipper | ah ok |
12:58.20 | NetRipper | :) |
12:58.22 | Kensan | ;) |
12:59.22 | Kensan | NetRipper: well the quick'n'dirty msm_fb chromium try did include vsync |
12:59.46 | NetRipper | try to find differences between the interrupt handling ;) |
12:59.53 | Kensan | but as mentioned it seems let's say "not so fun" to port that over |
13:00.19 | Kensan | NetRipper: when going over the commit messages wrt. msmfb it has other improvements |
13:00.27 | dcordes | Kensan, did you browse forum.xda-developers.com on the problem? I did some quick searches but I looked for disabling splash |
13:02.05 | Kensan | dcordes: the splash gets overwritten by the fbconsole output so it's not an issue anymore. |
13:02.25 | *** join/#htc-linux freakonlegs (~Craigtbal@host86-181-62-58.range86-181.btcentralplus.com) |
13:04.13 | dcordes | Kensan, do you get to see X in the debian rootfs? |
13:04.39 | dcordes | Kensan, I am asking because I'm wondering why the irregularexpression guide does not comment on the problem you face |
13:05.36 | Kensan | dcordes: he is using stock android kernel 2.6.29 and I am using the mobile-linux/htc-msm-2.6.32 tree |
13:05.55 | Kensan | dcordes: for some reason the phone always boots from nand |
13:06.20 | Kensan | dcordes: that's the main issue actually. otherwise the kernel seems to run fine |
13:06.54 | Kensan | dcordes: except for the locking issue in msm_fb vsync. |
13:07.09 | Kensan | dcordes: which is also prevalent on the leo. |
13:07.46 | dcordes | Kensan, so in stock android kernel 2.6.29 everything's working ? |
13:10.52 | Kensan | dcordes: it seems that way. |
13:11.02 | Kensan | dcordes: I have never actually tried that one. |
13:11.52 | dcordes | I see |
13:12.27 | NetRipper | does anyone feel like checking this diff for haret? i'm adding the initrd offset, but it doesn't work.. http://www.netripper.com/leo/20100602_initrdoffset.diff |
13:13.17 | dcordes | Kensan, think it would be possible to go back to stock and check the LeTama rootfs and possibly angstrom rootfs ? |
13:14.00 | *** join/#htc-linux RaptorX (~devilcuba@cpe-24-160-123-231.tampabay.res.rr.com) |
13:16.35 | Kensan | dcordes: yes, but I need to get the device to boot from sdcard instead of flash. |
13:16.45 | Kensan | dcordes: for some reason it always boots from nand. |
13:16.56 | dcordes | Kensan, ohh get it.. the nand-only thing is in stock |
13:17.42 | Kensan | ahhh |
13:17.58 | Kensan | dcordes: I didn't read the irregular-expression blog carefull enough |
13:18.04 | Kensan | let me give it another go |
13:18.12 | dcordes | what did you find? |
13:18.12 | Kensan | need to reformat my sdcard |
13:18.48 | dcordes | so it might default to nand when it can't mount root from other devices? |
13:18.49 | Kensan | dcordes: it seems that there *must* be a small fat partition as first partition otherwise the device will refuse to use the sdcard |
13:19.01 | Kensan | dcordes: part 1 in the blog entry |
13:19.04 | dcordes | strange |
13:19.07 | Kensan | yeah |
13:22.39 | Kensan | hm that would mean something in the kernel is making this decision... |
13:23.11 | *** join/#htc-linux madCoder- (~madcoder@c-68-42-30-56.hsd1.pa.comcast.net) |
13:25.11 | Kensan | dcordes: how were the drinks last night btw? ;) |
13:26.14 | dcordes | not too bad ^^ |
13:27.15 | LeTama | netripper, why did you keep the +0x500000 ? |
13:27.30 | *** join/#htc-linux thedicemaster (~thedicema@e200071.upc-e.chello.nl) |
13:28.06 | Kensan | hehe |
13:31.39 | NetRipper | LeTama, that's the original default |
13:31.55 | NetRipper | LeTama, the initrdOffset will increase/decrease that amount (it's a delta value) |
13:32.48 | NetRipper | so in order to get 10mb of space between kernel start and initrd start, you set initrdoffset 0x500000 (5mb) |
13:33.11 | NetRipper | this is how kevin did it for kernelOffset, and we should keep the two mechanisms the same |
13:33.47 | LeTama | ok, relative then, no problem, just have to remember that the 5 Mb is there |
13:33.52 | NetRipper | yep |
13:34.03 | LeTama | can't see anything wrong so far |
13:34.07 | NetRipper | thats why there are all the +'s and -'s :) |
13:34.15 | NetRipper | ok |
13:35.08 | NetRipper | dcordes, im also fixing haret's framebuffer to support mach-specific dma's after fbprintf() :) so we can see the famour black screen again before booting the kernel |
13:35.10 | dcordes | jeez howtoforge sucks |
13:35.12 | Kensan | man |
13:35.21 | Kensan | this phone just wants to boot android |
13:35.51 | NetRipper | Kensan, disable MTD in kernel ;) you'll be sure it doesnt boot android then :) |
13:35.51 | dcordes | NetRipper, sounds good. are you creating a new version then? |
13:36.01 | dcordes | lol :D |
13:36.04 | NetRipper | dcordes, just patching |
13:36.33 | dcordes | just asking cause you said it's about time to adjust version |
13:37.06 | NetRipper | yea i'll propose that as well sometim soon via ML |
13:37.15 | Kensan | grrrr |
13:38.50 | Kensan | something is probably off with the kernel |
13:38.57 | Kensan | would you look at that |
13:39.03 | Kensan | zHone on Nexus |
13:39.14 | dcordes | wut |
13:39.28 | Kensan | I booted a fso2-demo-image |
13:39.40 | Kensan | with the irregular-expression kernel |
13:40.02 | Kensan | it's displaying the zHone home screen |
13:40.08 | dcordes | ok |
13:40.12 | Kensan | but touch is not working |
13:40.19 | Kensan | neither are any of the buttons |
13:40.28 | dcordes | a pity the irregular expression person is unknown |
13:41.36 | dcordes | does he point to the source,revision,config used to build? |
13:41.38 | Kensan | well I'll diff the config and see why it does not work with our/my kernel |
13:41.43 | Kensan | dcordes: yes |
13:41.49 | Kensan | dcordes: he uses stock android kernel |
13:41.50 | dcordes | ok fine |
13:45.12 | pitillo | are you using OE to build kernels/initrds? |
13:46.42 | dcordes | pitillo, which? it is possible to build both with OE |
13:47.11 | pitillo | I mean htcleo kernel and the initrds which you are trying to test |
13:48.21 | pitillo | (shared initrds by more devices) |
13:49.03 | Kensan | nothing really sticks out in the diff |
13:49.13 | NetRipper | :( |
13:49.41 | dcordes | Kensan, can you boot the LeTama rootfs with the working kernel ? :> |
13:50.05 | NetRipper | Kensan, if i keep offset at 0 it works as expected, but wheni change the #define to 2MB and then add 3MB via the parameter in order to boot the kernel (4.2mb), it fails |
13:50.32 | NetRipper | Kensan, i think initrd overlaps kernel |
13:50.41 | NetRipper | memory-wise |
13:51.15 | NetRipper | when i enable kernelcrc, the crc of the kernel fails, crc of initrd succeeds |
13:51.35 | NetRipper | but to see thatyou need the fbprintf to work, that's not in this diff :p |
13:52.18 | NetRipper | i'll just play around more with it tonight |
13:52.36 | LeTama | netripper, the only weird thing I find in your diff is the pd->initrdOffset=initrdOffset; |
13:52.38 | dcordes | pitillo, sorry, what do you mean, shared initrds? |
13:53.18 | NetRipper | LeTama, why's that weird? im setting the initrdOffset of the struct to the global variable, the struct is then passed on in the __preload environment |
13:53.32 | pitillo | dcordes: seems that building a initrd from scratch works, but it doesn't when you use a pre-built (I don't know how to call it) initrds, which can be used with more devices |
13:54.19 | NetRipper | accessed as data->initrdOffset or pd->initrdOffset in other functions |
13:54.41 | Kensan | dcordes: I have no fbconsole output with that kernel so I don't know what's going on... |
13:55.09 | Kensan | dcordes: that's why I want to be able to boot from sdcard with my custom built one. |
13:55.20 | Kensan | dcordes: it should be trivial but then again... |
13:55.50 | dcordes | pitillo, ohh right. I remember it from the logs. I think that's a bit misleading. |
13:57.40 | LeTama | netripper, my bad, difficult to read the code on my home pc from work |
13:57.49 | NetRipper | LeTama, no prob, i value the input |
13:59.46 | *** join/#htc-linux kiozen (~oeichler@rgnb-5d87d8b2.pool.mediaWays.net) |
14:00.17 | pitillo | dcordes: NetRipper told that it's working if you build it from scratch, but if you try to use another one it doesn't work. Btw, I'm making noise, sorry and thank you for your time |
14:02.14 | NetRipper | the mediaplayer is prove that it works when everything is built from scratch with the same toolchain |
14:02.23 | dcordes | NetRipper, no it isn't |
14:02.26 | NetRipper | no? |
14:02.38 | NetRipper | the media player is a seperate process, isn't it |
14:02.43 | dcordes | mplayer and everything works to mount sd etc |
14:02.44 | NetRipper | everything that fails on other initrds, succeeds there |
14:03.23 | NetRipper | threading as well (so thread-context switches works) |
14:03.23 | dcordes | just like in other builds, some binaries work, some always fail |
14:03.41 | dcordes | threading ? |
14:03.44 | NetRipper | hm so some executables within that mediaplayer fail as well? |
14:03.55 | dcordes | yes and I never said that everything would work there |
14:04.14 | NetRipper | that was my (appearantly wrong) assumption |
14:04.20 | dcordes | everything is documented in the openembedded bug |
14:04.24 | dcordes | which is linked in ml |
14:04.26 | pitillo | dcordes: thank you for clarify that, I understood it wrong |
14:04.41 | NetRipper | i know that, i've read the bug report |
14:05.05 | NetRipper | but i thought it was working with the 4.4.4 toolchain, and not with others |
14:06.09 | *** join/#htc-linux balans (~Gebruiker@82-170-215-5.ip.telfort.nl) |
14:06.18 | NetRipper | dcordes, i had the feling that besides udev, everything else worked |
14:06.40 | NetRipper | and udev is only one thing, not nearly a pattern yet |
14:06.43 | dcordes | http://bugs.openembedded.org/show_bug.cgi?id=5435 |
14:06.49 | pitillo | have you tested with another udev version? (downgrade?) |
14:07.45 | dcordes | it's obvious our platform needs a gcc >= 4.4.0 |
14:08.10 | dcordes | NetRipper, wrong. other things fail. |
14:08.37 | NetRipper | ok |
14:08.46 | Kensan | dcordes: yes, I'd even go as far as 4.4.2 |
14:09.06 | dcordes | Kensan, maybe.. that's why I'm using 4.4.4 |
14:09.14 | LeTama | dcordes, android qaesd for 8250 is 4.4.0 though |
14:09.15 | Kensan | dcordes: very good :) |
14:09.36 | Kensan | dcordes: which rootfs were you talking about? |
14:09.51 | LeTama | and 4.5.0 seems a bit buggy |
14:09.56 | Kensan | dcordes: I am having another go with a rebuilt kernel but just so I can download the rootfs now that I have it later when I am ready for the tests. |
14:09.59 | dcordes | LeTama, yes and the toolchain in google git is also 4.4.0. that's why I said >= 4.4.0 .. but who knows what patches they apply to those toolchains |
14:09.59 | NetRipper | i disagree.. we only _need_ that if we want to use the optimizations.. but everything should work (non-optimized) on older gcc's as well |
14:10.14 | LeTama | err misread |
14:10.43 | Kensan | NetRipper: there are some bugs that suggest that wrong code is emmitted in some cases |
14:10.51 | dcordes | NetRipper, maybe. but it makes no sense to use obsolete gcc either way. |
14:11.37 | NetRipper | true and true |
14:12.11 | NetRipper | i doubt we're running into that though |
14:12.27 | Kensan | whops |
14:28.09 | *** join/#htc-linux flaep (~flaep@188.109.103.155) |
14:30.49 | *** join/#htc-linux finalbeta (~finalbeta@ip-83-134-158-79.dsl.scarlet.be) |
14:35.23 | *** join/#htc-linux mayohead (~ethan@c-71-59-131-74.hsd1.wa.comcast.net) |
14:36.46 | *** join/#htc-linux lucx (~luc@89-115-128-35.cl.ipv4ilink.net) |
14:38.12 | Kensan | ok |
14:38.13 | Kensan | finally |
14:38.21 | Kensan | I got a kernel to boot from sdcard |
14:38.33 | dcordes | wooo |
14:38.50 | Kensan | man that was unecessarily awkward... |
14:39.27 | Kensan | so |
14:39.32 | Kensan | what rootfs should I try? |
14:39.45 | dcordes | LeTama, |
14:39.52 | dcordes | that was posted here yesterday |
14:39.57 | dcordes | I'll get the link |
14:40.40 | dcordes | http://home.lestamas.fr:8080/and12.zip |
14:41.07 | dcordes | gues it's a cpio archive |
14:43.14 | Kensan | ok |
14:43.22 | Kensan | Unfortunately I have to run. |
14:43.32 | Kensan | Will test it later and come back with the results |
14:48.03 | dcordes | Kensan, ok if you find the time it would also be very interesting to try http://linuxtogo.org/~lgorris/builds/OE/leo/live/minimalist-image-htcleo.tar.gz |
14:48.09 | dcordes | Kensan, thanks a lot |
14:50.28 | NetRipper | dcordes, in that mediaplayer image of yours, did you manually change the configuration so that it boots from mmc + rootfs image? |
14:51.20 | NetRipper | i.e. did you unpack/modify/repack the initrd or did you change something in openembedded recipe or something |
14:51.26 | dcordes | NetRipper, configuration being init ? |
14:51.33 | dcordes | yes totally. |
14:51.45 | NetRipper | which of the two did you do? |
14:51.47 | *** join/#htc-linux [acl] (~abel@96.246.167.90) |
14:51.57 | NetRipper | modify initrd or change it directly in openembedded? |
14:52.33 | dcordes | it's all done manually. the changes to oe are only regarding the gcc version |
14:52.44 | dcordes | they can be looked up in the bug. all diffs are there. |
14:52.46 | NetRipper | ah ok |
14:53.24 | NetRipper | yes but as you know how opemembedded works i thought there would be a clean way to do that :) |
14:53.44 | NetRipper | i.e. so that it generates the initrd just like you want it right from the build ;) |
14:54.10 | LeTama | dcordes, kensan, yes it's an uncompressed cpio initrd. Sorry for the bad naming :) |
14:54.21 | dcordes | that would be no problem. I'd just have to install my custom init scripts into the rootfilesystems. but no sense in that |
14:58.10 | dcordes | NetRipper, if you want to investigate that rootfs further, mediaplayer actually has a good facility to that. it exectues a script located in the sd root |
14:58.18 | dcordes | NetRipper, so youc an even modify it from wince |
14:58.51 | NetRipper | yes i'll check it out |
14:58.57 | dcordes | NetRipper, it even has all our 'classical' initrd tools installed ^^ |
15:02.19 | [acl] | Looks like klinux has the diam froyo build running on the blackstone. time to celebrate |
15:04.00 | dcordes | NetRipper, btw, did you ever get the netripper.com OE fixed ? |
15:04.11 | NetRipper | it has a complete build |
15:04.42 | dcordes | awesome. how did you do it? created a bug ? |
15:05.28 | NetRipper | no i think we fixed some things and then last time we just let it build and went to sleep |
15:05.31 | NetRipper | next day build finisehd :P |
15:05.47 | NetRipper | you helped fix some problem |
15:05.51 | NetRipper | by setting a preferred |
15:06.07 | dcordes | awesome. couldn't remember that |
15:06.21 | dcordes | it was something about a *-native package right ? |
15:06.27 | dcordes | some host machine dependency problem |
15:06.34 | dcordes | because of the very recent distro version |
15:08.33 | NetRipper | dcordes, http://oe.netripper.com |
15:08.43 | NetRipper | yes |
15:09.38 | NetRipper | PREFERRED_VERSION_perl-native = "5.10.1" |
15:09.50 | NetRipper | that's the one i think |
15:14.12 | dcordes | http://shop.lenovo.com/us/landing_pages/info/10/skylight there goes my snapdragon laptop |
15:14.54 | dcordes | it says it's because of android or so. now I hate android. |
15:14.55 | NetRipper | aw |
15:15.01 | *** join/#htc-linux grhyme (~tjg04@sultan.simplelists.com) |
15:15.01 | NetRipper | no |
15:15.02 | NetRipper | lol |
15:15.06 | dcordes | :'( |
15:15.15 | NetRipper | they just shift their priorities |
15:15.25 | spetrillo | is no longer away : Gone for 12 hrs 54 mins 53 secs |
15:15.57 | NetRipper | you specifically want a snapdragon laptop or just the board? :) |
15:16.11 | dcordes | they are just suckers who don't see the market for keyboarded devices |
15:16.22 | NetRipper | lol. |
15:17.06 | dcordes | I want an ultra fast ARM based laptop with infinite battery life that runs linux |
15:17.16 | NetRipper | lol |
15:17.31 | NetRipper | someone needs a slap back to reality |
15:17.40 | dcordes | and lenovo skylight was #1 candidate |
15:18.07 | dcordes | well it was reality until lenovo crapped out |
15:18.23 | NetRipper | infinite battery eh? ;) |
15:20.13 | dcordes | imagine leo with some 4000Ah battery |
15:20.23 | pitillo | not ultrafast ARM and atm without infinity baterry life, but mininetbooks are great too (vt8500/wm8505) |
15:20.47 | *** join/#htc-linux XDS2010__ (~XDS2010@pool-72-82-5-188.prvdri.east.verizon.net) |
15:21.26 | NetRipper | i like my acer with 7 hours battery |
15:21.43 | pitillo | NetRipper: arm chipset? |
15:21.47 | NetRipper | no |
15:21.52 | pitillo | ah ok :) |
15:23.09 | pitillo | I will verify soon how many time stands up an wm8505 (I have only tested 1 day, but this weekend is near) |
15:23.58 | *** join/#htc-linux r0w3zz (~r0w3zz@p54A8D155.dip.t-dialin.net) |
15:24.32 | NetRipper | 7 inch screen, thats small.. |
15:25.04 | dcordes | only the lenovo skylight sepcs or better will satisfy needs |
15:25.09 | pitillo | a little one... 800x480 resolution, better and bigger than the jornada 720 |
15:25.32 | dcordes | now I have to wait for stupid chrome os to be usable |
15:26.41 | dcordes | so I can rip it off the device once it's available |
15:26.59 | pitillo | really nice the lenovo |
15:27.26 | pitillo | the wm8505 has nothing to do in front of one of them |
15:27.56 | *** join/#htc-linux maejrep[w] (~madCoder@68.64.144.221) |
15:27.59 | dcordes | hm yea |
15:28.34 | dcordes | lol the internet is full of chinese android tablets |
15:28.52 | dcordes | bet many of them are omap based |
15:31.18 | dcordes | hm wondering if we can attach bigger panel to leo |
15:32.23 | NetRipper | lol get the snapdragon developers board and put a display on that |
15:32.24 | NetRipper | :p |
15:33.29 | XDS2010__ | any1 willing to build? |
15:34.00 | dcordes | XDS2010__, sorry ?? |
15:34.20 | dcordes | NetRipper, why not put it on leo ? |
15:34.39 | XDS2010__ | need 2 patches that aren't in commit dcordes and i dont have the bandwidth to do this right now |
15:35.04 | dcordes | XDS2010__, ok |
15:35.13 | NetRipper | dcordes, it's probably more difficult ;) |
15:35.28 | XDS2010__ | dcordes u game? |
15:36.17 | dcordes | NetRipper, is the mdp on board ? |
15:36.57 | NetRipper | i have no idea, i've not disassembled it :p |
15:37.09 | NetRipper | but ther's probably some sort of connector for the screen |
15:37.12 | NetRipper | flat cable or so |
15:37.47 | dcordes | question is could you connect bigger screen to this or need different mdp |
15:39.03 | NetRipper | the qsd8250 supports upto 1280x720 resolution |
15:39.23 | XDS2010__ | dcordes ? |
15:39.48 | dcordes | NetRipper, is the display controller on chip ? |
15:39.55 | dcordes | doubt it |
15:40.01 | dcordes | XDS2010__, yes ? |
15:40.53 | NetRipper | dcordes, dont know |
15:41.03 | NetRipper | dcordes, i think there are disassembly pics on the forum somewhre of the hd2 |
15:41.44 | dcordes | NetRipper, I have some dismantling howto .doc but low res pics |
15:43.25 | *** join/#htc-linux balans (~Gebruiker@82-170-215-5.ip.telfort.nl) |
15:44.53 | dcordes | look what I found |
15:45.03 | dcordes | ftp://ftp.hp.com/pub/open_source/Handheld/AirLife100/kernel.tar.gz yet another qsd8250 tarball :D |
15:45.12 | dcordes | s/tarball/kernel/ |
15:46.02 | dcordes | NetRipper, can you download it on the oe machine ? |
15:47.34 | NetRipper | busy |
15:47.38 | NetRipper | 50 sec |
15:47.48 | NetRipper | im off to home, later |
15:49.24 | *** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk) |
15:50.32 | dcordes | 450 euros for that beast |
15:52.13 | NetRipper | does look nice |
15:52.27 | NetRipper | http://tweakers.net/nieuws/67061/hp-brengt-airlife-100-smartbook-voor-229-euro-naar-europa.html picture there |
15:53.59 | *** join/#htc-linux XDS2010__ (~XDS2010@unaffiliated/xds2010) |
15:54.17 | dcordes | et een data-abonnement van 48 euro. |
15:54.44 | dcordes | s/et/met/ |
15:56.24 | *** join/#htc-linux MethoS- (~clemens@134.102.106.250) |
15:59.29 | NetRipper | yes |
15:59.47 | NetRipper | 299 euro only combined with an expensive subscription |
16:00.30 | *** join/#htc-linux froezen (~me@i-195-137-126-143.freedom2surf.net) |
16:01.30 | dcordes | wondering if you can downgrade or cancel that subscription |
16:01.37 | NetRipper | no results on ebay or amazon hehe |
16:02.32 | *** part/#htc-linux kalemas (~kalemas@ns2.openhardware.ru) |
16:03.29 | dcordes | siempre conectado! |
16:03.39 | dcordes | http://pulso.telefonica.es/desarrollo.php?id=127 |
16:04.12 | *** join/#htc-linux Jack_E (~chatzilla@host86-133-109-12.range86-133.btcentralplus.com) |
16:08.35 | dcordes | bbl |
16:20.39 | *** join/#htc-linux mayohead_ (~ethan@c-24-21-226-236.hsd1.wa.comcast.net) |
16:28.27 | *** join/#htc-linux froezen (~ircap@i-195-137-126-143.freedom2surf.net) |
16:31.19 | *** join/#htc-linux Captnoord (~Captnoord@dc5147a47b.adsl.wanadoo.nl) |
16:33.37 | *** join/#htc-linux mastermerlin (~Adium@pD957C06B.dip.t-dialin.net) |
16:35.03 | *** join/#htc-linux kiozen (~oeichler@rgnb-5d87d8b2.pool.mediaWays.net) |
16:37.50 | *** join/#htc-linux XDS2010 (~XDS2010@unaffiliated/xds2010) |
16:49.16 | *** part/#htc-linux freakonlegs (~Craigtbal@host86-181-62-58.range86-181.btcentralplus.com) |
16:58.44 | *** join/#htc-linux DarkMasterHalo (~ssoulard@modemcable187.118-80-70.mc.videotron.ca) |
17:04.48 | *** part/#htc-linux DarkMasterHalo (~ssoulard@modemcable187.118-80-70.mc.videotron.ca) |
17:06.56 | Kensan | LeTama: what shoud I pass as init when booting your image? |
17:11.24 | LeTama | Kensan, nothing, it has init executable at root |
17:15.10 | *** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by) |
17:17.18 | Kensan | LeTama: ok, it's booting fine and I can connect via adb shell |
17:17.25 | Kensan | LeTama: what would you want me to test? |
17:17.39 | *** join/#htc-linux |Jeroen| (~jeroen@94-224-31-113.access.telenet.be) |
17:18.06 | LeTama | That's perfect, that's all I needed |
17:18.17 | LeTama | it confirms that the binaries are fine |
17:18.34 | LeTama | Thanks a lot Kensan |
17:19.16 | LeTama | I guess you don't have anything running on the phone, right ? Only adb ? |
17:20.01 | phh | LeTama: btw, I was thinking about your problems, it might sound totally stupid... but couldn't it be some weird clock problems ? |
17:20.05 | Kensan | wait |
17:20.13 | Kensan | the screen just got messed up |
17:20.51 | Kensan | hm |
17:21.05 | Kensan | might be because of sleep or something else? |
17:21.22 | LeTama | maybe |
17:21.23 | phh | idle sleep yeah |
17:21.24 | phh | possible too |
17:21.25 | Kensan | phh: clock? Could you elaborate? |
17:21.32 | phh | Kensan: cpu clock |
17:21.40 | phh | if acpuclock make it running at 1GHz |
17:21.41 | LeTama | phh: it could be, however it does that on multiple kernel with different clock initialization |
17:21.43 | phh | but the VDD doesn't apply |
17:21.45 | phh | or such stuff |
17:22.06 | Kensan | LeTama: you use clock-wince.c |
17:22.08 | LeTama | I thought of the acpuclock and vdd |
17:22.15 | Kensan | on leo |
17:22.28 | tmzt | NetRipper: we got a vanilla snapdragon source from compaq/hq it seems |
17:22.32 | phh | LeTama: did you also try to disable idle sleep ? |
17:22.35 | LeTama | I hacked the driver to force 576000, no change |
17:22.38 | Kensan | can I figure out from /proc in what state the display/device is? |
17:22.49 | LeTama | but I'm not sure I did it right |
17:22.49 | tmzt | yeah, there's no suport for airlife in there that I can see |
17:22.56 | phh | Kensan: cat /sys/power/state |
17:23.45 | Kensan | phh: brilliant, that's what I was looking for |
17:24.08 | LeTama | phh, I think I tried disabling PM, is it enough ? |
17:24.13 | phh | LeTama: no it's not |
17:24.27 | phh | LeTama: search for idle stuff in "general msms configuration" |
17:24.31 | phh | where you select board/amss and stuff |
17:24.51 | LeTama | ok |
17:27.25 | phh | (I don't have kernel sources right now, so forry for fuzzyness) |
17:27.56 | high-rez | Any of you built android from source before? I'm not sure how I define a board target... |
17:28.14 | phh | high-rez: ask stinebd |
17:28.17 | LeTama | phh: no problem |
17:28.41 | high-rez | phh: Thanks :-) |
17:31.32 | *** join/#htc-linux balans1 (~Gebruiker@53546421.cable.casema.nl) |
17:32.58 | phh | high-rez: you can also look for xdandroid build docs |
17:35.10 | *** join/#htc-linux balans (~Gebruiker@53546421.cable.casema.nl) |
17:35.35 | LeTama | high-rez, source build/envsetup.sh |
17:35.42 | LeTama | then choosecombo |
17:35.44 | LeTama | ? |
17:36.19 | Kensan | I'll try dcordes rootfs next. |
17:36.32 | Kensan | LeTama: you want me to test something different? |
17:37.15 | LeTama | Kensan, nothing yet thanks, we need to make this work on hd2 now :) |
17:37.53 | *** join/#htc-linux balans1 (~Gebruiker@53546421.cable.casema.nl) |
17:38.11 | Kensan | LeTama: I have some local patches that I apply to our htc-msm-2.6.32 tree. |
17:38.36 | Kensan | LeTama: we should try to make the same tree buildable for both devices via configuration. |
17:39.01 | Kensan | LeTama: currently clock-wince is built unconditionally and I need the default mach-msm/clock implementation. |
17:39.19 | LeTama | Kensan, yes, it could help |
17:40.40 | Kensan | LeTama: there's too many different kernel trees already all over the place. |
17:40.56 | LeTama | phh, the only thing I see is suspend sleep mode, idle sleep mode, minimum idle time before sleep, idle spin time |
17:41.12 | phh | LeTama: yup idle sleep mode |
17:41.32 | high-rez | LeTama: Will that ask me questions like the akm dev entry etc ? |
17:41.35 | high-rez | :) |
17:42.06 | LeTama | akm dev entry ? |
17:42.52 | LeTama | phh, I have Power collapse currently, should I go to wait for interrupt ? |
17:43.08 | phh | LeTama: definitely. |
17:43.10 | high-rez | Yeah for orientation etc. I've sort of got cyanogens build working on my device, but the resolution for the display and touch screen are off, as well as the /dev/akm<device>-aot (iirc) entry is just a little bit. if I symlink it it all works. |
17:43.19 | LeTama | ok, let's try that |
17:43.21 | high-rez | But creating a /dev symlink every time is no fun :) |
17:43.56 | LeTama | high-rez, huh, no, it only selects target |
17:44.10 | *** join/#htc-linux swc|666 (~infidel20@unaffiliated/swc666/x-4934821) |
17:44.16 | high-rez | LeTama: Ahh, ok. So I just need to figure out how to create a new target with all of this information then. :D |
17:44.35 | LeTama | probably yes |
17:49.37 | high-rez | LeTama: Any idea where the screen size definitions etc are configured for specific devices ? I'm looking in vendor/htc/sapphire-open and don't see where I'd edit this info. |
17:50.28 | *** join/#htc-linux balans (~Gebruiker@53546421.cable.casema.nl) |
17:54.01 | stinebd | high-rez: configure an android build with a buildspec.mk file in your aosp root directory. see http://xdandroid.com/wiki/Build_Configuration |
18:00.08 | high-rez | stinebd: That only appears to apply for existing supported targets, no? |
18:00.37 | stinebd | high-rez: if you're adding a new target you need to add android makefiles and a vendor tree for it anyway, so it applies generally |
18:01.08 | stinebd | if you need help with adding a target just copy the dream stuff |
18:01.58 | high-rez | stinebd: Right, I understand. My vendor tree is nearly identical to the dream (different offset kernel address offset, different screen resolution/touch resolution). I basically just want to try to copy the dream and change these things to see if it'll work. |
18:03.00 | LeTama | phh: no change... |
18:03.17 | phh | LeTama: ok |
18:03.36 | high-rez | stinebd: But I'm looking at the dream-open directory in the android kit - and I don't see where the screen resolution is configured, for example. |
18:04.22 | stinebd | high-rez: you only need to define the density, which goes in system.prop |
18:05.02 | high-rez | stinebd: ohh. interesting. ok so I gotta figure out screen density then. |
18:05.15 | stinebd | yeah, basically just try different values and pick what looks best |
18:05.26 | high-rez | stinebd: Does this also affect the touch screen ? |
18:05.42 | stinebd | no idea |
18:05.44 | high-rez | The touch screen is insane at the moment. :) Up and down are reversed with left and right |
18:05.57 | stinebd | it wouldn't affect that in particular, no |
18:07.45 | high-rez | I wonder if I could extrapolate the DPI from the UAProfile ScreenSizeChar :D |
18:08.17 | high-rez | Hmm probably not. |
18:11.25 | *** join/#htc-linux loop0 (~loop0@165.109.198-77.rev.gaoland.net) |
18:13.17 | *** join/#htc-linux xRaptorx (~devilcuba@cpe-24-160-123-231.tampabay.res.rr.com) |
18:15.48 | *** join/#htc-linux PSPdemon (~PSPdemon@c-76-123-109-83.hsd1.fl.comcast.net) |
18:16.43 | *** join/#htc-linux froezen_ (~ircap@i-195-137-126-143.freedom2surf.net) |
18:17.36 | *** join/#htc-linux balans (~Gebruiker@53546421.cable.casema.nl) |
18:18.53 | *** join/#htc-linux leviathan (~davidlan@nariwork-03.ee.ethz.ch) |
18:19.05 | *** join/#htc-linux akoma1s (~quassel@ppp-94-68-116-82.home.otenet.gr) |
18:19.26 | *** join/#htc-linux MarcLandis (~drettsch@quassel/contributor/marclandis) |
18:22.09 | *** join/#htc-linux bartman (~bart@tau.jukie.net) |
18:24.04 | *** join/#htc-linux GNUtoo (~GNUtoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
18:30.12 | *** join/#htc-linux NeoMatrixJR (~chatzilla@173-25-48-212.client.mchsi.com) |
18:32.49 | *** join/#htc-linux balans (~Gebruiker@53546421.cable.casema.nl) |
18:35.52 | thedicemaster | are back and hangup just 1 button on the diamond?, and same for dial and home? |
18:42.19 | *** join/#htc-linux meatshead (~non@c-24-21-226-236.hsd1.wa.comcast.net) |
18:51.31 | *** join/#htc-linux kiozen (~oeichler@rgnb-5d87d8b2.pool.mediaWays.net) |
18:52.43 | *** join/#htc-linux finalbeta (~finalbeta@ip-83-134-158-79.dsl.scarlet.be) |
19:07.19 | *** join/#htc-linux jira (~foo@77-58-108-196.dclient.hispeed.ch) |
19:07.41 | jira | hi |
19:08.23 | jira | I'm looking for a quite special smartphone, a friend of mine mentioned this channel |
19:09.19 | jira | should be tough, possibly with fold-in main display like nokia's communicators |
19:09.30 | jira | and it should run gnu/linux :) |
19:09.34 | jira | anyone any advice? |
19:09.56 | phh | 's googling for nokia's communicator |
19:10.37 | phh | ok i'm not totally sure of what you mean |
19:10.43 | phh | does the Touch pro2 matche your request ? |
19:11.00 | phh | (it runs gnu/linux fairly well, but perhaps ask for which features you need) |
19:12.56 | jira | not quite, since it exposes it*s main display to the environment |
19:13.12 | phh | ok |
19:13.18 | phh | then I know no such device |
19:13.48 | jira | nvm, thx |
19:14.13 | jira | reason I am looking for this is: currently i am using a nokia 6210 |
19:14.23 | tmzt | backflip has that |
19:14.32 | tmzt | not very good device otherwise though |
19:14.56 | phh | tmzt: you're sure of that ? |
19:15.08 | phh | that's not how I've understood its form factor |
19:15.17 | jira | erm |
19:15.37 | jira | i use that jut as mobile phone, i am looking for something different |
19:15.45 | tmzt | 15:12 < jira> not quite, since it exposes it*s main display to the environment |
19:15.56 | tmzt | maybe I misunderstand him |
19:16.13 | jira | reason i mentioned that one is, though it's quite sturdy, it's pretty much dying |
19:16.18 | tmzt | I haven't played with one though |
19:16.31 | tmzt | jira: we're all waiting for perfect snapdragon qwerty device |
19:16.37 | phh | tmzt: yes but as far as i've seen, the backflip doesn't "close" its screen |
19:16.43 | tmzt | I want two form factors, jornada replacement, tp2 replacement |
19:16.47 | tmzt | one for pocket, one for bag |
19:16.55 | tmzt | they can have the same chip for all I care |
19:17.35 | jira | have had a blue angel, it's display got lots of dents after short usage, and i guess i trashed it completely today |
19:17.57 | jira | that's y i want one that closed it's display |
19:18.37 | phh | tmzt: did you ever tried good screen protectors ? |
19:18.45 | phh | like invishield |
19:18.48 | phh | or invisible shield |
19:18.51 | phh | I don't remember how it's called |
19:18.54 | jira | nope |
19:18.55 | tmzt | no |
19:19.04 | tmzt | I think the stuffing came off my screen on the inside |
19:19.08 | tmzt | it's pretty weird |
19:19.13 | phh | jira: perhaps give it a try, it's quite incredible |
19:19.13 | tmzt | and ts is rainbow |
19:19.34 | jira | hm |
19:20.55 | jira | have to get a device before, and i thought i'd get one that stands me |
19:21.43 | phh | not really |
19:22.08 | jira | ? |
19:22.35 | phh | I mean there is no device that really outstands the others |
19:23.00 | jira | pretty common situation... |
19:23.23 | phh | TP2 was really good when it's been released |
19:23.34 | [acl] | tp2 is good now :-) |
19:23.51 | phh | but it would have been the best for at least a year, if it waited for snapdragon and hdmi out |
19:24.05 | phh | [acl]: right |
19:24.11 | [acl] | so true |
19:24.23 | tmzt | we push we ask we beg we don't receive |
19:24.23 | [acl] | phh: u ready for my next round of shenanigans ? |
19:24.31 | tmzt | june 7th comes and goes |
19:24.32 | phh | shenwhat ? |
19:24.34 | tmzt | no qwerty snappy |
19:24.55 | [acl] | phh: look it up |
19:25.15 | [acl] | anyways i did the small app on android to load the libgles_qcom directly |
19:25.19 | [acl] | loaded the ahi functions |
19:25.36 | [acl] | but there is no function to create surfaces so i had to stop there |
19:25.55 | phh | black behaves differently from rhod ? |
19:25.58 | *** join/#htc-linux balans1 (~Gebruiker@82-170-215-5.ip.telfort.nl) |
19:26.03 | [acl] | yes it actually fires up |
19:26.07 | [acl] | slow but it fires up |
19:26.20 | [acl] | rhod however still shows 15 mb of ram for the gpu |
19:26.33 | tmzt | no functions to create surfaces? |
19:26.35 | tmzt | what does that mean |
19:26.57 | phh | tmzt: you need some android library stuff to use libgles_qcom to actually render something |
19:27.03 | leviathan | [acl]: shenanigans? you mean the pub? |
19:27.09 | stinebd | surfaceflinger? |
19:27.12 | tmzt | it has the egl functions? |
19:27.32 | phh | tmzt: yes |
19:28.00 | [acl] | well i did on android sa well using egl |
19:28.02 | [acl] | that doesnt work at all |
19:28.07 | [acl] | it just goes blank |
19:28.17 | [acl] | but since the libgles has the ahi functions, you can access the chip directly |
19:28.41 | tmzt | and what can you do with that? |
19:28.45 | [acl] | its very similar to the wince version but it doesnt have the same functions available to create drawable sufraces |
19:28.47 | tmzt | I'm not familar with ahi |
19:29.55 | [acl] | ahi is that ati name for the chip i suppose |
19:30.00 | [acl] | ati handheld interface |
19:30.17 | tmzt | documentation? |
19:30.45 | [acl] | cant find any. there is some for the wince ahi2dati version and i figured the android would have the same |
19:30.48 | [acl] | it does have some but not all |
19:31.31 | tmzt | is it in htc-linux.org wiki of somewhere |
19:31.33 | [acl] | just search AhiDispSurfGet .. thats the function not available on the android version. It mus thave its own way to create surfaces that EGL access it |
19:31.41 | tmzt | can we get that from the xda group |
19:31.55 | [acl] | i think im the only one who even bothered to dive in this deep |
19:31.57 | tmzt | are surfaces like textures? |
19:32.01 | [acl] | yeah .. |
19:32.12 | tmzt | it's also possible you have to get the surface from pmem on blak |
19:32.13 | *** join/#htc-linux Kawaiius (~yadayada@pool-71-255-187-177.slsbmd.east.verizon.net) |
19:32.16 | tmzt | since it doesn't have kgsl |
19:32.57 | [acl] | well same in wince. The ahi2dati is wrapped by another lib to handle all the dirty work. but you can still access it directlyu and draw stuff on screen |
19:33.43 | *** join/#htc-linux dcordes (~dccordes@unaffiliated/dcordes) |
19:34.00 | *** join/#htc-linux rafyvitto (~rafyvitto@76-195-45-44.lightspeed.wlfrct.sbcglobal.net) |
19:34.02 | [acl] | phh: so any thouhts on this gpu haveing 15mb allocated in android? doesnt make sense right? |
19:34.12 | phh | [acl]: why doesn't make sense ? |
19:34.15 | phh | you have 8MB SMI + 8MB EBI |
19:34.33 | phh | hum no |
19:34.34 | phh | 7MB SMI |
19:34.43 | ali1234 | EBI stands for? |
19:34.52 | phh | external bus interface |
19:34.58 | phh | smi = stacked memory interface |
19:35.01 | [acl] | 15.25. which i guess is 7+8 plus the .25 internal ? |
19:35.03 | phh | "onchip" vs "offchip" basically |
19:35.08 | *** join/#htc-linux Zoolooc__ (~fredsibar@p54956D1F.dip.t-dialin.net) |
19:35.10 | ali1234 | i see thanks |
19:35.15 | phh | [acl]: perhaps |
19:36.00 | dcordes | Kensan, thanks for trying the LeTama initrd. this is very useful input.. did you manage to boot the oe image? |
19:36.13 | [acl] | i wonder if we can get the smi ebi and fb mem locations to line up from wince to android. |
19:37.49 | phh | [acl]: I no longer think it's the problem |
19:38.20 | [acl] | haha . i know.. but im just going here until the next idea pops up |
19:38.41 | phh | trace dex, rpc, gpios when enabling adsp or 3D ? |
19:38.48 | phh | perhaps clocks too |
19:39.29 | [acl] | dang.. you know im just a code monkey.. how do i even begin all that? |
19:40.19 | phh | you know haret's mmutrace command ? |
19:40.34 | *** join/#htc-linux balans (~Gebruiker@82-170-215-5.ip.telfort.nl) |
19:40.38 | *** join/#htc-linux k_linux (~klinux@adsl196-255-211-206-196.adsl196-7.iam.net.ma) |
19:40.50 | [acl] | phh: no but i didnt know what gpu was till last month. so i think i can learn |
19:40.54 | [acl] | :-p |
19:41.07 | phh | google haret documentation then |
19:41.12 | [acl] | sounds delicious |
19:41.35 | k_linux | hey guys |
19:41.48 | dcordes | heyyy |
19:42.11 | Kensan | dcordes: yes, it boots |
19:42.17 | k_linux | at last someone got froyo running on our devices ! |
19:42.19 | dcordes | Kensan, awesome! |
19:42.19 | Kensan | dcordes: I am trying to login |
19:42.23 | phh | k_linux: oh ? |
19:42.28 | Kensan | dcordes: the oe image I built. |
19:42.34 | phh | which froyo and where ? |
19:42.50 | k_linux | phh: acl didn't tell u ? |
19:42.51 | Kensan | dcordes: I tried booting your angstrom rootfs which starts booting and shows the angstrom screeny&progress bar |
19:42.55 | [acl] | k_linux: ppc geeks waiting for your froyo release .. |
19:42.56 | phh | k_linux: no |
19:43.00 | [acl] | i told everyone earlier |
19:43.15 | k_linux | http://forum.xda-developers.com/showthread.php?t=689223 |
19:43.20 | Kensan | dcordes: it then stops sometime (more than half judging by the progress bar) |
19:43.21 | phh | right, I didn't read logs today. |
19:43.24 | *** join/#htc-linux balans1 (~Gebruiker@82-170-215-5.ip.telfort.nl) |
19:43.38 | dcordes | Kensan, it stops? it doesn't show login? can you remove /etc/init.d/psplash ? |
19:43.43 | k_linux | I'm still comparing files with what I did b4 |
19:44.01 | Kensan | dcordes: I am trying to get access to the oe image. Forgot to build cdc_ether and friends so working on that. |
19:44.03 | k_linux | call still doesn't work |
19:44.10 | Kensan | dcordes: but it looks good so far. |
19:44.28 | dcordes | Kensan, I'm specifically wondering about the exact build I linked to |
19:44.49 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
19:44.50 | Kensan | dcordes: it would be really cool if somebody could do the arch/arm/mach-msm/clock-wince.c vs clock.c properly so we can both build from the same tree. |
19:45.02 | Kensan | dcordes: which build do you mean? |
19:45.03 | msd18 | hey guys |
19:45.11 | dcordes | Kensan, give me patch name email and I puish it |
19:45.25 | msd18 | hey dcords |
19:45.28 | phh | k_linux: this still doesn't say which froyo it is |
19:45.41 | msd18 | hey phh and kensan |
19:45.46 | Kensan | dcordes: well I simply hacked the makefile to switch back to clock.c statically because that's what I need for nexus. |
19:46.01 | k_linux | phh: sdk-eng 2.2 FRF42 36942 test-keys |
19:46.11 | Kensan | dcordes: I do not know the inner workings of clock-wince and what the actual differences are. |
19:46.14 | phh | k_linux: ok sdk |
19:46.16 | phh | so no thanks. |
19:46.20 | phh | k_linux: does it even have JIT ? |
19:46.24 | Kensan | dcordes: would be nice if whoever implemented it could fix it up. |
19:46.31 | Kensan | msd18: hi |
19:46.32 | tmzt | can we adopt the upstream patches to unify soc support |
19:46.33 | dcordes | Kensan, I'm interested in nexus bootability of this root http://linuxtogo.org/~lgorris/builds/OE/leo/live/minimalist-image-htcleo.tar.gz |
19:46.41 | tmzt | seems the abstract clock api better |
19:46.43 | Kensan | dcordes: right, give me a sec |
19:46.55 | k_linux | phh: I just run it once, I can give u more details in some mins |
19:47.10 | tmzt | Kensan: from what I remember of clock-wince.c it just forces certain registers |
19:47.15 | tmzt | otherwise it's the same as clock.c |
19:47.20 | [acl] | k_linux: ohh man i cant wait.. finally something else to butcher up besides sense ui |
19:47.35 | msd18 | lol |
19:47.52 | Kensan | tmzt: ok, the diff just seems a bit big to me. |
19:47.57 | k_linux | acl: yeah u can't imagine my hapiness ! :D |
19:48.35 | Kensan | msd18: going fine. Some minor progress on nexus |
19:48.40 | k_linux | phh: I will see what's in and mix it with nexus 1 |
19:48.50 | phh | k_linux: you can't. |
19:49.03 | phh | there is a reason if N1's rom hasn't already been ported. |
19:49.31 | k_linux | phh: n1 rom was ported to G1,hero,eris |
19:49.47 | phh | k_linux: the only things I've seen are SDK ports ... |
19:49.50 | phh | perhaps with some N1 apps |
19:49.59 | k_linux | phh: maybe |
19:50.07 | phh | anyway, know I understand why I no longer receive any donation at all ... |
19:50.15 | phh | everyone makes builds, and it's builders who get those ... |
19:50.20 | tmzt | sdk/goldfish |
19:50.23 | tmzt | lovely |
19:50.26 | phh | tmzt: yeah. |
19:50.32 | phh | tmzt: I think it lacks JIT |
19:50.36 | tmzt | it's like good old 0.8 |
19:50.41 | phh | so it's pretty pointless to be used |
19:50.43 | tmzt | but I've got me Froyo |
19:53.47 | msd18 | thats good kensan |
19:59.00 | stinebd | i put up a new kitchen+ingredients with jit and libhtc_acoustic |
19:59.26 | mastermerlin | nice progress ⦠hope that android will boot once again on my rhod since it doesn't for days no matter whar I try ⦠(mourning around :) ) |
20:01.18 | phh | stinebd: cool |
20:01.34 | stinebd | also with hw3d support (super secret package at http://www.mediafire.com/?2axgzmimtj5 ) |
20:01.59 | phh | :) |
20:02.16 | stinebd | probably the last tarball i'm gonna put out with that kitchen, i've got the python version underway now |
20:05.45 | Kensan | now where did dcordes go... *heh* |
20:06.14 | k_linux | stinebd: did u got froyo running ? |
20:06.27 | k_linux | with sound I mean |
20:06.27 | stinebd | k_linux: haven't tried. i only work with aosp |
20:06.36 | msd18 | kensan |
20:06.48 | msd18 | would it be possible 2 add python support in leo? |
20:07.14 | k_linux | stinebd: there is a "bootable" version if u r interessted |
20:07.22 | k_linux | but it's very buggy |
20:07.28 | phh | k_linux: yeah that's the sd |
20:07.30 | phh | basically. |
20:07.31 | phh | sdk* |
20:07.38 | phh | just wait for aosp |
20:07.43 | stinebd | k_linux: yes, that's why i don't do it. i'll be interested in froyo when it's open source |
20:08.33 | k_linux | stinebd,phh: yeah I understand but for me I can't wait ! |
20:08.47 | phh | k_linux: it's really not worth the work. |
20:08.56 | stinebd | well feel free to hack away at the asm level |
20:10.05 | phh | :p |
20:10.05 | k_linux | :D |
20:10.05 | stinebd | i suggest going through the nexus binaries and remove all neon instructions |
20:10.06 | phh | and recode it with normal asm, with same instruction length |
20:10.06 | phh | that sounds easy |
20:10.08 | stinebd | a trivial feat |
20:10.44 | k_linux | hey guys my dev level is beginner ! :P |
20:10.55 | stinebd | so is mine |
20:11.26 | phh | same here for asm |
20:11.50 | k_linux | so if there is any tuto to begin with I'll be thankful |
20:11.51 | Kensan | msd18: sure, as soon as the kernel issue is resolved you can put anything on the device |
20:12.01 | Kensan | msd18: using openembedded that would be quite easy actually |
20:12.28 | msd18 | hmm would it be possible 2 adda cron job system after its up and running |
20:12.39 | msd18 | or a http server from the fone lol |
20:12.54 | msd18 | i know an http server in py btw oits sweet |
20:13.58 | Kensan | msd18: take a look at openembedded there's a ton of software already packaged that you could install. |
20:16.14 | msd18 | ok |
20:16.28 | msd18 | so question guys |
20:16.44 | msd18 | when should we expect a gui |
20:20.10 | *** join/#htc-linux Kawaiius (~yadayada@pool-72-84-137-6.slsbmd.east.verizon.net) |
20:31.55 | NetRipper | years and years from now ;) |
20:34.41 | *** join/#htc-linux r0w3zz (~r0w3zz@p54A8D155.dip.t-dialin.net) |
20:34.44 | Kensan | NetRipper: hehe |
20:35.04 | Kensan | msd18: well as soon as the current issue is resolved things can move very quickly I assume |
20:38.21 | NetRipper | issues* :) |
20:38.56 | msd18 | ok so exactly where are the "issues" at |
20:39.01 | rafyvitto | you guys are talking about the hd2 linux kernel yes? |
20:39.38 | msd18 | ya |
20:39.46 | rafyvitto | though so |
20:44.00 | *** join/#htc-linux freakonlegs (~Craigtbal@host86-181-62-58.range86-181.btcentralplus.com) |
20:45.19 | *** join/#htc-linux M1DLGpc (~M1DLGpc@bb-87-81-252-83.ukonline.co.uk) |
20:58.30 | *** join/#htc-linux loop0 (~loop0@apijab1.apinc.org) |
21:11.31 | *** join/#htc-linux Kawaiius (~yadayada@pool-72-84-137-6.slsbmd.east.verizon.net) |
21:18.13 | *** join/#htc-linux Kawaiius (~yadayada@pool-71-255-191-119.slsbmd.east.verizon.net) |
21:20.55 | *** join/#htc-linux MCwithLeo (~mcurto88@p549F134E.dip0.t-ipconnect.de) |
21:21.48 | MCwithLeo | hello anyone there |
21:21.58 | MCwithLeo | i have a little question |
21:22.24 | [acl] | i dont talk to Leo lovers |
21:22.28 | [acl] | :-p |
21:23.01 | MCwithLeo | ^^ |
21:23.20 | MCwithLeo | do you know sometihing about windows mobile developing? |
21:23.37 | MCwithLeo | i want write a program with a telnet connection |
21:23.52 | MCwithLeo | but i dont know where i find this |
21:24.39 | [acl] | telnet? you want to make a telnet client? |
21:24.46 | MCwithLeo | yes |
21:24.50 | LeTama | <PROTECTED> |
21:25.05 | MCwithLeo | yes but i need the source code |
21:25.14 | MCwithLeo | i find there nothing |
21:26.08 | LeTama | source code is not on svn ? |
21:26.25 | MCwithLeo | there are many files ^^ |
21:26.36 | MCwithLeo | i can only develop on visual basic |
21:26.43 | [acl] | MCwithLeo: ahh |
21:27.02 | LeTama | dotnet ? |
21:27.26 | MCwithLeo | yes |
21:28.16 | MCwithLeo | i can?t download at pocketputty.net |
21:28.49 | LeTama | pocketptty is pure C |
21:28.57 | MCwithLeo | hm |
21:29.32 | MCwithLeo | do you know where can i find a little tutorial or a programm with open source code in visual basic |
21:32.25 | *** join/#htc-linux GNUtoo (~GNUtoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
21:35.55 | LeTama | check codeproject.com maybe |
21:39.52 | *** join/#htc-linux GNUtoo|laptop (~gnutoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
21:43.23 | antoszka | Oh, BTW, has anyone figured out how to emit control codes (like, say, ^c) on pocketputty on the Leo? |
21:46.51 | *** part/#htc-linux MCwithLeo (~mcurto88@p549F134E.dip0.t-ipconnect.de) |
21:52.39 | antoszka | It's somewhat useless without those. |
22:06.39 | *** join/#htc-linux GNUtoo|laptop (~gnutoo@host187-49-dynamic.21-79-r.retail.telecomitalia.it) |
22:12.37 | *** join/#htc-linux msd18 (kvirc@ip72-207-57-246.sd.sd.cox.net) |
22:13.08 | msd18 | hey guys |
22:13.59 | *** join/#htc-linux jumoit (~samuel@121.77.87.145) |
22:15.49 | *** join/#htc-linux |msd18| (kvirc@ip72-207-57-246.sd.sd.cox.net) |
22:17.29 | *** part/#htc-linux freakonlegs (~Craigtbal@host86-181-62-58.range86-181.btcentralplus.com) |
22:21.16 | *** join/#htc-linux Transformer (~Transform@ool-4a59e397.dyn.optonline.net) |
22:21.46 | *** part/#htc-linux Transformer (~Transform@ool-4a59e397.dyn.optonline.net) |
22:27.51 | *** join/#htc-linux Jack_E (~chatzilla@host86-133-109-12.range86-133.btcentralplus.com) |
22:31.38 | *** part/#htc-linux jumoit (~samuel@121.77.87.145) |
22:31.50 | *** part/#htc-linux loop0 (~loop0@apijab1.apinc.org) |
22:34.03 | *** join/#htc-linux jim3294 (~jim@208.120.226.30) |
22:42.30 | *** join/#htc-linux Igor (~zsirc@ip-109-41-22-133.web.vodafone.de) |
22:42.58 | *** join/#htc-linux joel1nux (~jlcarnes@rrcs-24-43-120-2.west.biz.rr.com) |
22:43.17 | joel1nux | Does anyone know why the kernel might not be accepting command lines? |
22:43.30 | Igor | kensan |
22:50.44 | *** join/#htc-linux ALoGeNo (~alogeno@unaffiliated/alogeno) |
22:51.00 | ToAsTcfh | phh: u around tonight? |
22:51.29 | joel1nux | Kensan, you there? |
23:04.59 | Igor | kensan ping |
23:06.50 | *** join/#htc-linux leaigor (~laigor@188.134.16.241) |
23:30.52 | Kensan | Igor: pong |
23:38.56 | *** join/#htc-linux mastermerlin (~Adium@pD957C06B.dip.t-dialin.net) |
23:45.09 | *** join/#htc-linux RaptorX (~devilcuba@cpe-24-160-123-231.tampabay.res.rr.com) |
23:50.05 | *** join/#htc-linux leaigor (~laigor@188.134.16.241) |