| 00:22.06 | *** join/#htc-linux mistadman (n=mistadma@adsl-156-124-48.msy.bellsouth.net) |
| 00:39.07 | AstainHellbring | hi jasta |
| 00:43.11 | *** join/#htc-linux aLeSD (n=alex@80.31.100.159) |
| 00:49.20 | jasta | hello :) |
| 00:59.47 | *** join/#htc-linux the_sys0p (n=the_sys0@116.199.69.89) |
| 01:03.25 | *** join/#htc-linux lama_ (i=lama@netbsd.pl) |
| 01:26.45 | *** join/#htc-linux rainabba (n=rainabba@ip70-176-62-147.ph.ph.cox.net) |
| 01:28.58 | *** join/#htc-linux dan-htc-touch (n=IceChat7@S01060001023217c9.cg.shawcable.net) |
| 01:29.39 | *** join/#htc-linux dullard (n=jim@82.132.136.194) |
| 01:30.27 | dullard | says hello from his htc universal |
| 01:31.48 | dullard | Would anyone in here know anything about the inner workings of titchy mobile? |
| 01:33.52 | dullard | ...I think I lost my xserver in an apt-get upgrade and I have no idea where to find it again |
| 01:35.45 | rainabba | You talking xserver on an HTC phone? (new here) |
| 01:36.46 | tcccp | apropos |
| 01:37.03 | tcccp | I could try and see if the iPaq can have X easily |
| 01:41.59 | *** join/#htc-linux dullard_ (n=jim@82.132.136.199) |
| 01:44.04 | dullard_ | <-- running debian on htc universal |
| 01:44.55 | tcccp | Debian on HP iPaq hw6915 |
| 01:47.30 | dullard_ | tcccp: do you know whether there is a generic name for the xservers running on debian handhelds? I want to find out if the server is still on my machine... xdm is doing nothing |
| 01:48.11 | tcccp | erm..hu? |
| 01:48.18 | tcccp | The package name should be xserver-xorg |
| 01:51.38 | dullard | do you know what it would be called at the command line to do a quick check that it exists? |
| 01:55.05 | tcccp | uuh |
| 01:56.07 | tcccp | dpkg -s? |
| 01:58.59 | dullard | I mean hmmm... something like startx but the name of the actual xserver |
| 01:59.44 | tcccp | ls -l /usr/bin/X |
| 02:00.13 | dullard | is that generally a symlink? |
| 02:00.19 | tcccp | aye |
| 02:00.34 | dullard | aah my symlink is missing |
| 02:01.14 | dullard | what does yours link to? that may or may not give me a clue |
| 02:01.40 | tcccp | Xorg for example - same dir |
| 02:03.37 | dullard | wierd, I really think mine's gone missing. I don't know where. |
| 02:06.17 | tcccp | And I need to fire up my "development virtual machine" to have a new kernel |
| 02:27.18 | *** join/#htc-linux MHazem (n=GoD@82.201.174.159) |
| 04:21.15 | *** join/#htc-linux goxboxlive (n=goxboxli@195.159.97.196) |
| 04:58.16 | *** join/#htc-linux jasta (n=jasta@75-165-29-181.tukw.qwest.net) |
| 05:13.14 | *** join/#htc-linux mistadman (n=mistadma@adsl-156-124-48.msy.bellsouth.net) |
| 05:36.49 | *** join/#htc-linux Othello__ (i=Magorium@gateway/tor/x-6f614daf973d6f56) |
| 05:47.52 | *** join/#htc-linux kiozen (n=oeichler@p54929C12.dip0.t-ipconnect.de) |
| 05:51.28 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 05:57.22 | BabelO | hi |
| 05:57.45 | kiozen | BabelO: morning :), how many bugs left ? |
| 05:59.01 | BabelO | kiozen: it depend, we have immediat major flags, so it is only two remaining |
| 06:00.47 | *** join/#htc-linux rob_w (n=bob@Ma927.m.pppool.de) |
| 06:06.59 | kiozen | BabelO: wake up the beast in you and kill them :) |
| 06:07.21 | *** join/#htc-linux mistadman (n=mistadma@adsl-156-124-48.msy.bellsouth.net) |
| 06:09.27 | *** join/#htc-linux Marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 06:20.03 | BabelO | kiozen: i prefer working on GT, more interesting thing |
| 06:20.23 | mistadman | Hello. |
| 06:20.34 | BabelO | ok, going to work |
| 06:21.04 | kiozen | BabelO: lol, definetly |
| 06:21.24 | mistadman | Does anyone here have any experience with hacking the Linux kernel? |
| 06:22.13 | kiozen | mistadman: yes but they are either sleeping or working |
| 06:22.29 | mistadman | Crap. Thanks! |
| 06:42.51 | *** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo) |
| 07:11.39 | *** join/#htc-linux rob_w|laptop (n=rob@p549B91C8.dip0.t-ipconnect.de) |
| 07:14.46 | *** join/#htc-linux Babel1 (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
| 07:25.23 | *** join/#htc-linux MHazem (n=GoD@82.201.174.159) |
| 07:34.14 | *** join/#htc-linux the_sys0p (n=the_sys0@116.199.69.89) |
| 08:02.48 | *** join/#htc-linux MHazem (n=GoD@82.201.174.159) |
| 08:10.31 | *** join/#htc-linux Dindon (n=dinde@193.27.79.0) |
| 08:27.51 | *** join/#htc-linux LunohoD (n=alex@e180064036.adsl.alicedsl.de) |
| 09:27.00 | *** join/#htc-linux p3t3r__ (n=peter@wlan.net-you.de) |
| 11:08.44 | *** part/#htc-linux p3t3r__ (n=peter@wlan.net-you.de) |
| 11:36.41 | *** join/#htc-linux p3t3r__ (n=peter@wlan1.net-you.de) |
| 12:03.10 | *** join/#htc-linux goxboxlive (n=goxboxli@208.84-48-176.nextgentel.com) |
| 12:19.42 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 12:21.08 | dcordes | hi |
| 12:28.48 | dcordes | martin__: ping |
| 12:31.30 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 12:40.39 | martin__ | dcordes: pong |
| 12:41.34 | dcordes | martin__: any AT news :) ? |
| 12:42.11 | martin__ | dcordes: nope |
| 12:42.27 | martin__ | haven't implemented my brute force attack yet |
| 12:42.59 | martin__ | was hoping dzo might appear, i'm curious as to why he told you to change the ints to shorts. |
| 12:43.37 | dcordes | martin__: you could email him. He always helped kindly |
| 12:44.12 | *** part/#htc-linux p3t3r__ (n=peter@wlan1.net-you.de) |
| 12:46.07 | martin__ | dcordes: yeah, I will |
| 12:46.38 | martin__ | get anywhere with the serial delay stuff? |
| 12:46.58 | dcordes | not yet |
| 12:55.09 | *** join/#htc-linux bd2 (n=cbou@85.21.88.2) |
| 13:08.21 | *** join/#htc-linux bd2_ (n=cbou@85.21.88.2) |
| 14:10.15 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 14:26.26 | *** join/#htc-linux no2chem|2 (n=no2chem@ip70-187-171-149.oc.oc.cox.net) |
| 14:42.44 | *** join/#htc-linux aLeSD (n=alex@80.31.100.159) |
| 15:05.24 | *** join/#htc-linux BabelO (n=Fabrice@unaffiliated/babelo) [NETSPLIT VICTIM] |
| 15:05.45 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 15:06.02 | *** join/#htc-linux TimRiker (n=timr@70-1-14-72.area1.spcsdns.net) |
| 15:14.03 | *** join/#htc-linux Othello (i=Magorium@gateway/tor/x-c4764ebbc0aeeaec) |
| 15:19.26 | *** join/#htc-linux Othello__ (i=Magorium@gateway/tor/x-24a00a26e7f85551) |
| 15:51.37 | *** join/#htc-linux rob_w (n=bob@M868b.m.pppool.de) |
| 16:03.45 | *** join/#htc-linux JohnnyK (n=johnnyk@nfx-nat-229.pilsfree.net) |
| 16:07.43 | *** join/#htc-linux TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
| 16:08.29 | *** join/#htc-linux miknix (n=miknix@81.193.82.67) |
| 16:12.41 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 16:53.19 | *** join/#htc-linux tsdogs (n=tsdogs@195.32.71.229) |
| 16:54.39 | tsdogs | LOL - ftp://ftp.trolltech.com/qtopia/README_QTOPIA_GPL.txt |
| 17:00.01 | *** join/#htc-linux AttractiveApe (n=phil@office.gossamer-threads.com) |
| 17:05.27 | jasta | anyone here familiar with HaRET? i need to know how to access the booting kernels output for debugging purposes. |
| 17:06.15 | jasta | trying to enable USB on the HTC Vogue (running the Android kernel), but thus far I'm being stopped blind with what seems to be a kernel panic. |
| 17:15.46 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 17:23.56 | *** join/#htc-linux Robwoerle (n=bob@X0247.x.pppool.de) |
| 17:30.39 | *** join/#htc-linux pikapika (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 17:30.51 | pikapika | hi |
| 17:57.56 | *** join/#htc-linux Marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 18:26.26 | *** join/#htc-linux diogene31_ (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
| 18:44.50 | *** join/#htc-linux paulproteus (n=paulprot@wide-rose.makesad.us) |
| 18:49.40 | goxboxlive | http://trolltech.com/qtopia-note |
| 18:53.03 | *** join/#htc-linux AstainZZZZZZ (n=Administ@unaffiliated/astainhellbring) |
| 19:04.19 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 19:10.43 | *** join/#htc-linux pH5 (n=ph5@e178192142.adsl.alicedsl.de) |
| 19:35.06 | *** join/#htc-linux tsdogs (n=tsdogs@62.123.180.130) |
| 19:52.55 | *** join/#htc-linux LunohoD_ (n=alex@e180073208.adsl.alicedsl.de) |
| 20:02.32 | *** join/#htc-linux kiozen (n=kiozen@rgnb-4db1da28.pool.einsundeins.de) |
| 20:03.51 | kiozen | hi |
| 20:16.06 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
| 20:21.25 | martin__ | dcordes: I think I may have found another smd channel |
| 20:22.01 | martin__ | look in your smem5 dump around 8220 |
| 20:22.29 | martin__ | looks like just a data channel of some kind |
| 20:22.46 | jasta | does anyone have any tips on how i might go about introducing USB support to the HTC Vogue (MSM7500, with I believe a driver present in the android-msm kernel tree) |
| 20:22.50 | jasta | ? |
| 20:23.25 | martin__ | jasta: have you talked to dzo about it? |
| 20:24.10 | jasta | yeah, but he is very busy and i feel bad bugging him about all my minutia. i'm unfamiliar with haret and kernel dev in general, and am just looking for some direction to get started with my exploration. |
| 20:24.47 | martin__ | hmm |
| 20:25.17 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 20:25.23 | jasta | for example, how can i access printk output? |
| 20:25.36 | martin__ | normally by seeing it on the framebuffer |
| 20:25.50 | martin__ | if it's working :) |
| 20:26.13 | jasta | but it appears only briefly when booting Android |
| 20:26.23 | martin__ | don't boot android, then. :) |
| 20:26.40 | jasta | well, that would be too obvious of course. |
| 20:26.46 | jasta | hehe |
| 20:26.52 | martin__ | i use a simple image that just boots to a shell |
| 20:26.59 | martin__ | on kaiser |
| 20:27.06 | martin__ | which i got off dcordes |
| 20:27.08 | jasta | i am embarrassed i didn't think to do that :) |
| 20:28.12 | martin__ | the one i'm using is from here: http://linuxtogo.org/~lgorris/images/ |
| 20:28.19 | jasta | can i have what you have prepared already? would be easier than creating my own simple initrd |
| 20:28.23 | jasta | ahh, thanks. |
| 20:28.38 | martin__ | i don't know for sure if that will work on the vogue but i think it should do. |
| 20:28.57 | jasta | dzo wrote a soft keyboard driver as well, which i for some reason assumed was part of android and not the kernel image. |
| 20:29.00 | jasta | so that should work all the same. |
| 20:29.46 | martin__ | oh, right, vogue doesn't have a keyboard |
| 20:30.11 | *** join/#htc-linux Marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 20:30.27 | martin__ | well, i dunno anything about that soft keyboard stuff |
| 20:30.30 | jasta | yes, but stil with the soft keyboard i could explore, even if very slowly. |
| 20:30.51 | jasta | dzo wrote it. it basically is just a hack on the framebuffer and touchscreen drivers. |
| 20:31.11 | martin__ | nice, so it draws the keyboard on the framebuffer directly? |
| 20:31.17 | jasta | ultimately i want USB up so i can access android's shell remotely and also the android log. |
| 20:31.28 | jasta | yeah, essentially as an overlay. |
| 20:31.58 | jasta | i've pined through the source code quite a bit, there just seems to be pieces that are quite magical to me, given that i have no experience developing on this sort of project. |
| 20:32.45 | martin__ | in some ways you might be best off finding a device linux already works well on |
| 20:32.58 | martin__ | and using that to play around with |
| 20:33.03 | martin__ | to get an idea of how things work |
| 20:33.34 | martin__ | e.g. putting debug messages in to help follow what happens as it starts up |
| 20:33.45 | jasta | well, i'm ultimately trying to work with Android and so only devices which have very similar processors will work |
| 20:33.51 | jasta | oh, i see what you mean |
| 20:33.53 | martin__ | or deliberately breaking things and seeing what happens |
| 20:34.14 | martin__ | there's good books on the kernel too that might help |
| 20:34.16 | jasta | what device would you recommend for that? |
| 20:35.09 | martin__ | one of the ipaqs maybe? |
| 20:35.27 | martin__ | or one of the older htc devices? |
| 20:35.47 | martin__ | but perhaps the best start is to read this: http://lwn.net/Kernel/LDD3/ |
| 20:37.28 | jasta | thanks, i will look through it. |
| 20:37.58 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 20:39.00 | martin__ | dcordes: another possible one at a240 |
| 20:46.42 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 21:06.22 | *** join/#htc-linux dcordes_ (n=dcordes@f049191162.adsl.alicedsl.de) |
| 21:09.08 | martin__ | dcordes: 36450 as well |
| 21:09.34 | martin__ | 38470 too |
| 21:10.33 | martin__ | 6a2a0 could be one too |
| 21:14.03 | dcordes_ | hi |
| 21:15.43 | dcordes_ | yes there are plenty. It should be 7 iirc |
| 21:17.29 | dcordes_ | martin__: 'brute forced' the at tx yet? |
| 21:17.50 | martin__ | dcordes: i don't get where the gps guess comes from, unless that address fills with gps stuff when the gps is used |
| 21:18.23 | dcordes_ | martin__: different dump |
| 21:18.27 | martin__ | k |
| 21:18.34 | dcordes_ | the one I sent has no gps activity |
| 21:18.40 | dcordes_ | let me see where I got it |
| 21:20.41 | *** join/#htc-linux pikapika_ (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 21:26.06 | dcordes_ | martin__: sent. so did you do that brute force code yet? |
| 21:26.41 | martin__ | no, i'm looking at the dumps to figure out how best to do it |
| 21:26.52 | martin__ | i'm not sure it'll really help with the at send stuff |
| 21:26.59 | martin__ | the location of that seems pretty clear |
| 21:27.19 | dcordes_ | you think correct how it is i the current state? |
| 21:27.35 | martin__ | i think it's more likely we're missing something about how to get the arm9 to read it |
| 21:27.57 | martin__ | i could try the head/tail swap i suppose |
| 21:28.09 | martin__ | i thought that was likely not right because it isn't needed on the vogue |
| 21:28.27 | martin__ | but then looking at the vogue addresses suggests the smem is a very different setup there |
| 21:28.47 | dcordes_ | martin__: if there is nothing to to notify the arm9 about reading in the vogue code, why would we do need it? |
| 21:29.19 | martin__ | the msm7500 might have made it automatic |
| 21:29.30 | martin__ | the smem setup is clearly different |
| 21:29.53 | dcordes_ | I see |
| 21:29.54 | martin__ | e.g. with the vogue all the heads and tails are together in one place |
| 21:30.29 | dcordes_ | so maybe we really need to throw an irq? |
| 21:33.31 | martin__ | possibly |
| 21:33.41 | martin__ | or we might need to write somewhere else |
| 21:34.09 | martin__ | there's a couple of stray bits set just before the heads and tails of the smd buffers |
| 21:34.18 | martin__ | they might be important |
| 21:35.57 | martin__ | but no idea what they're for or what they mean |
| 21:36.29 | dcordes_ | stray bits? can you give me a line number? |
| 21:36.42 | martin__ | well, look at 000041f0 |
| 21:36.51 | martin__ | 000041f0 02 00 00 00 00 01 00 00 00 00 00 00 df 1e 00 00 |................| |
| 21:36.55 | martin__ | 00004200 df 1e 00 00 00 00 00 00 40 53 59 53 54 45 4d 54 |........@SYSTEMT| |
| 21:37.25 | martin__ | you've got the 02 ... 01 ... then the head and tail, then the block |
| 21:37.45 | martin__ | now, search for 02 00 00 00 |
| 21:38.02 | martin__ | it comes up again at 8220 |
| 21:38.15 | martin__ | which also has what look like a head and tail |
| 21:38.39 | martin__ | but now there's more bits set: 02 00 00 00 01 01 01 00 |
| 21:39.04 | dcordes_ | maybe they identify the fifo? |
| 21:39.20 | martin__ | ah |
| 21:39.31 | martin__ | they're always 32-bit aligned |
| 21:39.49 | martin__ | so search for " 02 00 00 00" including the two spaces at the front |
| 21:40.02 | martin__ | you'll see all the smd locations |
| 21:40.23 | martin__ | and they've all either got: |
| 21:40.29 | martin__ | 02 00 00 00 00 01 00 00 |
| 21:40.42 | martin__ | 02 00 00 00 00 01 00 00 |
| 21:40.51 | martin__ | 02 00 00 00 01 01 01 00 |
| 21:40.53 | martin__ | sorry |
| 21:40.56 | martin__ | just the last two |
| 21:45.58 | dcordes_ | martin__: do you think we might need to write those bits with the send buffers? |
| 21:46.09 | martin__ | possibly |
| 21:47.03 | martin__ | i'll try printing out the state of those bits for the working smd |
| 21:47.20 | dcordes_ | I have no dump from the vogue but I believe somehow it looks similar there |
| 21:47.29 | martin__ | and maybe just wildly toggling them on the non-working one :) |
| 21:48.15 | martin__ | anyway |
| 21:48.18 | martin__ | got to go now |
| 21:48.29 | dcordes_ | ok cya |
| 21:49.03 | *** join/#htc-linux surgex (i=surge@pool-71-186-163-107.bflony.fios.verizon.net) |
| 22:21.00 | *** join/#htc-linux mistadman (n=mistadma@adsl-250-204-238.msy.bellsouth.net) |
| 22:55.59 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 23:07.55 | *** join/#htc-linux TimRiker (n=timr@rikers.org) |
| 23:09.34 | *** join/#htc-linux Marex (n=marex@vasut.kolej.mff.cuni.cz) |
| 23:57.45 | mistadman | PONG: anyone. |
| 23:59.43 | *** join/#htc-linux TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |