| 06:33.44 | *** join/#htc-linux sylvain (n=sylvain@APuteaux-154-1-87-103.w83-204.abo.wanadoo.fr) |
| 07:15.57 | *** join/#htc-linux rob_w (n=rob_w@p549B9604.dip0.t-ipconnect.de) |
| 10:15.49 | *** join/#htc-linux rejon (n=rejon@64-121-195-22.c3-0.sfpo-ubr4.sfrn-sfpo.ca.cable.rcn.com) |
| 10:31.31 | *** join/#htc-linux dullard (n=jim@adsl-static-1-30.uklinux.net) |
| 10:45.01 | *** join/#htc-linux LunohoD_ (n=alex@e180076158.adsl.alicedsl.de) |
| 10:56.25 | *** join/#htc-linux psokolovsky_ (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com) |
| 12:14.07 | *** join/#htc-linux awelux (n=awelux@lvps87-230-8-217.dedicated.hosteurope.de) [NETSPLIT VICTIM] |
| 15:36.07 | *** join/#htc-linux jeanseb (n=jeanseb@88.164.32.155) |
| 16:17.09 | *** join/#htc-linux redclay (n=redclay@lugbari/people/redclay) |
| 16:24.02 | redclay | hi all |
| 16:25.50 | *** join/#htc-linux g3gg0_ (n=g3gg0@ppp-82-135-72-127.dynamic.mnet-online.de) |
| 16:26.27 | redclay | does anyone knows if HTC 3600 has linux support? |
| 16:26.36 | redclay | I found this page: http://wiki.xda-developers.com/index.php?pagename=HTC_Trinity |
| 16:33.31 | *** join/#htc-linux rob_w (n=bob@p85.212.136.170.tisdip.tiscali.de) |
| 16:36.46 | *** join/#htc-linux lkcl (n=lkcl@host81-155-14-65.range81-155.btcentralplus.com) |
| 17:19.13 | *** join/#htc-linux pleemans (n=peter@d51A5E421.access.telenet.be) |
| 17:39.17 | lkcl | trying to get udc working on sable... |
| 17:45.52 | *** join/#htc-linux pH5 (n=ph5@e178205093.adsl.alicedsl.de) |
| 17:46.18 | lkcl | allo ph5 |
| 17:46.56 | pH5 | hey lkcl |
| 17:48.23 | lkcl | am looking for the asic3 gpio for udc on the sable... |
| 17:49.04 | lkcl | anyone seen cr2 for a week? |
| 17:50.06 | pH5 | asylumed: any news on the resume oops? |
| 17:50.17 | pH5 | lkcl: the usbc detect input gpio? |
| 17:50.21 | asylumed | pH5: alas no... |
| 17:50.42 | asylumed | at first i thought it was the udc using the asic before it was resumed... |
| 17:50.54 | asylumed | but i made all the asic devices child devices... |
| 17:51.28 | pH5 | asylumed: is the asic3 driver a proper platform driver? |
| 17:51.40 | *** join/#htc-linux g3gg0__ (n=g3gg0@ppp-82-135-11-56.dynamic.mnet-online.de) |
| 17:51.44 | asylumed | so the only strangeness i've seen left is that the opening some of the uarts causes and oops |
| 17:51.58 | *** join/#htc-linux rejon (n=rejon@adsl-75-5-124-98.dsl.pltn13.sbcglobal.net) |
| 17:52.21 | lkcl | both the usbc detect input gpio and also the asic3 gpio enable |
| 17:52.22 | pH5 | but indeed it doesn't have to do anything with the platform stuff. it seems this wake up problem can appears for various memory corruption issues. |
| 17:52.40 | asylumed | <PROTECTED> |
| 17:52.54 | pH5 | lkcl: isn't that as easy as doing an asic3gpio dump in haret, pulling the cable and checking again? |
| 17:53.21 | asylumed | ya think? |
| 17:53.28 | pH5 | asylumed: uh.. isn't that driver on the platform bus, too? I think you should try converting it. |
| 17:53.30 | asylumed | yeah... |
| 17:54.02 | lkcl | pH5: about 5 pins change |
| 17:54.19 | lkcl | this is out: |
| 17:54.24 | pH5 | asylumed: That's an ugly bug. Nobody got any problems with this so far. |
| 17:54.27 | lkcl | HaRET(7)# wasic3gpio 30 |
| 17:54.27 | lkcl | GPIOA7 S 1 ? 1618247 |
| 17:54.27 | lkcl | GPIOB6 S 1 ? 1618261 |
| 17:54.27 | lkcl | GPIOB14 S 1 ? 1618388 |
| 17:54.29 | lkcl | GPIOC1 S 0 ? 1618506 |
| 17:54.31 | lkcl | GPIOC2 S 0 ? 1618521 |
| 17:54.33 | lkcl | GPIOC1 A 0 |
| 17:54.35 | lkcl | GPIOC2 A 0 |
| 17:54.37 | lkcl | GPIO45 S 1 1619337 |
| 17:54.39 | lkcl | GPIO45 S 0 1619346 |
| 17:54.41 | lkcl | this is in: |
| 17:54.45 | lkcl | GPIOB6 S 0 ? 1622486 |
| 17:54.47 | lkcl | GPIOB14 S 0 ? 1622579 |
| 17:54.49 | lkcl | GPIOC1 A 1 |
| 17:54.51 | lkcl | GPIOC2 A 1 |
| 17:54.53 | lkcl | GPIOC1 S 1 ? 1622823 |
| 17:54.55 | lkcl | GPIOC2 S 1 ? 1622854 |
| 17:54.57 | lkcl | GPIOA7 S 0 ? 1622989 |
| 17:54.59 | lkcl | GPIOB14 S 1 ? 1623398 |
| 17:55.01 | lkcl | GPIOC1 S 0 ? 1623493 |
| 17:55.03 | lkcl | GPIOC2 S 0 ? 1623507 |
| 17:55.05 | lkcl | GPIOC1 A 0 |
| 17:55.07 | lkcl | GPIOC2 A 0 |
| 17:55.09 | lkcl | GPIOB14 S 0 ? 1623771 |
| 17:55.11 | lkcl | GPIOC1 A 1 |
| 17:55.13 | lkcl | GPIOC2 A 1 |
| 17:55.15 | lkcl | GPIOC1 S 1 ? 1623948 |
| 17:55.17 | lkcl | GPIOC2 S 1 ? 1623960 |
| 17:58.02 | pH5 | lkcl: which ones of those are outputs? (what does S and A mean?) I'd rule out C1,C2 and 45. |
| 17:58.49 | lkcl | so, hum... |
| 17:59.59 | pH5 | that leaves us with A7, B6 and B14. could it be that they are usbc detect, enable and charge enable? |
| 18:01.22 | pH5 | lkcl: dump asic3gpio should tell you which are inputs/outputs |
| 18:01.27 | lkcl | they're going to 1 rather than 0 whic is a bit odd |
| 18:01.35 | pH5 | maybe they are active low. |
| 18:02.02 | lkcl | http://wiki.xda-developers.com/index.php?pagename=Ipaq6915_Research |
| 18:02.07 | pH5 | ah right |
| 18:02.23 | lkcl | they're all marked LO |
| 18:02.58 | lkcl | except for B0, B6 and B7 which are all marked RE |
| 18:03.31 | pH5 | what does LO mean? |
| 18:03.36 | lkcl | clueless! |
| 18:03.49 | lkcl | the columns are like this: A3GPIOA# D S A s M IN |
| 18:03.52 | lkcl | oh dear :) |
| 18:04.06 | pH5 | RE/FE are rising/falling edge, probably interrupt triggers. |
| 18:04.14 | lkcl | ack. |
| 18:04.46 | lkcl | ok A7 is an output. |
| 18:05.04 | lkcl | B6 is an input. |
| 18:05.33 | lkcl | B14 is an output |
| 18:05.45 | pH5 | yup. so I'd say B6 is a candidate for usbc detect |
| 18:05.47 | asylumed | insanity@blueangel:~$ apm -s |
| 18:05.49 | asylumed | insanity@blueangel:~$ dmesg |
| 18:05.49 | asylumed | Connection to 192.168.0.202 closed by remote host. |
| 18:05.49 | asylumed | Connection to 192.168.0.202 closed. |
| 18:05.54 | asylumed | dead |
| 18:06.10 | lkcl | oo you have a blueangel - is it board rev 6? |
| 18:06.15 | pH5 | asylumed: yeah, I know that feeling.. |
| 18:06.17 | asylumed | yeah |
| 18:06.22 | asylumed | x6 |
| 18:06.34 | lkcl | does the screen come back on after a power-restore? |
| 18:06.38 | asylumed | yip |
| 18:06.43 | asylumed | was a mission |
| 18:06.45 | lkcl | hurrah! someone fixed that? |
| 18:07.02 | asylumed | erm... well... i just do the init twice :/ |
| 18:07.11 | lkcl | who fixed that? oh that's just _typical_ :) |
| 18:07.18 | asylumed | so it's an ordering thing... |
| 18:07.26 | lkcl | you have no idea how absolutely friggin typical that is :) |
| 18:07.32 | asylumed | wanna experiment... but the suspend this is a *real* issue |
| 18:07.59 | lkcl | what kernel version are you using, and do you have sound? |
| 18:08.10 | asylumed | nah... sound doesn't compile... |
| 18:08.20 | lkcl | cos when i go back to den haag in december i will go get my BA. |
| 18:08.30 | asylumed | oooh... awesome.... |
| 18:08.46 | asylumed | and you're keen to help out a bit? |
| 18:08.55 | asylumed | i'm losing momentum a bit |
| 18:09.27 | pH5 | Yuck. I've got my next hangup during suspend here when I enable the external interrupt controller. |
| 18:09.29 | lkcl | yep, that's typical... *Sigh*... it _did_ compile, it _did_ work - with 2.6.3 (i think) but it only worked if the wince device initialised the i2c bus. _however_... in the 2.6.13 and above kernels, now there is a proper uda1380 sound driver... |
| 18:09.36 | rob_w | asylumed, ,, one question , which cvs versions of the kernel are u working on .. |
| 18:09.53 | asylumed | 2.6.17... |
| 18:10.06 | lkcl | asylumed: in handhelds.org, yes? |
| 18:10.25 | lkcl | or my favourite hacked-to-bits xanadux cvs? |
| 18:10.25 | asylumed | yip |
| 18:10.28 | lkcl | ok. |
| 18:10.43 | lkcl | well, hang in there until some time in mid-december, ok? :) |
| 18:10.59 | rob_w | asylumed, do yourself the favour and check the .12 stuff at xanadux .. there we had all this working .. but someone checking in hh.org and not current xanadux code |
| 18:11.11 | lkcl | go get an ipaq hw6915 or something in the meantime |
| 18:11.21 | pH5 | lkcl: :-) |
| 18:11.27 | asylumed | :) eish... |
| 18:11.37 | rob_w | so by just moving the status of .12 to .1X you should be running usb detec, led , backlight , and lcd resume |
| 18:11.56 | asylumed | aaaah.... |
| 18:12.26 | rob_w | asylumed, maybe check my patches which did that for most parts ! |
| 18:12.32 | lkcl | we had nearly _everything_ working with 2.6.12 in xanadux - except for the backlight (after suspend/resume) and except for initialising the sound (which had to be switched on from wince). |
| 18:12.44 | lkcl | i even managed to make and receive phone calls using gomunicator. |
| 18:12.51 | asylumed | yeah... but it problem still remains... i've gone as far as running *just* the asic and suspend stuff... i disabled most of the platform devices en the pxa (generic.c even) |
| 18:12.55 | rob_w | yep .. those where the days |
| 18:13.04 | asylumed | i also made calls :( |
| 18:13.16 | lkcl | so if you got the screen working, then that only leaves sound. |
| 18:13.23 | asylumed | well... |
| 18:13.34 | asylumed | no... bluetoothe uart causes an oops |
| 18:14.05 | asylumed | very sad day... since this worked in .12 too... |
| 18:14.07 | lkcl | nope - bluetooth was working, too. it _was_ you who ran opie/irc on your blueangel using bluetooth, wasn't it, rob_w? :) |
| 18:14.16 | rob_w | uda1380 had big changes to .16 .. |
| 18:14.20 | rob_w | yep |
| 18:14.34 | rob_w | but it was xchat / gpe ;-) |
| 18:14.39 | lkcl | *snort* |
| 18:14.47 | rob_w | BIG difference |
| 18:18.01 | psokolovsky_ | Hi folks! |
| 18:18.20 | rob_w | hey dude |
| 18:18.28 | asylumed | hi |
| 18:18.42 | pH5 | hey psokolovsky_ |
| 18:18.50 | lkcl | ha ha a6 and b7 are already marked in the htcsable_asic3.h file |
| 18:18.56 | lkcl | allo psokolovsky |
| 18:18.58 | psokolovsky_ | rob_w, lkcl: You gentlemen miss crucial thing: 2.6.12 is not just old, it's dead. so whatever was working there, oops, almost dead too ;-( |
| 18:19.21 | lkcl | brb - food |
| 18:19.46 | asylumed | not looking to run 2.6.12 again... just gonna have a look for differences |
| 18:19.47 | psokolovsky_ | So, the only way to have something "working" for not yet fully supported device is to stay as close to the current mainline as possible. |
| 18:20.08 | rob_w | psokolovsky_, that pushes my feelings , that we need to reinvent the ba |
| 18:20.19 | asylumed | it was said that the move over to hh.org was bad? |
| 18:20.19 | psokolovsky_ | HH.org CVS is not perfect with that, but we're trying to cut latency with upgrading to new mainline releases |
| 18:21.14 | psokolovsky_ | rob_w, not reinvent, just "upgrade". But as there're big differnce bewteen .12 & .17, the work is indeed big enough ;-( |
| 18:21.34 | rob_w | psokolovsky_, so ur one with hh.org write access ? |
| 18:22.03 | psokolovsky_ | that's exactly why better do incremental small .x -> .x+1 upgrades regularly, then later grief about one big upgrade |
| 18:22.09 | psokolovsky_ | rob_w, yes |
| 18:22.53 | psokolovsky_ | rob_w, lkcl: and your help with that upgrade would be much appreciated. but asylumed does good thing doing that now |
| 18:23.09 | rob_w | yeah .. my patch i did from .12 to .16 was like 350kb patch |
| 18:23.17 | asylumed | *g* |
| 18:23.39 | psokolovsky_ | I hope you'll guys find way to colloborate |
| 18:23.48 | rob_w | yeah ., asylumed is one mover theses days .. i only spitting bad comments *argh* |
| 18:24.02 | asylumed | :/ |
| 18:24.03 | psokolovsky_ | why good thing about hh.org cvs is that it has many devices alerady, and promotes code standards and reuse |
| 18:25.13 | rob_w | so psokolovsky_ , lets say i check out .17-hh2 .. and try to split up stuff in small pieces .. thats the way to go ? |
| 18:25.38 | psokolovsky_ | rob_w, I understand your feelings, but well, let's make good conclusions from our experience - it's indeed good thing to push one thing together, than few things on each own ;-) |
| 18:26.06 | *** join/#htc-linux sylvain (n=sylvain@APuteaux-154-1-83-16.w83-204.abo.wanadoo.fr) |
| 18:26.14 | psokolovsky_ | rob_w, yes, at least as far as I see that. but quick look shows BA already has it like that, no? |
| 18:26.15 | rob_w | hey i am ok .. and i totally agree |
| 18:27.31 | rob_w | ok .. lets see .. i will check .17-hh2 and try to split up the patches as possible and logical i can .. |
| 18:27.39 | psokolovsky_ | I picked h4000 in kinda that state, and had to almost literally throw away much of old code and re-base port on the h1910 code. |
| 18:27.51 | psokolovsky_ | rob_w, nice plan! |
| 18:28.19 | rob_w | psokolovsky_, what device from your view is the best to steal drivers designs from ? |
| 18:29.13 | psokolovsky_ | rob_w, whatever device already has what you need, http://handhelds.org/moin/moin.cgi/HandheldHardwareXref ;-) |
| 18:31.27 | rob_w | i mean in terms of general drivers design ,, not functionility .. |
| 18:32.51 | psokolovsky_ | rob_w, shameless plug: you could have a look at h4000 ;-). but not everything is perfect that still. of "not the first place to look at" is hx4700, unfortunately, it has some tangled code still |
| 18:33.13 | pH5 | especially everything that involves asic3.. |
| 18:33.28 | rob_w | okok |
| 18:33.38 | pH5 | psokolovsky_: we just noticed that asic3 is a device_driver instead of a platform_device, I wonder how that worked for so long |
| 18:33.51 | rob_w | my intention is to just align design wise with the others .. but i get your sense |
| 18:34.30 | rob_w | yeah that platform - device misuse throw my understanding in quite some problems |
| 18:34.43 | rob_w | also some ba modules do mess as platform_device |
| 18:35.20 | pH5 | I just learned that the hard way when I had to git bisect between 2.6.18 and 2.6.19-rc1 until I understood the issue. |
| 18:35.48 | *** part/#htc-linux sylvain (n=sylvain@APuteaux-154-1-83-16.w83-204.abo.wanadoo.fr) |
| 18:36.10 | psokolovsky_ | pH5, you mean, driver vs platform_driver? beat me, but I yet need to learn what's the difference between them %). I guess, it's just platform_device should be served by platform_driver? |
| 18:36.21 | asylumed | yeah... |
| 18:36.51 | asylumed | just converted my copy here... |
| 18:37.02 | pH5 | The platform_driver wraps around a device_driver. The suspend/resume code in platform.c expects drivers on the platform bus to have this platform_driver shrink-wrap. |
| 18:37.06 | psokolovsky_ | rob_w, we yet of the beginning of the path to have consistent code patterns everywhere, so feel free to lead the cause. |
| 18:38.07 | psokolovsky_ | rob_w, general idea is to factor out all the stuff used by several machines into common driver, and have just small shims to interface with device-specific details |
| 18:39.24 | rob_w | yeah tsc2200 is such a candidate .. also as asic3 |
| 18:39.36 | rob_w | whats the correct tag to checkout .17-hh2 ? |
| 18:39.53 | psokolovsky_ | rob_w, just use CVS HEAD ;-) |
| 18:40.07 | asylumed | tsc2200 is tough one... |
| 18:40.17 | psokolovsky_ | rob_w, yes. one of my next items in queue is asic3_buttons driver . |
| 18:40.46 | pH5 | psokolovsky_: and finally rip those buttons out of the hx4700_ts driver. that's a good one. |
| 18:41.28 | psokolovsky_ | pH5, yeah! also, adhoc button drivers on h1910/h4000, etc. |
| 18:41.47 | lamikr | Is tsc2200 similar than tsc2101 or tsc2102? tsc2102 uses nicely the spi framework in omap kernel. I plan to move tsc2101 to follow same framework in future... (/spi/tsc2102.c) |
| 18:42.09 | rob_w | lamikr, yes it is a successor .. |
| 18:42.30 | lamikr | rob_w: Hi |
| 18:42.39 | rob_w | my patch moved the tsc2200 driver from himalaya dir into soc/ |
| 18:42.56 | rob_w | cvs co -ko -r K2-6-17-hh2 linux/kernel26 |
| 18:42.56 | rob_w | <PROTECTED> |
| 18:43.07 | lamikr | My understanding is that the spi/tsc2102 could work also for other devices than omap. |
| 18:44.31 | lamikr | rob_w: What is soc, is it also some kind of bus communication generation? |
| 18:45.07 | rob_w | drivers/soc in a recent kernel |
| 18:45.19 | pH5 | that's a hh.org-ism |
| 18:45.22 | rob_w | ah the cvs co startts |
| 18:50.54 | lkcl | for the himalaya i wrote a generic ssp driver. then made the tsc2200 use that. |
| 18:52.37 | rob_w | yeah .. looking at my patch again i also made a hack via extern static to toggle the keyboard led on pushing any key .. in combination with a 5 sec timer .. what a hack |
| 18:53.12 | rob_w | bbl |
| 18:54.42 | *** part/#htc-linux redclay (n=redclay@lugbari/people/redclay) |
| 18:54.52 | pH5 | shouldn't a keyboard led be implemented as a led device, too? |
| 19:33.49 | *** join/#htc-linux rob_w (n=bob@p85.212.183.227.tisdip.tiscali.de) |
| 19:37.37 | *** join/#htc-linux goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com) |
| 19:45.39 | *** join/#htc-linux psokolovsky__ (n=psokolov@236.usernat.ip.net.ua) |
| 19:59.13 | *** join/#htc-linux lamikr (n=chatzill@aragorn.kortex.jyu.fi) |
| 20:20.11 | lkcl | i got udc working! |
| 20:21.15 | asylumed | nice |
| 20:21.54 | *** join/#htc-linux psokolovsky (n=psokolov@ip.85.202.124.214.dyn.sub-9.broadband.voliacable.com) |
| 20:24.16 | lkcl | means i can do nfs |
| 20:24.30 | asylumed | nfs? |
| 20:24.49 | lkcl | nfs root-mount over usb gadget |
| 20:25.17 | lkcl | http://wiki.xda-developers.com/index.php?pagename=HimalayaLinuxBootingViaRootNFS |
| 20:25.25 | asylumed | hectic |
| 20:28.47 | asylumed | i've been meaning to build a rootfs into an initrd to test if the suspend break is mmc related... |
| 20:29.11 | *** join/#htc-linux seishin (n=seishin@e177179027.adsl.alicedsl.de) |
| 20:29.14 | seishin | hi |
| 20:30.26 | goxboxlive | hi seishin |
| 20:39.38 | psokolovsky | asylumed, if you use asic3_mmc, it is known to work well with suspen/resume in CVS HEAD (I did some fixings since 2.6.16-hh5) |
| 20:40.26 | asylumed | kewl... will take it for granted that it works then? |
| 20:41.00 | asylumed | though i have to hard code that the mmc card is not read only before it will boot off of it.... |
| 20:41.28 | asylumed | i get a obscure unkown-block(254, 2) kernel panic... |
| 20:41.42 | asylumed | booting through an initrd and then onto the mmc works fine... |
| 20:42.31 | asylumed | (even though the fact it has major and minor numbers means it's identified the device it needs before the panic...) |
| 20:42.32 | goxboxlive | Yes the suspend/resume does also work in the universal now. There are still som issues, but it resume, even wlan. |
| 20:44.44 | pH5 | asylumed: I need to set a rootdelay on the kernel commandline, otherwise the kernel tries to load the rootfs before the card is ready. |
| 20:44.53 | lkcl | yeh i get the same thing asylumed |
| 20:45.07 | lkcl | ahh - what's that, dude? |
| 20:45.20 | lkcl | what's the rootdelay and why isn't it documented in the wikis??? :) |
| 20:45.21 | asylumed | gave it 10 seconds... |
| 20:45.29 | lkcl | so just rootdelay=10 yes? |
| 20:45.45 | lkcl | arse i could have done with knowing that, last week... |
| 20:46.35 | asylumed | *g* the number of things i tried... turns out i went through one of rob_w's patchs and it was in there... |
| 20:46.57 | asylumed | it boots with no rootdelay now though... so it's odd... |
| 20:47.05 | lkcl | you don't need an initrd, you just need... well, actually, the initrd from 3 years ago, the one that i put xfbdev and sshd into, is the best practical example |
| 20:47.49 | lkcl | and now of course in the house-move i can't find my mini-sdcard and i'm going to have to get another one tomorrow from maplin's |
| 20:48.03 | asylumed | it didn't have apm :P |
| 20:48.16 | pH5 | rootdelay=1 is enough for me. it's documented in Documentation/kernel-parameters.txt |
| 20:50.20 | lkcl | i can't remember my password to ssh in to the box! |
| 20:52.49 | seishin | long time no see, since cr2's help got my 4gb sdcard running...any progress with power management at the universal front? |
| 20:53.46 | seishin | (i would like to switch away from m$ but i only have standard battery ;) ) |
| 20:53.53 | lkcl | ok in the linuxrc file i'm staring at, in an initrd, there is a sleep 2 before attempting to mount the partition |
| 20:54.02 | lkcl | echo "Setting up RAMFS, please wait... " |
| 20:54.02 | lkcl | depmod -ae |
| 20:54.02 | lkcl | modprobe asic3_mmc |
| 20:54.02 | lkcl | modprobe mmc_block |
| 20:54.02 | lkcl | sleep 2 |
| 20:54.03 | lkcl | mount /dev/mmc/blk0/part2 /mnt |
| 20:54.16 | lkcl | ar$e. |
| 20:57.03 | seishin | goxboxlive: suspend + resume: how do i do this (using gpe)? |
| 20:57.44 | goxboxlive | seishin: It works in both gpe and opie. Is included the latest kernel cvs |
| 20:59.06 | seishin | goxboxlive: can u point me to that cvs-url....i like to try it out.. =) |
| 21:01.00 | goxboxlive | seishin: I have made a opie-image with the suspend included, you can just download it. But be aware that the keyboard stop working after resume. |
| 21:01.34 | seishin | goxboxlive: i would use the info on http://www.handhelds.org/moin/moin.cgi/UniversalKernel but i think i have read something about 2.6.19?? |
| 21:01.54 | seishin | goxboxlive: w/o keyboard -_- |
| 21:02.07 | seishin | goxboxlive: i need keyboard =) |
| 21:02.15 | goxboxlive | http://gnulinux.biz/files/Universal/tmp/Angstrom/ use both kenrel and image |
| 21:02.27 | goxboxlive | yes, thats one of the issues |
| 21:02.47 | goxboxlive | And that the lcd is not switcing of after when suspending |
| 21:03.20 | seishin | switching off...ok so its eating battery in suspendmode? |
| 21:03.41 | seishin | s/switch/not switch |
| 21:03.42 | goxboxlive | But, cr2 told me that there where a aesy job to fix. The keyboard is more complicated, it must be moved over to the asic3 AFAIK. |
| 21:04.15 | goxboxlive | Yes it is, as i said, it still has some issues. But the wakup up part is now working. |
| 21:04.54 | seishin | goxboxlive: is 2.6.17 or .19 actual dev-working ground? |
| 21:05.04 | goxboxlive | 17 |
| 21:05.11 | seishin | okay |
| 21:05.57 | seishin | is the backlight or the lcd itself more power consuming? |
| 21:08.37 | goxboxlive | seishin: dont know actullay |
| 21:12.03 | seishin | i possibly can do some work (like building german keymaps) at boring hours at study...but switching between wm5 and linux just for powersaving...it's not funny |
| 21:15.42 | seishin | goxboxlive: do you know a howto for getting gpe+opie running aside |
| 21:16.31 | goxboxlive | Now, i have been trying to figure out that my self, but it is not working good. Actually i have a link, hold on |
| 21:21.34 | goxboxlive | seishin: http://wiki.openzaurus.org/HowTos/OPIE_and_GPE |
| 21:22.31 | seishin | thank u :) |
| 21:24.27 | seishin | okay i will try it all tomorrow (first two hours i have internet access :) ) |
| 21:24.36 | seishin | gn8 guys |
| 21:25.35 | seishin | single question: password for root was? |
| 21:31.26 | goxboxlive | rootme or nothing if u use the one in the link i gave you |
| 21:34.45 | *** join/#htc-linux Kmarc (i=kari@markos.biz) |
| 21:39.41 | lkcl | ah ha! i have an ssh login! |
| 22:14.02 | lamikr | lkcl: Wow, so nfs boot works, how about sd card boot? |
| 23:34.17 | *** join/#htc-linux lkcl (n=lkcl@host81-155-14-65.range81-155.btcentralplus.com) |
| 23:34.51 | lkcl | yeh i would use mmc but gotta test with rootdelay=1 on boot kernel parms |
| 23:34.58 | lkcl | plus i lost my sdcards |
| 23:35.04 | lkcl | tomorrow |
| 23:43.57 | rob_w | asylumed, did u catch the resume problem now ?? |