| 00:16.48 | *** join/#htc-linux surgex (i=surge@pool-71-186-163-107.bflony.fios.verizon.net) |
| 00:35.38 | *** join/#htc-linux AstainZZZZZZ (n=Administ@unaffiliated/astainhellbring) |
| 01:33.55 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 03:22.23 | *** join/#htc-linux MHazem (n=GoD@82.201.174.159) |
| 06:08.16 | *** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring) |
| 07:33.18 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfd5c5.pool.einsundeins.de) |
| 07:37.58 | *** join/#htc-linux goxboxlive (n=goxboxli@195.159.97.196) |
| 08:09.49 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfdb95.pool.einsundeins.de) |
| 08:13.10 | *** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net) |
| 09:17.50 | *** join/#htc-linux pH5 (n=ph5@e178252189.adsl.alicedsl.de) |
| 09:19.32 | *** join/#htc-linux mistadman (n=mistadma@adsl-156-124-48.msy.bellsouth.net) |
| 10:13.52 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfdb95.pool.einsundeins.de) |
| 11:07.45 | *** join/#htc-linux patoche (n=root@lns-bzn-55-82-255-130-5.adsl.proxad.net) |
| 11:07.58 | BabelO | hi patoche |
| 11:09.06 | *** join/#htc-linux pikapika (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 11:14.01 | pikapika | :) |
| 11:59.13 | *** join/#htc-linux diogene31_ (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
| 12:03.18 | *** join/#htc-linux pH5 (n=ph5@e178252189.adsl.alicedsl.de) |
| 12:27.15 | *** join/#htc-linux patoche (n=root@lns-bzn-27-82-248-29-181.adsl.proxad.net) |
| 12:27.33 | patoche | hi BabelO |
| 12:28.05 | patoche | how is going your artemis ? :) |
| 12:28.15 | BabelO | no more |
| 12:30.26 | *** join/#htc-linux kiozen (n=kiozen@rgnb-4db1dc47.pool.einsundeins.de) |
| 12:30.53 | kiozen | hi all |
| 12:31.05 | kiozen | BabelO: you broke your artemis? |
| 12:32.33 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
| 12:32.35 | BabelO | kiozen: nooo |
| 12:33.03 | BabelO | kiozen: but i can broke it if i did not found where battery monitor is :) |
| 12:33.41 | kiozen | BabelO: isn't that automatic in hw? |
| 12:34.37 | BabelO | kiozen: but there is a way to monitor mA and battery capacity |
| 12:34.46 | BabelO | kiozen: on bluenagel it is over w1 bus |
| 12:35.11 | kiozen | BabelO: ah, a bit like on the N560 |
| 12:35.41 | kiozen | no real monitoring, but at least some values to guess the condition |
| 12:43.16 | goxboxlive | my qtopia git tree is a mess. I have several conflicts |
| 12:43.20 | goxboxlive | hi btw |
| 12:45.26 | BabelO | hi goxboxlive |
| 13:10.42 | *** join/#htc-linux tsdogs_ (n=tsdogs@62.123.180.130) |
| 13:20.12 | *** join/#htc-linux LunohoD_ (n=alex@e180069082.adsl.alicedsl.de) |
| 13:27.10 | *** join/#htc-linux tsdogs (n=tsdogs@62.123.180.130) |
| 13:28.17 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 13:50.45 | *** join/#htc-linux andy_js (n=andy@AAmiens-152-1-27-107.w83-192.abo.wanadoo.fr) |
| 13:52.02 | *** join/#htc-linux ltxda0 (n=ltxda@unaffiliated/ltxda) |
| 13:53.10 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
| 13:54.59 | dcordes | hola |
| 13:58.07 | dcordes | martin__: I found the holy grail to fix kaiser booting issue: Check the latest haret version if that doesn't do, flash "duty's may 22nd rom" |
| 13:58.40 | dcordes | and use the latest haret. The combination makes it boot 100% here. Tried all kinds of initrds: Huge openmoko ones, angstrom-console, dzo's android |
| 13:59.38 | dcordes | all boot fine w/o any extra fiddling. You don't even need to softreset before. Unfortunately I didn't test on the stock rom so I can't tell if it is only haret updates or both, rom and haret. |
| 14:03.34 | dcordes | ow damn I forgot to commit the SD patches on initial commit |
| 14:06.41 | dcordes | hmm somebody put an ifdef around sdc3+4 in common.c |
| 14:07.26 | dcordes | ifndef |
| 14:08.00 | dcordes | ok so sdcc count is good |
| 14:08.22 | dcordes | now where did I set the regs |
| 14:11.50 | dcordes | martin__: did you notice the UART debug functions? |
| 14:12.06 | dcordes | maybe they could be of use for serial |
| 14:18.58 | pH5 | hi dcordes |
| 14:19.02 | pH5 | cr2_: asic3_mmc compiles now, I'm only missing the setup code in the asic3 core driver. |
| 14:19.09 | pH5 | I think next weekend I should be ready to submit asic3 gpio api + mmc patches for review. |
| 14:19.11 | pH5 | leds and clock api can come later. |
| 14:21.58 | dcordes | hej pH5 |
| 14:22.24 | dcordes | pH5: are you merging asic3_mmc upstream or is this new? |
| 14:25.26 | dcordes | can somebody explain a noob why there is clock.c and clock-7x00a.c in http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=tree;f=arch/arm/mach-msm;h=a5e1bc9367051e5beda59ad64859efc7fe64ef8f;hb=refs/heads/htc-msm ? |
| 14:26.12 | dcordes | Is clock.c built for all mach-msm boards and clock-7x00a.c only for 7x00a ones? |
| 14:32.04 | dcordes | also what is the difference between CLCK and PCLK? |
| 14:32.34 | pH5 | dcordes: nothing new, just updating asic3 and merging asic3_mmc |
| 14:33.02 | pH5 | dcordes: I didn't look in detail, but isn't clock.c the clock api code while clock-7x00a.c contains the actual clock definitions? |
| 14:33.02 | *** join/#htc-linux gundam (n=gundam@slackware.it/staff/gundam) |
| 14:35.57 | dcordes | pH5: ok :) |
| 14:36.51 | dcordes | I think sdc clock is even working. I remember when I first played around with sd I have seen those debug messages which said sdc had clock |
| 14:37.12 | dcordes | early after sdc init it said clock=0Hz then numbers showed up a second later |
| 14:37.20 | dcordes | but there were IRQ error messages |
| 14:37.31 | dcordes | I don't see either kernel messages anymore |
| 14:37.49 | dcordes | although I enabled mmc debug in the config |
| 14:39.05 | dcordes | ah of course that is the debug bit in msm_sdc.c |
| 14:40.15 | dcordes | #define MSMSDCC_DEBUG_DMA1 |
| 14:40.43 | dcordes | hm timeout debug was already switched on but I didn't see the timeout messages |
| 14:44.56 | dcordes | pH5: |
| 14:45.29 | Zoolooc | hi folks |
| 14:45.45 | Zoolooc | dcordes: are you at sd card support for kaiser? |
| 14:45.50 | dcordes | is the order of the different init lines in $BOARD_init significant? |
| 14:46.11 | dcordes | Zoolooc: I'm figuring out what I already did with it |
| 14:46.30 | dcordes | it was already doing something trying to get there again |
| 14:47.52 | Zoolooc | sounds good, wish you luck then, to get there sooner ;) |
| 14:49.35 | pH5 | dcordes: sure the order is important, at least for things that depend upon each other. |
| 14:50.23 | dcordes | ok I think the order is good though. kaiser_mmc is at the end so everything should be present already when it's initialized |
| 14:50.57 | dcordes | I hope I have the debug activated correctly now ./make.sh |
| 14:51.30 | BabelO | pH5: is asic3_mmc working now ? |
| 14:52.53 | pH5 | BabelO: I think it will next week. (didn't dare try it yet). |
| 14:53.21 | BabelO | pH5: ok |
| 14:54.54 | dcordes | Zoolooc: if you wanna boot reliably on kaiser you need the latest haret and probably a rom update |
| 14:55.54 | Zoolooc | dcordes: hmm, I'd hope not to have to update the ROM again, unless the ROM itself is really worth it. but if it's only haret, I could even crosscompile it |
| 14:56.32 | dcordes | Zoolooc: why not using haret builds on hh.org/~koconnor? |
| 14:56.43 | dcordes | which rom do you have? |
| 14:58.02 | dcordes | kaiser_init_mmc: vreg enable failed (-1) |
| 14:58.15 | *** join/#htc-linux gund4m (n=gundam@host58-44-dynamic.61-82-r.retail.telecomitalia.it) |
| 14:59.44 | dcordes | syslog still lacks the debug messages |
| 15:00.26 | Zoolooc | dcordes: I could get one from kevin's place, you're right. I have some Dutty's WM 6.1 (build 19716), but I'm scared of reading hundreds of forum pages for each released ROM to find out if there are any problems with it... |
| 15:04.30 | dcordes | hm the logs have a lot of mmc wisdom |
| 15:06.41 | dcordes | pH5: can you tell me what this message is about "kaiser_init_mmc: vreg enable failed (-1)" ? |
| 15:09.29 | *** join/#htc-linux revertive (n=revertiv@83.119.75.151) |
| 16:06.02 | *** join/#htc-linux tsrk (n=dontpani@c-76-27-223-191.hsd1.or.comcast.net) |
| 16:08.46 | *** join/#htc-linux the_sys0p (n=the_sys0@116.199.69.76) |
| 16:09.31 | pH5 | dcordes: it means either the vreg_get in line 338 failed or vreg_enable in line 339 |
| 16:10.23 | pH5 | I guess vreg_get shouldn't have failed, as it just looks up the string in the vregs array (which has a "mmc" entry). |
| 16:11.49 | pH5 | so there's something wrong with the msm_proc_comm call then? |
| 16:12.40 | pH5 | heh |
| 16:12.59 | pH5 | and if you look inside kaiser-smd.c, msm_proc_comm just returns -1 without doing anything |
| 16:13.01 | pH5 | even with a comment |
| 16:13.05 | pH5 | "not working yet" |
| 16:20.50 | dcordes | pH5: I had an approach on merging with dzo's latest patches for vogue which enable proc comm |
| 16:20.57 | dcordes | it doesn't work though |
| 16:21.00 | dcordes | wanna see? |
| 16:21.23 | dcordes | it's in my ~ |
| 16:21.46 | dcordes | http://linuxtogo.org/~lgorris/kaiser/merge-proc_comm.diff |
| 16:24.12 | pH5 | does it work on vogue? |
| 16:24.21 | dcordes | yes |
| 16:24.31 | dcordes | (dzo's patch of course, not my merge) |
| 16:24.55 | dcordes | http://it029000.massey.ac.nz/vogue/ |
| 16:25.05 | dcordes | that's mostly the proc comm code my merge was based on |
| 16:25.18 | dcordes | I have no ieda what I broke. everything builds fine but it doesn't boot |
| 16:26.04 | dcordes | dzo can use audio and vibration with pro ccomm on vogue |
| 16:26.12 | dcordes | he didn't mention sd |
| 16:31.06 | dcordes | I managed to boot with the moko filesystems btw :) |
| 16:32.37 | pH5 | I guess you should check with dzo how he came to find the needed msm_proc_comm code for his device, as it's different from the code in smd.c |
| 16:37.16 | dcordes | pH5: what's so device specific in proc_comm? the regs? |
| 16:37.33 | *** join/#htc-linux pikapika (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 16:37.51 | pH5 | dcordes: you tell me :) |
| 16:38.17 | pikapika | :) |
| 16:38.25 | pH5 | I guess it depends on the firmware running on the arm9, on the way the mmu is set up, where the smd memory range is located, something like that. |
| 16:38.45 | pH5 | is the memory setup identical on vogue and kaiser? |
| 16:38.48 | pH5 | hi pikapika |
| 16:39.11 | dcordes | pH5: smd is already working partly. We can read from at regs |
| 16:39.30 | dcordes | hm no but vogue memory setup=titan memory setup that's all I know |
| 16:41.57 | dcordes | pH5: what is the connection between smd and proc_comm exactly? |
| 16:42.18 | dcordes | in terms of scheme/how it works, not code level |
| 16:44.28 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 16:46.03 | pH5 | dcordes: smd is just shared memory area between arm11 and arm9, it's used to instruct the arm9 to read/write hardware registers, to communicate with the at interpreter running on arm9 or to instruct it to run certain commands. proc_comm seems to be this command mechanism (writing commands to the smd area, the arm9 reads them from there and executes) |
| 16:46.09 | pH5 | AIUI of course |
| 16:52.35 | dcordes | pH5: how can I read AT commands out of the smd then when proc_comm isn't setup? |
| 16:52.43 | dcordes | or returns -1 or whatsoever |
| 16:59.20 | pH5 | I guess because the AT interpreter uses a buffer in the smd region that is separate from the proc_comm stuff. |
| 17:00.00 | pH5 | but I'm just guessing, dzo certainly knows more about that. |
| 17:01.29 | dcordes | oks I will study the proc_comm code again and email him |
| 17:01.33 | dcordes | thanks for the advice |
| 17:10.45 | cr2_ | hi |
| 17:11.45 | cr2_ | dcordes: i think you'd change the clock regs directly, without any proc_comm things. or implement the proc_comm in a way that it manipulates the registers. this may be a better way. |
| 17:12.19 | cr2_ | pH5: great news. how do you sort out the SDIO/SD detection ? |
| 17:17.04 | pH5 | as far as I'm concerned, there is no such thing as sdio. doesn't the mmc core take care of that? |
| 17:26.28 | dcordes | cr2_: don't we need proc_comm in kaiser anyway to get audio? |
| 17:30.23 | cr2_ | pH5: cmd5 and cmd52/53 _are_ sdio. |
| 17:31.16 | cr2_ | pH5: cmd5 should be the first command to send to SD/IO card (htc not always doing it, sometimes they send cmd0) |
| 17:32.04 | cr2_ | so depending on the cmd5 response, you'd use the +0x800+ or +0x900+ register areas. |
| 17:33.29 | pH5 | cr2_: do you have a device with something connected to asic3 sdio? |
| 17:34.32 | *** join/#htc-linux Pablo (n=Pablo@chello089076070006.chello.pl) |
| 17:38.31 | cr2_ | pH5: i have a sdio gps sd501 |
| 17:39.04 | cr2_ | if i had a 2.6.26 kernel for n560, i could have tested it :) |
| 17:39.14 | cr2_ | pxamci should support sdio gps. |
| 17:46.48 | dcordes | cr2_: so I guess I should consider the second way you suggested |
| 17:49.08 | dcordes | bbl |
| 17:50.12 | pH5 | hm, I should get me some sdio card some time. but right now I'm mostly interested in sd storage, mostly because I didn't get nfs root to work for the hx4700 yesterday. |
| 17:51.06 | cr2_ | ok |
| 17:51.19 | *** join/#htc-linux andy_js (n=andy@AAmiens-152-1-27-107.w83-192.abo.wanadoo.fr) |
| 17:51.34 | pH5 | cr2_: what are the biggest problems before n560 on 2.6.26 would work? |
| 17:58.06 | cr2_ | htc-egpio, pxa serial power and the 2MB kernel offset. |
| 18:03.52 | pH5 | hm, but htc-egpio is there. the pxa serial power stuff is missing, that's true. I'll need something like that for phone/bluetooth soon. |
| 18:05.32 | cr2_ | ok. |
| 18:06.01 | *** join/#htc-linux kiozen_ (n=kiozen@rgnb-4db1de69.pool.einsundeins.de) |
| 18:08.01 | *** join/#htc-linux kiozen__ (n=kiozen@rgnb-4db1dcb6.pool.einsundeins.de) |
| 18:09.43 | BabelO | cr2_: i use device_attr for power |
| 18:13.17 | *** join/#htc-linux kiozem___ (n=kiozen@rgnb-4db1d912.pool.einsundeins.de) |
| 18:13.57 | kiozen___ | hates his wifi connection |
| 18:16.17 | cr2_ | BabelO: it's still a workaround. there should be some sensible separation between the kernel and userspace. the power management is certainly in the kernel domain. userspace may only provide some hints. |
| 18:22.23 | *** join/#htc-linux kiozen (n=kiozen@rgnb-4db1df0d.pool.einsundeins.de) |
| 18:26.53 | *** join/#htc-linux kiozen_ (n=kiozen@rgnb-4db1df4e.pool.einsundeins.de) |
| 18:30.00 | *** join/#htc-linux kiozen__ (n=kiozen@rgnb-4db1de4f.pool.einsundeins.de) |
| 18:30.33 | kiozen__ | does anyone have a good idea why freenode is closing my connection on a freequent base? |
| 18:39.24 | *** join/#htc-linux kiozen___ (n=kiozen@rgnb-4db1dce5.pool.einsundeins.de) |
| 18:53.21 | *** join/#htc-linux kiozen (n=kiozen@rgnb-4db1dc73.pool.einsundeins.de) |
| 18:54.42 | *** join/#htc-linux kiozen_ (n=kiozen@rgnb-4db1fa60.pool.einsundeins.de) |
| 18:56.18 | tsdogs | kiozen_: seems a problem with routes. Maybe some backbone went off... |
| 18:56.38 | tsdogs | kiozen__ ha lasciato questo server (Read error: 113 (No route to host)). |
| 18:58.44 | *** join/#htc-linux Othello (i=Magorium@gateway/tor/x-49898fd1707933b6) |
| 18:59.21 | kiozen_ | tsdogs: looks like my DSL connection is bad and gets into retrain state frequently |
| 18:59.51 | kiozen_ | tsdogs: maybe German Telekom is spying on me :) |
| 19:02.54 | *** join/#htc-linux diogene31_ (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
| 19:10.45 | *** join/#htc-linux SmallR2002 (n=SmallR20@c-67-162-60-33.hsd1.il.comcast.net) |
| 19:12.01 | kiozen | hm, a more conservative connetion profile seems to help :) |
| 19:13.18 | tcccp | kiozen: Erm...I'd suggest another ISP |
| 19:14.01 | kiozen | tcccp: won't help concerning the line it's all on and the same |
| 19:14.12 | tcccp | Ah, the copper itself bent? |
| 19:14.15 | kiozen | and I still have to live a year with 1&1 |
| 19:14.36 | tcccp | my condolences |
| 19:14.41 | kiozen | thanks :) |
| 19:14.47 | tcccp | is wether 1und1 nor T-${foo} customer |
| 19:15.28 | kiozen | tcccp: but the line will be maintained by the big T |
| 19:15.28 | tcccp | You're lost as soon as you need support |
| 19:15.28 | tcccp | I know :( |
| 19:15.28 | pH5 | kiozen: just use the bandwidth you paid for. I did that and they kindly asked me to leave :) |
| 19:15.42 | kiozen | lol |
| 19:15.59 | tcccp | I had 100GB+ per month with ${magenta} |
| 19:16.44 | kiozen | pH5: even having oprn bandwidth, I won't get better than 6MBits, you can't do too mauch harm with that |
| 19:17.38 | kiozen | but changing contract, won't help. It's all same same but different |
| 19:18.06 | kiozen | blowing up the central office might help |
| 19:18.42 | kiozen | that would at least single out bad hardware |
| 19:19.00 | kiozen | but I suspect bad copper |
| 19:19.37 | kiozen | for that I would have to ignite the whole street :) |
| 19:19.38 | tcccp | I'd suggest a raidteam taking care of |
| 19:20.06 | kiozen | next new year's eve :) |
| 19:20.27 | tcccp | Always think of thermite |
| 19:20.38 | tcccp | mix it up with vaselinum, and you have plastic thermite |
| 19:20.53 | tcccp | attach it to a door, ignite, have a lot of fun |
| 19:21.27 | kiozen | hm, better place it indoor to be sure |
| 19:21.47 | kiozen | but as told, I think the copper is bad in my area |
| 19:21.59 | tcccp | Or the DSLAM is beyond its capabilities |
| 19:22.06 | kiozen | at my office I will not get more than 3MBits |
| 19:22.18 | tcccp | kiozen: Yes, as you are a business customer |
| 19:22.31 | tcccp | ${magenta} cannot book bandwidth >3MBit/s to biz customers |
| 19:22.53 | kiozen | tcccp: no even as private, the area is 3Mbit only :/ |
| 19:22.58 | tcccp | ARGH |
| 19:23.14 | tcccp | I could immediately geht 10/50MBit here as private customer (VDSL) |
| 19:23.25 | kiozen | Regensburg is kind of country side :D |
| 19:23.35 | tcccp | Hannover not ;) |
| 19:23.55 | kiozen | oh Hannover has fibre optics? |
| 19:24.15 | tcccp | But ${magenta} refused to set up a second IDSN-Line for their booking system with 100% discount to add a 10/50 MBit line for 73 EUR |
| 19:24.19 | tcccp | Think so |
| 19:24.29 | tcccp | or broad copper ;) |
| 19:25.01 | kiozen | hm, VDSL is more for spreading fibre into the households |
| 19:25.35 | tcccp | HALP! |
| 19:25.41 | tcccp | My OpenBSD has an em0 interface! |
| 19:25.47 | cr2_ | pH5: oe update ? |
| 19:25.48 | tcccp | em0 baaad ;) |
| 19:33.41 | tcccp | np: Planet of the apes |
| 19:47.19 | *** join/#htc-linux LunohoD_ (n=alex@e180065104.adsl.alicedsl.de) |
| 19:59.21 | *** join/#htc-linux pikapika_ (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 20:04.03 | AstainHellbring | hey dcordes |
| 20:08.25 | *** join/#htc-linux pikapika (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 20:08.45 | *** join/#htc-linux JohnnyK_ (n=johnnyk@62.240.183.254) |
| 20:13.40 | *** join/#htc-linux johnnyk__ (n=johnnyk@nfx-nat-229.pilsfree.net) |
| 20:18.42 | *** join/#htc-linux CVirus (n=GoD@82.201.174.159) |
| 20:29.01 | *** join/#htc-linux andy_js (n=andy@AAmiens-152-1-27-107.w83-192.abo.wanadoo.fr) |
| 21:00.47 | martin__ | dcordes: ping? |
| 21:02.17 | AstainHellbring | martin__: do you know what dcordes was talking about with: If you can't wait talking to the modem in android, just boot up with the latest zImage havin phone activated in wince and call your kaiser :-) see what happens. It's not awesome but you can see it lives |
| 21:05.16 | martin__ | AstainHellbring: we have one way comms to the gsm modem |
| 21:05.24 | martin__ | we can read but not write |
| 21:05.26 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
| 21:05.34 | martin__ | dcordes_: hey |
| 21:05.49 | AstainHellbring | ahh ic |
| 21:05.52 | AstainHellbring | awesome |
| 21:06.09 | martin__ | AstainHellbring: so I presume what happens is it gets the ring and brings up the UI saying there's a phone call |
| 21:06.13 | martin__ | but that'll be all |
| 21:06.23 | martin__ | i'm working on getting the writes. |
| 21:06.33 | AstainHellbring | because we can't write the answer to it basically? |
| 21:06.47 | martin__ | yeah, we can't tell it to pick up |
| 21:08.15 | AstainHellbring | btw curious how goes the fight with sd drivers? |
| 21:09.20 | martin__ | dunno, not looked at that |
| 21:09.44 | martin__ | what i really want to do is get some sort of comms |
| 21:10.04 | martin__ | was hoping the bluetooth would be easy since it's just on a serial port internally |
| 21:10.14 | martin__ | but the serial driver hangs the kernel |
| 21:10.42 | AstainHellbring | damn the kernel having issues with serial driver |
| 21:10.59 | *** join/#htc-linux pikapika (n=pikapika@mar75-8-88-164-227-147.fbx.proxad.net) |
| 21:11.07 | martin__ | dcordes is working on that now |
| 21:11.16 | martin__ | i've swapped with him and am looking at the smem write stuff for the modem |
| 21:12.29 | AstainHellbring | nice some awesome colaboration going on eh? |
| 21:13.18 | martin__ | well, it hasn't got us much further yet, but it's nice to have moral support and people nagging each other to work on it :) |
| 21:13.55 | martin__ | anyway, gotta bike across town now, back from home later on. |
| 21:56.05 | Zoolooc | dcordes: I could get one from kevin's place, you're right. I have some Dutty's WM 6.1 (build 19716), but I'm scared of reading hundreds of forum pages for each released ROM to find out if there are any problems with it... |
| 22:49.52 | *** join/#htc-linux mistadman (n=mistadma@adsl-156-124-48.msy.bellsouth.net) |
| 23:05.22 | *** join/#htc-linux JohnnyK_ (n=johnnyk@62.240.183.254) |
| 23:14.29 | *** join/#htc-linux JohnnyK (n=johnnyk@nfx-nat-229.pilsfree.net) |
| 23:22.35 | *** join/#htc-linux johnnyk__ (n=johnnyk@62.240.183.254) |
| 23:37.44 | *** join/#htc-linux JohnnyK_ (n=johnnyk@nfx-nat-229.pilsfree.net) |