IRC log for #htc-linux on 20070421

04:46.58*** join/#htc-linux eremias (n=fdsfs@ACB0ADA8.ipt.aol.com)
06:10.13*** join/#htc-linux RoEn_PC (n=roen@p54a65e8b.dip.t-dialin.net)
06:26.11*** join/#htc-linux ellisway (n=ellis@host-87-74-241-174.bulldogdsl.com)
06:36.18*** join/#htc-linux tudenbart (n=willi@xdsl-81-173-174-115.netcologne.de)
07:02.54*** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk)
07:03.37*** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk)
07:09.16*** join/#htc-linux Ro_En_PC (n=roen@p54a6728e.dip.t-dialin.net)
07:38.13*** join/#htc-linux rob_w (n=bob@p85.212.10.79.tisdip.tiscali.de)
08:02.19*** join/#htc-linux psokolovsky (n=psokolov@82.193.98.7)
08:39.17*** part/#htc-linux lilliput (n=Touriste@82-47-146-8.cable.ubr11.brad.blueyonder.co.uk)
08:40.15*** join/#htc-linux eremias (n=fdsfs@ACB0ADA8.ipt.aol.com)
08:40.15psokolovskyHi!
08:40.31psokolovskycr2: going to rename himalaya to htchimalaya, as we agreed
08:43.45*** join/#htc-linux Ranpha1 (n=Ranpha@hlm-n-73ed.adsl.wanadoo.nl)
08:45.29Ranpha1Stupid question. I have a sprae sd-card and i really like to have linux on my qtek 9000. But do i need to replace the WM5 rom or can i run it when i insert the card pull it out and have WM5 back?
08:54.17*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
09:46.13cr2Ranpha1: linux run from wince5 works as a wince program. no known side effects afaik.
09:53.38*** join/#htc-linux twostupiddogs (n=twostupi@84.18.144.39)
09:55.11cr2twostupiddogs: there are no problems to build opie on 64bit cpus since 1.5 years
09:55.26twostupiddogshi all.
09:55.35cr2i don't have any other cpus :) 32bit only on the arm phones .
09:56.04twostupiddogsI'm trying to build opie-image for htcuniversal with an x86_64, but have some troubles building qt
09:56.16cr2sorry, the old vax is 32bit too ;)
09:56.20cr2works for me.
09:56.44cr2are these problems linked to 32bit ?
09:56.47twostupiddogsdon't think so.
09:57.01twostupiddogsit failes during configuration of the qt
09:57.12cr2i'm updating with monotone
09:57.27twostupiddogsme too
09:57.30cr2did the last opie compilation 2 days ago.
09:58.09twostupiddogsI set it up just few days ago, but never finished the build
09:58.49cr233 revs
09:59.03twostupiddogsI had to remove the locale for qemu problems with x86_64 on glibc, and compilation wen on
09:59.16cr2sometimes things break, but it's usually working soon.
09:59.24cr2yes, it's an old problem.
09:59.26twostupiddogsdoing an update now too be sure
09:59.40cr2i don't understand why it is still not solved.
10:00.04twostupiddogswell, at this time locales ain't a particular problem to me.
10:00.38twostupiddogsI just started the OE adventure so am not that expert. how do you get the version?
10:01.06cr2which version ?
10:01.32twostupiddogssorry revision
10:02.05cr2with monotone.
10:02.11twostupiddogsyes.
10:02.14cr2actually i compile just for fun.
10:02.37cr2it's pH5 and goxboxlive that do serious work there.
10:02.40twostupiddogsright now it's like this for me too, but looking forward to help out
10:02.53cr2i dont' try to do everything :)
10:03.00twostupiddogswell you look pretty active anyway :-)
10:03.27cr2i know that it compiles, but never use the output myself.
10:03.48twostupiddogsI did an mnt update, but compilation still stops in the qt package. would it help if I paste the output?
10:04.19cr2yes.
10:05.00twostupiddogsFATAL: Configuring qt failed. EXTRA_OECONF was -system-jpeg -system-libpng -system-zlib -no-qvfb -no-xft -no-vnc -gif                 -xplatform linux-gnueabi-arm-g++ -qconfig qpe -depths 8,16,32 -static -thread
10:05.47twostupiddogschecking the log
10:06.10cr2compiling myself.
10:06.32twostupiddogsactually that's all...
10:07.40twostupiddogsI have a bunch of output telling me all the available compilers
10:09.38cr2oh. it's recompiling gtk and some weird gnome stuff.
10:09.51twostupiddogswith opie?
10:10.26cr2somebody who writes gint instead of int, has included gdk dependency for bluez-something ;)
10:10.28twostupiddogsmaybe this might be the problem... "
10:10.28twostupiddogsNo static library support for platform/compiler  linux-gnueabi-arm-g++-stati
10:10.28twostupiddogsc
10:10.28cr2yes.
10:11.03cr2i've seen that problem half a year ago.
10:11.24twostupiddogsyou remember the solution?
10:11.28twostupiddogsshould I google?
10:11.47cr2it was solved somehow.
10:11.57cr2btw, which local.conf are you using ?
10:12.14cr2pango, cairo. wtf ?
10:12.30twostupiddogswell the original in OE with the machine modifications..
10:12.53twostupiddogsI followed the howto on angstrom...
10:13.30cr2can you pastebin it ?
10:13.56twostupiddogsok, but have to remove all the comments that are in, wait a sec.
10:15.16twostupiddogsDL_DIR = "/OE/downloads"
10:15.20twostupiddogsBBFILES := "/OE/org.openembedded.dev/packages/*/*.bb"
10:15.24twostupiddogsBBMASK = ""
10:15.28twostupiddogsPREFERRED_PROVIDERS = "virtual/qte:qte virtual/libqpe:libqpe-opie"
10:15.32twostupiddogsPREFERRED_PROVIDERS += " virtual/libsdl:libsdl-x11"
10:15.36twostupiddogsPREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc-initial:gcc-cross-initial"
10:15.40twostupiddogsPREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}gcc:gcc-cross"
10:15.52twostupiddogsPREFERRED_PROVIDERS += " virtual/${TARGET_PREFIX}g++:gcc-cross"
10:15.56twostupiddogsMACHINE = "htcuniversal"
10:15.56twostupiddogsDISTRO = "angstrom-2007.1"
10:15.56twostupiddogsENABLE_BINARY_LOCALE_GENERATION = "0"
10:15.56twostupiddogsIMAGE_FSTYPES = "jffs2 tar"
10:15.56twostupiddogsBBINCLUDELOGS = "yes"
10:15.57twostupiddogsmaybe I should change something in the PROVIDERS...
10:16.25*** join/#htc-linux BabelO (n=kvirc@lun34-2-82-238-28-28.fbx.proxad.net)
10:16.52cr2i think my local.conf is in the xanadux CVS.
10:17.11cr2you must only adapt the path
10:17.18twostupiddogsok I'll try checking that out
10:18.02twostupiddogstnks
10:20.58cr2no. it seems to be an old version.
10:21.13cr2http://xanadux.cvs.sourceforge.net/xanadux/oe
10:23.25twostupiddogscr2: just to know, you use htcuniversal.conf or local.conf or both?
10:26.26cr2local.conf
10:26.37cr2i'll put my current version there.
10:27.10cr2gtk+
10:27.19twostupiddogsyep, 'cause I think that distro familiar-unstable isn't the right one...
10:27.19cr2that's just insane.
10:32.59twostupiddogsthe local.conf there looks pretty old...
10:33.28twostupiddogscr2: you there?
10:34.24twostupiddogsbbiaf
10:35.23cr2done.
10:35.38cr2gnome-common-2.4.0-r0
10:35.47cr2now i really say WTF ?
10:36.00*** join/#htc-linux ballessay (n=balles@client420.amh.kn.studentenwohnheim-bw.de)
10:37.01twostupiddogsagreed
10:37.51cr2ok, we will clean this crap away eventually.
10:38.24twostupiddogsok. what should I do to get the bulid done?
10:39.07cr2did you create a working directory ?
10:39.17cr2i have it in ~/stuff
10:39.32cr2not /stuff like in the oe docs.
10:40.03cr2libglade
10:40.08twostupiddogsyes I created /OE and then a build one
10:40.16cr2my eyes are hurt.
10:40.33cr2so your working dir is /OE ?
10:40.39twostupiddogsyes
10:41.06twostupiddogslike the angstrom sayd, I'll move it once it is ok.
10:41.20twostupiddogswiki I mean
10:41.23cr2so you have /OE/org.openembedded.dev
10:41.29twostupiddogsyep
10:41.46twostupiddogsand a /OE/build also
10:41.46cr2then create /OE/build/conf
10:41.53twostupiddogsdone
10:42.01cr2and put local.conf in this directory.
10:42.04cr2ok.
10:42.10cr2edit local.conf
10:42.18twostupiddogswhich one? the one in CVS?
10:42.32cr2get the one from CVS and edit it.
10:42.34cr2BBFILES := "${HOME}/stuff/org.openembedded.dev/packages/*/*bb"
10:42.42cr2should be for you
10:42.49cr2BBFILES := "/OE/org.openembedded.dev/packages/*/*bb"
10:43.16twostupiddogsI've already done it, but it complains about the familiar-unstable...
10:43.21cr2you may change this one too
10:43.24cr2DL_DIR = "${HOME}/sources"
10:43.43cr2huh ?
10:43.45cr2DISTRO = "angstrom-2007.1"
10:43.57cr2what local.conf do you have ?
10:44.02twostupiddogsok i missed the distro.
10:44.15cr2http://xanadux.cvs.sourceforge.net/xanadux/oe
10:44.24twostupiddogsthe one from xanadux cvs now
10:44.29twostupiddogswait tring a build
10:44.30cr2README needs an update too.
10:45.44twostupiddogsby the way, to use psyco should I get a 32bit version of perl? does it speed up the process a lot?
10:46.38cr2don't use psyco
10:46.52cr2i think it does not work on 64bit.
10:47.16cr2lkcl said it is not doing anything useful anyway.
10:47.31cr2ok. opie-image built.
10:48.17twostupiddogsconfiguring now...
10:48.32twostupiddogsbut not the qt though.
10:49.05twostupiddogsho, missed that, qt did configure ...
10:49.07twostupiddogstnx
10:50.23twostupiddogsqte_mt compile ...
10:51.29*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.250)
10:54.20twostupiddogsok as this is gonna take long, going to have a pizza for lunch.
10:54.29twostupiddogsbbl. cr2: thanks a lot
10:54.39cr2:)
10:58.40BabelOhi all
10:59.30BabelOcr2: is there any thing i can to for lcd resume ? another dump for spi maybe ?
11:00.59*** join/#htc-linux pleemans (n=peter@d51A5E76A.access.telenet.be)
11:06.22cr2BabelO: no, if you have a boardid5
11:08.32BabelOcr2: ok :( sniff i would like to help fo this :( i m adding gpio to sound
11:08.41cr2BabelO: i'm slowly thinking of opie2. that will require a qt4 adaptation of roadmap. when i'll be finished, i'll switch.
11:08.53cr2ok.
11:10.44BabelOcr2: i finish to add gpio and swithc to my OPIEII version adding gsmd instead of gnokii maybe, or i need to add a new HTC model to gnokii
11:11.42cr2i don't think it's wise to drop gnokii completely.
11:12.20cr2do you know how the greenphone gui looks like ?
11:12.59cr2lkcl has disappeared, and i'll better buy athena instead of the greenphone :)
11:13.39cr2imho, the greenphone gui look-and-feel should be cloned, so the users are not confused.
11:14.57BabelO:) athena wow, greenphone gui is really nice... they use xml approach to define gui and it is fully included in OPIEII too
11:15.37cr2ok, where can i see the screenshot ?
11:16.44BabelOthere is some screenshot in Qtopia documentation of themeview class
11:17.10cr2BabelO: ok. i'll remove bleabgel_audio.c, because it's obsolete.
11:17.15BabelOi ve tried greephone vmware demo too
11:17.20cr2hehe.
11:17.31BabelOcr2: ok and blueangel_battery is obsolete too
11:17.35cr2ok.
11:18.05cr2blueangel_leds is not nice, but we don't have a replacement yet.
11:18.45BabelOyes and we don't have same charging led as in wince
11:20.00BabelOcr2: http://doc.trolltech.com/qtopia2.2/html/qtopiatheming.html
11:20.17BabelOthere is some screen and themed xml
11:21.25cr2yes :)
11:21.46cr2blueangel_tsc2200.c
11:21.51cr2is it still needed ?
11:23.01BabelOcr2: yes it is setup of tsc2200 soc
11:23.41cr2ok.
11:23.43cr2menuconfig MACH_BLUEANGEL_AUDIO
11:23.50cr2this is obsolete now ?
11:24.00BabelOyes
11:24.14cr2ok.
11:24.25cr2menuconfig MACH_BLUEANGEL_BATTERY ?
11:25.04BabelOyes, i use it for blueangel_power ;)
11:25.26cr2maybe it should be renamed BLUEANGEL_POWER ?
11:25.44cr2MACH_BLUEANGEL_KEYPAD
11:25.50BabelOyes, i don't difference between power and battery :)
11:25.55cr2<PROTECTED>
11:25.55cr2<PROTECTED>
11:26.01cr2is it still true ??
11:26.39BabelOlet me try again keyboard, last time i try it, it works, but each time i press a key, got a lot of repeat
11:28.04cr2POWER "Does not work yet"
11:29.39BabelOhumm power works..
11:30.01BabelOit hang after some times because of ds1wm issue
11:30.20cr2ok.
11:30.25cr2DPRAM is broken ?
11:31.21BabelOyes i think, no dpram wwhen i try gprs
11:31.42cr2afaik nobody tried writing to PXA flash :) it may not work, and some gpio enable is needed.
11:31.52cr2no dpram or no ppp ?
11:32.06*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
11:33.24BabelOno ppp dpram is found and tts/8 is added
11:33.38BabelOs/ppp/ppp,/
11:33.40*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
11:34.02cr2ok, so it's buggy.
11:34.21cr2suspend  "Does nothing useful right now"
11:35.30cr2what should we do with PCMCIA ?
11:35.42BabelOcr2: yes suspend is not working because of LCD resume, if we comment out lcd_hw_off() function it seems to work
11:35.48*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
11:36.56BabelOpcmcia, i don't know, you have added missing gpio in htcblueangel_acx.c... on my platform, i ve used the both missing gpio to drive ACX power over pcmcia insert and eject
11:37.14BabelOand we can see acx card into pcmcia module of opie or gpe
11:37.23cr2ok.
11:38.22BabelOhow it is working on universal ? you can set up and set down easyly ?
11:39.06goxboxlivetest
11:39.23BabelOtest ok ;)
11:39.56goxboxliveI have ust installed the new kubuntu distro so i have to setup xchat again :-)
11:40.04goxboxlivehi btw
11:40.07cr2BabelO: yes. there are some programming bugs, but they are irrelevant in t his context.
11:40.34cr2hi goxboxlive. do you have a new notebook that does not crash because of overheating ?
11:40.45goxboxlive:-) no
11:41.00cr2goxboxlive: i'm thinking about athena :)
11:41.14goxboxlivemy good old ine, It's not that old either, it's just 2 1/2 year
11:41.17cr2BabelO: do we really need 159 modules ???
11:41.40BabelOcr2: 139 modules ;) but no not needed
11:41.43goxboxlivecr2: Are you going to buy it?
11:41.49BabelOneed to cleanup maybe
11:45.13*** join/#htc-linux twostupiddogs (n=towstupi@84.18.144.39)
11:45.53cr2goxboxlive: i'm thinking.
11:45.56BabelOcr2: asylumed say to me that it use BA with rndis connected to windowws host with a samba share
11:47.50BabelOcr2: athena demo video is really nice
11:50.48*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
11:50.53*** join/#htc-linux gox (n=goxboxli@176.84-48-210.nextgentel.com)
11:53.44cr2BabelO: but can one telnet over rndis now ?
11:55.58BabelOyes i think he can see a share on is BA in Windows
11:56.00BabelOso telnet is a formality
11:57.29cr2ok.
11:57.43cr2compiling the cleaned tree now.
11:57.50BabelOok ;)
11:58.10BabelOmaybe we have to remove drivers/input/touchscreen/tsc2200_ts.c too
11:58.24cr2can we revise the old ramdisk ?
11:59.15*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
11:59.33BabelOramdisk ? i don't use ramdisk
12:00.28cr2yes, but where do you install the modules ?
12:00.48BabelOon sd card
12:00.50cr2i'd like to have a fallback option.
12:00.59cr2imho it's a bad idea.
12:01.31BabelOcr2: why a bad idea to put modules on sd card ?
12:01.38cr2if we will get the LCD resume working, i'll think about linux flashing.
12:01.52cr2because the kernels change too often.
12:02.14cr2and the same image can be reused on multiple devices.
12:02.29cr2while the modules (even with the same name) are incompatible.
12:03.17BabelOwe can compile without setting kernel version module into it
12:03.24cr2i'd like to test on 4 devices without taking care about the modules.
12:03.49cr2you can't use pxafb from pxa27x on pxa26x, for example.
12:03.57cr2or will not be able soon ;)
12:04.29cr2ok, compiled.
12:08.04cr2you can update from CVS now.
12:08.50BabelOok i do that in another directory and if it works i use this new base
12:09.13cr2ok.
12:12.10BabelOyou update defconfig too ?
12:14.15cr2done.
12:17.46BabelOhow this ramdisk works ? modules are embedded into zImage, or it is a standard initrd ?
12:19.00cr2standard initrd
12:19.06BabelOcr2: do we have adcm i2c modules code somewhere ?
12:19.29cr2get one from hh.org, gzip -d, and mount as ext2 over loop
12:19.37cr2i think yes, i'll have a look.
12:19.58cr2i think wiki had a link.
12:22.34BabelOlink was removed
12:23.46BabelOhe he my hardrive is full, but lot of interesting thing ;) i have the patch locally ;)
12:24.03BabelOadcm2650 i2c module
12:24.09cr2look here
12:24.15cr2http://wiki.openezx.org/CodeAnalysis
12:24.28cr2it's also in the motorola a780 kernel
12:24.51cr2hm 2700
12:25.00BabelOhe he there is a 22c module and a video modules for this chips
12:25.02cr2and not very clean code.
12:25.22cr2yes, the i2c side is easy.
12:25.39cr2ati capture port is painful.
12:26.37BabelObut it is not in a780 module, there is adcm2700 and 3800 but no 2650
12:32.00BabelOcr2: i send to you 2.6.9 kernel patch for adcm and pxa_camera
12:32.15BabelOit is old patch from link in the wiki
12:33.00cr2ok, maybe it's also available somewhere else ?
12:34.18BabelOit is to keep it somewhere, maybe i had adcm2650 i2c chip detect if it is not hard
12:35.03cr2ok, let's find the latest version, and use it locally.
12:35.22cr2CONFIG_BLUEANGEL_CAMERA or something like that.
12:35.43BabelOyes
12:38.19*** join/#htc-linux twostupiddogs (n=towstupi@84.18.144.39)
12:38.21BabelOlast time i try to apply this patch, got lot of error
12:38.37BabelObut if i remember, i can load adcm module
12:41.41cr2check the a780 patches
12:41.43cr2i2c_adcm2650_inc_use
12:41.58cr2i think these are not needed anymore
12:42.01*** join/#htc-linux twostupiddogs (n=towstupi@84.18.144.39)
12:42.30*** join/#htc-linux twostupiddogs_ (n=towstupi@84.18.144.39)
12:42.34*** part/#htc-linux twostupiddogs (n=towstupi@84.18.144.39)
12:43.21*** join/#htc-linux twostupiddogs (n=towstupi@84.18.144.39)
12:43.23*** part/#htc-linux twostupiddogs_ (n=towstupi@84.18.144.39)
12:44.34*** join/#htc-linux rob__w (n=bob@p213.54.35.44.tisdip.tiscali.de)
12:44.59cr2this driver uses pxa27x-cif
12:45.09cr2and needs a big rewrite.
12:45.52BabelOon ba we need imageon instead of this ?
12:46.55cr2yes.
12:46.59cr2+// Sets the bit to 60 Hz; sample duration is 25
12:46.59cr2+WS( 0x0e, 0x19);
12:47.16cr2you should do extensive i2c traces,
12:47.27cr2otherwise we can blow this sensor ;)
12:48.23cr2it's probably easier to document the chip using this driver first.
12:48.52BabelOyes, but first step is to have a loadable module for this and can detect chip when powered on
12:49.14cr2nice code:
12:49.18cr2+// Note!! Document is wrong. 0x0076 shall be 0x0074 instead.
12:49.18cr2+RL( STATUS_FLAGS, 0x0008, 0x0008 );
12:49.19psokolovskycr2: good cleanup on himalaya! I assume you didn't kill too much ;-)
12:50.02cr2psokolovsky: no, the drivers are the same as on blueangel, and the gpio config is documented.
12:50.09psokolovskycool!
12:50.20psokolovskyI hope uni is next ;-)
12:50.57cr2:)
12:51.04cr2asic3 ?
12:52.14cr2this &foobar_asic3.dev stuff is sick. can we reuse the same trick as in asic3_mmc with pdev->dev.parent ?
12:52.16psokolovskycr2: I mean deprecated drivers in htcuni dir
12:52.20cr2ok.
12:52.29psokolovskycr2: reuse where?
12:52.43cr2in other asic3 slave drivers.
12:53.09psokolovskycr2: which exactly?
12:53.28cr2i will really need asic3_spi and asic3_pwm
12:53.35cr2ok, it's a bit another issue.
12:54.00psokolovskycr2: well sure, use parent-> in them. they just don't exist yet ;-)
12:54.31cr2i'm asking because you are doing a major asic3_base cleanup
12:54.47cr2maybe we should keep in mind the asic3 API too.
12:56.49cr2BabelO: we can add the adcm2650 headers anyway.
12:57.09cr2register definitions & such.
12:59.02psokolovskycr2: I do syntactic cleanup mostly, preparing it for mainline submit.
12:59.34psokolovskycr2: I want to renaming GPIO accessors and add timebase for LED setter though.
13:00.29bd2psokolovsky, I guess it's pointless to think about mainline stuff, before we resolve dependency issues, no?
13:00.49psokolovskybd2: Hi! which deps?
13:01.12cr2bd2: i agree that it's too early to include it into mainline.
13:01.19bd2psokolovsky, look for hx4700_power2.c you can't merge it with hx4700.c because of asic3 stuff
13:01.56psokolovskybd2: so what? h4000_udc is also kinda not mergeable because of that. so what?
13:02.06cr2hx4700_acx too.
13:02.51cr2i only wish there was a better asic3 -> such_driver communication mechanism.
13:02.53bd2psokolovsky, so we should implement something in soc core, that will register asic3 dependant *devices* only when asic3_base actually loaded
13:03.16cr2bd2: they can do request_module(asic3_base)
13:03.38cr2and fail to load if it fails.
13:04.17bd2cr2, asic3_base module registers base driver. the driver needs asic3 device, which should be loaded at proper order too
13:04.36cr2ok.
13:04.49psokolovskybd2: I see no connection first of all, secondly, it's crappy-linux's not our problem. stupid linux doesn't provide any dependency management in kernel, offloading it to userspace. so, let's have it in userspace.
13:05.00bd2so, it's pointless to request asic3_base, because it just registers driver (which may, or may not bound to the device)
13:05.58bd2psokolovsky, we can pass to platform data devices which should be registered after asic3_probe()
13:06.14cr2well, how do we solve it ? request_module() is a usespace way of doing things.
13:06.27psokolovskybd2: what you mean "we can"? we *do*!
13:07.50cr2psokolovsky: ? can you boot with asic3 not loaded ?
13:08.06bd2psokolovsky, hmmmm. wait wait. so, we can put hx4700_power to hx4700_asic3_devices, and it will load it in proper time??
13:08.12psokolovskycr2: I have no idea, never tried.
13:08.33psokolovskybd2: kinda can, if there're no other pre-dependencies.
13:09.06bd2hmmm.. I should really try that, thus we *could* merge power to hx4700
13:09.09psokolovskybd2: issues is exactly few pre-dependencies, and the fact that we need to make "proxy" device and driver, instead of mere module.
13:09.09bd2.c
13:09.55psokolovskybd2: see for example h4000_bl.c vs hx4700_bl.c. mine is *driver*. yours is *module*
13:10.48cr2psokolovsky: all the slave drivers should oops, i guess.
13:10.51bd2s/*driver*/*device*/ ;-) but yeah
13:11.17bd2psokolovsky, so, you can put it in h4000.c... that's great
13:11.35bd2I'll do it for hx4700, including power stuff
13:11.52cr2because they attempt to manipulate the asic3 registers directly, which is not mapped.
13:12.22*** join/#htc-linux WizMaui (n=WizMaui@62.112.90.250)
13:12.38psokolovskybd2: ah damn, yeah, it's no longer a driver ;-). so well, you know, static loading issues of asic3 vs friends are solved now. and module loading is compeltely another matter.
13:13.31psokolovskycr2: what exactly wants to manipulate? and I wrote about that some time ago to k-d. there's way to solve it too.
13:13.37bd2yup.. so, everything is great, I guess. sorry for the panic
13:14.07psokolovskycr2: solve, for static case. because there's nothing to solve for module case. just load modules in write order, voila.
13:14.14psokolovskyok
13:14.49cr2psokolovsky: if a random driver calls asic3_*** , and asic3_base is not registered, then it's an oops()
13:14.58cr2ok, but we are not doing it right now.
13:15.29cr2htcuniversal_acx removal crashes the machine for a simmilar reason.
13:15.33bd2psokolovsky, yup. but for driver to call anything asic3_**, it should be bound to device. And devices which depends on asic3, should be passed as platform_data
13:15.41cr2i guess hx4700_acx will crash too.
13:15.46bd2s/psokolovsky/cr2/
13:16.02psokolovskycr2: so we should (load modules in the right order; note that modprobe doesn't necessarily should be able to do that)
13:16.34cr2yes, that's the problem.
13:16.48psokolovskycr2: can you give more details why uni acx crashes?
13:17.02cr2yes, i'll look at the code now.
13:17.45bd2because hx4700_acx.c : return platform_device_register( &acx_device );
13:18.19bd2thus it's registers device itself. instead it should be passed as child device to asic3
13:18.50cr2mem.c:2224         (void) hwdata->start_hw();
13:18.57bd2s/hx4700/ba/
13:19.13cr2this pointer is dead if foo_acx is removed.
13:19.50psokolovskybd2, cr2: good catch! let's fix it.
13:22.10psokolovskybd2: and I don't even want to tell how long I want to cleanup BT crap in hx4700.c/*_core.c ;-)
13:22.30cr2mem.c:5164 (void) hwdata->stop_hw();
13:22.37cr2it's a point of failure too.
13:24.34psokolovskycr2: ok, so as bd2 points out, there should no be hx4700_acx.c/htcuni_acx.c/etc. in the first place.
13:27.00bd2psokolovsky, yup. but actually hx4700_acx.c seem to not use asic3. but htcuni/ba do use asic3, thus they must be asic3's child devices
13:27.28cr2bd2: good idea.
13:28.24bd2though, hx4700_acx should be placed in hx4700.c too. just for consistency/good sense
13:28.39psokolovskybd2: yes. but we must adopt consistent pattern here. so, apparently all machines must have device registration as machine def. code - either directly, or via SoC child devices. But never as separate linux modules (but of course, can be in separate file).
13:28.46psokolovskyyep
13:28.54cr2there should be a more general solution.
13:29.20psokolovskygeneral solution for what?
13:29.34cr2psokolovsky: a module is not allowed to oops even if a user removes7inserts it a a random time.
13:30.26cr2general ? i have a cpld in hermes which replaces asic3. should i do the slave driver model for it too ?
13:30.28psokolovskycr2: once again: hx4700_acx or htcuniversal_acx or anything like that MAY NOT be module.
13:31.03cr2ok, that's a point.
13:31.10psokolovskycr2: yes, you have. Alternatively, we can add to linux generic device dependency model. But *you* will push it to mainline ;-F
13:31.43cr2:) it's not going to be accepted.
13:31.49bd2:-D
13:32.48cr2because it's a business of a module A to know if it needs module B, and that can be solved in userspace.
13:33.04psokolovskyyep ;-)
13:36.10cr2mem.c (acx) obviously needs foo_acx, so it's not allowed to be a module by your logic :)
13:37.12cr2another question. can you confirm that hx4700 enables CDEX_SDBUS clock ?
13:37.52cr2because i don't see it on other 4 asic3-SD using devices
13:38.10psokolovskycr2: not by my logic, but by mem.c's logic ;-) I just accept that logic ;-)
13:38.16cr2btw, what about h4000 ?
13:38.20cr2LOL.
13:38.24bd2mem.c is *driver*, thus it can be a module
13:39.09psokolovskycr2: h4000 & hx4700 work pretty well with asic3_mmc as is. I dunno much about internal settings of asic3-sd ;-)
13:39.36psokolovskycr2: see asic3_base.c:901:
13:39.39cr2bd2: ok, but it blows on null pointers. and it's an obvious bug.
13:39.40psokolovsky/* XXX: should get correct SD clock values from pdata struct  */
13:40.10cr2psokolovsky: run "dump asic3" if you have wince installed :)
13:40.16cr2that's all what i need.
13:40.27bd2cr2, sure. the question is why pointers becoming null
13:40.34psokolovskycr2: it just doesn't expect a device to be gone behind its back
13:40.50psokolovskycr2: will do a bit later ;-)
13:40.57cr2yeah, but goxboxlive did it all the time .
13:41.18bd2psokolovsky, indeed. but not device it's bound to. but device/driver which used by foo_acx
13:41.35cr2and that should be ok.
13:42.19psokolovskybd2: yep, so foo_acx is unloaded, pointer starts to point to "somewhere", then in crashes/hangs
13:43.38bd2cr2, psokolovsky, the only thing mem.c is wrong, is thet is calls stop_hw (not start) at module_exit function, instead of acxmem_e_remove (i.e. in driver's remove() handler)
13:44.02psokolovskybd2: hm, ok, maybe that too ;-)
13:44.53bd2yeah, but commed at acxmem_e_cleanup_module() (which calls stop_hw) tells about that it's not all that easy
13:45.16psokolovsky;-)
13:45.29psokolovskylet's just disallow foo_acx to be module ;-)
13:46.18psokolovskynote btw that it can't done right away either, due to botched Kconfig ;-D
13:46.22bd2sure. but mem.c needs some fixing anyway (not a priority at all, because whole acx stuff is not in mainline yet)
13:46.32psokolovskyso, instead indeed should be moved towards machine.c ;-)
13:47.05*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
13:48.58bd2psokolovsky, ready to proceed x/50 patchset? ;-)
13:49.32psokolovskybd2: what?! 8-o
13:50.13bd2hehe.. yeah, that's diff to my battery tree ;-)
13:50.35psokolovskyoh my. but you sent yesterday */10 one?
13:50.57bd2yea, that's another patchset ;-)
13:52.11bd2too bad we aren't on git rails yet.. merging would be much easier ;-) I'll send it soon, please test it in spare time, and feel free to commit whole stuff as "syncing with battery work tree"
13:52.11psokolovskyoh my ;-)
13:52.46psokolovskybd2: well ok, if iit's really required. or we can do it a bit later (committing I mean) ;-)
13:53.34bd2psokolovsky, sure. but then it will grow to x/100 patchset ;-))
13:53.46psokolovskyok ;-)
13:56.11psokolovskybd2: I hope you also monitor commits/diff with CVS, because there were few commits to battery-related files
13:57.16bd2psokolovsky, yup. I've done rebaseing few minutes ago
13:57.22psokolovskyok
14:15.22bd2ok, sent. I hope I've not exceed size limit
14:21.32bd2crap, it seems I've really exceed. base64 encoding increased mail size
14:25.06psokolovskybd2: nothing arrived so far at least
14:26.33psokolovskycr2: so, I'm goint to kill ipaq-asic-led.h, and move stuff directly to ipaq-asic2.h/ipaq-asic3.h. sounds good?
14:52.50cr2yes.
14:52.59psokolovskybd2: ok, both versions arrived ;-)
14:53.05psokolovskycr2: ok, committed
14:53.10cr2great.
14:55.04bd2psokolovsky, %-O
14:55.43bd2probably some mailing list admin got notified about size exceed email
14:56.50psokolovskyyep ;-)
15:02.29bd2kick me now if I promised something to do soon, and forgot. going to dig in adc (ssp) stuff, thus might become unresponsive for some time :-))
15:10.10psokolovskybd2: nope, all's ok ;-)
15:11.14psokolovskyand time to make new tag...
15:16.24Kevin2Hi
15:29.47cr2Kevin2: hi. i have a patch and a question for you.
15:32.01Kevin2cr2: Ok.
15:33.20cr2why do you use 16MHz clock on hermes ?
15:34.10cr2the haret patch implements 'playsound N' function.
15:34.18Kevin2cr2: Not sure what you mean - where do I do that?
15:35.05Kevin2cr2: Send the patch to haret@handhelds.org -- sounds like a useful feature (no pun intended).
15:35.52cr2ok :)
15:36.43cr2s3c24xx_init_clocks(12000000);
15:36.46goxboxliveKevin2: I have made a linboot.exe but it isent not executeable when i try to launch it in wince? Could this be that i skipped the ramdisk in it?
15:37.03cr2what value do you have here ?
15:38.01Kevin2cr2: I use s3c24xx_init_clocks(16934400);
15:38.21Kevin2because that was your recommendation - I haven't really looked at the clocks yet.
15:39.10Kevin2goxboxlive: No, you don't need an initrd.  Can you create the file earlyharetlog.txt and see what it says?
15:40.25goxboxliveKevin2: Ok, yes i can try that.
15:40.26Kevin2goxboxlive: Can you do "cvs up" also.  I just added a patch which will cause commands being executed to get logged.
15:41.16Kevin2What was your make line?
15:43.19cr2Kevin2: sent.
15:44.51cr2Kevin2: i know a wince function in a dll, how can i dump r0,r1,r2 when it is called and catch it's return value ?
15:45.43*** join/#htc-linux pleemans (n=peter@d51A5E76A.access.telenet.be)
15:45.52cr2imho you should try to set the clock to 12MHz -> s3c24xx_init_clocks(12000000);
15:46.17psokolovskycr2: now point me to binary which does "dump asic3" ;-)
15:46.19Kevin2cr2: On Hermes or PXA?
15:46.22psokolovskyKevin2: Hi!
15:46.32cr2and if it will be wrong, we need to fix the CVS.
15:46.34Kevin2Hi psokolovsky
15:46.54cr2psokolovsky: http://jornada820.sf.net/files/haret
15:47.05psokolovskyok, thanks
15:47.18cr2the asic3 code is so terrible that i don't want to port it to the mainline.
15:47.42goxboxliveKevin2: after make (to build haret.exe) i ran: make linload KERNEL=zImage SCRIPT=startup.txt with mt zImage and startup.txt in the root of haret
15:47.46cr2Kevin2: on hermes.
15:49.04Kevin2goxboxlive: What is in your startup.txt?  Is the last line "ramboot"?
15:49.17goxboxliveKevin2: No, it's like a regular one with boot2
15:49.46cr2Kevin2: sorry. 12MHz on hermes, and to trace a function on PXA.
15:49.53Kevin2cr2: I haven't implemented arch generic break points.  Only pxa can do it.
15:50.34psokolovskycr2: doesn't run. again hardcoded phone dependencies?
15:50.57cr2psokolovsky: hm. yes. i'll remove it.
15:51.02Kevin2cr2: set insn 0xaddr ; wi 99
15:52.12Kevin2you can change insnreg1 and insnreg2 to display any two registers.  It doesn't currently support showing a third.  You could modify the code to do so, or you could set a second breakpoint using insn2, insn2reg1, insn2reg2.
15:53.07cr2Kevin2: thanks.
15:53.25cr2psokolovsky: removed the RIL library now.
15:54.33psokolovskycr2: ok, this starts
15:55.10Kevin2goxboxlive: Haret is lacking good documentation.  You need to use "ramboot" to boot the kernel stored in the exe.
15:55.24goxboxliveKevin2: ok thx, i will try that
15:55.41Kevin2goxboxlive: see docs/linboot.txt
15:57.22goxboxliveKevin2: I thought that was just needed when using a initrd.
15:58.17Kevin2goxboxlive: You should really only need to run:  make linload KERNEL=my-zimage
15:58.30*** join/#htc-linux eremias (n=fdsfs@ACB0ADA8.ipt.aol.com)
15:58.31psokolovskycr2: http://pastebin.ca/451489 - h4000
15:58.32Kevin2The initrd defaults to empty and the script defaults to txt/linload.txt
15:58.54psokolovskycr2: on hx4700, gnuharet segfaults on dump asic3 %)
15:58.54goxboxliveo
15:58.56goxboxlivek
15:59.58cr2psokolovsky: hm. really. SDBUS is on. i guess it's the same on hx4700.
16:00.19psokolovskycr2: tried again, segfaults.
16:01.06cr2check the latest version, i've made an update.
16:03.15cr2so we have 3 combinations in wince.
16:05.23cr2btw, your wince h4000 setup also does not match the current asic3_mmc setup.
16:09.00goxboxliveI have asked france at hh.org if we could host files/images at hh.org and he said it is ok. I was thinking that we could have a common one for the htc-pxa devices.
16:09.48cr2goxboxlive: i think we are close.
16:09.49goxboxliveBut to make it i have ti send france my public ssh key.
16:10.03goxboxliveHow do i make such a key?
16:10.21cr2generate one.
16:10.46cr2man ssh-keygen
16:11.18goxboxlivecr2: I didnt think about a common opie-image and s, i was thinking about a common place to have all our files. I think it is bether to have it at hh.org than at gnulinux.biz since the *biz ftp server is private
16:11.23goxboxliveok thx
16:11.36cr2i think my key is 8192 bits. just for fun ;)
16:12.04cr216384 will probably work too.
16:12.52cr2ok.
16:14.58cr2psokolovsky: i'm inclined to create a ${MACHINE}_asic3.c and do all the asic3-related stuff there.
16:15.10goxboxlivecr2: so i should send france this key? id_dsa.pub
16:15.19cr2yes.
16:15.29psokolovskycr2: create for what?
16:15.55cr2to separated the machine init from asic3 init.
16:16.23goxboxlivecr2: But what if i have two machines i would like to connect to hh.org? SHould i make two then?
16:16.25cr2i'm already removing all device driver init to the appropriately named files.
16:16.33psokolovskycr2: I don't understand. it is already separated.
16:16.49cr2goxboxlive: you can connect from any machine that has your private key.
16:17.14psokolovskycr2: that's strange, because we just recently spoke with bd2 that it's time to merge all stuff into single machine file ;-)
16:17.42goxboxliveok, so if i just copy my id_dsa.pub over to my other machine then that will be enough. good
16:18.38cr2psokolovsky: it's for testing purposes. not each device is at the same stage as hx4xxx
16:19.36cr2eventually we may put all htc devices in a htc subdir, like the 'eseries'.
16:19.48psokolovskycr2: I think it's superfluous. I alreday suggested extending platform_data structures, if there're additional info to be passed.
16:20.41cr2it is not linked to each other.
16:21.58*** join/#htc-linux eremias (n=fdsfs@ACB0ADA8.ipt.aol.com)
16:22.34bd2merging stuff is exactly matter of stable enough machines.
16:25.06psokolovskyyep, I just try to hope all active ports in cvs are on ~same stage, and we can move in one front, and elaborate how we do stuff, not fall back to older state ;-)
16:25.52psokolovskylike goxboxlive said, otherwise it feels like one step ahead, 2 steps back.
16:25.56psokolovskybut nevermind
16:26.53bd2yup. And actually, sparating *devices* to modules makes a sense only if platform_data stuff is about to debug. because usually driver is being debugged, not device (which is usually just two structs: device + its platform data)
16:27.57psokolovskycr2: http://jornada820.sourceforge.net/files/haret/gnuharet-200704211800.exe still segfaults
16:29.17cr2bd2 psokolovsky: i can't boot on himalaya from the SD. it's some timing issue, so i'm trying to debug asic3_mmc which works perfectly on many other machines. and there are some differences. or course all the research will come back to the common driver.
16:29.38cr2psokolovsky: ok, then it's some different problem ;)
16:29.54psokolovskycr2: so it's not like different asic3 reg values after all?
16:29.55cr2psokolovsky: can the dump the CDEX register with 'pd' ?
16:30.11psokolovskycr2: especially if you tell me address ;-)
16:30.28cr2hmm. bus_shift is 1...
16:30.44psokolovskycr2: ok, will look up myself ;-)
16:30.57cr2http://wiki.xda-developers.com/index.php?pagename=ASIC3
16:31.09cr2i need to move this page to hh.org
16:31.59psokolovskycr2:
16:32.00psokolovskyHaRET(1)# pd 0x0c000500 0x20
16:32.00psokolovsky0c000500 | 000563cb 00000000 00000000 00000000 | .c..............
16:32.00psokolovsky0c000510 | 00000000 00000000 00000000 00000000 | ................
16:32.07cr20x0c000000 + 0x500
16:32.09cr2ok.
16:32.26cr2cdex is 63cb, sel is 0005
16:33.01cr20110.0011.1100.1011
16:37.20cr2spi off, pwm off, leds on, SDhost on, sdbus off.
16:37.24cr2hmm.
16:37.40psokolovskycr2: and sd clock different?
16:38.27cr2so h4000 and rx3000 have sdbus on, everything else sdbus off.
16:39.07cr2and sel can differ.
16:39.41cr20x5 vs 0x7 if sdbus is on.
16:40.25cr2so if sdbus is set on by wince, the speed is set to 24MHz.
16:40.27psokolovskycr2: ah, ipaq-asic3 says "sel" for sdio, so they kinda match...
16:41.16cr2the asic3_mmc has sdbus on, 24MHz off (=12MHz).
16:41.42cr2that's the only visible difference.
16:42.08cr2well, and this code too.
16:42.11cr2<PROTECTED>
16:42.11cr2<PROTECTED>
16:44.09cr2is asic3 capable only of 3.3v ?
16:44.25cr2ASIC3_MMC_REG(host, SD_CONFIG, SDHC_Power1) = SD_CONFIG_POWER1_PC_33V;
16:45.09cr2probably i need to check it for different cards. also for sdio.
16:48.13Kevin2cr2: Would it be possible to add the asic3 register definitions to haretconsole (eg, in memalias.py)?  This would make it simple to monitor those things under mainline haret.
16:52.42cr2Kevin2: good idea. is it possible to name the bits ?
16:52.52cr2i've zero python experience.
16:53.09cr2all names are in include/asm-arm/hardware/ipaq-asic3.h
16:53.10Kevin2cr2: Yes.  See Regs_s3c2442.
16:53.16cr2ok.
16:53.46Kevin2You shouldn't need any python experience - you just need to populate the variable with register addresses and bit names.
16:54.07cr2yes, i've got it.
16:55.01cr2Kevin2: there are some power-management related structures and defines missing from cegcc. where should i put them ?
16:57.08Kevin2We need to push them to the cegcc folks.  But in the meantime, you can put them into a header in include.  Use the same header the MSN docs say they should be in, and put #include_next <header> at the top of the file.
16:57.24cr2ok.
16:57.55cr2Kevin2: memalias.py obviously needs to be per-machine.
16:58.23cr2because the asic3 register locations depend wildly on a machine.
16:59.00Kevin2It is - RegsList['Hermes'] = Regs_Hermes - will add the registers defined in Regs_Hermes for the machine that identifies itself as "Hermes".
16:59.40cr2ok.
17:21.22*** join/#htc-linux twostupiddogs (n=towstupi@62.123.180.130)
17:23.59Kevin2cr2 / psokolovsky : See http://www.handhelds.org/hypermail/haret/current/0861.html
17:35.31Kevin2I'll be back later.
18:13.27*** join/#htc-linux MrVanx (n=chatzill@82-69-60-250.dsl.in-addr.zen.co.uk)
18:41.20*** join/#htc-linux tudenbart (n=willi@xdsl-213-196-240-174.netcologne.de)
19:11.34*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
20:31.55*** join/#htc-linux Ranpha1 (n=Ranpha@hlm-n-73ed.adsl.wanadoo.nl)
20:58.54*** join/#htc-linux goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
21:05.01cr2goxboxlive: does your new haret boot ?
21:06.33goxboxlivecr2: i havent testet it yet. Since i setup my laptop to day i havent had time.
21:07.52cr2ok.
21:08.15goxboxliveand also cdgcc is failing when i try to compile it on my laptop
21:08.52goxboxliveit compiled with debian, but with kubuntu it failes. Probably missing some libs
21:23.39goxboxlivecr2: tested linload now, and it works
21:24.17goxboxliveKevin2: Yes with ramboot in startup.txt linload boots. Great, thx.
21:26.05goxboxlivecr2: Seems like it can be a problem to host files at hh.org. Rene says that we also should host the source to our images because of GPL.
21:30.18cr2sounds a bit overzealous, but ok.
21:30.30cr2post them at sf.net ?
21:30.46cr2i don't know hot to do it, btw.
21:34.23goxboxlivei guess we can host files at linuxtogo, but since our kernel source is at hh.org i thought it was great to have it at same place.
21:34.43*** join/#htc-linux alsuren (n=alsuren@host86-148-18-74.range86-148.btcentralplus.com)
21:34.43*** join/#htc-linux Whacko (n=Whacko@s5593e8a2.adsl.wanadoo.nl) [NETSPLIT VICTIM]
21:34.44*** join/#htc-linux Kevin2 (n=Kevin@207-237-65-88.c3-0.avec-ubr12.nyr-avec.ny.cable.rcn.com) [NETSPLIT VICTIM]
21:34.44*** join/#htc-linux ljp (n=lpotter@203.94.178.46)
21:34.58cr2btw, i have compiled opie today.
21:34.59goxboxlivegood
21:35.01cr2in includes tons of completely irrelevant stuff
21:35.03goxboxlivewithout any hacks?
21:35.09goxboxlivedoes it, i dint know
21:35.16cr2beginning with gtk/atk/pango etc, and even such things like gnome-whatever ;)
21:35.17cr2without any hacks.
21:35.18goxboxliveYes i have seen it, i think it is because of dbus
21:35.20cr2imho the bluez-utils should be removed from the distro
21:35.20goxboxlivewhy?
21:35.20cr2unless somebody fixes the source.
21:35.20goxboxliveplace a bug at OE
21:35.20cr2because bluez-utils have nothing to do with gtk.
21:35.24cr2if comebody can't type 'int' instead of 'gint' that does not mean we should compile a lot of irrelevant software.
21:35.26goxboxliveok
21:35.39cr2i don't want to engage in opie oe bugfixing.
21:35.58cr2i prefer to fix opie2 instead and write the phone gui for it.
21:36.27cr2i'm also working on the qt4 compatibility layer for roadmap.
21:36.36cr2so it can be included in opie2.
21:36.51goxboxliveok
21:37.24cr2we talked with BabelO today, and will probably use gsmd for opie2.
21:38.45goxboxliveok, that sounds good. Has he worked on Opie2 lately?
21:39.01goxboxlivehas he done any progress?
21:39.11cr2don't know but he plans to work.
21:39.39goxboxliveSeems like no one is intrested in Opie2
21:39.53goxboxliveIt isent in OE yet, and nobody is talking about it
21:40.37cr2i need to copy some stuff from the virtual machine to have a normal setup.
21:40.54cr2openmoko does not compile from oe too.
21:41.15cr2git pull fails for me since 1 month and nobody cares.
21:43.18goxboxlivewell, it might be that no one is aware of it.
21:43.35goxboxliveYou have to place a bug so they are informed about it.
21:43.44goxboxliveHave you tried this?
21:44.13goxboxlivehttp://wiki.openmoko.org/wiki/MokoMakefile
21:47.00cr2hm. it will setup its own tree ??
21:47.33goxboxliveYes, fully automatic, but you have to abort change machine in local.conf before it start to build the image.
21:48.06goxboxliveAnd it also creates openmoko distro insted of angstrom (eabi vs non-ebai )
21:48.53cr2ok, probably it's too much for me :)
21:50.11goxboxlive:-)
21:50.23cr2goxboxlive: is it possible to read the "other" rtc ?
21:50.39goxboxlivewhat do you mean?
21:50.44cr2do we have this chip on the motherboard at all ?
21:50.59cr2sable aka paq69xx has it.
21:51.21cr2the wince kernel on universal has software support for it.
21:51.35goxboxlivei dont know, we are using two versions as far as i know
21:51.47cr2sa1100-rtc
21:51.54goxboxlivebut i dont know wich one is the right to use
21:51.58cr2i'm talking about the i2c chip.
21:52.45cr2you can just load the driver and check.
21:52.57cr2or even use i2cdump.
21:53.16cr2ok. maybe i'll try it myself eventually.
21:54.10goxboxliveyes i think that is better, i don't know what to look for anyway
21:54.50cr2:)
21:55.10cr2what do you think about creating a new eabi ramdisk ?
21:55.33*** join/#htc-linux MrVanx (n=chatzill@82-69-60-250.dsl.in-addr.zen.co.uk)
21:56.01cr2we have an old .12 ramdisk for blueangel and the apache ramdisk by Kevin2.
21:57.07goxboxlivewell, do we rely need one?
21:57.49cr2for the installation, and for the modules.
21:58.48cr2goxboxlive: does openmoko-dialer support PIN ?
21:58.56goxboxliveBut how will that help us for the installation. A user will still be neded to create a linux partition on his SD card
21:59.32cr2you can do it from the ramdisk ?
21:59.45goxboxlivecr2: I have never tried the pin stuff. I am not using it wheni have tried it out. I can try now
22:00.02cr2the blueangel ramdisk even has an Xserver :)
22:00.42cr2somebody at xda-dev asks where to set a pin and enter the provider.
22:01.26goxboxliveok, i am trying it now
22:04.54goxboxliveNo does not seems like pin os working in opie/openmoko-dialer
22:05.30cr2ok, does it work on neo1973 ?
22:05.38goxboxliveno idea
22:05.59*** join/#htc-linux RoEn_PC (n=roen@p54A6728E.dip.t-dialin.net)
22:06.35goxboxliveif it did it would have been working on universal too. It might be that it works with openmoko but i haven't tried it
22:07.26cr2it's a pure AT gsm issue, so i don't see a reason why it fails.
22:07.44goxboxliveIf we make a ramdisk, and if there are some updates how do we update the ramdisk, do we have to make a new one? in example bluez
22:08.10goxboxliveAre we able to build ramdisk in OE?
22:14.48cr2don't know, but it's probably not an issue.
22:15.26cr2i'll try to unpack the busybox.ipk to the ramdisk and write some minimal scripts.
22:16.02cr2i'm curious if we can do a 16MB ramdisk, and what are the actual limits.
22:16.12goxboxliveok
22:16.33cr2there was a 4M limit on the compressed initrd, but i think Kevin has solved the problem.
22:16.46goxboxliveok
22:17.03cr2going to bed now. good night.
22:17.08goxboxlivegood noght

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.