| 00:03.29 | wasup | k |
| 00:03.33 | wasup | what do u need? |
| 00:03.43 | ginge | a single keypress |
| 00:03.47 | ginge | launch haretconsole |
| 00:03.51 | wasup | k |
| 00:03.53 | wasup | already done |
| 00:04.07 | ginge | type the following: |
| 00:04.11 | ginge | watch gpios 1 |
| 00:04.31 | ginge | see what fills the screen and remember the numbers in the brackets |
| 00:04.36 | ginge | dont press any keys yet |
| 00:04.47 | wasup | k |
| 00:05.06 | ginge | now you need to remove those spamming gpios with: |
| 00:05.20 | ginge | ibit gpios numbers in brackets |
| 00:05.51 | ginge | press up to get back to watch gpios and try it again |
| 00:06.16 | wasup | k just a sec... my phone is haveing issues connectin |
| 00:06.19 | wasup | there it goes |
| 00:06.20 | wasup | ok |
| 00:06.31 | ginge | repeat until you see nothing continually scrolling down the page when you run it |
| 00:07.06 | BabelO | good ngiht |
| 00:07.36 | ginge | BabelO: night |
| 00:08.00 | wasup | hmmm... (203) |
| 00:08.05 | wasup | number in bracket? |
| 00:08.19 | wasup | i put ibit gpoios 203 |
| 00:08.37 | wasup | unknown variable 'it' in expression |
| 00:09.48 | ginge | ibit gpios 203 shoud work |
| 00:12.34 | wasup | just a sec... im reconnecting |
| 00:14.21 | wasup | k.its working now |
| 00:15.12 | ginge | run the watch again |
| 00:15.19 | wasup | i did... |
| 00:15.24 | wasup | no spam... |
| 00:15.34 | ginge | press q |
| 00:15.36 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 00:15.42 | *** part/#htc-linux eTiger13 (n=eddie@67.116.236.221) |
| 00:16.03 | ginge | did you get some GPIOS in/out stuff? |
| 00:16.37 | wasup | um... what do i type into haretconsole to watch? |
| 00:16.57 | ginge | you did it already, didn't you? watch gpios 1 |
| 00:17.05 | ginge | you can press up to get history |
| 00:17.30 | wasup | yeah then it runs and goes back to haret(4)# |
| 00:17.41 | ginge | okay, instead of 1 do 10 |
| 00:17.45 | ginge | then press q |
| 00:17.49 | wasup | ok |
| 00:18.06 | wasup | it froze... just a sec |
| 00:19.40 | wasup | connection closed when i type q |
| 00:19.48 | ginge | lol |
| 00:19.52 | ginge | I meant q on the titan |
| 00:19.54 | wasup | on the titamn? |
| 00:19.55 | ginge | sorry |
| 00:19.56 | wasup | yeah |
| 00:20.07 | wasup | haha thats what i was wondering |
| 00:20.32 | ginge | this is why they don't let me write user manuals at work... I miss steps :) |
| 00:20.51 | wasup | hahaha |
| 00:20.58 | wasup | k when i hit q |
| 00:21.32 | wasup | gives me...gpios(6), (11), (13) in that order |
| 00:22.00 | wasup | i am running watch gpios 10 |
| 00:22.34 | ginge | can you pastebin the output of keys w s z shift and u j n please |
| 00:22.53 | wasup | sure... just a sec |
| 00:22.57 | ginge | you might want to change that 10 to a bigger number. it sets how long that command will run for |
| 00:25.19 | wasup | http://pastebin.com/m6cedb50f |
| 00:26.21 | wasup | it is in w s z shift u j n order |
| 00:29.34 | ginge | that looks a bit odd |
| 00:29.56 | ginge | did you only ibit 203? |
| 00:30.15 | wasup | 203 was the only one that kept coming up |
| 00:30.45 | ginge | I would expect different output from haretconsole |
| 00:30.54 | ginge | like this: 006.551 GPIOS out1_en: out1_en-15(367)=0 out1_en-16(368)=0 out1_en-17(369)=0 out1_en-18(370)=0 out1_en-19(371)=0 out1_en-20(372)=0 |
| 00:31.13 | wasup | oh i didnt copy that part... |
| 00:31.18 | wasup | justa sec |
| 00:31.31 | dcordes_ | what's your haret version wasup ? |
| 00:31.58 | wasup | 5.1 i think |
| 00:32.23 | wasup | i got that info before... but when i ran watch gpios 50 it didnt come up |
| 00:32.58 | ginge | go back to 10 I guess |
| 00:33.44 | wasup | hold on... here... http://pastebin.com/d1c55ffb3 |
| 00:33.51 | ginge | dcordes_: I have everything ported to 2.6.25 but there are still some sd problems. I am getting there though. We should plan the upstream merge of android-msm-2.6.25 into linuxtogo branch at some point |
| 00:33.56 | wasup | that was before it froze and i reconnected |
| 00:34.40 | ginge | which key was that you pressed? |
| 00:35.07 | ginge | oh wait, thats the initial gpio dump |
| 00:35.20 | ginge | thats more like what we should see |
| 00:35.36 | dcordes_ | ginge: that's great. did you hear anything about google talking about going mainline? |
| 00:35.59 | ginge | dcordes_: no, I fraid not |
| 00:36.11 | wasup | just a sec.. i re-did it... im copying to pastebin.. with key presses wsz shift ujn |
| 00:36.49 | dcordes_ | ginge: we should speak to swetland |
| 00:37.04 | dcordes_ | s/to/with/ |
| 00:37.06 | ginge | dcordes_: dunno anythig about that |
| 00:37.13 | ginge | dcordes_: to what end? |
| 00:37.28 | wasup | k... here. http://pastebin.com/d836cd4c |
| 00:38.00 | ginge | perfect |
| 00:38.10 | dcordes_ | ginge: about our code,their cdode,mainline |
| 00:38.13 | wasup | took a little time... but im learning |
| 00:38.23 | ginge | wasup: thats the fun bit |
| 00:38.29 | wasup | yep |
| 00:38.31 | wasup | :) |
| 00:38.53 | dcordes_ | http://wiki.xda-developers.com/index.php?pagename=Titan_GPIO |
| 00:38.55 | ginge | dcordes_: our code == nasty their code == passable |
| 00:39.18 | ginge | quite empty |
| 00:39.20 | dcordes_ | ginge: there already is bits of the early(?) msm code in mainline |
| 00:39.47 | ginge | dcordes_: yeah, the stuff they got past qc. everything else is not quite finished by the looks of it |
| 00:40.10 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 00:40.21 | dcordes | sorry |
| 00:40.28 | ginge | dcordes_: I said ... yeah, the stuff they got past qc. everything else is not quite finished by the looks of it |
| 00:40.52 | dcordes | qc is quality check that needs to passed for mainline? |
| 00:41.22 | ginge | dcordes_: yeah, there are kernel code reviews that check for formatting and if it actualyl works |
| 00:41.28 | ginge | dcordes_: mostly anyway |
| 00:42.14 | dcordes | ok |
| 00:42.22 | ginge | I;m not sure they would get that android specific stuff in either considering the closed nature of android |
| 00:42.33 | dcordes | I also doubt that |
| 00:42.41 | dcordes | also if you look at stuff like the onscreen keyboard |
| 00:42.48 | ginge | probably more like sdcc driver and clock stuff |
| 00:42.53 | ginge | dcordes_: yeah no chance |
| 00:43.13 | ginge | dcordes_: there are some things that shouldn't need to exist ;) |
| 00:43.29 | dcordes | what is that binder stuff anyway? |
| 00:43.48 | dcordes | you looked into that? |
| 00:43.54 | Marajin | I don't think anyones work out what binder's for |
| 00:44.00 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
| 00:44.03 | ginge | its like IPC |
| 00:44.09 | dcordes_ | not my day. wrong button |
| 00:44.11 | ginge | but for that javaese shit |
| 00:44.55 | ginge | look on archive.org at openbinder.org for some clues |
| 00:45.09 | dcordes_ | inter process communication?? |
| 00:45.15 | dcordes_ | ok |
| 00:45.34 | *** join/#htc-linux wasup1 (n=Tech@208.47.103.106) |
| 00:45.34 | ginge | yeah |
| 00:46.04 | ginge | apparently its not derived from palm / openbinder |
| 00:46.28 | *** part/#htc-linux wasup1 (n=Tech@208.47.103.106) |
| 00:46.30 | *** join/#htc-linux wasup1 (n=Tech@208.47.103.106) |
| 00:46.31 | ginge | some guys are working it out http://www.macrobug.com/blog/2007/12/02/beginning-to-decode-android-ipc/ |
| 00:47.01 | *** join/#htc-linux rakeem (n=rak@n058152131193.netvigator.com) |
| 00:47.51 | dcordes_ | uuh painful |
| 00:49.08 | wasup1 | wow i got a headache from reading that article... too many really smart people |
| 00:49.12 | dcordes_ | wasup1: what works for you on titan/what doesn't? |
| 00:49.21 | wasup1 | what do u mean? |
| 00:49.28 | dcordes_ | hardware drivers |
| 00:49.36 | dcordes_ | does touchscreen work? |
| 00:49.51 | wasup1 | um... no usb, keyboard, camera, |
| 00:49.57 | wasup1 | touchscreen...yes |
| 00:50.06 | wasup1 | though the calibration is off |
| 00:50.12 | wasup1 | even when i calibrate it |
| 00:50.17 | wasup1 | it is still off. |
| 00:51.28 | wasup1 | yeah h/w wise... not much works |
| 00:51.33 | wasup1 | except the touchscreen |
| 00:51.44 | wasup1 | the on screen keyboard doesnt even work |
| 00:51.48 | wasup1 | :D |
| 00:52.01 | ginge | sounds like th kaiser ts |
| 00:52.27 | dcordes_ | ginge: how'd we figure if it is the same? |
| 00:52.36 | dcordes_ | he could try my moko image |
| 00:52.37 | ptl | anyone knows a dialer program that can use the primary camera for videocalls? |
| 00:53.01 | wasup1 | huh? |
| 00:53.07 | wasup1 | that was random..hahaha |
| 00:53.38 | wasup1 | http://forum.xda-developers.com/showthread.php?t=296758 |
| 00:53.49 | wasup1 | try that thread something about video calls htc |
| 00:54.02 | dcordes_ | wasup1: does the touchscreen work for you on kaiser with the vogue zImages? |
| 00:54.09 | AstainHellbring | phone also works in titan for pick up but then can't hang up |
| 00:54.35 | dcordes_ | ok so titan smd=vogue smd |
| 00:54.51 | wasup1 | um... i tried booting a kaiser image and it gets to the main screen then goes back to laser of death |
| 00:55.07 | AstainHellbring | yes dcordes_ |
| 00:55.10 | dcordes_ | wasup1: I mean vogue, not kaiser |
| 00:55.51 | dcordes_ | does the titan ts do anything when you boot the zImages on http://it029000.massey.ac.nz/vogue/? |
| 00:55.52 | AstainHellbring | wasup1, you have to do the SD images not the standard ones |
| 00:55.59 | AstainHellbring | the SD ones boot completely |
| 00:57.35 | wasup1 | my ts works on the vogue images... just the calibration is off, even after calibrating |
| 00:57.52 | wasup1 | come to think of it im not sure if i did try to boot the sd image |
| 00:58.01 | AstainHellbring | try that wasup1 |
| 00:58.08 | wasup1 | k |
| 00:58.25 | wasup1 | whats the command to change my name to wasup |
| 00:58.29 | wasup1 | - the 1 |
| 00:58.44 | AstainHellbring | do /nick (whatever) |
| 00:58.57 | wasup | k :D |
| 00:59.11 | wasup | u have a link to where i can download the sd images |
| 01:01.54 | wasup | whats the command to do this? (5:55:32 PM) dcordes_: wasup1: I mean vogue, not kaiser |
| 01:02.06 | wasup | like talk to someone else without a private message? |
| 01:02.33 | dcordes_ | you put nick: in front or what do you mean? |
| 01:03.12 | dcordes_ | or do nickna<tab key> if your client supports auto completion |
| 01:03.33 | wasup | unknown command. |
| 01:03.35 | wasup | hmmm |
| 01:05.08 | dcordes_ | ginge: we use no specific code to enable the speakerphone (for calls) no? doesn't kaiser amss enables it automatically? |
| 01:05.20 | ginge | dcordes_: yeah, amss |
| 01:05.31 | *** join/#htc-linux Othello_ (i=Magorium@gateway/tor/x-174149049f5b8619) |
| 01:06.43 | AstainHellbring | wasup, http://it029000.massey.ac.nz/vogue/android.zip |
| 01:06.50 | dcordes_ | ginge: I wonder why ril sends the at commands to enable it |
| 01:06.57 | joshts0 | ginge: hmmph is itw orking yet ;) |
| 01:07.20 | ginge | I got some excellent traces from wasup, just making a spreadsheet with the matrix data now |
| 01:07.20 | dcordes_ | ginge: while dzo needs to use his vogue-hw.c code |
| 01:07.27 | joshts0 | sweet |
| 01:07.33 | ginge | dcordes_: nfc |
| 01:07.51 | ginge | dcordes_: i guess dzos must be doing the right thing |
| 01:08.30 | AstainHellbring | ginge: do you want traces of the front buttons |
| 01:08.39 | dcordes_ | ginge: yes he turns it on himself // This data is sent to the arm9 to enable audio |
| 01:08.55 | ginge | AstainHellbring: they are on the cpld, so if you could it would be good;) |
| 01:09.14 | ginge | dcordes_: I would have thought that is a job for proc_comm |
| 01:09.51 | AstainHellbring | ginge: ok i'll need you to walk me through how to do it, I'm in windows as well.... |
| 01:10.00 | ginge | groans |
| 01:10.08 | AstainHellbring | sorry |
| 01:10.15 | ginge | sorry man, its getting really late here :( |
| 01:10.30 | AstainHellbring | I can do the windows really well just not 100% sure what to do to start it |
| 01:10.49 | ginge | its gonna be a couple of days before I can really get anywhere |
| 01:11.10 | ginge | you could do with python and haretconsole, not absolutely needed but saves you hassle decoding the data |
| 01:11.27 | AstainHellbring | ok so proally best to get a linux setup running then eh? |
| 01:11.37 | dcordes_ | yes |
| 01:12.47 | AstainHellbring | ok will do |
| 01:15.15 | ginge | AstainHellbring: sorry, nothing personal. |
| 01:15.26 | ginge | anyone want to test another titan kernel? |
| 01:17.07 | ginge | http://www.headfuzz.co.uk/files/android/zImage-titan if you do |
| 01:19.21 | ginge | damn forgot to save the file.... need to reupload |
| 01:20.10 | wasup | ill test it right now |
| 01:20.17 | ginge | updated |
| 01:20.22 | wasup | so.. |
| 01:20.32 | wasup | i just replace that with my other zImage? |
| 01:20.39 | wasup | and boot android? |
| 01:20.45 | ginge | yeah, not android |
| 01:21.00 | wasup | what do i boot? |
| 01:21.03 | wasup | angstom? |
| 01:21.04 | ginge | download angstrom and edit default.txt |
| 01:21.20 | wasup | ok.. u have the link for angstrom?> |
| 01:21.20 | dcordes_ | wasup: are you sure you fetched the file that ginge put up a minute ago? |
| 01:21.54 | dcordes_ | wasup: http://linuxtogo.org/~lgorris/kaiser-bootkit/angstrom.bin |
| 01:22.19 | wasup | fetched the zImage-titan? |
| 01:23.44 | dcordes_ | wasup: yes I'm reffering to 03:19 < ginge> damn forgot to save the file.... need to reupload |
| 01:25.01 | wasup | yeah.. i just got it |
| 01:25.36 | wasup | our time zones are different? |
| 01:25.40 | wasup | :D |
| 01:26.43 | dcordes_ | probably, it's late at night here in germany |
| 01:26.54 | Marajin | dcordes_: Nope, it's early! |
| 01:26.54 | ginge | not quite that late at night here in the uk |
| 01:27.04 | ginge | Marajin: get back in that coffin! |
| 01:27.29 | wasup | its 6:30 pm here in the hell hole yuma, az |
| 01:27.39 | Marajin | ginge: I think most people consider 2:30am late :P |
| 01:28.01 | ginge | Marajin: oh yeah. I forget. |
| 01:28.06 | wasup | k i booted it |
| 01:28.25 | dcordes_ | Marajin: not for me. I'm getting sleep today :P |
| 01:28.39 | Marajin | dcordes_: sleep? What's that? |
| 01:28.42 | ginge | press some buttons, does anything happen |
| 01:30.48 | wasup | q,w,shift, left softkey(on keyboard),right softkey(on keyboard), return key.leftarrow, ok key,windows key <-- who needs that?... all do something |
| 01:30.57 | wasup | random error comes up |
| 01:31.17 | wasup | kaiser_kbd_irq_handler |
| 01:31.28 | dcordes_ | :) |
| 01:31.49 | ginge | random error? |
| 01:31.51 | dcordes_ | wasup: q,w=whole keyboard works? |
| 01:32.07 | wasup | qwer |
| 01:32.09 | wasup | works |
| 01:32.18 | ginge | getting closer then |
| 01:32.25 | dcordes_ | ginge: you're da man |
| 01:32.36 | wasup | hey hey hey.... im not a very technical guy... looked like errors or something to me |
| 01:32.38 | wasup | hahaha |
| 01:32.42 | ginge | :) |
| 01:33.04 | ginge | so some keys do nothing? |
| 01:33.06 | *** join/#htc-linux pronto (n=pronto@pool-71-179-232-167.bltmmd.fios.verizon.net) |
| 01:34.01 | wasup | when i type q.....mmki>mmki>mmki>mmki>mmki>mmki>mmki>bhjuvgytrcfdecfdevgytr bhju |
| 01:35.02 | ginge | so q prints all that? |
| 01:35.08 | wasup | yep... |
| 01:35.18 | ginge | do they all do that? |
| 01:35.41 | wasup | no.... |
| 01:36.27 | wasup | e = VGYTRkaiser_keyboard: kaiser_kbd_irq_handler() |
| 01:36.42 | ginge | ignore they handler stuff |
| 01:36.44 | wasup | w= BHJU |
| 01:37.01 | wasup | r = CFDE |
| 01:37.32 | wasup | right softkey bhju |
| 01:37.54 | wasup | left softkey = VGYTR |
| 01:38.09 | ginge | looks like a windows license key :) |
| 01:38.13 | wasup | left arrow = XZSW |
| 01:38.18 | wasup | hahaha |
| 01:38.21 | wasup | :D |
| 01:39.06 | ginge | any not working? |
| 01:39.43 | wasup | yeah |
| 01:39.50 | wasup | all the ones i didnt list |
| 01:40.02 | wasup | tyuiop |
| 01:40.06 | ginge | oh. hmm |
| 01:40.11 | wasup | asdfghjkl |
| 01:40.26 | wasup | backspace doesnt work either |
| 01:40.31 | wasup | zxcvbnm |
| 01:40.47 | ginge | oh well. I think I know what needs to be done. I need to get some sleep now, but I will be looking at those logs very closely. This matrix keyboard is set up a bit differently. |
| 01:40.50 | wasup | up down and right arrow = doesnt work |
| 01:40.58 | wasup | ok. |
| 01:41.05 | ginge | night all |
| 01:41.08 | wasup | take it easy... have a nice night |
| 01:41.11 | dcordes_ | night ginge |
| 01:44.55 | *** part/#htc-linux wasup (n=Tech@208.47.103.106) |
| 01:45.01 | *** join/#htc-linux wasup (n=Tech@208.47.103.106) |
| 01:45.40 | wasup | well im getting off work talk to you all tomorrow... |
| 01:45.43 | wasup | bye |
| 02:07.38 | *** join/#htc-linux tmzt (n=tmzt@adsl-70-228-92-50.dsl.akrnoh.ameritech.net) |
| 02:18.06 | Marajin | hmhm |
| 03:03.06 | Marajin | dcordes_: ping? |
| 03:08.56 | *** join/#htc-linux proverse (n=proverse@32.145.230.75) |
| 03:09.21 | fhteagle | greetings all |
| 03:09.28 | Marajin | allo |
| 03:10.02 | fhteagle | having trouble getting the data connection to work in android |
| 03:10.22 | fhteagle | anyone else get it to work with latest android / android-data from ~lgorris? |
| 03:10.32 | Marajin | on what device? |
| 03:10.45 | Marajin | Gotta bare in mind we're basically supporting 4 differet devices atm |
| 03:10.47 | fhteagle | kaiser... |
| 03:10.59 | fhteagle | 1.62 something radio I think |
| 03:11.10 | Marajin | Oh it's about as reliable as a goldfish with alzheimers |
| 03:11.30 | Marajin | data work find under angstrom for me, I've never yet got it to work under android |
| 03:11.38 | Marajin | *fine |
| 03:12.29 | Marajin | Very few people do get android to go on data and it'll lock up within 5 minutes anyay |
| 03:12.56 | fhteagle | ahh. |
| 03:13.17 | Marajin | I've used it for an hour straight under angstrom. It's just android being strange basically |
| 03:13.17 | fhteagle | forum made it sound like it was working more reliably than that |
| 03:13.22 | fhteagle | nice. |
| 03:13.30 | fhteagle | any gui's in the works for angstrom? |
| 03:13.34 | Marajin | Not yet |
| 03:13.49 | fhteagle | x? gnome? openmoko's gui? etc? |
| 03:13.50 | Marajin | technically we did get X to load butI don't think we've got the touchscreen to work with X yet |
| 03:14.44 | Marajin | dcordes_: Ping ping? |
| 03:14.50 | fhteagle | ahh |
| 03:15.37 | Marajin | I think we're most interested in getting openmoko going really. |
| 03:15.41 | Marajin | Android's just too unreliable |
| 03:18.24 | fhteagle | latest files still using the old/buggy android release, nobody's gotten their hands on anything newere? |
| 03:19.57 | Marajin | Nah we're using the m5 release |
| 03:21.22 | fhteagle | just strikes me as bass ackwards that there are all these little apps being made for an OS that almost nobody uses yet... |
| 03:21.34 | fhteagle | cept the nokia tablets maybe |
| 03:21.58 | Marajin | Nokia tablets run something else |
| 03:22.16 | fhteagle | openmoko/angstrom calls work yet? |
| 03:22.41 | Marajin | heh, console image, no dialer |
| 03:23.15 | Marajin | But in theory, yeah |
| 03:24.05 | fhteagle | hmm. |
| 03:24.06 | *** join/#htc-linux surgex (i=surge@pool-71-186-163-107.bflony.fios.verizon.net) |
| 03:24.12 | fhteagle | anything need testing? |
| 03:24.20 | Marajin | Not that I know of. |
| 03:24.57 | Marajin | You're welcome to hang around though, small things tend to crop up multiple times a day |
| 03:33.05 | fhteagle | mmk. |
| 03:33.27 | fhteagle | not a whole lot of free time these days, but want to help if/how I can... |
| 03:33.50 | fhteagle | will be nice to be free of M$ on all of the devices I use on a daily basis ;^) |
| 03:35.29 | Marajin | fhteagle: heh =) well we'll see what we can do eh? Give it a month |
| 03:38.03 | CPress | Hey guys |
| 03:38.13 | Marajin | 'lo CPress |
| 04:10.53 | CPress | Where are the updated files for android? |
| 04:24.30 | *** join/#htc-linux pronto (n=pronto@pool-71-179-232-167.bltmmd.fios.verizon.net) |
| 04:27.10 | *** join/#htc-linux rakeemflex (n=rak@n219079207150.netvigator.com) |
| 04:31.16 | *** join/#htc-linux Othello_ (i=Magorium@gateway/tor/x-7e00ff7df2379ea2) |
| 05:14.49 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 05:18.40 | *** join/#htc-linux smev (n=smev@S010600215514f029.cg.shawcable.net) |
| 05:37.03 | *** join/#htc-linux dex__ (n=dex@ANancy-154-1-81-226.w81-49.abo.wanadoo.fr) |
| 05:42.27 | *** join/#htc-linux pleemans (n=peter@dD577D009.access.telenet.be) |
| 05:49.46 | *** join/#htc-linux joshts0 (i=joshts0@cpe-76-186-198-67.tx.res.rr.com) |
| 06:04.05 | *** join/#htc-linux kiozen (n=oeichler@p54929B67.dip0.t-ipconnect.de) |
| 06:17.05 | Rroet | moin |
| 06:17.16 | Marajin | 'lo |
| 06:21.24 | Rroet | for the thursday morning music theme, we've selected http://www.youtube.com/watch?v=XrkThaBWa5c this week. Enjoy |
| 06:23.10 | kiozen | hm, think I stick with my "Divine Madness".. |
| 06:25.07 | Rroet | Faith ? |
| 06:26.22 | Rroet | the babe of the divine madness ain't badlooking.. yet the goth type music.. neh. |
| 06:26.53 | Rroet | I'm more a Groove Armada or Pavarotti type ;P |
| 06:27.12 | kiozen | nope just "Madness" (some British Ska band) |
| 06:43.47 | Rroet | me like Sex Pistols :P God Shave the queen! |
| 06:45.13 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 07:02.30 | Marajin | Rroet: FWIW I just lookedb ack to IRC from sorting my music collection heh |
| 07:10.33 | Rroet | :P |
| 07:14.39 | *** join/#htc-linux marbalon (n=marbalon@212.122.223.98) |
| 07:19.46 | *** join/#htc-linux kiozen (n=oeichler@p54929B67.dip0.t-ipconnect.de) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux pleemans (n=peter@dD577D009.access.telenet.be) |
| 07:19.47 | *** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux ptl (n=patola@unaffiliated/ptl) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux tcccp (i=hey@223.66.238.89.arpa-addr.in) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux toi (n=pleemans@d5152D3B4.access.telenet.be) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux Foxdie (n=foxdie@fox.akao.co.uk) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux vr (n=Vr@iliade.daycom.net) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux Dinde (n=kayser@sur-internet.net) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux raph_ael (i=raphael@kikoolol.orbus.fr) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux lama (n=lama@estel.wpia.uw.edu.pl) [NETSPLIT VICTIM] |
| 07:19.47 | *** join/#htc-linux mickey|zzZZzz (i=mickey@openmoko/coreteam/mickey) |
| 07:19.47 | *** join/#htc-linux dase (i=dase@p1atin.de) [NETSPLIT VICTIM] |
| 07:20.04 | *** join/#htc-linux paulproteus (n=paulprot@2002:cbb2:8293:0:0:0:0:1) |
| 07:20.04 | *** join/#htc-linux lpotter (n=ljp@CPE-124-191-144-181.vic.bigpond.net.au) |
| 07:20.05 | *** join/#htc-linux hlbot (n=adm@iclem.net) [NETSPLIT VICTIM] |
| 07:27.15 | *** join/#htc-linux zoolooc (n=lucian@nrbg-4dbfcd7a.pool.einsundeins.de) |
| 07:31.30 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 07:33.48 | *** join/#htc-linux rob_w (n=bob@M8bae.m.pppool.de) |
| 08:01.30 | marbalon | dcordes_: ping |
| 08:02.25 | Marajin | marbalon: He's actually asleep I think! It's novel I know |
| 08:03.39 | marbalon | Marajin: thanks for info, any info about new images for android on kaiser ? |
| 08:03.53 | Marajin | Nothing significant that I know of |
| 08:07.20 | *** join/#htc-linux Robwoerle (n=bob@Maf0e.m.pppool.de) |
| 08:20.44 | *** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo) |
| 08:21.55 | BabelO_ | hi |
| 08:24.04 | ptl | hello |
| 08:24.18 | Marajin | 'lo |
| 09:35.17 | *** join/#htc-linux axe- (n=axe@217.116.62.236) |
| 09:54.54 | *** join/#htc-linux goxboxlive (n=goxboxli@31.84-48-212.nextgentel.com) |
| 09:59.12 | *** join/#htc-linux exco (n=exco@e181092148.adsl.alicedsl.de) |
| 10:02.42 | *** part/#htc-linux exco (n=exco@e181092148.adsl.alicedsl.de) |
| 10:02.50 | *** join/#htc-linux exco (n=exco@e181092148.adsl.alicedsl.de) |
| 10:12.41 | *** join/#htc-linux joshts0 (i=joshts0@cpe-76-186-198-67.tx.res.rr.com) |
| 10:25.25 | *** join/#htc-linux ellisway (n=ellis@80-46-67-47.static.dsl.as9105.com) |
| 10:32.44 | cr2 | kiozen: charging works ? |
| 10:38.33 | *** join/#htc-linux Marex (n=vasum7am@auryn.karlin.mff.cuni.cz) |
| 10:39.00 | Marex | cr2: hi, how's N560 going? |
| 10:39.16 | Marex | cr2: are you planning to mainline it any soon ? |
| 10:39.36 | *** join/#htc-linux Bastiaan_Wakkie (n=chatzill@212.71.15.163) |
| 10:41.41 | Bastiaan_Wakkie | i have the possibility to replace my BlueAngel for a Prophet s200 good idea? |
| 10:42.55 | Bastiaan_Wakkie | How is the support of linux on this device sofar? |
| 10:56.31 | Marajin | Bastiaan_Wakkie: Not really, it's a less powerful device AFAIK |
| 10:56.32 | Bastiaan_Wakkie | ok... good to know |
| 10:57.34 | Marajin | Bastiaan_Wakkie: Slower CPU, less RAM, etc. |
| 10:58.53 | Bastiaan_Wakkie | sorry wrong button |
| 10:59.26 | Bastiaan_Wakkie | so the latest greatest imagez... where are they now a days? |
| 10:59.54 | Marajin | Bastiaan_Wakkie: Clarify, linux images? |
| 11:00.07 | Bastiaan_Wakkie | yes.. best for my BlueAngel |
| 11:00.35 | Bastiaan_Wakkie | qutopia? openmoke? android? |
| 11:01.00 | Bastiaan_Wakkie | %s:ke:ko:g |
| 11:01.23 | Marajin | Bastiaan_Wakkie: http://handhelds.org/moin/moin.cgi/BlueAngel as far as I know, I've never had a BA myself |
| 11:01.55 | Marajin | Android doesn't work well on /any/ phone so I wouldn't advise using it if anyone has even made it run on the BA yet |
| 11:02.46 | Marajin | Bastiaan_Wakkie: http://www.linuxtogo.org/~htcpxa/htcblueangel/ |
| 11:03.04 | Marajin | Bastiaan_Wakkie: Makes sense, that's the main central area for linux images at the moment |
| 11:05.01 | pigeon | cr2: hi, what did you want me to do with haret again? |
| 11:14.32 | *** join/#htc-linux drasar (n=maik@77.93.211.13-msol.msol.cz) |
| 11:14.33 | *** join/#htc-linux LunohoD_ (n=alex@e180068053.adsl.alicedsl.de) |
| 11:21.15 | pigeon | hmm, funny, nledset 0 is the led, nledset 1 seems to be the vibrator |
| 11:45.36 | *** join/#htc-linux pigeon_ (n=pigeon@60-241-137-179.static.tpgi.com.au) |
| 11:48.51 | *** join/#htc-linux Othello_ (i=Magorium@gateway/tor/x-c2fc3b5e0035ab0a) |
| 11:57.45 | *** join/#htc-linux paulproteus (n=paulprot@2002:cbb2:8293:0:0:0:0:1) |
| 11:57.45 | *** join/#htc-linux lpotter (n=ljp@CPE-124-191-144-181.vic.bigpond.net.au) |
| 11:57.45 | *** join/#htc-linux hlbot (n=adm@iclem.net) [NETSPLIT VICTIM] |
| 11:59.00 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 12:00.40 | cr2 | pigeon_: create the earlyharetlog.txt in the haret directory, and boot linux. pastebin the haretlog.txt file |
| 12:01.02 | cr2 | pigeon_: the led1 is the vibrator. |
| 12:01.44 | cr2 | Marex: i'm more concerned about hardware RE now, than about cleaning the code an porting to 2.6.26 right now. |
| 12:02.10 | pigeon_ | cr2: http://pastebin.com/m420a6f2e |
| 12:02.27 | pigeon_ | looks like i need to add the machine to haret |
| 12:05.46 | cr2 | ps , lsmod and kill are registered :) |
| 12:06.19 | cr2 | we may need to write some .py decoder to make tracing easier. |
| 12:06.25 | *** join/#htc-linux exco (n=exco@e181092148.adsl.alicedsl.de) |
| 12:06.58 | cr2 | pigeon: powermon should work too. |
| 12:07.13 | pigeon | yup |
| 12:07.50 | cr2 | pigeon: i've created a haret version, which has more contol over power* functions, bt and IR. |
| 12:08.10 | cr2 | so a lot of tracing is possible. |
| 12:08.28 | cr2 | you may also try 'mmutrace' on the SD area. |
| 12:09.12 | cr2 | http://wiki.xda-developers.com/index.php?pagename=WallabyMemoryMap |
| 12:10.12 | dcordes_ | hi |
| 12:10.44 | Marajin | sleep well dcordes_ ? |
| 12:12.11 | dcordes_ | yes |
| 12:13.13 | kiozen | hi cr2, you saw the results yestarday night? |
| 12:13.56 | pigeon | cr2: so what do you reckon i should do next? |
| 12:14.56 | dcordes_ | Marajin: looks like we need to continue the driver development on our own for a while! |
| 12:15.07 | Marajin | dcordes_: Why? what's up? |
| 12:15.45 | dcordes_ | because of the whole groundlord thing |
| 12:15.59 | Marajin | dcordes_: Huh? You'll have to explain |
| 12:16.13 | dcordes_ | he won't be able to code with the keyboard in a box :( |
| 12:17.08 | dcordes_ | s/groundlord/landlord/ |
| 12:20.58 | cr2 | pigeon: it's necessary to adapt the gpio tracing .py decoder (i think), and to check if mmutrace works. |
| 12:21.15 | cr2 | kiozen: after my patching ? |
| 12:21.21 | kiozen | cr2: yes |
| 12:21.37 | kiozen | cr2: no power AC=1 usb=1 |
| 12:21.43 | kiozen | cr2: ac power AC=0 usb=1 |
| 12:21.51 | kiozen | cr2: usb power AC=1 usb=0 |
| 12:23.02 | kiozen | cr2: but I am not sure what happens if battery is full |
| 12:23.14 | kiozen | cr2: don't think it stops loading it |
| 12:23.39 | kiozen | cr2: at least it does not change state |
| 12:24.32 | pigeon | hmm |
| 12:25.20 | cr2 | kiozen: without the monitoring you can't see/stop anything. |
| 12:26.06 | kiozen | cr2: yes that what I suspect, we need monitoring to stop charging |
| 12:26.13 | kiozen | cr2: cheep crap.. |
| 12:26.26 | cr2 | kiozen: maybe it's solved in hardware ? i don't know what is inside n560, and what chip is responsible for the charging. on BA the hw chip takes care of this problem |
| 12:27.08 | cr2 | kiozen: less hw == less power is lost |
| 12:27.29 | kiozen | cr2: don't think that the control unit real would add :) |
| 12:27.39 | cr2 | pigeon: try to run mmutrace on the SD register area. |
| 12:28.13 | cr2 | kiozen: ok, but i don't have the motherboard scans/ BOM. |
| 12:28.28 | Marajin | cr2: Hey, what'd you say works on thehermes now? |
| 12:28.33 | pigeon | cr2: but the mmutrace command isn't being registered |
| 12:28.43 | kiozen | cr2: right I wanted to get these little screwdrivers... |
| 12:29.51 | kiozen | cr2: so right now the power state is just recognized, it won't start charging in Linux, right? |
| 12:31.49 | Marajin | Poor cr2 |
| 12:31.55 | Marajin | he's being pestered :P |
| 12:32.56 | cr2 | pigeon: hmm. ok. |
| 12:33.06 | dcordes_ | cr2: is there any news regarding boardid 6 display init code since I last asked? |
| 12:33.28 | cr2 | Marajin: TS, keyboard, LCD |
| 12:33.56 | cr2 | kiozen: i think it should be charging now, but you can't monitor/stop it. |
| 12:34.20 | Marajin | cr2: Hmm, how close are we to getting other stuff running? |
| 12:34.33 | cr2 | dcordes_: no. i think i've done what i could. maybe there is some bug there, though ;) |
| 12:34.35 | kiozen | ok, I let the device run for half an hour.. let's see |
| 12:34.48 | cr2 | Marajin: do you have the 2442 cpu manual ? |
| 12:34.56 | Marajin | cr2: Nope |
| 12:35.21 | cr2 | Marajin: the NAND is detected properly, but produces some block errors. maybe it's better with 2.6.26, i don't know |
| 12:35.47 | Marajin | hmm |
| 12:35.48 | cr2 | Marajin: i think the easiest thing to do is to fix the seial port clocks. |
| 12:35.54 | Marajin | ok |
| 12:36.54 | cr2 | Marajin: btw, the wifi control is on s3c-sdi, so it can be explored too. but serial clocks (BT, IR and GSM AT) should be easy to fix |
| 12:37.21 | Marajin | right |
| 12:37.24 | cr2 | Marajin: it should be somewhere on the samsung website. or i can upload it. |
| 12:37.30 | Marajin | cr2: Is anyone else vaguely active on the hermes? |
| 12:37.37 | cr2 | no afaik. |
| 12:37.44 | cr2 | because of the SD. |
| 12:37.55 | cr2 | which is the same as on athena. |
| 12:38.12 | Marajin | why, what's the problem there? the ATi thing? |
| 12:38.34 | cr2 | i have a lot of traces and notes about ATI W228x, but waiting for the working asic3-mmc port to 2.6.26 |
| 12:38.38 | cr2 | yes. |
| 12:39.18 | cr2 | the s3c-sdi driver works, so you'd be able (in theory :) to init the wifi, and to read in/out the wifi eeprom. |
| 12:39.36 | cr2 | btw, it's the same on athena,n560 and others. |
| 12:39.49 | *** join/#htc-linux proverse (n=proverse@32.148.195.45) |
| 12:39.56 | Marajin | Ok |
| 12:39.58 | Marajin | good to know |
| 12:41.36 | cr2 | kiozen: do you know the 'g3data' program ? |
| 12:41.48 | dcordes_ | cr2: bugs _I_ won't be able to fix. I'll better not play with this or I will end up frying ba6 |
| 12:41.52 | kiozen | cr2: no |
| 12:42.05 | *** part/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 12:42.14 | cr2 | kiozen: is there some similar qt4 program ? |
| 12:42.26 | dcordes_ | cr2: can you provide some pointer on what might be wrong? |
| 12:42.33 | cr2 | http://www.frantz.fi/software/g3data.php |
| 12:42.57 | kiozen | cr2: no that I would know, I am more a graph producer :) |
| 12:43.16 | cr2 | dcordes_: i think i've done the spi things right. but there may be some timing problem between applying power, and initializing the ATI chip. |
| 12:43.26 | kiozen | looks a bit like referencing maps |
| 12:43.27 | cr2 | kiozen: lol |
| 12:43.42 | cr2 | kiozen: yes, picking out the waypoints :) |
| 12:44.39 | cr2 | i'd like to change some things, but hacking gtk is real pita ;) |
| 12:44.41 | kiozen | cr2: what's wrong about using g3data? |
| 12:44.52 | kiozen | ok :) yes gtk sucks |
| 12:44.55 | cr2 | kiozen: only 2 points on the x and y axes. |
| 12:45.05 | Marajin | kiozen: I can definitel agree with that sentiment! |
| 12:45.12 | cr2 | it can be done much better. |
| 12:45.43 | cr2 | kiozen: so it's like 2point calibration now. |
| 12:46.15 | kiozen | Marajin: once tried to use gtk for a customer, after one week I had enought frustration to make him buy a QT license |
| 12:46.27 | fhteagle | ubuntu mobile uses gtk or something else? |
| 12:46.38 | Marajin | kiozen: Haha :) |
| 12:47.20 | *** join/#htc-linux tsdogs (n=tsdogs@62.13.169.86) |
| 12:49.45 | cr2 | fhteagle: ubuntu == gnome ? |
| 12:49.45 | kiozen | cr2: yes more or less |
| 12:50.35 | cr2 | fhteagle: then it may be c#.njet |
| 12:51.17 | fhteagle | http://www.ubuntu.com/products/mobile |
| 12:51.26 | fhteagle | yeah gtk + python and gtk + java |
| 12:51.47 | fhteagle | pardon gtk +python and gtk+ c |
| 12:51.51 | fhteagle | but java as well |
| 12:52.11 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
| 13:00.24 | fhteagle | http://www.gnome.org/mobile/ |
| 13:16.06 | *** join/#htc-linux Othello_ (i=Magorium@gateway/tor/x-c547e2b00070ead2) |
| 13:21.55 | *** join/#htc-linux meredydd (n=meredydd@cpc4-cmbg2-0-0-cust471.cmbg.cable.ntl.com) |
| 13:22.16 | meredydd | prods ginge_ gently |
| 13:26.23 | *** join/#htc-linux Othello__ (i=Magorium@gateway/tor/x-0e22f0aceddc0387) |
| 13:26.45 | kiozen | cr2: battery is charging in Linux. back to wince it still has 100% |
| 13:31.31 | *** join/#htc-linux proverse_ (n=proverse@32.147.132.211) |
| 13:33.31 | cr2 | kiozen: good. now i only need to undestand wtf is 15bit, and which ADC channel is used for the monitor. |
| 13:34.21 | Marajin | meredydd: We may not see much of ginge |
| 13:34.22 | kiozen | cr2: I stand haret-ready by your side :) |
| 13:34.42 | meredydd | What's happened to him, Mara? |
| 13:34.43 | cr2 | kiozen: i think it's useful to make some led experiments. but i need to add the group data into wiki first |
| 13:35.14 | kiozen | ok |
| 13:35.16 | cr2 | kiozen: i have your data already, i'll look at the dll |
| 13:37.46 | ginge_ | meredydd: you rang? |
| 13:38.21 | meredydd | Nothing important; just wondering whether you'd got the SD driver back upright |
| 13:39.09 | ginge_ | not had chance to look. busy packing for my house move :( |
| 13:39.33 | meredydd | Aha. That's why we're not supposed to be seeing much of you? :) |
| 13:39.39 | meredydd | Oh, well, in that case, the very best of luck. |
| 13:42.46 | Marajin | heh |
| 13:42.53 | Marajin | convienient timing |
| 13:42.59 | Marajin | eyes Ginge. |
| 13:43.00 | Marajin | Lurker! |
| 13:49.25 | ginge_ | ;) |
| 13:53.42 | Marajin | O.o |
| 13:53.57 | cr2 | <PROTECTED> |
| 13:54.11 | Marajin | why is this code limitin the maximum rows returned to 128 in the SQLite wrapper |
| 13:54.18 | Marajin | that's fucked |
| 13:54.32 | cr2 | haha |
| 13:54.36 | cr2 | an uncompromised Web 2.0 experience |
| 13:54.56 | Marajin | 96kb of memory and 128 rows max haha |
| 13:55.05 | Marajin | per table o returned data |
| 13:55.07 | cr2 | x86 sucks. power. |
| 13:55.20 | Marajin | man you'd be /screwed/ if you were using blobs to store images |
| 13:56.32 | Marajin | cr2: Iunno didn't geode have a fairly decent power useage? |
| 13:56.54 | Marajin | cr2: Ya do realise they made x86 compat clamshell devices like 15-20 years ago right? ^_~ |
| 13:57.01 | cr2 | BabelO: http://freshmeat.net/projects/cuneiformlinux/?branch_id=74963&release_id=281807 |
| 13:57.22 | *** join/#htc-linux smev (n=smev@S010600215514f029.cg.shawcable.net) |
| 13:57.25 | Marajin | 1.5W x86 compat fr the geode |
| 13:57.39 | cr2 | Marajin: i had a cpq 386sx16 notebook >10 years ago. |
| 13:58.19 | Marajin | I'm talking about pocket sized devices but sure |
| 13:58.27 | Marajin | anyway, there's low power x86 chips |
| 13:58.32 | cr2 | Marajin: you can't beat arm with x86. |
| 13:58.56 | cr2 | because it's a much more simple and sane cpu |
| 13:59.09 | Marajin | Oh I agree |
| 13:59.25 | Marajin | for embedded use certainly |
| 13:59.31 | Marajin | but they make 'em |
| 13:59.38 | Marajin | supposedly not bad CPUs either |
| 14:00.11 | cr2 | ok, but i use embedded stuff to save power |
| 14:00.26 | cr2 | not because of the rich 3D web 2.0 experience ;) |
| 14:00.41 | Marajin | Well the Geode GX will run WinXP or something apparently at 1.1W |
| 14:01.06 | cr2 | Marajin: lol. in suspend mode ? |
| 14:01.16 | Marajin | Nah under load |
| 14:01.28 | Marajin | the NX line is the performance model tho', that can use up to 14 W! |
| 14:01.49 | cr2 | my (linux) notebook needs 5A@20V under load. |
| 14:02.15 | cr2 | it's 100W for the 1.8GHz cpu |
| 14:02.17 | *** join/#htc-linux BlueCopy (n=BlueCop@c-71-228-205-211.hsd1.tn.comcast.net) |
| 14:02.47 | kiozen | well AMD is not really known for energy savings :) |
| 14:02.57 | cr2 | i'd like to see the winxp notebook that runs with 1.1W |
| 14:03.19 | Marajin | haha |
| 14:03.34 | cr2 | kiozen's LCD needs 180mA only :) |
| 14:03.56 | kiozen | btw how much does the eeePC need? |
| 14:03.56 | cr2 | i think with 3.3 and 1.8V |
| 14:03.57 | Marajin | cr2: All I know is they make 'em mate, if you want to play you'd have to get a dev board from AMD |
| 14:04.45 | cr2 | Marajin: the cpu is not the only power consumer, so this 1.1W is pure marketing fluff. |
| 14:05.01 | Marajin | yeha I know |
| 14:05.07 | Marajin | heh they have a 0.9W one |
| 14:05.18 | cr2 | Marajin: i wish AMD has released the ati w228x docs ;-) |
| 14:05.38 | Marajin | huh |
| 14:05.40 | Marajin | 5.1W TDP |
| 14:05.51 | cr2 | kiozen: how much power does pxa270 take at 90 MHz ? |
| 14:06.13 | Marajin | @600mhz FWIW |
| 14:06.17 | kiozen | cr2: wish I would get 90 Mhz |
| 14:06.37 | cr2 | kiozen: you can try. 104 is a normal mode. |
| 14:06.51 | kiozen | cr2: but I can check for 104 MHz later on, now I have to collect my son from kindergarten |
| 14:06.56 | kiozen | bbl |
| 14:07.40 | cr2 | Marajin: i don't remember the numbers for pxa @624MHz |
| 14:10.11 | Marajin | coupla watts apparently |
| 14:12.03 | AstainZZZZZZ | hey guys I know of a guy that wrote an app and dll to control the leds on kaiser and any msm7x00 proc for the phones in wimo his stuff could help you get control of them in linux... |
| 14:17.35 | *** join/#htc-linux infernixx (i=nix@unaffiliated/infernix) |
| 14:19.06 | Marajin | AstainZZZZZZ: Could be |
| 14:20.14 | AstainZZZZZZ | the guy is no2chem |
| 14:20.30 | AstainZZZZZZ | when he's on again I'll have him jump in here to explain his stuff |
| 14:20.45 | Marajin | cool |
| 14:20.48 | AstainZZZZZZ | his app called nueled will let you control leds change colors for different stuff etc |
| 14:23.40 | Marajin | wasn't someone talking about that earlier? |
| 14:24.04 | AstainZZZZZZ | might have be me earlier too can't recall |
| 14:24.13 | Marajin | heh |
| 14:24.28 | Marajin | I'm too tired/lazy/in pain to bother searching the logs so we'll assume it was :P |
| 14:27.47 | AstainZZZZZZ | on this page is a link to his led drivers/apps: http://www.weienterprises.com/nue/ |
| 14:43.57 | cr2 | AstainZZZZZZ: we have nled* command in haret |
| 14:45.20 | cr2 | The source code is provided under the terms of the license agreement included with nueLEDControl ? |
| 14:47.19 | AstainZZZZZZ | umm dunno for sure on that one but the dev is a great guy so I'm sure he'd be willing to give it and help out with the efforts |
| 14:49.30 | cr2 | AstainZZZZZZ: don't see the source in the .zip , i'll start ida. |
| 14:50.13 | AstainZZZZZZ | ok and I know nochem will be on later today/tonight will have him get on and share what he can then |
| 14:51.03 | cr2 | ok. |
| 14:51.46 | cr2 | i'm only interested in the c api, to add it to haret (gpl of course). |
| 14:53.00 | *** part/#htc-linux ginge_ (n=baz@80.229.188.31) |
| 14:54.28 | *** join/#htc-linux marex_ (n=marex@88.81.95.205) |
| 14:54.36 | *** join/#htc-linux marex_ (n=marex@88.81.95.205) |
| 15:05.32 | cr2 | it goes over devioctl on LEDx: |
| 15:06.12 | cr2 | maybe wince5 has the ioctl params documented in its SDK headers. |
| 15:41.32 | *** part/#htc-linux zoolooc (n=lucian@nrbg-4dbfcd7a.pool.einsundeins.de) |
| 16:03.25 | cr2 | 0x7530=30000 |
| 16:03.53 | cr2 | 0x1388=5000 |
| 16:04.39 | cr2 | val*30000 > 5000 |
| 16:08.20 | cr2 | a=10% extreme low |
| 16:09.04 | cr2 | 26150 == % ? |
| 16:10.03 | cr2 | 16bit |
| 16:19.21 | *** part/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo) |
| 16:19.58 | ginge | al, hrm. I just got a stern talking to by a customer who purchased our codebase. They found my comment in the source |
| 16:19.58 | ginge | //take me down to overflow city where this bugs _still not patched cos the coders shitty (QA?) |
| 16:20.05 | ginge | ack, wrong window |
| 16:20.18 | ginge | oh well, still quite amusing |
| 16:36.50 | *** join/#htc-linux pH5 (n=ph5@e178195035.adsl.alicedsl.de) |
| 16:43.58 | dcordes_ | ginge: haha |
| 16:44.03 | dcordes_ | nice one |
| 16:44.57 | *** join/#htc-linux JohnnyK (n=johnnyk@nfx-nat-229.pilsfree.net) |
| 16:50.13 | cr2 | 0xe|0x8100|0x80 |
| 16:50.17 | cr2 | 0x818e |
| 16:52.53 | cr2 | pH5: are they insane ? why do they want to make 15bit spi transfers from tsc2046 ? |
| 16:53.58 | pH5 | cr2: who? |
| 16:54.16 | pH5 | that sounds like they are going for the max. continuous conversion rate |
| 16:54.26 | cr2 | on n560 |
| 16:54.34 | pH5 | I think the command + answer interleaved were around 15 clocks per conversion |
| 16:54.46 | cr2 | weird. |
| 16:54.59 | pH5 | doesn't make a lot of sense if you have to wait for TS settling time anyway, or does it? |
| 16:55.11 | cr2 | msleep 100 |
| 16:55.38 | cr2 | i need to check the command they send. |
| 16:55.52 | cr2 | TS is working with ads7846 driver. |
| 16:56.16 | cr2 | it's not 100% happy, but works. |
| 16:58.26 | *** join/#htc-linux BlueCopy (n=BlueCop@c-71-228-205-211.hsd1.tn.comcast.net) |
| 16:58.49 | pH5 | cr2: the old 8bit spi driver? |
| 16:59.05 | cr2 | i think so |
| 16:59.17 | pH5 | cr2: is the machine setup in hh.org? |
| 16:59.32 | pH5 | I'd love to have a look at it, I still can't get the SPI transfers to work on magician/2.6.26 |
| 16:59.33 | cr2 | they also do 3 ADC transfers. oversampling ? |
| 16:59.43 | cr2 | pH5: yes |
| 16:59.49 | cr2 | looxc550/ |
| 17:00.15 | *** join/#htc-linux tmzt (n=tmzt@adsl-70-228-92-50.dsl.akrnoh.ameritech.net) |
| 17:01.12 | dcordes_ | hi tmzt |
| 17:01.37 | tmzt | hey |
| 17:01.49 | dcordes_ | no news on Xfbdev issue yet |
| 17:02.00 | tmzt | did you switch to .25 kernel? |
| 17:03.26 | dcordes_ | not me |
| 17:03.30 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
| 17:03.35 | dcordes_ | but ginge |
| 17:04.30 | tmzt | do the hardware buttons on kaiser work? |
| 17:04.46 | pH5 | Hm, it would be about time to switch to .26. Isn't .26 merged yet into android-msm? |
| 17:04.47 | *** join/#htc-linux Marajin_ (n=marajin@87-194-102-189.bethere.co.uk) |
| 17:05.52 | *** join/#htc-linux OpnSrc1 (i=harisha1@gateway/tor/x-c6962b1ee118362d) |
| 17:06.24 | tmzt | on git.android or ltg? |
| 17:06.45 | pH5 | git.android |
| 17:08.23 | tmzt | is sdio supposed to be more stable in .26? |
| 17:09.19 | cr2 | tmzt: you use sdio ? |
| 17:09.26 | tmzt | but there's no kgdb or ?trace merged yet for arm? |
| 17:09.40 | tmzt | no, I don't have htc, just following kernel dev |
| 17:10.07 | tmzt | in know sdio was merged in .25, I just wondered if the .26 stack would be more stable |
| 17:11.29 | tmzt | only windows phone I have right now is my primary phone |
| 17:11.45 | tmzt | but I plan to get titan, or newer msm with keyboard |
| 17:11.49 | tmzt | cdma |
| 17:12.00 | dcordes_ | tmzt: pH5 no google is at 25 only http://git.android.com/?p=kernel.git;a=summary |
| 17:12.16 | cr2 | tmzt: ok. |
| 17:13.05 | tmzt | I tried to start a port for my phone last year, but got stuck on the eabi thing, the only thing that would boot was kevin2's hermes initrd |
| 17:13.09 | dcordes_ | ginge: I tried building htc-egpio form mainline .26 against the 2.6.25 branch with dzo's patches on top, didn't work |
| 17:14.24 | pH5 | dcordes_: fail in htc-egpio or in the kaiser board file? would you mind showing me the patch? |
| 17:14.42 | dcordes_ | pH5: no patch. I just copied the bare code from .26 |
| 17:15.24 | dcordes_ | added Kconfig and Makefile entries, enabled CONFIG_HTC_EGPIO and built |
| 17:15.35 | pH5 | dcordes_: that won't work, the platform_device setup changed quite a bit. |
| 17:15.35 | dcordes_ | there's nothing using egpio in the vogue tree |
| 17:15.44 | dcordes_ | oh I see |
| 17:16.53 | pH5 | dcordes_: I could try to cook up a patch for conversion. |
| 17:17.24 | dcordes_ | pH5: for the board file? |
| 17:17.30 | pH5 | yup |
| 17:17.47 | pH5 | dcordes_: you could try merging current git.android.com into the htc-msm tree, we should do that from time to time. |
| 17:17.49 | dcordes_ | we should bug ginge for his kaiser .25 code first |
| 17:18.03 | pH5 | dcordes_: ok, or ginge should do it ;) |
| 17:18.06 | dcordes_ | pH5: ginge already rebased our stuff on it |
| 17:19.28 | cr2 | tmzt: you have hermes ? |
| 17:19.53 | tmzt | no, Motorola CDMA Franklin |
| 17:20.00 | cr2 | ok. |
| 17:20.00 | tmzt | not ezx either |
| 17:21.54 | tmzt | I had the same setup working in qemu, I could boot the initrd and chroot into the sd |
| 17:21.57 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d86554c.pool.einsundeins.de) |
| 17:22.20 | tmzt | But, I couldn't find the gpio to bring up the card without removing it and reinserting |
| 17:22.31 | tmzt | and even rootdelay (??) didn't work |
| 17:22.53 | pH5 | cr2: ah no, you're using the ads7846 ssp adc driver. this stuff is hh.org only, the mainline guys still can't agree about how ADC infrastructure should look like... |
| 17:24.23 | dcordes_ | tmzt: sorry, you have no clue about what the invalid Xfbdev messages on kaiser are, do you? |
| 17:24.25 | cr2 | pH5: hehe. |
| 17:24.55 | dcordes_ | s/invalid/invalid update/ |
| 17:25.12 | tmzt | what do you mean update messages? |
| 17:25.24 | tmzt | the driver flags? |
| 17:26.26 | dcordes_ | no the errors I get from Xfbdev when I touch the screen |
| 17:26.48 | tmzt | the ones you got before? |
| 17:27.13 | dcordes_ | right, they're in the OE bug I filed http://bugs.openembedded.net/show_bug.cgi?id=4448 |
| 17:27.49 | tmzt | can you grep tslib for "Invalid update" |
| 17:28.10 | tmzt | no, that looks like x.org |
| 17:28.16 | dcordes_ | I already did and pH5 also took a look but nothing. let me look again |
| 17:28.21 | dcordes_ | ok |
| 17:28.35 | tmzt | probably screen regions (dirty rectangle) or accel |
| 17:28.46 | dcordes_ | tmzt: is Xorg automatically started when Xfbdev is ran? |
| 17:28.57 | tmzt | fbset show now accel, right |
| 17:28.58 | tmzt | ? |
| 17:29.13 | dcordes_ | didn't try |
| 17:29.24 | dcordes_ | but ts_test and calibrate work like a charm |
| 17:29.24 | tmzt | Xfbdev is x.org, without support for xorg.conf and using a different main loop |
| 17:30.04 | tmzt | can you zcat /proc/config.gz > tmp |
| 17:30.09 | tmzt | grep OABI tmp |
| 17:30.22 | tmzt | or check defconfig is your on host |
| 17:30.26 | dcordes_ | ok after I did the stuff? |
| 17:30.32 | tmzt | doesn't matter |
| 17:30.37 | dcordes_ | ok |
| 17:30.43 | kiozen | cr2: powermon, wifi on, bt off, backlight off 104MHz |
| 17:30.46 | kiozen | 009065: 1 99 % 4091 119 119 274 0 0 -1 -1 0 255 0 0 -1 -1 0 0 0 4 |
| 17:31.11 | tmzt | s/is/if/ |
| 17:31.47 | tmzt | or check defconfig if you are on your host |
| 17:31.53 | cr2 | kiozen: remove SD, put haret on mdoc |
| 17:32.14 | dcordes_ | tmzt: CONFIG_OABI_COMPAT not set |
| 17:32.20 | tmzt | oh |
| 17:32.31 | dcordes_ | anything else I can try real quick on device? battery dies in a minute |
| 17:32.35 | cr2 | kiozen: add powermon to default.txt, use other power commands before it. (seltcd, pwrctl) |
| 17:32.54 | cr2 | kiozen: then you'll check the mdoc-only 104MHz ops. |
| 17:32.57 | tmzt | no, I had a known good tslib/Xfbdev but it is oabi |
| 17:33.06 | tmzt | works on my device/kernel |
| 17:33.07 | cr2 | kiozen: i've documented cpld2* bits |
| 17:33.11 | tmzt | mp900c jlime |
| 17:33.20 | cr2 | kiozen: have fun with cpld1* bits yourself. |
| 17:33.27 | cr2 | kiozen: i'll edit wiki now. |
| 17:34.21 | cr2 | kiozen: check my current wiki edits now. |
| 17:34.33 | kiozen | cr2: without SD |
| 17:34.36 | kiozen | 009065: 1 98 % 4087 114 114 270 0 0 -1 -1 0 255 0 0 -1 -1 0 0 0 4 |
| 17:34.48 | *** join/#htc-linux miknix (n=miknix@81.193.87.90) |
| 17:35.01 | miknix | nickserv identify 808189alabama! |
| 17:35.01 | cr2 | kiozen: wifi off ? |
| 17:35.05 | miknix | wtf |
| 17:35.22 | kiozen | cr2: wifi on |
| 17:35.54 | cr2 | kiozen: wifi off is more interesting. |
| 17:36.08 | cr2 | 114 mA is still a lot. |
| 17:36.24 | cr2 | kiozen: how much does sirf3 need ? |
| 17:36.29 | kiozen | hm, need it for haret console |
| 17:36.39 | kiozen | sirf ? wait .... |
| 17:36.57 | cr2 | kiozen: you can put output on mdoc |
| 17:37.13 | cr2 | just write the script. |
| 17:37.36 | cr2 | or into ram, it's even better. |
| 17:37.46 | cr2 | put haret into ramdisk :) |
| 17:38.05 | kiozen | cr2: sirf is about 110mA |
| 17:38.23 | cr2 | delta ? |
| 17:38.27 | kiozen | yes |
| 17:38.41 | cr2 | ok. |
| 17:38.50 | cr2 | you have a fix ? |
| 17:38.53 | kiozen | i try the default.txt later, have to ground my son first :) |
| 17:38.58 | cr2 | ok |
| 17:44.52 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-76-88-212-37.bak.res.rr.com) |
| 17:58.00 | *** join/#htc-linux BlueCop1 (n=BlueCop@c-71-228-205-211.hsd1.tn.comcast.net) |
| 18:05.11 | *** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de) |
| 18:06.17 | kiozen | cr2: anything special to add to default.txt to make haret use a log file |
| 18:06.19 | kiozen | ? |
| 18:07.57 | cr2 | http://knol.google.com/k/the-family-handyman-magazine/toilet-clogs |
| 18:08.22 | cr2 | google is not so evil |
| 18:08.26 | cr2 | kiozen: no. |
| 18:08.41 | cr2 | kiozen: i've added the gpio matrix for LED2 |
| 18:08.58 | kiozen | hm, I have a default.txt with just "powermon 10" |
| 18:09.05 | kiozen | if I press run nothing happens |
| 18:09.11 | cr2 | kiozen: looks like it's bt/left led control. maybe wifi too. |
| 18:09.34 | cr2 | kiozen: it's written into haretlog.txt ? |
| 18:09.36 | *** join/#htc-linux tmzt_ (n=tmzt@adsl-70-228-92-50.dsl.akrnoh.ameritech.net) |
| 18:10.09 | kiozen | no haretlog to see |
| 18:10.49 | cr2 | log command ? |
| 18:10.53 | cr2 | 'log' ? |
| 18:14.37 | tmzt_mp900c | dcordes: if you want me to send you that Xfbdev, I can, but you'll need to add CONFIG_OABI_COMPAT to .config and recompile the zImage |
| 18:15.48 | *** join/#htc-linux amd64lover (n=miknix@81.193.87.90) |
| 18:18.38 | kiozen | cr2: 57mA, no wifi, no light, 104Mhz |
| 18:22.54 | kiozen | cr2: ok, let's try the LEDs |
| 18:23.41 | cr2 | kiozen: try to track the bit settings depending on the led state. |
| 18:24.24 | kiozen | cr2: trace the CPLDs or write them? |
| 18:31.27 | kiozen | cr2: can you look at the wiki if I got your bit notation right? |
| 18:31.39 | kiozen | cr2: edited the LED table |
| 18:34.06 | cr2 | kiozen: dump the shadow area, and check the bits which are in the table, and write down the led state. |
| 18:35.43 | cr2 | kiozen: you have added your current values ? |
| 18:36.05 | kiozen | no I just converted your bits to hex values |
| 18:36.50 | cr2 | why is 0 0 = 6 ? |
| 18:36.56 | cr2 | in the first line |
| 18:37.20 | kiozen | lol stupid me |
| 18:37.38 | cr2 | m,n means bank m, bitmask n |
| 18:38.25 | kiozen | ok |
| 18:44.19 | kiozen | cr2: can you cross check once again? |
| 18:48.24 | cr2 | kiozen: looks ok. |
| 18:48.44 | cr2 | check with the real data now |
| 18:49.15 | cr2 | bt on/off, wifi on/off, gps on/off, charging on/off( but it may be right led). |
| 18:51.20 | *** join/#htc-linux amd64lover (n=miknix@213.13.201.69) |
| 18:54.25 | kiozen | cr2: hm, don't think these are all bits used by leds |
| 18:54.34 | kiozen | c2 have a look at wiki |
| 18:55.50 | cr2 | kiozen: i think these are for the left led only. |
| 18:56.10 | cr2 | kiozen: for the right led there is 1,n (maybe) |
| 18:56.22 | cr2 | kiozen: what about bt on/off ? |
| 18:56.31 | kiozen | second... |
| 18:57.17 | cr2 | 1 1 is green, 0 0 is off. good. |
| 18:57.24 | cr2 | 4 is gps power on 0 |
| 18:57.39 | cr2 | so you may disable gps while testing. |
| 18:57.47 | *** join/#htc-linux wasup (n=Tech@208.47.103.106) |
| 18:58.00 | wasup | good morning everyone |
| 18:58.17 | cr2 | hm. 0 1 is green |
| 18:58.33 | cr2 | hi wasup |
| 18:58.49 | *** join/#htc-linux mike6043 (n=mike6043@ip98-170-208-103.pn.at.cox.net) |
| 18:59.11 | cr2 | kiozen: you may check this program, too http://www.weienterprises.com/nue/nueled.html |
| 19:00.29 | *** join/#htc-linux mike6043 (n=mike6043@ip98-170-208-103.pn.at.cox.net) |
| 19:01.01 | kiozen | added bt |
| 19:01.25 | cr2 | 1 0 |
| 19:01.30 | cr2 | looks good. |
| 19:01.59 | cr2 | bank 2 is pwm control, bank 0 - power/enable ? |
| 19:02.01 | *** join/#htc-linux OpnSrc1 (i=harisha1@gateway/tor/x-e24c0ebc0ff8f3c0) |
| 19:02.29 | cr2 | kiozen: blinking speed may be different ? |
| 19:02.50 | wasup | hey ehats the subject of choice right now? |
| 19:02.56 | wasup | whats* |
| 19:03.14 | cr2 | kiozen: it seems i (or htc/fsc) mixed 3 and 4 |
| 19:03.56 | cr2 | wasup: diamond, only diamond :) i don't even know if somebody booted linux there :) |
| 19:04.48 | cr2 | kiozen: GPIOA1 0x0002 bt (led?) related |
| 19:04.54 | cr2 | kiozen: looks like wifi led. |
| 19:05.48 | cr2 | kiozen: +nk (led?) means i've seen it while tracing. |
| 19:05.50 | kiozen | 0x0000 0x0003 is green blinking led too |
| 19:06.36 | kiozen | cr2: GPIOA1 0x0002 seems to be IR |
| 19:06.41 | cr2 | kiozen: how have you created 0x0000 0x0003 |
| 19:06.48 | cr2 | kiozen: IR led ? maybe. |
| 19:07.06 | kiozen | gps on |
| 19:07.07 | cr2 | kiozen: it's in the serial driver together with bt. |
| 19:07.17 | cr2 | ok. |
| 19:07.30 | cr2 | so it is more complex. |
| 19:07.40 | wasup | oh... |
| 19:08.09 | cr2 | kiozen: you have these 8 'leds' in wince kernel |
| 19:08.25 | cr2 | kiozen: so only these combinations are present in wince. |
| 19:08.29 | kiozen | hm, it's not reproducable at all |
| 19:09.45 | cr2 | kiozen: you may watch the bank1 too. 3 first bits. |
| 19:09.56 | *** join/#htc-linux marbalon (n=balon@aegk72.neoplus.adsl.tpnet.pl) |
| 19:10.11 | kiozen | couldn't see any chnage for ir on/off |
| 19:15.14 | *** join/#htc-linux mike6043 (n=mike6043@ip98-170-208-103.pn.at.cox.net) |
| 19:16.16 | kiozen | cr2: ok, looks like these are all combinations I can do |
| 19:17.51 | kiozen | hm, that does not make sense to be at all |
| 19:22.38 | *** join/#htc-linux LunohoD_ (n=alex@e180068233.adsl.alicedsl.de) |
| 19:23.32 | cr2 | hmm. |
| 19:25.00 | kiozen | think I do a new table, just enabling one component after another |
| 19:25.22 | kiozen | and writing down all cpld register |
| 19:26.50 | cr2 | ok |
| 19:31.38 | kiozen | try to do this tomorrow, I am too tired today |
| 19:31.42 | *** join/#htc-linux jeebster (n=kanakana@a88-114-192-27.elisa-laajakaista.fi) |
| 19:42.41 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 19:49.53 | drasar | pH5: Hi. So what else is needed change in hima sources? |
| 19:53.23 | *** join/#htc-linux JEEB (n=kanakana@a88-114-192-27.elisa-laajakaista.fi) |
| 19:54.21 | drasar | pH5: I have added "<asm/arch/pxa2xx_udc_gpio.h>" header file that is needed. |
| 19:55.12 | drasar | pH5: But there is still error on ".power_gpio = { &blueangel_asic3.dev, ASIC3_GPIOA_IRQ_BASE + GPIOA_USB_PUEN}," |
| 19:55.44 | pH5 | drasar: "blueangel_asic3"... |
| 19:56.24 | pH5 | that should probably be turned into himalaya_asic3, or whatever the name of the asic3 platform device is on hima |
| 19:57.06 | drasar | pH5: Yes, but himalaya_asic3 doesn't exists |
| 19:57.32 | pH5 | looks |
| 19:58.06 | pH5 | "struct platform_device himalaya_asic3", there it is |
| 19:58.37 | pH5 | just make sure you have your udc platform device below that, or use a forward declaration. |
| 20:07.45 | drasar | pH5: With udc platform device do you mean "struct platform_device himalaya_asic3 = {"? |
| 20:08.54 | *** join/#htc-linux dwaradzyn (n=gudz666@damian8155.net.autocom.pl) |
| 20:10.10 | drasar | pH5: No, you probably mean "static struct platform_device himalaya_udc" |
| 20:11.43 | dcordes_ | tmzt_mp900c: #xorg has no clue either |
| 20:16.05 | *** join/#htc-linux tmzt_ (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 20:17.34 | *** join/#htc-linux no2chem2 (n=user@dhcp-100c-213.mobile.uci.edu) |
| 20:17.41 | no2chem2 | hmm? questions about the led driver? |
| 20:17.59 | *** join/#htc-linux tmzt_mp910c (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 20:18.10 | AstainHellbring | cr2: here he is and Marajin_ too |
| 20:20.16 | pH5 | drasar: that's right |
| 20:21.31 | dcordes_ | arrgh that Xfbdev makes me go nuts |
| 20:22.13 | tmzt_mp900c_ | dcordes: yeah, I was out, and I was also trying to keep this hostap card up |
| 20:22.52 | tmzt_mp900c_ | dcordes: but I am on irssi and I haven't got it to notify me yet |
| 20:23.05 | pH5 | dcordes_: does strace help at all? or you could add some debug printfs in the tslib driver. |
| 20:23.26 | drasar | pH5: How can I use that forward declaration? |
| 20:23.31 | tmzt_mp900c_ | what did you ask on #xorg? |
| 20:23.33 | dcordes_ | pH5: I have traced the Xfbdev process one time on tmzt_mp900c_'s suggestion. |
| 20:23.48 | dcordes_ | 19:45 < dcordes_> Did somebody ever come across the error "invalid update: .." when using a raw data ts device with tslib on Xfbdev? |
| 20:24.31 | tmzt_mp900c_ | I believe that is related to sw cursor and no accel, it only happens when you touch the screen might be a good thing |
| 20:24.40 | tmzt_mp900c_ | s/it/that it |
| 20:24.47 | pH5 | drasar: a forward declaration of himalaya_asic3 would be just the line "struct platform_device himalaya_asic3;" somewhere earlier in the file. |
| 20:24.51 | tmzt_mp900c_ | apt hates me |
| 20:24.52 | apt | yes. |
| 20:25.05 | tmzt_mp900c_ | tried trailing slash and without, still |
| 20:25.12 | tmzt_mp900c_ | and he agrees |
| 20:26.05 | dcordes_ | oh right you suggested to try something and I forgot to do it |
| 20:26.09 | dcordes_ | got battery now |
| 20:26.49 | tmzt_mp900c_ | do you have a CONFIG_OABI_COMPAT zImage |
| 20:26.55 | *** join/#htc-linux tmzt (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 20:26.56 | tmzt_mp900c_ | there goes my desktop |
| 20:27.59 | dcordes_ | tmzt_mp900c_: no |
| 20:28.17 | tmzt_mp900c_ | can you build one with the patch from a few days ago (tsc2003.c)? |
| 20:28.37 | dcordes_ | isn't that thing in OE? |
| 20:28.39 | cr2 | no2chem2: hi. i'm interested in the led ioctl numbers |
| 20:28.49 | drasar | pH5: I have already had it, but I had &himalaya_asic3_dev below instead of &himalaya_asic3.dev, so I have received still error :) |
| 20:29.10 | drasar | pH5: So what now? |
| 20:29.29 | tmzt_mp900c_ | no2chem2: the ones in nk that can't be traced (I wondered about that as well) |
| 20:35.13 | cr2 | tmzt: it should be possible to set a debug printk() inside nk, at least on pxa. |
| 20:35.24 | tmzt_mp900c_ | nk.exe? |
| 20:35.34 | cr2 | tmzt_mp900c_: yes, why not. |
| 20:35.50 | tmzt_mp900c_ | I though you would have to have source to do that |
| 20:36.31 | cr2 | tmzt_mp900c_: you can't set a breakpoint, obviously, but you can hook the printk() to the virtual address |
| 20:37.06 | cr2 | tmzt_mp900c_: i think the current haret prints r0 and r1 on reaching the breakpoint (pxa only) |
| 20:37.17 | tmzt_mp900c_ | I had vibra as a led that could be turned on with nledset in haret, but I could not find a gpio to active it from early kernel |
| 20:37.33 | cr2 | tmzt_mp900c_: on which device ? |
| 20:37.45 | tmzt_mp900c_ | I was debugging pxafb, which would not init until later |
| 20:37.52 | tmzt_mp900c_ | on MotoQ CDMA |
| 20:38.01 | cr2 | ok. |
| 20:38.21 | cr2 | maybe it'd be easier to dump the wince stuff, and disassemble it. |
| 20:38.22 | tmzt_mp900c_ | Franklin was the name I had from lsusb or something, sorry |
| 20:38.48 | tmzt_mp900c_ | oddly enough, when kevin2's hermes initrd came up, fbcon worked |
| 20:38.50 | cr2 | tmzt_mp900c_: check the pxa breakpoints anyway. |
| 20:39.00 | cr2 | hermes does not use pxafb |
| 20:39.03 | tmzt_mp900c_ | but I got no dmesg (kernel boot text) before that |
| 20:39.14 | cr2 | hermes has vsfb. |
| 20:39.54 | cr2 | and initializing atiw228x is not trivial. |
| 20:40.10 | no2chem2 | oops i missed the conversation |
| 20:40.13 | tmzt_mp900c_ | yeah, I was just using the initrd and busybox |
| 20:40.19 | cr2 | but not impossible |
| 20:40.27 | cr2 | ok. |
| 20:40.30 | tmzt_mp900c_ | q is pxafb, there's no graphics chip I can find |
| 20:40.54 | no2chem2 | led ioctl numbers; let me get them for you |
| 20:41.07 | tmzt_mp900c_ | sorry, I had read that as gpio |
| 20:41.16 | cr2 | tmzt_mp900c_: you can see it from the vram address. if it's inside sdram, then you have pxafb. you can also use 'dump pxa27x' |
| 20:41.24 | dcordes_ | < tmzt> do the hardware buttons on kaiser work? <- yes, all of them. |
| 20:41.43 | tmzt_mp900c_ | I was able to draw on the screen from haret, I have txt logs somewhere |
| 20:41.44 | cr2 | no2chem2: we use nled api for now. it was documented in itsutils. |
| 20:41.51 | pH5 | cr2: or sram, for qvga devices |
| 20:42.05 | cr2 | pH5: agreed. |
| 20:42.14 | tmzt_mp900c_ | with the memory write command (can't remember what is) |
| 20:42.43 | cr2 | tmzt_mp900c_: dump pxa27x will decode all pxafb params, and do many other useful things. |
| 20:42.53 | no2chem2 | ok, |
| 20:43.06 | no2chem2 | allledmgr dll ioctls coming in |
| 20:43.07 | no2chem2 | #pragma region LED IOCONTROLS //definition of IOCTLS |
| 20:43.07 | no2chem2 | #define IOCTL_LED_SETLED0x80020004 |
| 20:43.08 | no2chem2 | #define IOCTL_LED_FORCE_SETLED0x80020008 |
| 20:43.08 | no2chem2 | #define IOCTL_LED_SETVIBRATOR0x8002000C |
| 20:43.08 | no2chem2 | #define IOCTL_LED_GET_STATUS0x80020010 |
| 20:43.09 | no2chem2 | #define IOCTL_LED_LEDTESTINIT0x80020014 |
| 20:43.11 | no2chem2 | #define IOCTL_LED_LEDTESTDEINIT0x80020018 |
| 20:43.13 | no2chem2 | #define IOCTL_LED_SETNUMSTATE0x8002001C |
| 20:43.18 | no2chem2 | er.. put a space there, stupid tabs. |
| 20:43.46 | drasar | pH5: Now it compiles fine. Anything else is needed? |
| 20:43.51 | cr2 | no2chem2: thanks. are they htc-specific or ms-generic ? |
| 20:44.00 | no2chem2 | htc-specific |
| 20:44.03 | cr2 | ok. |
| 20:44.10 | no2chem2 | for inbuf; put a 0x14 byte, |
| 20:44.11 | dcordes_ | tmzt_mp900c_: "fbset show now accel, right" <- that's what I forgot to probe. it's "accel false" |
| 20:44.13 | tmzt_mp900c_ | it might have been lcd init, just from the pxafb driver, and I was using mostly htcapache code |
| 20:44.16 | pH5 | drasar: I don't know. I'm sure you'll notice ;) |
| 20:44.25 | no2chem2 | first byte is address (group) and second byte is mode |
| 20:44.27 | tmzt_mp900c_ | that was to cr2, |
| 20:44.31 | drasar | pH5: OK :) |
| 20:44.42 | no2chem2 | actually no; |
| 20:44.44 | no2chem2 | pInBuf[2] = (m_setting); |
| 20:44.44 | no2chem2 | pInBuf[0] = (m_mode); |
| 20:45.08 | *** join/#htc-linux dwaradzyn (n=gudz666@damian8155.net.autocom.pl) |
| 20:45.18 | no2chem2 | if you figure out how to control the leds via cpld or whatever; let me know |
| 20:45.33 | no2chem2 | the ledmgr dll is kind of weak |
| 20:45.35 | cr2 | no2chem2: it's already documented for kaiser. |
| 20:45.39 | no2chem2 | oh |
| 20:45.49 | no2chem2 | how is it controlled? |
| 20:46.03 | cr2 | no2chem2: but it's very device-specific to manipulate the cpld |
| 20:46.13 | cr2 | no2chem2: set_gpio |
| 20:46.30 | cr2 | i'm looking for a link. |
| 20:46.31 | no2chem2 | that doesn't seem to work on the titan though; |
| 20:46.46 | *** join/#htc-linux CoKeSERO (n=me@pool-96-249-151-134.hrbgpa.fios.verizon.net) |
| 20:47.15 | cr2 | no2chem2: titan cpld is at another address. and the gpio numbers may differ. |
| 20:47.27 | dcordes_ | http://wiki.xda-developers.com/index.php?pagename=Kaiser_CPLD ? |
| 20:47.29 | no2chem2 | well, i never got watch gpios working |
| 20:47.41 | no2chem2 | i have the hw switch working though =p |
| 20:47.49 | drasar | pH5: Need I "Support for Host-side USB" compiled into a kernel? |
| 20:48.11 | cr2 | no2chem2: mmutrace is better (more reliable). the cpld gpios are sometimes write-only |
| 20:48.42 | no2chem2 | oh |
| 20:48.44 | no2chem2 | hnm |
| 20:48.51 | cr2 | dcordes_: yes. |
| 20:48.55 | no2chem2 | anyway so , on the kaiser according to this |
| 20:49.21 | pH5 | drasar: no. pxa25x don't have a USB host controller |
| 20:49.38 | no2chem2 | if i SetKMode(TRUE); then write FF to CPLD + GPIOA6, I should get some led activity yes? |
| 20:49.42 | drasar | pH5: ok |
| 20:49.57 | tmzt_mp900c_ | theres on in the data sheet on 27x, if I can remember correctly |
| 20:50.11 | cr2 | no2chem2: you should do 'orr' with a bitmask. |
| 20:50.30 | cr2 | no2chem2: afair the kaiser cpld is not write-only. but i'm not 100% sure. |
| 20:50.45 | no2chem2 | well, for example, titan cpld is readable |
| 20:50.49 | no2chem2 | let me give you example |
| 20:51.18 | dcordes_ | can somebody hint me on what the fbset geometry parameters signify? <xres> <yres> <vxres> <vyres> <depth> |
| 20:51.31 | no2chem2 | #define ADDRESS_WIFISWITCH_REGISTER0xBA00000A |
| 20:51.34 | dcordes_ | xres yres are pretty obvious but what's vxres vyres? |
| 20:51.36 | cr2 | no2chem2: i'll check my files on titan. |
| 20:51.43 | tmzt_mp900c_ | virtual? |
| 20:51.57 | no2chem2 | bKModePrevious = SetKMode(TRUE); |
| 20:51.57 | no2chem2 | RegisterStatus = (BYTE*) WiFiSwitchRegister; |
| 20:51.57 | no2chem2 | WiFiStatus = !((*RegisterStatus & 0x40) >> 6); |
| 20:51.57 | no2chem2 | SetKMode(bKModePrevious); |
| 20:52.09 | no2chem2 | will get you the status of the wifi switch |
| 20:52.16 | cr2 | no2chem2: ok. |
| 20:52.33 | no2chem2 | but yeah, i notice strange behavior when i read/write cpld |
| 20:53.03 | dcordes_ | no2chem2: fwif, you can browser the kaiser cpld code http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=tree;h=43abb4b319926c1dff1be8379e4e688ac9df1bcd;hb=43abb4b319926c1dff1be8379e4e688ac9df1bcd |
| 20:53.10 | no2chem2 | the data abort then, it is coming from A9? |
| 20:53.12 | no2chem2 | oops.. |
| 20:53.13 | tmzt_mp900c_ | udc is usually connected to otg isn't it? |
| 20:53.16 | cr2 | no2chem2: let me check. |
| 20:53.37 | cr2 | no2chem2: it's better to ioremap the cpld to your own process. |
| 20:53.47 | no2chem2 | ah |
| 20:54.23 | no2chem2 | you mean virtualcopy? |
| 20:54.27 | no2chem2 | (in ce). |
| 20:54.39 | cr2 | yes |
| 20:54.47 | cr2 | alloc+copy |
| 20:55.02 | no2chem2 | hmm |
| 20:55.07 | no2chem2 | yeah i guess ill try that |
| 20:56.01 | tmzt_mp900c_ | man fbset says visible res (xres/yres), virtual res (vxres/xyres), depth bits per pixel |
| 20:56.16 | tmzt_mp900c_ | visual and virtual should usually match |
| 20:56.51 | cr2 | no2chem2: 41444, 41178 have some cpld status data |
| 20:57.21 | cr2 | no2chem2: cpld is readable on titan. |
| 20:57.33 | cr2 | just a usual ldrh |
| 20:58.12 | cr2 | no2chem2: the +0xa reg should have some led-related data in lower 2 bits. |
| 20:58.23 | no2chem2 | hmm |
| 20:58.43 | no2chem2 | so i should be able to TST or ORR them |
| 20:59.02 | dcordes_ | tmzt_mp900c_: oh should have looked close. they do not match here in my current settings on kaiser |
| 20:59.10 | cr2 | 41420, 41422, 41424 are cpld shadow areas. |
| 20:59.19 | dcordes_ | tmzt_mp900c_: they are 240 320 240 640 16 |
| 20:59.25 | cr2 | no2chem2: yes. after you'll remap the data. |
| 20:59.31 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfcd7a.pool.einsundeins.de) |
| 21:00.08 | tmzt_mp900c_ | set vyres to match yres with fbset, or is that the swap mechanism used by android/mdp? |
| 21:00.44 | tmzt_mp900c_ | is there a special swap ioctl on fb in android kernel? |
| 21:00.52 | cr2 | no2chem2: i've located orr_cpld and bic_cpld functions. |
| 21:00.53 | dcordes_ | tmzt_mp900c_: I don't cope with android at all. I'm on the X thing still |
| 21:01.12 | no2chem2 | orr_cpld and bic_cpld? |
| 21:01.12 | no2chem2 | where? |
| 21:01.12 | tmzt_mp900c_ | I know, but this kernel was from android tree, right? |
| 21:01.56 | dcordes_ | right.. don't know if it has such mecahnisms. I don't care if it breaks android if that's your point |
| 21:02.04 | cr2 | no2chem2: in allledmgr |
| 21:02.27 | tmzt_mp900c_ | no, I'm just wondering if that is why it is sending that value, meaning that two qvga screens are mapped in memory |
| 21:02.28 | cr2 | 0x41120-30 is the cpld shadow bit copy. |
| 21:02.42 | dcordes_ | tmzt_mp900c_: where would I look to figure that out? |
| 21:03.12 | no2chem2 | ah |
| 21:03.15 | cr2 | no2chem2: but the msm7500 gpio functions are also there. so some bits may be on the msm. |
| 21:03.51 | no2chem2 | yeah; i recall orring lower CPLDA bits didn't do anything |
| 21:04.12 | cr2 | no2chem2: i can tell you which cpld bits are led-related. |
| 21:04.49 | cr2 | ox4b and 0x51 . looks like msm gpio numbers. |
| 21:04.49 | no2chem2 | which ones? |
| 21:04.55 | cr2 | looking. |
| 21:05.38 | cr2 | 2,8 |
| 21:05.41 | cr2 | 2,0x10 |
| 21:05.55 | cr2 | 2,0x20 |
| 21:06.04 | cr2 | 2,0x40 |
| 21:06.54 | no2chem2 | hmm |
| 21:06.58 | no2chem2 | ok, guess ill play with that |
| 21:07.01 | cr2 | setkeypadbacklight |
| 21:07.39 | cr2 | 2,0x1 |
| 21:08.03 | no2chem2 | 2 = group 2? |
| 21:08.48 | cr2 | no2chem2: yes. the whole bank2 is led gpios. |
| 21:09.02 | cr2 | 2,2 and 2,4 too |
| 21:09.21 | no2chem2 | ah, cool |
| 21:09.54 | cr2 | no2chem2: backlightautosense is 6,4 |
| 21:10.14 | cr2 | get_cpld(6,4) |
| 21:10.24 | tmzt_mp900c_ | dcordes: Xfbdev was looking for dbus/something in that strace you set me |
| 21:10.31 | tmzt_mp900c_ | but I don't have it anymore |
| 21:10.57 | tmzt_mp900c_ | what suggest that it is hal, input-hotplug |
| 21:11.19 | cr2 | no2chem2: 0x51 and 0x4b (msm gpios) are Fnshiftled-related. whatever that is :) |
| 21:11.30 | dcordes_ | tmzt_mp900c_: hold up I'm trying to save those -g mode |
| 21:11.47 | cr2 | no2chem2: 0x51 is Fnshiftled control. |
| 21:12.17 | no2chem2 | hm |
| 21:12.33 | no2chem2 | im guessing it is the msm letting cpld to know if shift is on =/ |
| 21:12.39 | cr2 | the gpio_mode is 2. need to check with kaiser_gpio wiki |
| 21:13.02 | cr2 | no2chem2: i think it's the direct gpio led control. without cpld. |
| 21:14.42 | no2chem2 | see- i am fairly uh, unfamiliar with cpld except that it has some things i need |
| 21:14.54 | no2chem2 | as i understand; cpld offloads gpios from msm, yes? |
| 21:15.10 | cr2 | no2chem2: yes. these are extra gpios. |
| 21:15.19 | cr2 | no2chem2: 2,0x80 is qkey. |
| 21:16.01 | cr2 | ok 6,4 is lightsensor. |
| 21:16.09 | cr2 | day/night |
| 21:16.59 | cr2 | some weird mddi stuff is there too. |
| 21:17.13 | cr2 | probably for the lcd backlight or so. |
| 21:17.57 | cr2 | yes, that's all. |
| 21:18.07 | cr2 | time to create a wiki page. |
| 21:19.07 | dcordes_ | tmzt_mp900c_: I do not get how I save those modes, I did fbset 240 320 240 320 16. when I run fbset -i afterwards, it still shows the old value. where does the old value come from? |
| 21:19.15 | no2chem2 | ah, yeah |
| 21:19.35 | no2chem2 | mddi is probably for backlight, allledmgr controls backlight as well. |
| 21:19.51 | cr2 | no2chem2: ok, now i see the ioctl numbers too. |
| 21:20.19 | cr2 | vibra is on DEX1: ? |
| 21:20.33 | cr2 | it seems the arm9 takes care of it. |
| 21:22.00 | drasar | pH5: So still no usb event on PC :( |
| 21:22.27 | drasar | pH5: Here are new logs: http://www.stud.fit.vutbr.cz/~xmichl07/temp/himalaya/ |
| 21:23.06 | pH5 | drasar: I've just stumbled across something (again) - could it be that the PUEN gpio is wrong? |
| 21:23.21 | pH5 | right now you are using asic3 GPIOA3 |
| 21:23.39 | pH5 | but in -gpio.h there's also a definition for PXA GPIO60 |
| 21:24.20 | pH5 | can you check in the xanadux kernel, I think pxa GPIO60 is the correct one |
| 21:24.34 | *** join/#htc-linux tmzt_mp900c_ (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 21:28.03 | drasar | pH5: Is it himalaya-gpio.h in xanadux kernel? |
| 21:28.20 | cr2 | pH5: somebody probably copied too much from ba on hima. |
| 21:28.27 | pH5 | drasar: look at the himalaya_udc.c code |
| 21:28.39 | pH5 | cr2: right, we had that issue already some time ago, right? |
| 21:28.43 | cr2 | drasar: i'll check the puen RSN. |
| 21:28.45 | pH5 | I forget all the time. |
| 21:28.49 | cr2 | yeah. |
| 21:29.16 | cr2 | so wiki and the code drifted away. now it's too late to rememeber. |
| 21:29.32 | no2chem2 | yes, vibra is on DEX1:... |
| 21:29.48 | pH5 | I'm going to pull the himalaya changes into my 2.6.26 tree when that is cleared up. |
| 21:29.53 | no2chem2 | i have no idea why a9 takes care of that, and I haven't been able to control it |
| 21:30.06 | no2chem2 | (i wanted to control the strength of vibrate) |
| 21:30.50 | cr2 | pH5: nice. do you have asic3-mmc working ? |
| 21:31.13 | pH5 | cr2: no, that's the big stumbling block for hx and blueangel, too. |
| 21:31.14 | cr2 | pH5: apart from asic5, hima is BA with different gpios. |
| 21:31.20 | cr2 | ok. |
| 21:32.04 | cr2 | pH5: i think hima backpack on asic5 is too much PITA, but the asic5 uart may be decoded (bluetooth) |
| 21:33.20 | drasar | pH5: There is no himalaya_udc.c file in xanadux tree |
| 21:33.21 | pH5 | cr2: agreed |
| 21:33.53 | pH5 | drasar: is it in the main himalaya.c file? the udc_command function has to be defined somewhere. |
| 21:33.59 | cr2 | pH5: you have seen the grmn's ti2200 driver ? |
| 21:34.19 | pH5 | drasar: otoh you're right, looking at -gpio.h might be good enough. if you have gpio 60 as PUEN there, chances are good that this is correct :) |
| 21:34.28 | *** join/#htc-linux pronto (n=pronto@pool-71-179-232-167.bltmmd.fios.verizon.net) |
| 21:34.48 | pH5 | .zZ |
| 21:34.50 | pH5 | good night |
| 21:35.01 | cr2 | drasar: but check it with BA -gpio.h |
| 21:35.13 | drasar | pH5: Yes, himalaya_udc_command() is in himalaya.c |
| 21:35.22 | *** join/#htc-linux tmzt_mp900c (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 21:37.01 | *** join/#htc-linux pronto (n=pronto@pool-71-179-232-167.bltmmd.fios.verizon.net) |
| 21:38.15 | pigeon | is the kernel tree at xanadux.cvs.sourceforge.net the one that's being developed for the htc phones? |
| 21:38.54 | pigeon | (linux-2.6-xda) |
| 21:38.55 | drasar | pH5: What should I looking for in that function? Sorry, but I don't know what "gpio 60 as PUEN" means :( |
| 21:40.30 | cr2 | pigeon: hh.org should be better |
| 21:40.56 | cr2 | pigeon: i've edited wallaby wiki a bit. unfortunately i've removed the rom ;) |
| 21:41.43 | pigeon | cr2: do you need the rom btw? :) |
| 21:41.54 | *** join/#htc-linux lamikr (n=chatzill@78.84.154.115) |
| 21:42.28 | pigeon | cr2: so, the one at http://handhelds.org/cgi-bin/cvsweb.cgi/linux/kernel26/ ? |
| 21:43.03 | tmzt_mp900c | dcordes: do you see installing ?? panel in dmesg, can you give me the values (its KERN_INFO so I'm not sure you will see it) |
| 21:43.30 | cr2 | pigeon: yes. all your patches will be merged :) |
| 21:44.26 | dcordes_ | tmzt_mp900c: I just noticed a hal error after killing Xfbdev |
| 21:44.57 | dcordes_ | tmzt_mp900c: not quite sure what you mean. grep for panel? |
| 21:45.09 | tmzt_mp900c | yres_virtual = pi->height*2 in android-msm msbfb |
| 21:45.34 | tmzt_mp900c | grep installing |
| 21:45.42 | drasar | cr2: "gpio 60 as PUEN" -- what does it means please? |
| 21:45.47 | tmzt_mp900c | do you have hal running |
| 21:45.59 | tmzt_mp900c | I think you need an fdi |
| 21:46.06 | dcordes_ | fdi? |
| 21:46.12 | tmzt_mp900c | pullup enable |
| 21:46.31 | tmzt_mp900c | fdi is the xml files used by hal |
| 21:46.35 | dcordes_ | ook |
| 21:46.41 | cr2 | drasar: i'm checking now. |
| 21:46.53 | *** join/#htc-linux LanceHaig (n=LanceHai@foresight/member/lhaig) |
| 21:46.55 | tmzt_mp900c | you need one for the event device, so that it shows up in Xfbdev |
| 21:47.09 | tmzt_mp900c | do you have lshal? |
| 21:47.46 | dcordes_ | no lshal |
| 21:47.56 | tmzt_mp900c | but this would seem to bypass tslib, so I am confused again |
| 21:48.16 | *** join/#htc-linux lamikr (n=chatzill@78.84.154.115) |
| 21:48.42 | tmzt_mp900c | who did you ask in xorg earlier |
| 21:49.08 | lamikr | cr2 ping |
| 21:49.33 | cr2 | hi lamikr |
| 21:49.45 | dcordes_ | tmzt_mp900c: I asked public |
| 21:49.53 | cr2 | lamikr: are you back home ? we are hacking on hima with drasar now. |
| 21:49.53 | tmzt_mp900c | anyone answer? |
| 21:50.51 | cr2 | drasar: GPIO_NR_HIMALAYA_USB_PULLUP_N |
| 21:51.08 | dcordes_ | tmzt_mp900c: no response |
| 21:51.26 | cr2 | GPIO 60 10000000 USB Power, 0 = on, 1 = off |
| 21:52.11 | cr2 | drasar: you should set this gpio instead of asic3 gpio in udc_enable |
| 21:52.57 | dcordes_ | tmzt_mp900c: here's the hal error at the very end of Xfbdev output: "[config/hal] couldn't initialise context: (null) (null)" <- that doesn't sound too good |
| 21:53.05 | tmzt_mp900c | dcordes: does the bb for xfbdev mention x.org as a source |
| 21:53.31 | dcordes_ | tmzt_mp900c: let me see |
| 21:54.04 | cr2 | pigeon: http://www.handhelds.org/moin/moin.cgi/HTCWallaby |
| 21:54.25 | cr2 | pigeon: i think that's the latest status. but some things may be obsolete. |
| 21:54.53 | pigeon | cr2: yeah, a lot of things on hh.org have been like that... :\ |
| 21:54.57 | cr2 | ~ping Kevin2 |
| 21:54.58 | apt | pong Kevin2 |
| 21:55.26 | cr2 | pigeon: we should also make a closer look at asic1 and asic2. |
| 21:56.02 | pigeon | i didn't know 2.6 is already working though. back to few years ago i was only playing with 2.4 |
| 21:56.30 | cr2 | drasar: i can modify the current himalaya_udc.c, but since you do it ba-way, i'll not do it. |
| 21:56.34 | pigeon | just for fun i built a kernel straight from angstrom for the htcwallaby machine and it didn't boot very well. |
| 21:56.56 | cr2 | pigeon: i think 2.6 described at hh.org wiki was working. |
| 21:57.05 | dcordes_ | tmzt_mp900c: do you have any clue how I can save those geometry settings? |
| 21:57.09 | pigeon | or at least, the linux framebuffer isn't working, and i don't see any booting messages on the serial console. |
| 21:57.13 | cr2 | pigeon: but afair it misses suspend/resume and power control. |
| 21:57.50 | cr2 | pigeon: check the binary distro mentioned in wiki. then we can pick the CVS tag. |
| 22:00.02 | *** join/#htc-linux tmzt_mp930c (n=tmzt@adsl-70-228-87-174.dsl.akrnoh.ameritech.net) |
| 22:00.04 | dcordes_ | tmzt_mp900c: there is definetly xorg references in the bitbake |
| 22:04.39 | drasar | cr2: So in himalaya_udc.c file in himalaya_udc_command() on PXA2XX_UDC_CMD_CONNECT should I set asic3_gpio_set_value(asic3_dev, GPIO_NR_HIMALAYA_USB_PULLUP_N , 0) instead of asic3_gpio_set_value(asic3_dev, GPIO_USB_PUEN, 0), right? |
| 22:07.02 | cr2 | drasar: without asic3_ |
| 22:07.10 | cr2 | drasar: gpio_set_value(asic3_dev, GPIO_NR_HIMALAYA_USB_PULLUP_N , 0) |
| 22:07.20 | cr2 | heh |
| 22:07.27 | cr2 | gpio_set_value(GPIO_NR_HIMALAYA_USB_PULLUP_N , 0) |
| 22:07.41 | cr2 | because it's a pxa gpio. |
| 22:09.33 | drasar | crt2: ok, and on PXA2XX_UDC_CMD_DISCONNECT gpio_set_value(GPIO_NR_HIMALAYA_USB_PULLUP_N , 1), right? |
| 22:10.36 | lamikr | cr2 No I am not yet at home, will be on sunday. I will still have next week holliday. |
| 22:13.44 | drasar | cr2: Anything else to modify? |
| 22:13.52 | lamikr | cr2 dsasar So you will are building the kernel for himalaya? |
| 22:13.56 | cr2 | lamikr: ok. |
| 22:14.08 | cr2 | drasar: check this one first. |
| 22:14.26 | cr2 | lamikr: yes, the usb for himalaya. |
| 22:15.49 | pigeon | i wish there's a tree in git i could just use |
| 22:17.59 | lamikr | cr2 To get the nfs boot over usb to work? |
| 22:18.50 | cr2 | lamikr: no, to login over usb |
| 22:19.02 | cr2 | lamikr: the root on SD works anyway. |
| 22:19.46 | lamikr | ok, anyway just to get the tcp/ip & udp working over usb. |
| 22:21.12 | cr2 | yes# |
| 22:24.37 | drasar | cr2: no change :( |
| 22:26.49 | cr2 | drasar: change 0 to 1. |
| 22:27.06 | cr2 | and 1 to 0 |
| 22:27.12 | drasar | cr2: There is no message about "_udc_control: (dis)connect" |
| 22:27.26 | drasar | cr2: ok |
| 22:27.59 | cr2 | drasar: strange, then it's something else |
| 22:28.32 | drasar | cr2: I continuously updating logs at: http://www.stud.fit.vutbr.cz/~xmichl07/temp/himalaya/ |
| 22:28.40 | drasar | cr2: you can check it |
| 22:30.31 | drasar | cr2: really strange, because the only change that I have made is in gpio_set_value() |
| 22:37.54 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 22:46.55 | *** join/#htc-linux Othello_ (i=Magorium@gateway/tor/x-393eb85956af47cb) |
| 22:52.13 | tmzt_mp900c | dcordes: did I miss an answer in xorg by any chance, I can't seem to scrollback |
| 22:54.10 | dcordes_ | tmzt_mp900c: yes, there is xorg sources being referenced in the kdrive metadata |
| 22:56.05 | tmzt_mp900c | can I have that line |
| 23:00.31 | dcordes_ | tmzt_mp900c: SRC_URI = "${XORG_MIRROR}/individual/xserver/xorg-server-${PV}.tar.bz2 \ |
| 23:00.45 | tmzt_mp900c | and pv |
| 23:01.06 | dcordes_ | 1.4.0.90 |
| 23:01.24 | dcordes_ | tmzt_mp900c: SRC_URI = "${XORG_MIRROR}/individual/xserver/xorg-server-${PV}.tar.bz2 \ |
| 23:02.26 | tmzt_mp900c | $PV would be set by bitbake, or is it in the bb |
| 23:02.49 | dcordes_ | no it is set by bitbake it's package version let me give you the full url |
| 23:07.50 | dcordes_ | tmzt_mp900c: http://xorg.freedesktop.org/releases/individual/xserver/xorg-server-1.4.0.90.tar.bz2 |
| 23:10.29 | marajin | 'lo there |
| 23:22.00 | CPress | Hey guys |
| 23:23.49 | *** join/#htc-linux dcordes__ (n=dcordes@f049002169.adsl.alicedsl.de) |
| 23:28.55 | *** join/#htc-linux dzo (n=dzo@121.98.128.127) |
| 23:31.27 | dcordes__ | tmzt_mp900c: when I try to understand the error messages, it comes to my mind that the cursor position 'updates' which are by Xfbdev being recognized as wrong, are just in a wrong order. they always have a zero at the beginning in the Invalid update: errors. it is this order: zero pressure 320 some_changing_value |
| 23:33.40 | dcordes__ | and the hal error at the end just fits in "[config/hal] couldn't initialise context: (null) (null)" probably that is the fisrt value that stays zero all the time plus the pressure which is 0 at the end |
| 23:34.38 | marajin | hey CPress |
| 23:34.41 | marajin | dcordes__: Hello |
| 23:35.13 | wasup | is everyone still talking about the diamond? |
| 23:35.24 | dzo | hi all, i'm just trying to get rpc working on vogue, it's fairly similar to android-msm but doesn't do any routing, and obviously codes are different. If I can get it working that should open up lots of exciting things and adsp should work. |
| 23:35.54 | wasup | sounds good...:) |
| 23:36.07 | dcordes__ | marajin: hi |
| 23:36.21 | dzo | i bet it's the same for kaiser too. |
| 23:36.44 | wasup | and hopefully the titan? |
| 23:36.51 | dcordes__ | that's great news dzo |
| 23:36.54 | wasup | Remote procedure call (RPC) is an Inter-process communication technology that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. That is, the programmer would write essentially the same code whether the subroutine is local to the executing program, or remote. When the software in q |
| 23:36.56 | dzo | almost certainly |
| 23:37.03 | wasup | thats good |
| 23:37.04 | dcordes__ | wasup: thanks ;) |
| 23:37.23 | dcordes__ | dzo: why do you think that it is the same on vogue/kaiser/titan? |
| 23:37.28 | wasup | well i was gonna ask but i thought i was gonna sound stupid... so i googled it |
| 23:37.38 | dcordes__ | I didn't know it either |
| 23:38.18 | wasup | oh... i feel better now |
| 23:38.21 | wasup | ;) |
| 23:38.26 | dcordes__ | :p |
| 23:39.02 | dcordes__ | wasup: how's titan keyboard? |
| 23:39.22 | dzo | RPC is really the main interface to the radio, proc_comm is just something extra i think. |
| 23:39.22 | wasup | was it released? |
| 23:40.06 | dcordes__ | wasup: hm? I mean the titan keybaord code ginge wrote |
| 23:41.14 | wasup | idk... last i checked... he gave me the newest zImage.. and some of the keys were doing stuff.. but the gpios (i think thats what it is) data i gave him he was gonna put in a speadsheet. |
| 23:41.23 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 23:41.26 | wasup | he said it was a little different or something... then he went to bed |
| 23:44.33 | dcordes__ | ok so nothing new. best will be to put them into wiki.xda-developers.com/TitanGPIO |
| 23:45.13 | dcordes__ | dzo: do the mechanisms for setting up the extusb in your latest patch work already? |
| 23:45.24 | dcordes__ | AudioParams at the very beginning |
| 23:46.41 | dzo | No Idea, those parameters are for a proc comm call, I found them in the wince image. |
| 23:47.05 | dzo | i think it just determines how audio is routed. |
| 23:49.24 | dcordes__ | I see. does usb work at all yet on the vogue? I mean can you initialize it? |
| 23:50.52 | dzo | no, usb is very different to msm7x00a, I think its a transdimension part but don't know which one or how to get docs for it. It will be really tedious to reverse engineer. |
| 23:54.24 | dcordes__ | dzo: any chance to output audio out of it in future? |
| 23:55.23 | dzo | how do you mean, I don't think the headset has anything to do with usb. |
| 23:55.49 | marajin | I think the headset is just pretty much wired via their extusb plug, it's not really related to USB |
| 23:55.54 | dcordes__ | ok. I fear I have a wrong understanding of how the headset works then |
| 23:55.56 | tmzt_mp900c | extusb, the additonal pins on the usb connecter? |
| 23:56.22 | dcordes__ | so that's what extusb is about.. |
| 23:56.58 | marajin | dcordes__: It's just minib with er 4? extra pins for Stereo out and microphone in |
| 23:57.28 | marajin | there's nothing at all in the hermes' headset apart from wiring a pair of headphones into the right pins on the connector |
| 23:57.32 | dcordes__ | quite obvious when I compre the headphone connector and a normal mini b |
| 23:57.37 | dzo | headset should work with those audio params then i guess, the proc_comm may be different though. |
| 23:57.59 | dcordes__ | dzo: can you tell me where in wince you got the audio parm regs? |
| 23:58.04 | dcordes__ | I'd like to find them for kaiser |
| 23:58.14 | marajin | I always figured it just switched the audio redirection on a jacksense |
| 23:59.16 | dzo | They were in a file called AudioParam.csv in the windows directory i think. |
| 23:59.49 | dcordes__ | ok thanks |