IRC log for #htc-linux on 20080703

00:02.29gingeI changed in on the server for your next build.
00:02.35gingeshould work a little smoother now
00:05.02gingedcordes: did you try renaming libril-reference to the original one?
00:15.02martin__dcordes: you might as well commit the current kaiser-smd.c
00:15.32martin__anything coming out of this smd.c splitup is going to be a long way off working for a while probably
00:20.26*** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbfcb39.pool.einsundeins.de)
00:21.14dcordesmartin__: everything up to date in git
00:21.34dcordesginge: you updated the script at the same URI?
00:25.13gingeyeah
00:27.09dcordeshttp://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm
00:27.32dcordeswould be cool if premy could provide the polaris stuff
00:27.49dcordesmartin__: I put the kaiser-smd.c from your server. 1:!
00:27.51dcordes1:1
00:31.18martin__ok cool
00:43.02dcordesginge: does the loopback interface come up for you automatically?
00:43.17gingeyeah, should do
00:43.50dcordesdoesn't here. only have the ppp after running the script.
00:44.05gingeI have nothing before and only ppp after
00:44.33dcordesso no loopback interface at all?
00:44.45gingeno, it appears not
00:44.59dcordesso ifup is not called
00:45.07dcordesshould we put it in the script?
00:45.19dcordesoh wait that's something that should be done in OE
00:45.21gingewhy not put it all in init
00:45.26dcordesyea
00:51.51*** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au)
00:56.08gingegoodnight
01:13.11*** join/#htc-linux andy (i=andy@ool-45718cdd.dyn.optonline.net)
01:14.19*** join/#htc-linux Metal3d (n=patachou@ALyon-257-1-162-64.w90-48.abo.wanadoo.fr)
01:14.22Metal3dhello
01:14.49Metal3dexcuse me, I've got a HTC pharos... is it possible to boot linux ?
01:15.02Metal3dbecause i've a MTYPE error with HaRET
01:16.34dcordeswhat are you trying to boot?
01:16.58Metal3dHaret universal
01:17.22Metal3dhttp://www.linuxtogo.org/~htcpxa/htcuniversal/index.html
01:17.40Metal3d--> http://www.handhelds.org/moin/moin.cgi/UniversalHowtoInstallLinux
01:19.18Metal3dI use http://www.linuxtogo.org/~htcpxa/htcuniversal/images/ramdisk/Ramdisk.cab
01:20.30dcordespharos is omap850, universal is pxa
01:21.00Metal3dyou mean i can't use linux on my pharos ?
01:21.17dcordesyou can't use the htcuniversal linux for your pharos
01:21.35Metal3dwhat have i to use ?
01:21.45dcordestry booting a kernel that was made for an omap850 device. I usually refer to the linwizard project at #linwizard
01:22.03dcordeshtc wizard is for omap850 and the project is vital
01:22.11Metal3dok
01:22.13Metal3dthans
01:22.16dcordesI can't help you much with the omap stuff, sorry
01:22.17Metal3dthanks
01:22.24Metal3dno prob
01:26.00Marexjeez :S
01:29.18Marexmmc in mainline is broken for some cards :(
01:32.22Marex_WAS_ broken ;D
01:34.17dcordesmartin__: hi, you did some palm improvements?
01:35.28Marexdcordes: what do you mean ?
01:37.30dcordesit _WAS_ broken ;D sounds like you did fix it
01:39.37*** join/#htc-linux Othello (i=Magorium@gateway/tor/x-0b7fb5f5038888e1)
01:41.51dcordesand since you're the palm guy I thought you probably meant you updated palm mmc stuff
01:42.01dcordesbut sorry for bothering
01:42.04dcordesneed some sleep
01:45.41Marexah that ... yea
01:57.49*** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au)
02:54.33*** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbf9474.pool.einsundeins.de)
02:58.46*** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au)
03:14.34Kevin2martin__:  If you have better luck booting from telnet - I would guess it is because something in the kernel prefers it when the wifi (or usb) is active.  What do you use to telnet in - usb or wifi?
03:22.51*** join/#htc-linux ali1234 (n=al@62.24.214.38)
03:40.25*** join/#htc-linux swc|666 (n=swc|666@unaffiliated/swc666/x-4934821)
04:17.47*** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbf9474.pool.einsundeins.de) [NETSPLIT VICTIM]
04:17.47*** join/#htc-linux JohnnyK (n=johnnyk@nfx-nat-229.pilsfree.net)
04:17.47*** join/#htc-linux ljp (n=lpotter@218.185.108.156)
04:17.47*** join/#htc-linux JEEB (n=kanakana@a88-114-192-27.elisa-laajakaista.fi)
04:17.47*** join/#htc-linux toi (n=pleemans@d5152D3B4.access.telenet.be)
04:17.47*** join/#htc-linux Dinde (n=kayser@sur-internet.net) [NETSPLIT VICTIM]
04:17.47*** join/#htc-linux raph_ael (i=raphael@kikoolol.orbus.fr) [NETSPLIT VICTIM]
04:17.47*** join/#htc-linux dase (i=dase@p1atin.de) [NETSPLIT VICTIM]
04:18.15*** join/#htc-linux jeebster (n=kanakana@a88-114-192-27.elisa-laajakaista.fi)
04:18.16*** join/#htc-linux _Dinde (n=kayser@sur-internet.net)
04:29.08*** join/#htc-linux toi (n=pleemans@d5152D3B4.access.telenet.be)
04:29.08*** join/#htc-linux _Dinde (n=kayser@sur-internet.net) [NETSPLIT VICTIM]
04:29.08*** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbf9474.pool.einsundeins.de) [NETSPLIT VICTIM]
04:29.08*** join/#htc-linux JohnnyK (n=johnnyk@nfx-nat-229.pilsfree.net)
04:29.09*** join/#htc-linux ljp (n=lpotter@218.185.108.156)
04:29.09*** join/#htc-linux JEEB (n=kanakana@a88-114-192-27.elisa-laajakaista.fi)
04:29.09*** join/#htc-linux Dinde (n=kayser@sur-internet.net) [NETSPLIT VICTIM]
04:29.18*** join/#htc-linux _Dinde (n=kayser@sur-internet.net)
04:31.46*** join/#htc-linux toi_ (n=pleemans@d5152D3B4.access.telenet.be)
04:32.12*** join/#htc-linux dase (i=dase@p1atin.de) [NETSPLIT VICTIM]
04:33.19*** join/#htc-linux raph_ael (i=raphael@kikoolol.orbus.fr) [NETSPLIT VICTIM]
04:33.27*** join/#htc-linux ljp_ (n=lpotter@218.185.108.156)
05:09.07*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
05:53.14*** join/#htc-linux ali1234 (n=al@62.24.214.38)
05:55.21*** join/#htc-linux kiozen (n=oeichler@p54929E6C.dip0.t-ipconnect.de)
06:25.10*** join/#htc-linux goxboxlive (n=goxboxli@195.159.97.196)
06:25.44*** join/#htc-linux nighthawk06 (n=nighthaw@nighthaw.bb.netvision.net.il)
06:27.01nighthawk06I am trying to install the openmoko package (.cab) file on imate ppc (htc-universal) but it fails to open files, and I do not know how to copy them manually
06:49.08*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
06:52.57*** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net)
06:53.56*** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net)
06:58.54*** join/#htc-linux Alex[sp3dev] (n=alex_dfr@86.110.163.25)
07:05.14*** join/#htc-linux rob_w (n=rob@p549B9595.dip0.t-ipconnect.de)
07:32.21*** join/#htc-linux lalala (i=c3390b4d@gateway/web/ajax/mibbit.com/x-ecd9dc907a6d0593)
07:49.07*** join/#htc-linux AstainHellbring (n=Administ@unaffiliated/astainhellbring)
08:11.08*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
08:13.28*** join/#htc-linux goxboxlive_ (n=goxboxli@242.84-48-176.nextgentel.com)
08:14.24*** join/#htc-linux premy (n=pr@73.205.76-86.rev.gaoland.net)
08:44.27*** join/#htc-linux exception13 (n=exceptio@testdrive.kgts.ru)
08:44.32exception13all:
08:48.09martin__Kevin2: I was doing it over USB. What was interesting is what ginge was reporting though, which is that it seemed to work from him telnetting to localhost on the kaiser itself.
08:48.10*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
08:48.25BabelOhi
08:56.22kiozenhi BabelO, I manged to compile gdal_1.4.4 with bitbake and (!) to add it by bitbake to console-image
08:56.33kiozennext I try gdal_1.5.2 :)
08:56.53BabelOkiozen: ohh :) keep the bb file and send it to OE
08:57.27kiozenyes
08:58.44kiozentoday is the "hunting the bug" day
09:00.11kiozenBabelO: ah, crud, gdal_1.5.2 still has that cross compile bug
09:04.57kiozenBabelO:  you know by any chance what to add to the *.bb file to make configure use the oe includes instead of the system includes?
09:11.41BabelOkiozen: no :(
09:14.29*** join/#htc-linux goxboxlive (n=goxboxli@195.159.97.196)
09:19.42*** join/#htc-linux GPFerror (i=GPF@cpe-76-187-41-132.tx.res.rr.com)
09:22.48*** join/#htc-linux exco (n=exco@e181089145.adsl.alicedsl.de)
09:28.57exception13linuxtogo.org is down? :(
09:43.50*** join/#htc-linux gibke (i=jibril@adopt-a-camel.com)
09:44.31gibkemorning. the mirror for kaiser bootloader is down?
09:44.39gibkebootkit*
09:50.57*** join/#htc-linux ginge_ (n=baz@80.229.188.31)
09:52.41ginge_Kevin2: Yeah, tenet to localhost from pocket putty work for booting kaiser
10:00.47*** join/#htc-linux Iumentum2 (n=iumentum@195.137.253.25)
10:01.29Iumentum2Greetingz Folkz
10:02.42Iumentum2Was wondering if anyone in here got Android running on HTC touch diamond using Haret ?
10:55.52exception13if extract gsmcode & gsmdata from the image htc artemis gsm module will work? excuse for bad English, using a translator.
10:58.56*** join/#htc-linux rob_w (n=rob@p549B9595.dip0.t-ipconnect.de)
11:05.59*** join/#htc-linux Marex (n=vasum7am@auryn.karlin.mff.cuni.cz)
11:11.41kiozencr2: BabelO: looks like I have gdal_1.5.2 for oe
11:40.30*** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz)
11:56.43premyhttp://rafb.net/p/ZqDDgV87.html
11:57.45premyGuys, can anyone have a look at the traces there ? There seems to be 4 additional fifos that get updated during a call. I have no clue what the data in there is.
12:03.09Kevin2ginge_: Okay - that's odd.  I have to go to work.  But, can you create a file "earlyharetlog.txt" and try to boot the kernel both ways (via default.txt and via telnet).  And then forward the two log files (from haretlog.txt) to the mailing list at haret@handhelds.org.
12:03.37ginge_Kevin2: sure.
12:14.04ginge_premy: interesting. Each address starts with the same 3 bytes of data
12:14.07*** join/#htc-linux adam2591 (n=adam2591@ben230.neoplus.adsl.tpnet.pl)
12:14.11adam2591hi all
12:14.20ginge_hi adam2591
12:16.48adam2591can i get here some help with linux on dell axim x30?
12:17.27exception13adam2591: handhelds.org?
12:19.22adam2591last update on that site is from 12.02.08 maybe something changed
12:19.48adam2591its hard to find how to run linux on my axim
12:20.30Marexadam2591: download all you can, install haret, tap boot ?
12:20.31adam2591only good site that i found is some 'hazard control' so i'm compiling toolchain
12:24.00adam2591so what can i do after installing initrd? i saw some patch for lcd driver but i get 404 error ;/
13:16.56*** join/#htc-linux Alex[sp3dev] (n=Alexande@86.110.163.25)
13:21.52*** join/#htc-linux goxboxlive1 (n=goxboxli@242.84-48-176.nextgentel.com)
13:31.11*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
13:36.11*** join/#htc-linux pleemans (n=peter@d51A5E76A.access.telenet.be)
13:48.07*** part/#htc-linux exception13 (n=exceptio@testdrive.kgts.ru)
14:02.52*** join/#htc-linux LunohoD_ (n=alex@e180076099.adsl.alicedsl.de)
14:15.19premyginge_: the first 6 ints is where the headers of the fifo are. The actual data starts after those 6 ints (with something like "80010034"). It looks like a TLV structure, with "8001" being the type of PDU, "0034" the length, and the 0x34 next bytes the actual value.
14:29.42ginge_hmm. PDU eh? So it will be in 7 bit encoding. I would expect to see the service centre number though.
14:33.52premyginge_: sorry, with PDU I only meant a data structure. Not necessarily SMS-related. Actually, that's my question : what type of data does this structure convey ?
14:35.09premyginge_: as for SMS, they're sent using regular AT commands using the AT channel. At least when it's over GSM. I think you can send SMS over GPRS, but I'm not sure how this would work.
14:36.11*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
14:36.20ginge_sure. never tried the GPRS SMS, but seen it on spec sheets.
14:36.20ginge_did you diff the pre-call and post call? Anything interesting in there?
14:39.51dcordes_ginge_: can you connect to the dropbear ssh server on your kaiser
14:41.26ginge_dcordes_: I can connect to the ssh server in a number of places (all that I tried) but not sure what ssh daemn they use.
14:42.06dcordes_ginge_: I can't connect to kaiser. it just times out
14:42.17ginge_youcant connect externally to your kaiser?
14:42.21dcordes_although I have dropbear started and a password setup
14:42.23dcordes_right
14:42.40ginge_well, if it is anything like orange, you get a natted IP that you cant use to connect back in
14:42.43ali1234over gprs?
14:42.51dcordes_ali1234: yep
14:42.55dcordes_change port?
14:42.58ali1234yeah, no external connections
14:43.09ali1234doesn't matter what port you use
14:43.10ginge_ssh out, setting up a tunnel, and then ssh back in
14:43.16dcordes_alright
14:43.19ali1234yes, do that
14:43.20dcordes_sshing out worked fine
14:44.46ali1234bbl
14:48.55*** join/#htc-linux zwox (n=zwox@par69-7-82-243-234-94.fbx.proxad.net)
14:51.15kiozencr2: new http://www.qlandkarte.org/rootfs.tar.gz
14:51.33kiozenwith proj4, gdal and QLandkarteM
14:52.25kiozenhowever without setting up environment vars for M
14:52.43kiozenthink we have to puzzle that out again
15:04.51martin__premy:
15:04.52martin__dcordes_:
15:04.53martin__ginge_:
15:04.56martin__I just spotted something
15:05.13martin__The offsets between the send and receive fifos of each smd channel are equal
15:06.13martin__AT send at 0x41f0, receive at 0x32418, difference is 2e228
15:06.22martin__same for data
15:06.47martin__and same for two pairs of the mystery channels
15:09.58dcordes_mystery=pc?
15:10.00dcordes_proc_comm
15:10.08martin__no, proc_comm is a separate mechanism
15:10.14martin__it doesn't have an smd fifo
15:10.32dcordes_ok
15:11.27martin__also, the spacings between the channels in smem are all multiples of 8216
15:11.40martin__they're in a regular pattern
15:12.11martin__there may be other channels in the missing spots.
15:13.33dcordes_maybe there's secret hardware
15:13.46ginge_coul it be something to do with the 3g/hspda?
15:13.58dcordes_accerlometers and height sensors
15:14.30martin__http://void.printf.net/~martin/kaiser-smd.c
15:14.44martin__I've added the two that we've seen in smem dumps
15:14.55martin__assuming they follow the same send->recv offset pattern
15:15.10dcordes_ginge_: you think gprs and 3g data are two different channels?
15:15.11martin__now we know the pairings and which way round they go
15:15.33dcordes_3g phone calls must already work with the current setup because people say they can only call while ina 3g area
15:15.48dcordes_could only be 3g data
15:16.20dcordes_btw: is the modem turned on/off through the AT channel or is this done through proc_comm or anything else?
15:21.37*** join/#htc-linux dcordes__ (n=dcordes@f054171196.adsl.alicedsl.de)
15:31.49adam2591quit
15:31.54adam2591argr
15:33.16kiozencr2: http://www.linuxdevices.com/news/NS8827997755.html
15:33.27kiozendidn't know Garmin went linux
15:33.52ginge_can someone update the wiki pagename=Kaiser_CPLD
15:33.53ginge_GPIOF7 0x0080 Touchscreen Pen Up/Down
15:35.59dcordes__tis done
15:36.42dcordes__ginge_: are you in angstrom right now? an openmoko developer person asked me what kaiser replies to AT+MUX=?
15:38.38ginge_one mo, will check
15:44.49ginge_4
15:46.01*** join/#htc-linux SmallR2002 (n=SmallR20@c-67-162-60-33.hsd1.il.comcast.net)
15:47.16dcordes__ginge_: thanks did you get this from cu? I also get a 4 there only but sometimes cu ommits stuff in the modem replies
15:47.50ginge_from cat echo
15:51.10*** part/#htc-linux ginge_ (n=baz@80.229.188.31)
15:53.17*** join/#htc-linux ali1234 (n=al@62.24.214.38)
15:54.31*** join/#htc-linux patoche (n=pat@lns-bzn-20-82-64-0-97.adsl.proxad.net)
15:55.29dcordes__ginge: think it probably ommited something?
16:02.49dcordes__ginge: in screen I also only get an O instead of OK when I type AT enter
16:03.48dcordes__but that does only apply tp replies to commands I send in, the @HTCSQ and +CREG come in well
16:08.15*** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net)
16:08.20*** join/#htc-linux kiozen (n=oeichler@rgnb-5d86539f.pool.einsundeins.de)
16:13.01*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfb494.pool.einsundeins.de)
16:34.17*** join/#htc-linux pH5 (n=ph5@e178216180.adsl.alicedsl.de)
16:36.49BabelOhi pH5
16:37.27pH5hi BabelO
16:37.58BabelOpH5: sorry for my last commit on git , but my computer always lost time and date :(
16:41.17pH5BabelO: ntp :)
16:41.29MarexpH5: hi :)
16:41.35pH5hi Marex
16:41.43MarexpH5: Im leading palmtx towards mainline ;)
16:41.44BabelOpH5: yes i ve to reactivate the daemon
16:41.51MarexpH5: or at least trying to
16:41.53BabelOhi Marex
16:41.55pH5Marex: I saw, good stuff!
16:41.56Marexhi BabelO
16:42.17MarexpH5: Im still a bit confused what kernel tree should I use and what patches to apply on it though
16:42.36pH5Marex: for arm specific stuff it's good to be based on arm-devel
16:43.50MarexpH5: you mean this http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git/ ?
16:44.05MarexpH5: I started using that and applied arm:pxa-pwm.diff on it
16:44.05pH5also sending to linux-arm-kernel instead of lkml might help
16:44.28pH5Marex: exactly, the devel branch is what I'm always basing on
16:44.37pH5(it merges the pxa, pxa-pwm and other branches)
16:44.55MarexpH5: pxa-pwm isnt there yet though
16:45.01Marexis it ?
16:45.22pH5it is, look at http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git/refs/heads/
16:45.57MarexpH5: I see
16:45.59pH5I'm using devel because it also has pxa-multi merged in, and that one I need.
16:46.24MarexpH5: so I should use "devel" head, right ...
16:46.37pH5gnn, right now stupid pxa25x/pxa27x_udc can't be compiled at the same time
16:46.51pH5Marex: that's what I'd recommend
16:47.04MarexpH5: btw pxa2xx_udc_gpio isnt in mainline ?
16:47.21pH5Marex: not needed, pxa25x_udc has gpio support integrated
16:47.33MarexpH5: I see :)
16:47.46pH5although I'm just working on replacing that (with otg_transceiver/usb_transceiver/whatever interface)
16:48.11MarexpH5: can you check my palmtx patch then ? :)
16:48.30MarexpH5: btw pxamci seems to be broken :(
16:49.22pH5again? I was using it on magician just a week ago.
16:49.46pH5time to boot that one again, I almost exclusively played with the ipaq last week.
16:50.16*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbf9633.pool.einsundeins.de)
16:50.45MarexpH5: well it doesnt like my toshiba card, see LKML, I posted a RFC/patch there
16:54.51pH5BabelO: wow, that's harsh
16:54.59pH5is this a serious bug in pxamci?
16:55.09pH5you should send that patch to the mmc list, too
16:55.21BabelOpH5:  ?
16:55.26pH5BabelO: sorry, I meant Marex
16:57.30pH5BabelO: I've just moved the master branch on mobile-linux to master-old and created a new master based on current mainline
17:00.27MarexpH5: Im already solving it with Piere
17:00.54*** join/#htc-linux evildarknight (n=charles@41.207.132.189)
17:01.02BabelOpH5: ok, i try to look if i can remove the EFB patch, but it is very very usefull :) easy to debug the proc cpu arm926.S with that
17:01.24pH5Marex: great, seems I was just lucky to have a card where this bug does not appear.
17:01.37MarexpH5: :)
17:01.43MarexpH5: I have two buggy
17:02.20pH5BabelO: so you say we should merge it into the master tree?
17:03.04pH5Marex: btw, you could push your stuff to mobile-linux, too.
17:03.06BabelOpH5: no, just it help a lot for new device.
17:03.53pH5BabelO: ok. are there any other changes in htc-omap that should not go into master?
17:05.22BabelOpH5: mach-omap and  include-omap + new ts and spi driver, other thing are mainline
17:05.55MarexpH5: what's that ?
17:06.56pH5Marex: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=summary
17:07.00pH5(or git://linuxtogo.org/home/groups/mobile-linux/kernel.git)
17:09.41MarexpH5: jeez ... which one should I use then :S
17:10.08pH5Marex: arm-devel!
17:10.21MarexpH5: ok!
17:12.32pH5boots blueangel..
17:14.16Marexboots his brain
17:14.24pH5gnn. "ether gadget: controller 'pxa25x_udc' not recognized"
17:15.17MarexpH5: yea ... mainline seems to be pretty much fun
17:15.36MarexpH5: moreover for someone new, it's pretty much something
17:15.45pH5Marex: but once you're in, people fix your stuff for you when kernel interfaces change :D
17:17.00pH5also it seems my asic3 setup is wrong. pressing keys results in asic3 interrupt processing overrun and the VBUS sensing gpio doesn't fire at all when I plug in USB :/
17:17.29BabelOpH5: on omap i ve put out the vbus sense :)
17:18.27pH5BabelO: on pxa27x it works like a charm. I'm just trying to hack the pxa27x udc driver so power saving on cable plug-out can be implemented.
17:18.51BabelOah :) that's can be very good :)
17:18.56BabelOok back to home now
17:18.58BabelObbl
17:19.05*** part/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
17:21.37pH5heh, found the problem. it was me who broke it and that patch was accepted already quite some time ago.
17:22.01pH5stupid pxa2xx -> pxa25x rename
17:25.00*** join/#htc-linux Tonny (n=chatzill@set25-1-88-166-169-49.fbx.proxad.net)
17:26.18*** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net)
17:27.03MarexpH5: :)
17:34.00pH5compiles
17:34.37Marexdamned irda ...
17:35.13pH5what about it?
17:38.51gingedoes anyone know what touchscreen we have in the kaiser?
17:40.20MarexpH5: is there any way to test irda from simple initramfs ?
17:44.05pH5Marex: irdaping or irdadump?
17:47.59MarexpH5: dont have that there :(
17:48.57pH5time to rebuild initramfs
17:48.58pH5wait, don't you have an usbnet connection yet?
17:50.36MarexpH5: nah ... not in mainline
17:50.50MarexpH5: time to check busybox ;)
17:52.40*** join/#htc-linux kiozen (n=oeichler@rgnb-5d86539f.pool.einsundeins.de)
17:53.26pH5great, "usb 2-1: device descriptor read/64, error -71"
17:53.41pH5at least it correctly loads the usb drivers now, they just don't work
17:53.51pH5back to pxa27x..
17:56.32pH5I think the blueangel interrupt overruns are SPI IRQ firing like there's no tomorrow.
18:00.19*** join/#htc-linux Othello__ (i=Magorium@gateway/tor/x-e1df2398ae33318f)
18:04.43*** join/#htc-linux zwox (n=zwox@par69-7-82-243-234-94.fbx.proxad.net)
18:10.15*** join/#htc-linux mickey|working (i=mickey@openmoko/coreteam/mickey)
18:10.27mickey|workingmorning folks
18:11.37mickey|workingwhew, it's been 3 years since i was last in this channel
18:11.44mickey|workingtime flies
18:11.56mickey|workingwell, 2 years
18:17.07mickey|workingthinking about purchasing a Kaiser. Does it matter which incarnation I chose?
18:25.07tsdogsmickey|working: can't see much differences beside the HSUPA supported only by AT&T version
18:25.14tsdogsreference: http://pdadb.net/index.php?m=pdacomparer&id1=946&id2=856&id3=861&id4=818&id5=791&id6=872&id7=733
18:25.31mickey|workingah, great overview, thanks
18:28.00*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
18:41.41MarexpH5: so we have fourth version of palmtx patch :p
18:46.00*** join/#htc-linux BabelO (n=Fabrice@lun34-2-82-238-28-28.fbx.proxad.net)
18:47.38*** join/#htc-linux Othello (i=Magorium@gateway/tor/x-126cd4af8e6e28a4)
18:56.42cr2mickey|working: why not a diamond ?
18:58.34mickey|workingi'm looking for anything where kernel is in a good state. I'm a userland guy, I want to push a free phone softwarestack, but not do any kernel work. is the diamond similarly well supported?
19:00.06MarexpH5: what is "patch system"?
19:01.38MarexI see
19:03.47cr2mickey|working: i will say neither kaiser nor diamond is well supported, but diamond has the msm-*A cpu, which is the main target for the android code. we did invest a lot of time in researching kaiser, that's true, but imho diamond has better chances for the full hw support. imvho
19:04.18mickey|workingcr2: oh, i see. dcordes__ tells me a lot is already working ;)
19:04.39mickey|workingthe diamond is more sexy, of course
19:05.11cr2mickey|working: he is right, because most work is done on kaiser.
19:05.37cr2mickey|working: but there are still a lot of unknown and not working things. like SD ;)
19:08.43mickey|workingi see. so lets assume I buy a diamond. would i be able to boot into linux and talk AT yet ?
19:13.37cr2if you will run off the ramdisk, yes (afaik). the cpu-phone IPC is very similar to kaiser.
19:14.58mickey|workingok, thanks.
19:23.05kiozencr2: you saw that rootfs?
19:23.42cr2kiozen: which one ?
19:24.15kiozenmade a new one today with gdal 1.5.2 (!) proj4 and M
19:24.29cr2kiozen: see a funny thing now. gps works in linux, but not in wince :)
19:24.33cr2no.
19:24.45cr2where do i get it ? i'll install immediately.
19:25.01kiozenwww.qlandkarte.org/rootfs.tar.gz
19:25.04cr2ok.
19:25.16kiozenbut you have to set the environment vars
19:25.28kiozenand the ususal stuff :)
19:25.37goxboxlive_hi all
19:25.37kiozenif you have it sent me the diff
19:26.02cr2ok
19:26.10cr2hi goxboxlive_
19:26.23BabelOhi goxboxlive_
19:26.28cr2goxboxlive_: already disassembled the ephone ?
19:27.33goxboxlive_cr2: :-) No, i havent got it yet, but i found some intresting on the net. I think it will even will get you a little intrested :-) http://www.iphonelinux.org/index.php/Main_Page
19:27.36cr2kiozen: btw, what are you doing on the 8th in the evening ?
19:28.18kiozencr2: sitting at home, guarding my son :)
19:29.02cr2kiozen: late in the evening ?
19:29.54kiozenthe same no wife during the week. But I have a BBQ and fridge with beer ;)
19:30.07cr2lol
19:30.28kiozenand I can engage the neightbours as babysitter
19:30.32cr2ok. i must be at 14:00 in Munich, don't know how much time i'll stay there.
19:30.50BabelOkiozen: no pstis or ricard ? that's poor
19:31.18cr2BabelO: i'm driving the car
19:31.18kiozenBabelO: but loads of French wine, is that ok?
19:31.33kiozencr2: you can stay the night at my place if you want
19:32.21kiozenbut I have to get up early, around 6:00 :p
19:32.38cr2kiozen: i don't mind driving at night, but talking about n560 may take some time :)
19:32.53kiozendefinetly
19:33.04kiozenthink about it
19:33.27cr2ok, i guess we will decide it somehow.
19:33.45kiozenafter the second bottle of wine, sure..
19:34.03cr2goxboxlive_: i thought you got the umts version ?
19:34.08cr2kiozen: sure.
19:34.49goxboxlive_cr2: i that's the one i have ordered.
19:35.08goxboxlive_s/i/yes/
19:38.33cr2goxboxlive_: the bootloader looks like heavily edited idapro output.
19:41.39*** join/#htc-linux tsdogs (n=tsdogs@62.123.180.130)
19:42.28*** join/#htc-linux NickBee (i=NickBee@122.160.64.226)
19:45.46*** join/#htc-linux rmoravcik1 (n=rmoravci@ip-89-102-255-171.karneval.cz)
19:46.19*** join/#htc-linux derekS (n=dereks@unaffiliated/dereks)
19:47.12derekShi. where can i find documents on how to install linux on an xv6700 (htc apache)? all the links i found have links that are dead
19:50.25cr2derekS: you need to decide which userspace image you'll use
19:51.07derekScr2: what are my choices?
19:51.21derekSi don't use my phone anymore, so i am just playing
19:52.31derekSonly instructions i found resulted in a kernel panick :)
19:53.28kiozenyes! now I have the *csv data for gdal in /usr/share, too
19:59.47cr2derekS: the CDMA phone is not supported anyway, so you can use any PDA userspace.
19:59.51cr2kiozen: booting :)
20:00.02*** join/#htc-linux patoche (n=pat@lns-bzn-20-82-64-0-97.adsl.proxad.net)
20:00.50derekScr2: do you have any links to how to do that?
20:01.20cr2derekS: use the image made for universal, and replace the kernel/modules
20:02.49derekScr2: ok. what should i replace the kernel/modules with?
20:03.12cr2derekS: you can use the image for n560, that we are discussing with kiozen. it's for pxa27x too.
20:03.50cr2derekS: checkout the hh.org CVS and compile the kernel for apache. you'd try to ~ping Kevin2 about apache kernel.
20:04.01kiozencr2: you should test it befor advertising it ;)
20:04.24cr2kiozen: hangs at boot :(
20:04.32kiozenarrrgh
20:04.49cr2kiozen: more eyes catch more bugs.
20:05.17kiozenany hint what's wrong?
20:05.43cr2kiozen: i'll run fsck, and try again.
20:06.28cr2lol. i hate broken localizations ;)
20:06.34cr2Gelöscht Inode 31162 hat "zero dtime".  Repariere<j>?
20:07.37cr2i'm still supposed to press 'y' here, not talking about the weird sentense itself ;)
20:09.09cr2no. still hangs after 'Freeing init memory: 112K'
20:09.31kiozenI upload the original
20:10.44cr2ELF 32-bit LSB shared object, ARM, version 1 (SYSV), for GNU/Linux 2.6.14, stripped
20:10.50cr2let's hope it's eabi
20:11.31cr2kiozen: it must be some problem with busybox.
20:12.17kiozenis there a special syntax for tar to do rootfs.tar.gz?
20:12.57BabelOkiozen: i do only cvjf here
20:13.29kiozendo the same cvfz
20:13.54kiozencr2: try www.qlandkarte.org/console-image-looxc550.tar
20:15.14*** join/#htc-linux zwox (i=zwox@par69-7-82-243-234-94.fbx.proxad.net)
20:16.22kiozencr2: are the link to busybox ok?
20:17.07cr2kiozen: i think yes.
20:18.54kiozencr2: does the 2nd one work?
20:19.54cr2umounting
20:20.15cr2fs*king suse!!!
20:20.34cr2the kernel oopsed on umount again.
20:22.05cr2hmm. need to reboot.
20:26.23kiozencr2: got to go, I will read the logs, bbl
20:37.02*** part/#htc-linux patoche (n=pat@lns-bzn-20-82-64-0-97.adsl.proxad.net)
20:46.25*** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de)
20:47.32dcordes__cr2: did somebody boot diamond yet?
20:49.38cr2dcordes__: don't know, but i'd guess it's relatively easy to do. the fb is at the end of the ram, so you just need to boot with mem=95M, and without any kernel offset.
20:50.25dcordes__cr2: diamond has 95M of ram?
20:50.33cr2and hardcoding the wince fb address, which is in wiki
20:51.42cr2dcordes__: wince uses 95MB mapping. then there is some 20MB fb-related mapping, several 1MB mappings (qdsp ?) and some mysterious 32MB mapping at 0x02000000
20:52.07dcordes__20MB for fb?
20:52.09cr2it's all documented in the diamondmemorymap wiki page.
20:52.11cr2yes.
20:52.18dcordes__isn't that a lot?
20:52.27cr23D buffers ?
20:52.31dcordes__oh
20:52.41cr2android reserves 9MB sram for that.
20:52.43dcordes__I'll read the wiki
20:53.12cr29MB sram vs. 20MB sdram. sounds feasible.
20:53.49*** part/#htc-linux derekS (n=dereks@unaffiliated/dereks)
20:55.47cr2kiozen disappeared...
21:04.48tsdogscr2: [2008-07-03 22:26] <kiozen> cr2: got to go, I will read the logs, bbl
21:07.12cr2tsdogs: ok.
21:07.22cr2kiozen: the old one boots as expected.
21:09.01cr2tsdogs: i'm so busy with the job-related things, that forgot about roadmap completely.
21:11.30tsdogscr2: well not that i did work on it myself either :)
21:11.34tsdogsbtw now I really thing that my patch went to /dev/null
21:12.02tsdogshmm my dsl line is going up and down :(
21:12.53cr2tsdogs: how far is xanadux cvs behind the mainline ?
21:14.44tsdogshmm, last update was 4 weeks ago
21:15.13tsdogsSat May 31 13:05:52 2008 UTC
21:16.15tsdogsmany commits but nothing very relevant imho
21:20.26cr2ok.
21:36.02dcordes__premy: ping?
21:38.17cr2tsdogs: it may be better to resync, mainly because of the wince.
21:40.20premydcordes_: hi
21:41.00dcordes__premy: do you have the keypad and touchscreen working on polaris?
21:41.08dcordes__hello, sorry :)
21:42.08premydcordes_: touchscreen is ok. Some of the keys also, but not all of them. And I'm using dzo's initial soft keyboard (not looked at his new one yet).
21:44.14dcordes__premy: do you use dzo's touchscreen code?
21:44.16tsdogscr2: ok I'll do in the next days
21:44.57dcordes__premy: I am asking because I started putting the current developments into git, although the big merge is to come. and it would be nice to also see your polaris stuff in there
21:46.43premydcordes_ : yes, I'm using vogue-ts.c, with some calibration changes.
21:46.48*** join/#htc-linux swc|666 (n=swc|666@unaffiliated/swc666/x-4934821)
21:47.03gingepremy what changes, I am just looking at that now
21:47.21dcordes__yea probably it's the same as on kaiser :)
21:48.27gingepremy: also the new code is all interrupt driven. Do you have a pen interrupt on the polaris?
21:49.03cr2tsdogs: thanks.
21:49.30premyginge_: I posted my code on xda here : http://forum.xda-developers.com/showthread.php?p=2308602#post2308602
21:50.19dcordes__I've been looking for this sort of thread :)
21:51.29dcordes__premy: mobile gets into sleep (so puts off the screen, and slow down the processor) sounds like you got proc_comm working on polaris?
21:52.08dcordes__oh that was not you
21:52.41gingepolaris touchscreen works the same way as the vogue
21:53.08premydcordes_: the code might need some clean-up if it has to be included in your repository
21:53.16premydcordes_: ?
21:54.51dcordes__premy: I'm looking through the diff
21:55.23dcordes__I already commit the version of kaiser-smd.c which was already polished by martin__, so we might just ommit this from the diff
21:57.47dcordes__on screen keyboard would be useful for vogue in the git anyway. a seperate machine type for polaris also makes sense. my question is what are we doing about the ts.c
21:57.55dcordes__ginge: could you test it on kaiser?
21:58.08dcordes__the vogue-ts.c from premy' diff?
21:58.19gingedcordes__: no point. The touchscreen works differently on kaiser.
21:58.27gingeI already ported all of dzos code over
21:58.51gingeI have the onscreen keyboard working, but the p1 p2 and y value all interact with each other in a different way
21:58.54dcordes__ok but what about the calibration thing?
21:59.35gingewell calibration is hard because the screen outputs the y value relational to the pressure and the x value
22:00.45marajinallo allo allo
22:01.08gingeso I have calculated the offsets and the scew value for p, now I need to do the same for x and it should output nearly sane values
22:02.26dcordes__ginge: I mean the calibration changes premy provides for polaris?
22:02.33dcordes__marajin: merhaba
22:03.01gingethe calibration changes are not the issue. I can calculate the min and max x for the screen easily enough, but the y scale is not linear
22:03.11dcordes__ok
22:03.39dcordes__premy: do your changes to vogue-ts.c go together with vogue well?
22:04.01ginge//x(0)y(0) = 1800
22:04.01ginge//x(240)y(0) = 2350
22:04.01ginge//x(0)y(320) = 3700
22:04.01ginge//x(240)y(320) = 3760
22:04.38gingethats the raw pressure readings from the touchscreen at coordinates 0,0 240,0 0,320 240,320
22:04.40dcordes__premy: I doubt anybody built vogue from htc-msm recently anyway so it's not too important at this point. I'm just curious
22:08.49marajindcordes__: What?
22:10.22dcordes__brb
22:11.18premydcordes_: they were supposed to, but to be honest I was assuming that vogue would not build anyway, so was not too concerned about breaking it.....
22:19.48*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
22:22.27dcordespremy: yea that's what I say. I assume premy will take care of vogue and dzo will give some reference info and testing
22:23.06dcordespremy: with that given, I think I can just commit everything except of kaiser-smd.c which is already in
22:25.36*** join/#htc-linux pH5_ (n=ph5@e178216180.adsl.alicedsl.de)
22:25.44premydcordes_: it would still be good to test at least once that my code doesn't break the kaiser build.
22:27.27dcordespremy: I'm trying to make sure it doesn't touch anything kaiser critical before I apply it to my local tree. what about msm_fb.c? looking at the diff it seems like everything only affects polaris/vogue throgh ifdefs?
22:28.41premydcordes_: yes, that was the intention.
22:31.33dcordespremy: ok everything else looks cool. I will apply all the stuff except of kaiser-smd.c locally and check if kaiser still builds and works
22:32.07dcordesginge: did you try a kaiser build since the last commits?
22:32.15gingeno
22:32.47dcordescould you run a test while I check premy patch?
22:36.03gingenot right away. I am busy trying to find somewhere to live. Been asked to move out by the landlord because he is selling :/
22:37.25dcordes~lart landlord
22:37.25aptbrandishes Excalibur! "With this sword, I vanquish thee, landlord!" and lops off landlord's head
22:38.32Marex:D
22:38.38Marexchainsaw is better anyway ;)
22:38.48ginge:)
22:38.51dcordessince the last commits are from my working tree it should be all good. I can get online with its builds
22:41.57premyYey, it's vibrating !!!!!!
22:42.06ginge!!
22:42.19dcordesbrrrrr
22:42.30dcordesI'll wait with the commit
22:42.32dcordes00:41 < premy> Yey, it's vibrating !!!!!!
22:42.36dcordesops
22:44.57premyThe commands are different from vogue and from what's in the google code, though
22:45.42premySo I'm not sure we'll be able to reuse the exisiting code directly.
22:51.24dcordesnevermind at least proc_comm's working
22:53.53*** join/#htc-linux tsdogs_ (n=tsdogs@62.123.180.130)
23:03.44*** join/#htc-linux swc|666 (n=swc|666@unaffiliated/swc666/x-4934821)
23:03.56marajindcordes: What's "merhaba" ?
23:04.28marajinnevermind
23:04.31marajinturkish greeting
23:04.34marajinheh
23:05.01dcordesright
23:16.53dcordespremy: what did you do to make it work?
23:19.30premydcordes: I'm cleaning up a bit and will post the code soon.
23:20.47premyIt's basically the same as for vogue. Although I'm not sure that the vogue code doesn't simplify a bit.
23:21.02dcordesdzo said it should be very similar
23:22.56premydcordes_: I wouldn't recommend to include this in your commit. I'm not sure it's not going to break something else, because the commands are not the same.
23:23.22premyFor ex, vibrate on is 0x17 on my polaris, and 0x4 on vogue
23:23.37premyMight even be different for kaiser.
23:23.38dcordesand I bet it's also 0x17 on kaiser
23:23.59premyWe'll see.
23:24.09dcordesI could try
23:25.43premyOk, the code is there : http://rafb.net/p/lPFOuD24.html
23:26.40premyI've included a safeguard to limit the use of msm_proc_comm to the vibrate commands (doesn't boot without this, actually).
23:27.04*** join/#htc-linux surgex (i=surge@pool-71-186-163-107.bflony.fios.verizon.net)
23:27.35premyTo test it, I'm using dzo's soft keyboard which vibrates when a key is pressed.
23:29.28dcordeshow'd I manually trigger a vibrate signal?
23:29.50dcordesputting the soft keyboard for kaiser makes not much sense
23:32.36premydcordes_: you have to call msm_proc_comm(0x17,0,0); then msm_proc_comm(0x18,0,0).
23:33.02premyyou need to find a relevant place in the kernel to do this.
23:34.44premyts.c  or board-kaiser-keypad.c ?
23:35.32premyNeed to get some sleep. I'll read the logs tomorrow. Bye.
23:35.41dcordesbye premy
23:35.48*** part/#htc-linux premy (n=pr@73.205.76-86.rev.gaoland.net)
23:43.00gingeinteresting. I have that code already in my touchscreen hack.
23:44.19dcordesginge: msm_proc_comm(0x17,0,0); msm_proc_comm(0x18,0,0) ?
23:45.19gingedcordes: yes it was in dzo's code. I just need to uncomment it
23:45.36gingeand patch in premy's addresses.
23:45.39gingethats if they even work
23:46.20dcordesdoes the dzo comment cause vibrate (with the coorrect pc adresses) on P event?
23:47.01gingeI'd have to try premy's code
23:48.34dcordesI can also try it if you give me your kaiser ts .c with the vibrate event comment thing
23:48.54gingethis code will make your eyes bleed
23:49.21gingewhy not just patch it in a more convenient place to test it.
23:49.26gingelike keyboard.
23:49.53dcordesI can only copy paste code :)

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