IRC log for #openmoko on 20080423

00:03.14mwesteryes, if you are permitted to tell me
00:03.45mwesterI'm wondering about the connection from the s3c2410 UART to the GSM modem -- what is the mux chip, does it have specs?
00:03.55rohthere is no chip
00:04.07rohits firmware only inside the gsm arm
00:04.29mwesterSo where does the console connect? to the GSM?
00:06.11mwesterSpecifically I'm observing that when the GSM wakes up the system from suspend, data is transmitted immediately after the 50606 driver is resumed -- I'm wondering if that is coincidence.  That then brings up the question of how is the PMU connected to the GSM and the device that muxes the serial port?
00:07.02rohmwester: there is a latch in between
00:07.07mwesterThis is important because I think this may impact how to resume without risking overruns; it would be pointless to manipulate the I/O lines if the device on the other end were unpowered (for example).
00:07.35mwesterAh, and is the latch powered by a bus switched by the PMU?  and what clocks it to latch the contents?
00:07.48rohits controlled by GSM_EN which has a pullup and a line to EINT2/GPF2
00:08.16rohcontrolled by the regular soc, not pmu
00:11.11*** join/#openmoko netx (n=rlange@osiris.darkempire.org)
00:11.12*** join/#openmoko christooss (n=matic@84-255-246-158.static.t-2.net)
00:11.37rohthe latch is powered by io_3v3.. thats sane
00:12.02rohhm.. one could remove 2 resistors and add 2 nc and have the modem tx and rx on the usb conn *shiver*
00:12.10rohbut no cts/rts
00:12.15*** join/#openmoko morricone (n=foobar@dslb-084-057-128-025.pools.arcor-ip.net)
00:14.48rohthe latch is a SN74LV125ARGYR, means negative logic control line, noninverting or so
00:15.07mwesterAh, that's a rather simple device, IIRC.
00:17.10rohjap. it only switches all 4 lines from/to the modem through to it.
00:17.39rohthe rx and tx on the debug conn are connected directly to the samsung.
00:17.52mwesterHow is the console disabled when the modem is activated?  does it have its own buffer/line driver that is disabled when the modem is enabled?
00:17.55rohso you should 'see' the modem talking there
00:18.21mwesterAh, but I don't see the modem talking there...
00:18.30rohuhm.. well.. see the cpu talking to the modem and you can talk to the cpu,
00:18.46roheeheheh.. would need some hacky 2nd serial to see both directions
00:18.55mwesterAh, of course.
00:19.34rohone could mod a debugboard for that. or a moko
00:20.00mwester:) Now there's the problem :D  I don't have enough of either.
00:20.14*** join/#openmoko nnpiggy (n=nnpiggy@static-63-131-51-132.pro.onecommunications.net)
00:20.15SpeedEvilmwester: or I think you can get to the GPS CTS/RTS pads easily
00:20.32SpeedEvilI seem to recall tehy are brought out to solderpads just above the LCD
00:20.36roh*remark* really need a 2-way usb serial sniffer with all blinkylights on, flow control, wiggling of single lines, hw as well as sw uart and baudrate measurement
00:20.44SpeedEvilthese can be configured as /dev/ttySAC3
00:20.57*** join/#openmoko mboldisc (n=mike@c-66-41-225-167.hsd1.mn.comcast.net)
00:20.57mwesterroh: plus the scope on the interrupt line from the GSM.
00:21.01SpeedEvilthese can be configured as /dev/ttySAC2
00:21.15SpeedEvilIf the aim is simply to have an uninterrupted console
00:22.02mwesterI would really *LOVE* somebody to confirm that there are no glitches on any of those signals during suspend and resume; I have no such confidence as it seems to me that the serial driver was never written to save the UART state; rather it seemed to be written to re-init each time.
00:22.40SpeedEvilonly has an analog scope, which isnt' great for that.
00:22.44*** join/#openmoko greentux_ (n=lemke@Z5899.z.pppool.de)
00:22.45rohi fear something like that.
00:22.48mwesterSpeedEvil:  one of the big "regrets" of the GTA01, I suspect, is the split use of ttySAC0 for console and GSM -- it's hard to get worse.
00:23.06rohmwester: agreed.
00:23.11SpeedEvilmwester: yeah - you don't have to use SAC0 for console though - you can make it SAC2 I think.
00:23.19*** part/#openmoko caratorn (n=aratorn@tui75-3-88-168-237-15.fbx.proxad.net)
00:23.24SpeedEvilIf you don't care about the GPS not working
00:23.43mwesterFor example, as you dig through the suspend/resume code, you find that the console changes fundamental behavior (the port is initi'd twice, with different termios structures, for example).
00:23.44rohthe only thing is, you cannot disconnect the gps, only power it down and hope
00:23.57SpeedEvilroh: oh yeah. Hmm.
00:24.02mwesterSpeedEvil:  u-boot would need to initialize SAC2 for that to work; I tried it.
00:24.10SpeedEvilmwester: yes, it would.
00:24.57mwesterI think it's easier to disable the console in inappropriate spots, and avoid the problems that way.
00:25.14*** join/#openmoko SirBob1701 (n=mcginley@ns2.LASALLE.EDU)
00:25.31SpeedEvilroh: I suppose it depends if the GPS loads the lines when powered down enough to ignore it serial input.
00:25.50SpeedEvilponders.
00:26.02SpeedEvilSigh. I need a digital scope of some description.
00:26.02mwesterBut, but, but - I want my GPS too! :D
00:26.19SpeedEvilmwester: yeah - this would only be a debug tool for looking at glitches
00:26.45SpeedEvilroh: happen to know anything about the GSM-firmware-flashing-in-the-field quesiton?
00:26.51rohSpeedEvil me too. friends of mine at the cccb have a agilent 2+16channel mixed signal dso.. thats cool
00:27.09SpeedEvilroh: that's a bit more than what I'm looking at.
00:27.15rohmeans 2 channel dso (still ctr, no lcd) and 16 channel logic input
00:27.20*** join/#openmoko Relate (n=dieb@unaffiliated/relate)
00:27.31SpeedEvilroh: unfortunately. Ebay, china.
00:27.33rohsuperb for this problem, but sadly i cannot just get it from there.
00:27.34mwesterWell, I'm changing strategies now, and I'm just going to disable and delay things longer, and hope that all glitching is done and over.  Hence the quesitons about the PMU; I think I shall wait until after the PMU is init'd to enale the GSM.
00:28.14mwesterBTW, I suspect that the MMC resume is adding ~ 200 - 230 ms to the resume time.  We'll need to do something about that.
00:28.19rohmwester: there is this spike on all gpio on suspend.. could that change state somewhere?
00:28.57mwesterroh: I wouldn't have thought it long enough to do so, but it is certainly possible.
00:29.02rohits while powering off rails. there seems to be some discrepancy between what the arm wants as order and whats possible with that pmu (but there isnt a more fitting one afaik)
00:29.38*** join/#openmoko poffy (n=toast@c-98-199-135-173.hsd1.tx.comcast.net)
00:29.58rohwell.. my assumption atm is to get a moko, wire all 4 modem lines at the arm to it and measure it
00:30.11rohs/moko + 4channel dso/
00:30.59mwesterI suspect there will be a number of very low cost GTA01's on eBay as soon as the 02 ships, perhaps that would be a good way to aquire some stock for testing purposes.  (I lack equipment to do it correctly, I'm afraid).
00:31.07rohwe could try asking seanc if they have a board wired up like that already in taiwan
00:31.23SpeedEvilwants brokenmoko bits.
00:31.28SpeedEvilCases, ...
00:31.40rohmokos shouldnt be the problem. time and soldering caps are it ;)
00:31.50SpeedEvilI think I've got a way to fit a wifi card into my GTA01.
00:31.58mwesterThat might not be a bad idea.  The GSM module is the same on the GTA02, and if this is a kernel/GSM problem, we'll have it on the 02 as well (although that has twice the FIFO on the UARTs IIRC)
00:32.02SpeedEvilBut I don't want to butcher my only case.
00:32.14rohSpeedEvil rip out the speakers, wire it to spi?
00:32.30SpeedEvilroh: I have a USB board only, so it'd be that.
00:33.00SpeedEvilroh: rip out the GPS antenna, place board where it is, place small ceramic antenna on top of where GPS antenna was.
00:33.12SpeedEvilroh: rip out the GPS antenna, place board where it is, place small ceramic GPS antenna on top of where GPS antenna was.
00:33.13rohmwester: as more as i think about it i am quite sure the issue has to do with that latch and the spikes (which should be gone on gta02 , i think)
00:34.28mwesterIf we assume that a spike occurs as the PMU powers things up, and that this affects the latch, that could account for the consistent pattern of the overrun.
00:36.27summatusmentisCRAP! Just deleted the VM I had openmoko in
00:39.04*** join/#openmoko tombhadAC (n=tombhad@pD95DC6A4.dip.t-dialin.net)
00:39.52dcordes1downer
00:40.44*** join/#openmoko behdad (n=behdad@CPE001217b19226-CM0012c9c84bc4.cpe.net.cable.rogers.com)
00:40.49*** join/#openmoko Khem (n=Khem@adsl-71-146-20-69.dsl.pltn13.sbcglobal.net)
00:53.05*** join/#openmoko niclone (n=nicolas@blurp.yi.org)
00:56.39*** join/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
00:56.51*** part/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
01:04.21*** join/#openmoko retracile (n=eli@76-204-213-211.lightspeed.allntx.sbcglobal.net)
01:09.19*** join/#openmoko alex-weej_ (n=alex@cpc1-acto9-0-0-cust931.brnt.cable.ntl.com)
01:10.14*** join/#openmoko alex-weej_ (n=alex@cpc1-acto9-0-0-cust931.brnt.cable.ntl.com)
01:20.22*** join/#openmoko moko-bunny (n=reik@CPE-76-178-148-218.natnow.res.rr.com)
01:34.08*** join/#openmoko fgau (n=fgau@pD95395A3.dip0.t-ipconnect.de)
01:40.47bmk789Will i be able to connect my BT headphones to my Freerunner and make calls with the headphones?  or is that one of those things that seems easy but is almost impossible in the FOSS world?
01:40.51SpeedEvilyes
01:41.02SpeedEvilin the 'the hardware is there' sense
01:41.16*** join/#openmoko Crfrod (n=Crfrod@88.214.193.26)
01:41.28*** join/#openmoko broedje (n=hellvis@92.116.187.168)
01:41.42bmk789but i dont imagine it will be able to do it out of the box right?
01:42.38*** join/#openmoko playya__ (n=playya@pD9E0889F.dip.t-dialin.net)
01:48.48SpeedEvilDo the headphones have microphone on them?
01:49.42bmk789yes
01:50.29*** join/#openmoko retracile (n=eli@76-204-213-211.lightspeed.allntx.sbcglobal.net)
01:51.03SpeedEvilI recall mentions on the wiki of bluetooth calling working - but not to initiate calls.
01:53.24bmk789hmm, ill have to search the wiki
01:53.49SpeedEviljust search onb bluetooth
01:53.51SpeedEvilthere isn't much
01:54.02*** join/#openmoko slomo (n=slomo@ubuntu/member/slomo)
01:54.04*** join/#openmoko nnpiggy (n=nnpiggy@dsl093-060-111.pit1.dsl.speakeasy.net)
01:58.11*** join/#openmoko poffy_ (n=toast@c-98-199-135-173.hsd1.tx.comcast.net)
02:11.35*** join/#openmoko ahven (n=kala@194.126.113.157)
02:12.06*** join/#openmoko j_ack (n=j_ack@dsbg-4db7d619.pool.einsundeins.de)
02:15.35*** join/#openmoko jadams_ (n=jadams@68.117.153.158)
02:15.43jadams_my ipod touch just came in
02:16.26SpeedEvilturns off his innuendo filter.
02:17.07mjrwhat, you have an innuendo filter?
02:17.56jadams_is there any effort being made to super-simplify gprsification on the moko?
02:17.56rtmThe ipod touch is not fun.   It comes with functional software.
02:18.10*** part/#openmoko tomjoad (n=tomjoad@adsl-70-130-139-0.dsl.stlsmo.swbell.net)
02:18.10jadams_rtm: I don't agree with it philosophically.  But jailbroken, it's pretty fun
02:18.58rtmjadams: I guess a fugitive ipod is ok.
02:19.34mjrthe problem with fugitive iThings is you still pay the jailer..
02:22.14*** join/#openmoko heikkit_ (n=chatzill@c-67-188-122-139.hsd1.ca.comcast.net)
02:25.05*** join/#openmoko jeffdamet1 (n=jeff@dyndsl-091-096-044-087.ewe-ip-backbone.de)
02:40.36*** join/#openmoko olv (n=olvaffe@122-116-62-89.HINET-IP.hinet.net)
02:51.34*** join/#openmoko Crfrodf (n=Crfrod@88.214.193.26)
02:58.30*** join/#openmoko broedje (n=hellvis@92.117.21.188)
02:58.52*** join/#openmoko behdad (n=behdad@CPE001217b19226-CM0012c9c84bc4.cpe.net.cable.rogers.com)
03:05.25*** join/#openmoko abraxa__ (n=abraxa@pD95FD207.dip.t-dialin.net)
03:08.46*** join/#openmoko raster (n=raster@firewall.tw.openmoko.org)
03:53.19*** join/#openmoko josch_ (n=josch@p57AD640E.dip.t-dialin.net)
03:55.18*** join/#openmoko mbuf (n=shakthim@61.16.248.242)
04:07.03*** join/#openmoko jkilb_ (n=jkilb@p5B208697.dip0.t-ipconnect.de)
04:19.20*** join/#openmoko fobos (n=fobos@78.90.88.244)
04:21.31*** join/#openmoko rtm (n=rtm@pool-151-199-46-27.bos.east.verizon.net)
04:32.37*** join/#openmoko justin_ (n=justin@208.74.129.215)
04:33.12justin_is there any date set in stone for the consumer release yet
04:40.06rtmgosh, there's no date for the *developer's* release yet.
04:47.42*** join/#openmoko XXLT (n=XXLT@herkules.hrz.tu-chemnitz.de)
04:56.35*** join/#openmoko SP-8472 (i=8472@dslb-084-056-228-207.pools.arcor-ip.net)
05:02.15*** join/#openmoko rtm__ (n=rtm@pool-151-199-57-58.bos.east.verizon.net)
05:14.50*** join/#openmoko Crfrod (n=Crfrod@88.214.193.26)
05:26.41ScaredyCathrmm... anyone else found their neo in a funny state in the morning ?
05:26.50*** join/#openmoko kW_ (n=kW@130.216.42.69)
05:29.36*** join/#openmoko fobos (n=fobos@78.90.88.244)
05:32.54*** join/#openmoko tholin (n=tholin@85.8.6.155.static.se.wasadata.net)
05:38.16*** join/#openmoko jeddy3 (n=mattiast@gw.sbg.se)
05:39.33mwesterwonders at the question, as if the neo is ever in a "normal" state
05:41.30*** join/#openmoko danilos (n=danilo@canonical/launchpad/danilos)
05:45.22*** join/#openmoko peter__b (n=biertrin@p54979CF9.dip0.t-ipconnect.de)
05:47.14*** join/#openmoko cibomahto (n=matt@ip145.coronado-crossing.phx.ygnition.net)
05:47.32*** part/#openmoko Khem (n=Khem@adsl-71-146-20-69.dsl.pltn13.sbcglobal.net)
05:59.18*** join/#openmoko affen (n=kala@194.126.113.157)
06:02.58ScaredyCatwell, perhaps not, but twice now about a week apart I've come back to the neo to find it in an apparent off state but the only way to get it to respond in any way is to remove and replace the battery
06:06.04cibomahtoScardeyCat:  That happens to me when I had the 'dim first, then lock' suspend mode selected
06:06.20cibomahtosurely you have a more interesting problem :-)
06:07.01*** join/#openmoko wolog (n=wolog@s15209028.onlinehome-server.info)
06:07.14*** join/#openmoko drath_ (i=vmaster@p5B07D421.dip.t-dialin.net)
06:07.43*** join/#openmoko ccube_ (n=ccube@ssh.ccube.de)
06:12.58*** join/#openmoko fgau (n=fgau@62.8.133.125)
06:18.58*** join/#openmoko geaaru (n=geaaru@host217-207-dynamic.8-87-r.retail.telecomitalia.it)
06:22.49*** join/#openmoko adjaxio (n=adjaxio@lns-bzn-49f-81-56-215-221.adsl.proxad.net)
06:25.32*** join/#openmoko trickie_ (n=trickie@basesoft.demon.nl)
06:28.42*** join/#openmoko ccube__ (n=ccube@ssh.ccube.de)
06:37.23*** join/#openmoko rmoravci1 (n=rmoravci@gtsgw.ttc.cz)
06:40.24*** join/#openmoko wolog (n=wolog@s15209028.onlinehome-server.info)
06:45.13*** join/#openmoko starox (n=starox@freeway.rd.francetelecom.com)
06:45.22*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
06:46.32Mekokay... my openmoko-devel-image/openmoko-qtopia-image builds succeeded, now only my openmoko-feed build is failing...
06:46.48*** join/#openmoko dneary (n=dneary@mne69-9-88-163-116-163.fbx.proxad.net)
06:46.52*** join/#openmoko adjaxio (n=adjaxio@lns-bzn-49f-81-56-215-221.adsl.proxad.net)
06:47.32*** join/#openmoko buz (n=buz@84-72-53-89.dclient.hispeed.ch)
06:48.13*** join/#openmoko adjaxio (n=adjaxio@lns-bzn-49f-81-56-215-221.adsl.proxad.net)
06:51.08cibomahtoMek:  Good job.  I haven't gotten an openmoko-devel-image to work in some days
06:51.35*** join/#openmoko jpieper__ (n=jpieper@207-180-187-171.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com)
06:52.43*** join/#openmoko Tanu (n=tanuva@e177232030.adsl.alicedsl.de)
06:54.17*** join/#openmoko aloril_ (n=aloril@h14939.gprs.dnafinland.fi)
06:55.21*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
06:57.49*** join/#openmoko tobmaster (n=tobmaste@gw.sinnerschrader.com)
07:04.53Hopscotchgood morning
07:13.18*** join/#openmoko vaiursch (n=erwin@84-72-189-254.dclient.hispeed.ch)
07:21.20*** join/#openmoko Sup3rkiddo (n=sudharsh@unaffiliated/sudharsh)
07:25.07*** join/#openmoko mjbroek (n=martijn@188.Red-213-97-48.staticIP.rima-tde.net)
07:28.03*** join/#openmoko TRIsoft (n=mac@p57A2BFE2.dip.t-dialin.net)
07:31.45*** join/#openmoko Bubbi (n=Bubbi@firewall.dwarf.dk)
07:32.25*** join/#openmoko bentob0x (n=laurent@ip-213-49-77-207.dsl.scarlet.be)
07:32.56*** join/#openmoko christian_ (n=christia@p5B16EDDF.dip.t-dialin.net)
07:38.49*** join/#openmoko t_s_o (n=tso@129.84-49-131.nextgentel.com)
07:39.20*** join/#openmoko Crfrodf (n=Crfrod@88.214.193.26)
07:40.08*** join/#openmoko fehmicans (n=canavar@78.164.154.217)
07:42.04*** join/#openmoko ccube__ (n=ccube@ssh.ccube.de)
07:45.00*** join/#openmoko jpieper__ (n=jpieper@207-180-187-171.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com)
07:56.59*** join/#openmoko caratorn (n=aratorn@tui75-3-88-168-237-15.fbx.proxad.net)
07:58.47*** join/#openmoko Deniz__ (n=deniz@212.156.217.162)
08:02.01*** join/#openmoko simon_ (n=simon@vcmsms1.soft.uni-linz.ac.at)
08:02.26*** join/#openmoko simon_ (n=simon@vcmsms1.soft.uni-linz.ac.at)
08:04.36*** join/#openmoko MarcOChapeau (n=mbarre@bgn92-4-82-238-213-101.fbx.proxad.net)
08:11.04*** join/#openmoko emilis_info (n=emilis@clt-84-32-58-67.vdnet.lt)
08:11.49*** join/#openmoko pyknite (n=pyknite@83.68.218.53)
08:14.57*** join/#openmoko lrg (n=liam@lrg2.demon.co.uk)
08:17.53*** join/#openmoko polz (n=polz@ozone.rtvslo.si)
08:29.07*** part/#openmoko Dunedan (n=dunedan@phoenitydawn.de)
08:29.10*** join/#openmoko Dunedan (n=dunedan@phoenitydawn.de)
08:33.51*** join/#openmoko zedstar (n=john@82-44-200-69.cable.ubr08.haye.blueyonder.co.uk)
08:36.16*** join/#openmoko Marex (n=marex@vasut.kolej.mff.cuni.cz)
08:37.26*** join/#openmoko ruoso (n=ruoso@195.23.92.2)
08:41.38josch_!seen michaelshiloh
08:41.40cdbot2MichaelShiloh (n=chatzill@166.129.245.150) was last seen quitting from #openmoko 15 hours, 6 minutes ago stating (Read error: 110 (Connection timed out)).
08:41.46josch_darn
08:49.08*** join/#openmoko elation (i=elation@gateway/tor/x-e825be9c4280a382)
08:50.44*** join/#openmoko polz (n=polz@lbcsi.fri.uni-lj.si)
08:52.04fish_can someone clarify that for me: i've read about that 'power management issue' here and there. is that a software-only problem or is there still an issue with the hardware?
08:52.53*** join/#openmoko suuuper (n=suuuper@81-208-88-100.ip.fastwebnet.it)
08:55.34*** join/#openmoko geaaru_ (n=geaaru@host106-213-dynamic.2-87-r.retail.telecomitalia.it)
08:58.16*** join/#openmoko nibbo (i=nibbo@gateway/shell/blinkenshell.org/x-d5043d7e30b5de9d)
08:59.52*** join/#openmoko mbuf (n=shakthim@61.16.248.242)
09:02.57*** join/#openmoko lu_zero (n=lu_zero@62-101-126-223.ip.fastwebnet.it)
09:03.00*** join/#openmoko tobmastr (n=tobmaste@gw.sinnerschrader.com)
09:04.00*** join/#openmoko greentux (n=lemke@ip-217-18-181-130.static.reverse.dsi.net)
09:14.37*** join/#openmoko ruoso (n=ruoso@195.23.92.2)
09:15.59*** join/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
09:21.07*** join/#openmoko cnwdup (i=harlekin@v1107.ncsrv.de)
09:21.10cnwduphello
09:21.50*** join/#openmoko geaaru__ (n=geaaru@host215-22-dynamic.21-87-r.retail.telecomitalia.it)
09:23.20*** join/#openmoko onisac (n=ale@p5B07397A.dip0.t-ipconnect.de)
09:23.20cnwdupI am seriously considering ordering a freerunner, but I have a few questions first I couldn't find answers for in the wiki. First: Is phoning possible? Seems as if sending SMS is possibly by now. What's the deal with receiving SMS? How is standby working?
09:24.15edistarcnwdup: phoning is possible
09:25.02emilis_infowhatabout battery life?
09:25.26edistaremilis_info: afaik it runs 6h when used actively
09:26.02emilis_infohmm
09:26.05emilis_infoand standby?
09:26.12cnwdupedistar: That's good. If it was possible receiving sms as well, I'd buy it right away. But with this not being the case, I am not quite sure. Thus I am interested in what exactly isn't working with receiving sms.
09:26.30edistaremilis_info: I suppose you mean suspend, I think about 60h is manageable
09:26.39edistarcnwdup: it can
09:26.46emilis_infocan you receive calls and sms in suspend?
09:26.56emilis_info60h is decent enough for me, for a linux phone ;-)
09:26.57edistaremilis_info: yes, it wakes up
09:27.01emilis_infocool
09:27.03emilis_info;)
09:27.12edistarat least usually;)
09:27.20cnwdupedistar: I can receive SMS but it's not able to read them or what? Or is the wiki outdated and it can send *and* receive sms?
09:27.58edistarcnwdup: last time someone asked here some people said that reading and writing sms is possibe
09:28.04edistar*possible
09:28.24cnwdupedistar: Oh, that's pretty cool.
09:28.34cnwdupThanks for your information. (= I think I'll order today.
09:29.07cnwdup*going to
09:29.32emilis_infowhere can you order it today?
09:29.45emilis_infoshop says it is sold out
09:29.52edistaremilis_info: trisoft.de/openmoko
09:29.56cnwdupemilis_info: On trisoft.de you can pre-order it for the german (european?) market.
09:29.57edistaremilis_info: for europe
09:30.11emilis_info404
09:30.18cnwdupAnd it says it'll be shipped at the end of this month.
09:30.27emilis_infoah, redirected to somewhere where it works
09:30.27*** join/#openmoko johncylee (n=john@firewall.tw.openmoko.org)
09:30.29emilis_info:)
09:30.55cnwdupAre there any reasons against ordering a freerunner now?
09:30.58*** join/#openmoko aloril__ (n=aloril@h15010.gprs.dnafinland.fi)
09:32.06edistarcnwdup: the usual.. might still be hw bugs that have't been found yet.. but that's na permanent reason
09:32.22edistarcnwdup: so in half a year you might think the same
09:32.34emilis_infohmm
09:32.49cnwdupYeah, the fact that it's open source and still has its bugs is actually no big deal for me.
09:33.47cnwdupEh, the bugs are not a big deal. The "open source" thing is actually a huge pro. :D
09:34.47edistarcnwdup: :)
09:35.45*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
09:36.25*** join/#openmoko pyknite (n=pyknite@83.68.218.53)
09:36.58*** join/#openmoko hatty (n=Hatty@203.193.154.146)
09:37.51*** join/#openmoko florian (n=fuchs@217.146.132.69)
09:39.09*** join/#openmoko DPThuught (n=tilli@mail.collax.com)
09:41.21pykniteis there a backup manager on the freerunner (for sms/mail/calendar/...)?
09:42.46*** join/#openmoko rd_ (n=dr@vnsecurity.net)
09:48.09ScaredyCatscp
09:48.58thosrsync?
09:50.17pyknitehum ok
09:50.33*** join/#openmoko Sup3rkiddo (n=sudharsh@unaffiliated/sudharsh)
09:50.55pyknitewhen i get my freerunner and got time (to work at school) i will see if i can code one (like some software on windoews mobile)
09:52.13rohpyknite well. you could write some ui for rsync or boxbackup
09:52.50zedstaror unison
09:52.51pykniteyeah exactly...
09:53.11pyknitethe graphiq tools are gtk? or something else?
09:53.31CIA-42openmoko: 03thomas * r4391 10/trunk/src/target/opkg/libopkg/opkg.c: opkg: add some safety macros
09:53.36zedstari think there are some gtk front ends to rsync and unison u can adapt
09:53.45rohpyknite basically everything that can render to x11
09:53.57rohgtk or efl or similar stuff is propably preferred
09:54.03*** join/#openmoko Gybrush_ (n=Gybrush@f053153046.adsl.alicedsl.de)
09:54.09rohyour choice
09:54.13pykniteok... and main language is python? c++?
09:54.36thospyknite, gtk+ is available on the default images
09:54.47pykniteok
09:54.51thospyknite, and python is not available on default images
09:54.54thosyet anyway
09:55.10thospyknite, I would suggest C and GTK+ if you have the apprioriate experience
09:57.18ScaredyCatsyncml !!
09:57.43pykniteok.. i will read some tut on gtk ;) (and c too, make too many c++ and ada at school :( )
10:00.17pyknite....ada is to boring
10:00.52Sup3rkiddopyknite, remember, real men directly program using logic gates
10:01.15*** join/#openmoko Heinervdm (n=thomas@pD9E151CF.dip.t-dialin.net)
10:02.03pykniteSup3rkiddo: hum... I'm not a men... I'm a student :D
10:02.14Sup3rkiddotoo :/
10:02.21Sup3rkiddoi am a student man
10:02.58pyknitein dev?
10:10.17SpeedEvilmwester:pin
10:15.59*** join/#openmoko lrg (n=liam@lumison.wolfsonmicro.com)
10:21.31*** join/#openmoko Varox_NB (n=doug@p4FD44090.dip.t-dialin.net)
10:25.09*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
10:32.53*** join/#openmoko morricone (n=foobar@dslb-084-057-171-203.pools.arcor-ip.net)
10:39.09*** part/#openmoko caratorn (n=aratorn@tui75-3-88-168-237-15.fbx.proxad.net)
10:41.13*** join/#openmoko ecraven (n=nex@plc31-103.linzag.net)
10:48.59*** join/#openmoko Mathiasdm (n=Mathias@vpna072.ugent.be)
10:49.40*** join/#openmoko geaaru_ (n=geaaru@host201-171-dynamic.25-79-r.retail.telecomitalia.it)
10:55.49*** join/#openmoko broedje (n=hellvis@92.116.110.198)
11:11.53ScaredyCatgoes a little ott with the btkb script
11:12.11SpeedEvilbtkb?
11:12.21SpeedEvilbluetooth keyboard?
11:15.10ScaredyCatyeah
11:15.32ScaredyCatworks well now... and I have zenity so it's all wizzy
11:15.40SpeedEvilzenity?
11:15.58ScaredyCatx dialogs for scripts
11:16.06SpeedEvilah
11:16.16ScaredyCatso now at least you get to pick the keyboard it connects to...
11:16.28ScaredyCatrather than it just attaching to the first one it finds
11:16.53SpeedEvil'It comes from the same family as dialog, Xdialog, and cdialog, but it surpasses those projects by having a cooler name.'
11:17.05ScaredyCatheheh
11:17.13ScaredyCatwell, it works too.
11:17.28ScaredyCatand I couldn;t get xdialog to compile properly
11:17.48ScaredyCatzenity was a pain - but now it compiles ok
11:18.11SpeedEvilNice.
11:20.10ScaredyCathttp://scap.linuxtogo.org/
11:21.15SpeedEvilNow all you need is a flexible configuration script for GPRS :)
11:21.26ScaredyCat:)
11:33.51*** join/#openmoko geaaru__ (n=geaaru@host253-212-dynamic.30-79-r.retail.telecomitalia.it)
11:40.48*** join/#openmoko profoX` (n=wesley@ubuntu/member/profox)
11:40.54profoX`hello everyone
11:41.07profoX`does the Openmoko support OpenGL ES?
11:42.02SpeedEvilNo
11:42.18SpeedEvilAt least - if you're asking 'is it 3D acceleerated'
11:42.39profoX`oh :(
11:42.40SpeedEvil3D acceleration will not happen in the freerunner
11:43.03thoswell, OpenGL ES is supposed to be in there, but no one is planning on writing a driver for it
11:43.10thosand it will probably suck balls anyway
11:43.29SpeedEvilYeah - it'll 'work' in the sense that it's all software emulated.
11:43.46thosSpeedEvil?
11:43.56rasterthe only way it will be written is if the specs get out from nda
11:44.02thosSpeedEvil, the glamo chip is supposed to have (some) GLES support
11:44.10thosbut like raster says...
11:44.11rasterthose with nda's dont have the time/money to work on it
11:44.12raster:(
11:44.33SpeedEvilAs I understood it , ES supports an emulated mode on dumb framebuffer too
11:44.36rastereven if u spent the time - i am very dubious of the qialty of 3d u will experience and if it was worth the effort :(
11:44.38SpeedEvilwhich is what I meant.
11:44.57*** join/#openmoko morricone (n=foobar@dslb-084-057-171-203.pools.arcor-ip.net)
11:45.05rasterSpeedEvil:  all GL can be eumlated
11:45.06rasterin software
11:45.09raster... in theory
11:45.10SpeedEvilIn that it's just a software 3D library in effect, not significnatly hardware accelerated.
11:45.16rasterits just a question of how slow it will be
11:45.17raster:)
11:45.21SpeedEvilYeah.
11:45.43rasterchances are it will be so slow - continental drift will begin to look interesting and fast
11:45.53SpeedEvil:)
11:45.57rasteru only get a fast software 3d enigne if u cut features and take shortcuts
11:46.11rasterand "introcue errors" in rendering that are "acceptable" tradeoffs for speed
11:46.13raster:)
11:46.15SpeedEvilAnd you have a fast video bus.
11:46.19rasteryeah
11:46.20rasterthat too
11:46.32*** join/#openmoko Lord_M (n=larry@200.184.118.132)
11:49.30*** join/#openmoko cesarb (n=cesarb@wikipedia/cesarb)
11:50.47SpeedEvilgoes back to routing his graphics board, such as it is.
11:52.20*** join/#openmoko Selveste1 (n=chatzill@85.235.243.199)
11:56.07*** join/#openmoko rtm (n=rtm@pool-129-44-185-65.bos.east.verizon.net)
12:02.06*** join/#openmoko geaaru_ (n=geaaru@host46-168-dynamic.24-79-r.retail.telecomitalia.it)
12:02.41*** join/#openmoko edistar_ (n=edistar@ip503ddd09.speed.planet.nl)
12:06.36*** join/#openmoko christooss (n=matic@84-255-246-158.static.t-2.net)
12:06.47*** join/#openmoko massoud (n=massoud@85.233.200.18)
12:09.32*** join/#openmoko pitbullpc (n=mbergand@194.32.100.97.cfl.res.rr.com)
12:13.13*** join/#openmoko Onef (n=Onef@host23-197-static.106-82-b.business.telecomitalia.it)
12:13.27Onefgood day to all!!!
12:13.49Bubbiwell hello Onef
12:14.09Onefthere are any information about the mass release?
12:14.34Onefin interne I've found many info... but no one are in agree with the others...
12:16.30BubbiOnef: shh.. it's a secret..
12:17.03Bubbias the topic suggests.. "The Freerunner phone (with wifi) will be released at some time"
12:17.11*** join/#openmoko tr2x (n=alvar@80-218-176-45.dclient.hispeed.ch)
12:17.22Bubbiso no-one really knows yet.. but hopefully soon
12:17.32CIA-42openmoko: 03thomas * r4392 10/trunk/src/target/opkg/libbb/ (unarchive.c unzip.c): opkg: fix some initialisation and double free issues in libbb
12:18.46OnefBubbi: I've read on top :D but I've thought maybe here on IRC someone know somthing more :)
12:19.50BubbiOnef: we're all here for the same thing then ;) Everybody wants to know when and what.. but no-one can reply :)
12:20.46Onefeheh understood ;) nevermind we'll wait lil'bit...
12:21.22rtmI think that CIA-42 guy knows the release date.
12:24.19ScaredyCat~lart the CIA
12:24.19apttakes the CIA to the vet for a "special" visit
12:24.53*** join/#openmoko tombhadAC (n=tombhad@pD95DC589.dip.t-dialin.net)
12:25.56Bubbidon't think you can trust the CIA...
12:26.18*** join/#openmoko andrunko (n=andrunko@200.184.118.132)
12:27.20*** join/#openmoko Sup3rkiddo (n=sudharsh@unaffiliated/sudharsh)
12:28.17rtmThe DVT tests involve waterboarding.
12:28.54pitbullpchi all, anyone seen sameo around?
12:29.17ScaredyCat~seen sameo
12:29.20aptsameo <n=samuel@AAnnecy-257-1-141-89.w90-41.abo.wanadoo.fr> was last seen on IRC in channel #openmoko, 126d 2h 3m 59s ago, saying: 'CM: let's hope so, yes.'.
12:29.33ScaredyCatthat would be a no hten pitbullpc
12:29.52pitbullpcdamn, he fell of the face of the earth
12:30.21pitbullpci was wondering what ever came of the AR6001 driver he was working on
12:31.02joschcould someone ping me when michaelshiloh comes online? i would be very grateful - a camisole is at stake!!
12:31.26ScaredyCatwhatever information we have is at least 26d 2h 3m 59 old
12:32.20ScaredyCats/26/126/
12:32.38pitbullpcwhere might that information be found
12:33.55ScaredyCatgoogle ... or sameo's website (where ever that may be)
12:34.32ScaredyCatlists.openmoko.org/pipermail/commitlog/2008-January/003453.html
12:34.42ScaredyCatlast commit
12:34.57*** join/#openmoko mbuf (n=shakthim@61.16.248.242)
12:35.06*** join/#openmoko lrg (n=liam@lrg2.demon.co.uk)
12:38.04pitbullpc<PROTECTED>
12:38.30pitbullpcat any rate, thanks for the info
12:39.22XorAhis driver work is effectively finished AFAIK
12:39.37*** join/#openmoko zedstar (n=john@82-44-200-69.cable.ubr08.haye.blueyonder.co.uk)
12:39.54pitbullpclast I talked to him he was having significant throughput issues
12:40.18XorAI beleive that was fixed with a firmware update from atheros if I recall the correct problem
12:40.46pitbullpcgood deal
12:41.15pitbullpci also sent him an Eye-fi card to hack at. anyone ever hear anything about that?
12:42.03XorAno
12:42.40pitbullpcdo you know what the eye-fi card is?
12:43.47XorAnope
12:44.17pitbullpcit is really pretty impressive. a 2 GB SD card with an embedded AR6001
12:44.45XorAsweet
12:44.57XorAlike the old Sandisk Connect+ cards
12:44.58pitbullpcdesigned to be cofigured via a pc and stuck in a digital camera to wirelessly upload your pics to flickr or whereever
12:45.47pitbullpchttp://www.eye.fi/
12:46.01mjryeah I've heard of it, it's a nifty kludge since digital cameras are so limited in wireless connectivity...
12:46.16mjrI mean come on, gimme at least bluetooth for cheap cams...
12:46.47mjrhaha, first vanity fi domain I've seen :)
12:46.55mjrWell, there's sci.fi, but that doesn't count ;)
12:47.27pitbullpcit has special firmware that would need to be changed, but i envision that this card could be hacked to be an easy wireless upgrade to any linux based cell/pda platform that doesn't have wireless and has an SD slot
12:47.42pitbullpclol
12:48.30pitbullpcnot sure with they just didn't use www.eye-fi.com
12:49.15mjrI dunno, the card is rather limited as sold, would probably be a nontrivial firmware hack...
12:49.35mjrdon't we have sdio wifi anyways?
12:49.58pitbullpcnot in that form factor
12:50.11mjrokay
12:50.32anrpyeah, usually its got extra length and thickness beyond the standard sd size
12:50.52anrpthat would be quite handy for a zaurus, for instance
12:51.08pitbullpcsince it is the size of a generic SD card it can be completely house within the SD slot
12:51.23anrpof course... many sd card slots are made & surrounded by metal
12:51.23pitbullpcnothing poking out to get broke off
12:51.30anrpso who knows how well it would work
12:52.22pitbullpcthat is true, but this thing is supposed to work in older SD digital cameras, and you know they didn't use plastic slot with this in mind
12:53.23ScaredyCathttp://dist.trolltech.com/video/wince/qtembedded44video.html
12:53.51anrpwince
12:53.52anrp~_~
12:53.53apt:/
12:54.14anrp...
12:54.17*** join/#openmoko krau (n=cktakaha@200.184.118.132)
12:56.59pitbullpcif the firmware could be replaced with the normal Atheros firmware for the chip, then this could be extremely easy (provided one has access to an Atheros Radio Test station and the stock firmware)
12:57.15*** join/#openmoko YetAnotherNoob (n=darkschn@dslb-084-058-163-238.pools.arcor-ip.net)
12:57.58*** join/#openmoko raster (n=raster@61-230-51-37.dynamic.hinet.net)
12:59.00Onefsorry to bother you again... there is some emulation of the current point of the release (usable under Windows...)
12:59.33*** join/#openmoko pyknite (n=pyknite@pub1.heig-vd.ch)
12:59.41anrpmentally swaps is and there
13:00.10mjrpitbullpc, I don't think it's likely to be hooked up in a way that the normal firmware would be able to function as directed from the host computer, but *shrug
13:01.06pitbullpcwell, you would need to have an SD interface to the PC
13:02.12pitbullpcin particular this thing called an Ellen Card (SD to PCI) and the PC would need to run the ART software to reflash the firmware
13:02.23*** join/#openmoko ewanm89_ (n=ewanm89@unaffiliated/ewanm89)
13:02.55YetAnotherNoobhello everyone. i'm building a devel image for neo1973 - or at least i'm trying - on an debian system. make setup works and after make openmoko-devel-image the system was busy for 2h or so. the process terminated with ERROR: '/home/darkschneider/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb' failed question: how do i find out what is wrong ? looks like the kernelbuild faild ...
13:03.31*** join/#openmoko krau (n=cktakaha@200.184.118.132)
13:03.34*** join/#openmoko jeddy3 (n=mattiast@gw.sbg.se)
13:03.44pitbullpcthe harder part would be doing the calibration
13:05.32pitbullpcanyway, i'll give this some more thought and ping some ideas of off some engineers i know at one of the Atheros authorized design centers
13:05.54pitbullpcgot to run, take care
13:05.59*** part/#openmoko pitbullpc (n=mbergand@194.32.100.97.cfl.res.rr.com)
13:06.17anrpYetAnotherNoob: maybe post the last 50 lines of the build process to pastebin
13:06.21anrpthat isn't really enough to say
13:07.19YetAnotherNoobwhat is pastebin ?
13:07.31*** join/#openmoko kdean06 (n=Kevin@fsf/member/kdean06)
13:08.45anrphttp://pastebin.com/
13:09.00anrpjust a tool to help to not clutter irc
13:09.40*** join/#openmoko massoud (n=massoud@59-124-111-20.HINET-IP.hinet.net)
13:12.14YetAnotherNoobvery well. posted to pastebin.
13:12.54anrp... now, you have to post the link here so we can see it :\
13:13.40YetAnotherNoobgood point. sorry. http://pastebin.com/m6332ff90
13:13.54*** join/#openmoko nnpiggy (n=nnpiggy@209.195.169.219)
13:14.10*** join/#openmoko sameo (n=samuel@AAnnecy-256-1-14-133.w90-10.abo.wanadoo.fr)
13:15.48anrpmmm, it actually failed on coreutils
13:16.02anrperror: short SHA1 4194 is ambiguous.
13:16.13anrpdunno where that 4194 came from
13:16.25anrpmaybe post /home/darkschneider/moko/openembedded/packages/coreutils/coreutils-native_5.3.0.bb ?
13:18.11ScaredyCatwonders if 1 freerunner could power another from it's usb port creating an endless supply of electricity
13:18.38mjrGood idea. If not, should be a goal for the next-gen device!
13:18.39ScaredyCatit's because someone didn't change the srcrev
13:18.42XorAScaredyCat: we should ship you two and see if you can end the universe from there
13:18.49ScaredyCatok..
13:18.51YetAnotherNoobposted: http://pastebin.com/d102279ed
13:18.52ScaredyCatno problem
13:18.58ScaredyCatship them now! :S
13:19.00ScaredyCat:D
13:19.02ScaredyCateven
13:19.44XorAScaredyCat: heh, Im first in the Queue for freerunner
13:20.23ScaredyCatdon't you just have to reach over to one of hte other desks in the office to get one though?#
13:21.15anrppokes ScaredyCat to elaborate on the srcrev
13:21.37ScaredyCatXorA: just be sure to say 'Yoink!' when you take them
13:21.38*** join/#openmoko AzalynHD (n=junon@mcbain.semsolutions.com)
13:21.52ScaredyCatanrp: there was a move from svn to git
13:22.11XorAScaredyCat: well as Im a few thousand miles away from office, that would have to be a loud YOINK!
13:22.34ScaredyCatXorA: yoip
13:22.56*** join/#openmoko massoud (n=massoud@59-124-111-20.HINET-IP.hinet.net)
13:22.57XorAYoink Over Internet Protocol :-)
13:26.01*** join/#openmoko pvborza (n=pvborza@79.119.153.220)
13:26.45*** join/#openmoko bmk789 (n=bmk789@165.138.40.201)
13:28.08*** join/#openmoko massoud (n=massoud@59-124-111-20.HINET-IP.hinet.net)
13:29.12Sup3rkiddowoo...dbus server support for vala :D
13:29.19Sup3rkiddooops..wrong window
13:33.49pvborzadoes anyone know Daniel Willmann's nick?
13:34.36*** join/#openmoko spydon (n=spydon@90-227-33-55-no42.tbcn.telia.com)
13:39.23fgaupvborza: i think, alphaone
13:39.25*** join/#openmoko nnpiggy (n=nnpiggy@209.195.169.219)
13:41.23CIA-42openmoko: 03sean_chiang * r4393 10/trunk/src/target/audio/om-gta02/gsmhandset.state: loud the voulume of mic
13:43.07pvborzathanks
13:43.17*** part/#openmoko pvborza (n=pvborza@79.119.153.220)
13:44.15*** join/#openmoko ruoso (n=ruoso@195.23.92.2)
13:45.09*** join/#openmoko `pwgen` (n=ew@62.156.207.10)
13:54.35*** join/#openmoko retracile (n=eli@66.205.179.175)
14:01.46SpeedEvilhttp://xkcd.com/413/
14:02.42*** join/#openmoko emonkey (n=emonkey@ubuntu/member/emonkey)
14:03.44*** join/#openmoko andrunko (n=andrunko@200.184.118.132)
14:03.59mwesterSpeedEvil:  pong!
14:04.32Bubbigreat fun there :P
14:04.48SpeedEviltries to remember what he was thinking of.
14:05.07SpeedEvilOh yeah.
14:05.10mwestersuggests ginsing; it's supposed to be good for memory
14:05.30SpeedEvilCan you give me an exact test that you'd like to do with a scope on the GTA01
14:05.37SpeedEvilto find glitches
14:07.52*** join/#openmoko retracile_ (n=eli@76-204-213-211.lightspeed.allntx.sbcglobal.net)
14:07.58mwester:)  I'll have to put together some test cases that would be reproducable.  Do you have a working SIM, or do we need to find a way to tickle the GSM w/o SIM?
14:08.07SpeedEvilyes.
14:10.12mwesterOk.  The new day has brought me new suspicions on this; I'll see if this new line of investigation reveals anything before I trouble you.  Thanks!
14:10.19BubbiSpeedEvil: I believe you need to specify which of the two things, you are saying yes to.. :)
14:10.25*** join/#openmoko tombhadAC (n=tombhad@pD95DC589.dip.t-dialin.net)
14:11.23SpeedEvilthe first
14:11.27SpeedEvilIt works.
14:11.32SpeedEvil(the SIM)
14:12.01*** part/#openmoko Onef (n=Onef@host23-197-static.106-82-b.business.telecomitalia.it)
14:12.11mwesterhas a prepaid one, and has refilled it several times now in troubleshooting this problem. This is becoming pricey...
14:13.00*** join/#openmoko paul0 (n=paulo@201-25-203-85.fnsce701.dsl.brasiltelecom.net.br)
14:14.06SpeedEvilwhy do you need cash?
14:14.35mwesterto send it SMS messages to make it wake up.
14:14.44SpeedEvilHuh?
14:14.48SpeedEvilOh
14:15.11SpeedEvilI assumed that incoming SMSs are free.
14:15.44ScaredyCatnot for americans
14:15.50mwesterIt will *occaisionally* fail when getting incoming signal quality messages, but the only sure way to cause the overrun is to send a few SMS's, and in the US the recipient is charged per message.
14:15.59ScaredyCatthey pay for both ends of a call too
14:16.00mwesterIt's a huge ripoff.
14:16.24SpeedEvilYes, I know that - I just forgot.
14:18.28*** join/#openmoko diego_at_work (i=5960ae7b@gateway/web/ajax/mibbit.com/x-9108c97bcda0b8d0)
14:18.51ScaredyCatw000t!
14:19.02ScaredyCatjust fixed audio on resume!
14:19.07SpeedEvil:)
14:23.10*** join/#openmoko jeffdameth (n=jeff@host-091-096-147-184.ewe-ip-backbone.de)
14:25.42*** join/#openmoko niclone (n=nicolas@d90-144-86-162.cust.tele2.fr)
14:27.40*** join/#openmoko icman (n=icman@123-240-172-21.cctv.dynamic.lsc.net.tw)
14:34.51*** join/#openmoko simon_ (n=simon@w208.wist.uni-linz.ac.at)
14:38.41*** join/#openmoko n0on3 (n=n0on3@81-208-83-247.fastres.net)
14:39.35BubbiScaredyCat: so if you wanted somebody to go broke, then you just spam him with a lot of SMS's?!
14:40.03Bubbipoor americans.. they never learn..
14:40.17ScaredyCatI guess so, americans get ripped off over calls...
14:40.34summatusmentisit's not all plans... some providers give you free incoming, mine does
14:40.42summatusmentisbut I don't think gsm providers do
14:42.46Bubbiincredible.. in Denmark you don't pay for stuff that you don't have a saying in.. so incomming calls/sms/mms are free of charge.. and IF you need to pay for a service, then you need to interact with the device, accepting to connect..
14:43.15I-MODin america all the providers want is an arm and a leg! i say let's give it to them!
14:43.15Bubbibut that's only if you are downloading stuff of your own choice
14:43.47*** join/#openmoko tomjoad (n=tomjoad@adsl-70-130-139-0.dsl.stlsmo.swbell.net)
14:44.12*** join/#openmoko ccube_ (n=ccube@ssh.ccube.de)
14:44.46summatusmentisBubbi: yeah, well, the US is seemingly incredibly backward in the way they do mobile stuff
14:45.10I-MODverizon is soooo great, that they strip all sms/mms down to 160 characters of text with none of the other media if it goes outside their network
14:45.14summatusmentisand by incredibly backward, I mean they want to suck the life and soul out of their consumers
14:45.26I-MODsummatusmentis, agreed
14:45.47summatusmentisI-MOD: they do? my parents won't be getting VZW
14:46.04I-MODyeah...i have a razr right now, i can't tether with EVDO either
14:46.13I-MODas verizon expressly forbids it
14:46.23summatusmentisyou're not even supposed to be tethering
14:46.51I-MODit lets me tether with 1xRTT
14:47.01summatusmentisyeah, still forbidden in ToS
14:47.14I-MODanother issue I have with verizon...
14:47.35*** join/#openmoko j_ack (n=j_ack@dsbg-4db7c01e.pool.einsundeins.de)
14:47.43summatusmentispeople out here really life VZW, but they're not paying attention
14:48.29I-MODthe one thing that is awesome is their coverage, when others don't have a signal, i still get signal 90% of the time
14:48.35anrplikes a (almost-)world-usable phone a bit more, but dislikes the mostly-lacking-3g in the us
14:48.47anrpso we use verizon for data cards :\
14:49.17I-MODmy company uses gprs/edge data cards through t-mobile for tech support that
14:49.23I-MOD's on-call
14:49.26summatusmentisthat's why I'm still not sure I'll be able to justify a FreeRunner, because I'll want to use it as my phone, and GSM doesn't work at my parents house
14:49.52summatusmentisI think it works where I go to school though
14:50.20I-MODgsm coverage where I am is pretty decent
14:50.40I-MODincluding the surrounding rural areas (which is surprising and nice)
14:51.23summatusmentiswhere are you located?
14:51.28summatusmentisif you don't mind my asking
14:51.54I-MODnorthern alabama (huntsville if you know the area)
14:52.00*** join/#openmoko key (n=key@nat/ibm/x-7ee518b5fb27b0b1)
14:52.03summatusmentisah, I'm in MN
14:52.13*** join/#openmoko zipola (n=zipola@zip.kortex.jyu.fi)
14:52.20I-MODmmmm....cold weather
14:52.27I-MODneed more of that down here
14:58.17*** join/#openmoko haakeyar (n=haakeyar@c9C364BC1.dhcp.bluecom.no)
14:59.00ScaredyCatmwester: ping
15:04.21spydonsoon this month has ended too without a released freerunner :'(
15:05.12*** join/#openmoko martijn_ (n=martijn@188.Red-213-97-48.staticIP.rima-tde.net)
15:09.06*** join/#openmoko JanMalte (n=janmalte@dslb-088-067-247-066.pools.arcor-ip.net)
15:09.50*** part/#openmoko JanMalte (n=janmalte@dslb-088-067-247-066.pools.arcor-ip.net)
15:15.11CIA-42freesmartphone.org: 03mickeyl * r243 10/trunk/specifications/otapi/org.freesmartphone.GSM.Call.xml.in: otapi/org.freesmartphone.GSM.Call.xml.in: docs++
15:16.02*** join/#openmoko kdean06 (n=kdean06@fsf/member/kdean06)
15:16.24summatusmentisspydon: the month isn't over yet
15:16.44*** join/#openmoko mjbroek (n=martijn@188.Red-213-97-48.staticIP.rima-tde.net)
15:17.00summatusmentisdoes anyone know why testing for MP is taking so long?
15:18.06spydonsummatusmentis, yeah you can always hope they release it before the month is over ^^
15:18.19summatusmentisthat's my hope, until May 1
15:20.18summatusmentisSup3rkiddo: you around?
15:21.18spydonone week :P
15:21.39spydonyou better buy a whip :P
15:21.56*** join/#openmoko SirBob1701 (n=mcginley@139.84.102.34)
15:22.06*** join/#openmoko jmichel (n=jmichel@modemcable135.172-56-74.mc.videotron.ca)
15:22.07summatusmentisI don't have $400 anyway, so...
15:23.23SpeedEvilMultiprocessor is a big step.
15:23.33CIA-42openmoko: 03zecke * r0ff5de564e25 10/src/libraries/qtopiaprediction/ (qtopiaprediction.pro wordprediction.cpp wordprediction.h): [prediction] Start extracting the prediction into a library used by other processes
15:23.33CIA-42openmoko: 03zecke * r42ff2ca73828 10/src/libraries/qtopiaprediction/ (qtopiaprediction.pro wordprediction.cpp wordprediction.h): [prediction] Start with the header file
15:23.33CIA-42openmoko: 03zecke * r3019cc28cb1c 10/src/libraries/qtopiaprediction/ (wordprediction.cpp wordprediction.h): [prediction] First implementation of the C Interface, untested
15:23.35CIA-42openmoko: 03zecke * rf39ac37db3b1 10/src/plugins/inputmethods/predictivekeyboard/pred.cpp: [prediction] Fix a wtf. Converting is a char to string is not guaranteed to be null terminated
15:23.50summatusmentisSpeedEvil: multiprocessor?
15:23.57SpeedEvilMP
15:24.00SpeedEvilignore me.
15:24.08summatusmentislol, oh
15:25.22*** join/#openmoko sameo_ (n=samuel@AAnnecy-256-1-29-58.w90-10.abo.wanadoo.fr)
15:26.54*** join/#openmoko ken_ (n=user@84.92.70.37)
15:27.02*** join/#openmoko polz (n=polz@cpe-213-157-235-31.dynamic.amis.net)
15:28.37CIA-42freesmartphone.org: 03mickeyl * r244 10/trunk/specifications/otapi/org.freesmartphone.GSM.MUX.xml.in: otapi/org.freesmartphone.GSM.MUX.xml.in: docs++
15:31.15*** join/#openmoko MarkTheDaemon_II (i=MarkTheD@phpbb/modifications/MarkTheDaemon)
15:32.50*** join/#openmoko summatusmentis (n=summatus@umm-yrless170.morris.umn.edu)
15:36.31*** join/#openmoko ahven (n=kala@194.126.113.157)
15:37.57jmichelAny ideas why I would get an error like "linux-openmoko_2.6.24+git.bb' failed" when building my image ?
15:39.01jmichelMore details here: "error: short SHA1 4194 is ambiguous."
15:39.21jmicheland: "fatal: Not a valid object name 4194"
15:40.31CIA-42openmoko: 03thomas * r4394 10/trunk/src/target/opkg/libopkg/ (opkg.c opkg_cmd.c opkg_download.c opkg_download.h): opkg: improve download callback handling and integrate into opkg_update_package_lists
15:41.47thoswooooo!
15:42.00thosopkg_update_package_lists() is pretty much complete!
15:42.46ScaredyCat!logs
15:42.48cdbot2Channel logs for #openmoko are archived at:
15:42.49cdbot2http://hentges.net/tmp/logs/irc/%23openmoko
15:42.50cdbot2Live-logs are available at
15:42.51cdbot2http://hentges.net/tmp/logs/irc/livelogs/%23openmoko.livelog
15:42.53cdbot2See ?? help-logs for usage instructions
15:44.35ScaredyCatjmichel: change the rev in openembedded/conf/distro/include/sane-srcrevs.inc to ${AUTOREV}
15:45.23*** join/#openmoko lunartear (n=cayres@ip68-103-160-30.ks.ok.cox.net)
15:46.36ScaredyCatand you anrp
15:48.44jmichelScaredyCat: what is anrp?
15:49.03ScaredyCatsomeone else in here wiht the same issue
15:49.31ScaredyCatt's someone's nick
15:49.48ScaredyCat/'s'
15:49.56*** join/#openmoko p3t3r__ (n=p3t3r__@gate1.net-you.de)
15:53.01jmichelScaredyCat: I think it worked... it succeeded the fetch part... thanks
15:53.26*** join/#openmoko zAMz1 (n=chatzill@dslb-084-058-072-232.pools.arcor-ip.net)
15:54.20ScaredyCatnp
15:55.32SpeedEvilScaredyCat: and me
15:56.31ScaredyCatnd you
15:56.34ScaredyCata
16:05.21*** join/#openmoko libervisco (n=libervis@tuxhacker/libervisco)
16:07.05*** join/#openmoko sandman__ (n=willis@c-71-63-44-103.hsd1.va.comcast.net)
16:08.23*** join/#openmoko kdean06 (n=kdean06@fsf/member/kdean06)
16:08.56*** join/#openmoko Tobi (n=tobi@pD9E87CD9.dip.t-dialin.net)
16:08.59*** join/#openmoko geaaru (n=geaaru@host23-213-dynamic.0-79-r.retail.telecomitalia.it)
16:15.50*** join/#openmoko MichaelShiloh (n=chatzill@166.129.17.252)
16:16.40*** part/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
16:21.51*** join/#openmoko key_ (n=key@nat/ibm/x-39e5a97b3d033e38)
16:22.49*** join/#openmoko j_ack (n=j_ack@dsbg-4db7c01e.pool.einsundeins.de)
16:27.14*** join/#openmoko rd_ (n=dr@vnsecurity.net)
16:28.49*** join/#openmoko playya (n=playya@pD9E0889F.dip.t-dialin.net)
16:34.31ScaredyCatSpeedEvil:
16:34.32ScaredyCatping
16:34.34*** join/#openmoko geaaru_ (n=geaaru@host194-218-dynamic.16-79-r.retail.telecomitalia.it)
16:35.22SpeedEvil...
16:36.40ScaredyCatyou said about the 01 have 60m/s to the gpu, but can it actually do that?
16:37.15SpeedEvilIn some ways, yes.
16:37.29ScaredyCati mean, can the cpu throw that much data fast enough
16:37.32SpeedEvilThe fundamental write speed is around that order of magnitude.
16:37.52SpeedEvilOf course, you're not really going to get much processing at that rate
16:38.07*** join/#openmoko behdad (n=behdad@209.167.232.101)
16:38.32ScaredyCatis there any data on the speeds currently being used on the 01...
16:38.43ScaredyCatit seems kinda scarey - the difference
16:38.57playyawow. the qt stuff looks cool
16:39.01*** join/#openmoko greentux (n=lemke@Z5899.z.pppool.de)
16:39.19SpeedEvilspeeds?
16:39.22SpeedEvilIt's 200MHz
16:39.57SpeedEvilThe display reads data out of main memory at 640*480*2*60 bytes/second
16:40.00SpeedEvilOr 36M
16:40.06*** join/#openmoko SP-8472 (i=8472@dslb-084-056-209-039.pools.arcor-ip.net)
16:40.16ScaredyCatk
16:41.23*** join/#openmoko mboldisc (n=mike@c-66-41-225-167.hsd1.mn.comcast.net)
16:41.27ScaredyCatright but the bandwidth is 5 times (ish) less on the 02
16:41.31*** join/#openmoko MarcOChapeau (n=MarcOCha@bgn92-4-82-238-213-101.fbx.proxad.net)
16:41.38SpeedEvilUm - no.
16:41.42SpeedEvilOk.
16:41.46SpeedEvilFrom the top.
16:41.50ScaredyCatk
16:42.00SpeedEvil02 - CPU - 7M/s pipeline - GPU
16:42.13SpeedEvilGPU refreshes the screen locally using local memory.
16:42.16SpeedEvil01 - CPU -
16:42.19SpeedEvil01 - CPU - LCD
16:42.32*** join/#openmoko Fauphi (n=kill@p5491AA5C.dip0.t-ipconnect.de)
16:42.52SpeedEvilIt's directly connected, and refreshes the framebuffer from main system RAM timeshared with normal RAM accesses.
16:43.21ScaredyCatok.. so th cpu is only concerned with getting the data to the gpu, once it's there the gpu will handle it easing the cpu load
16:43.27SpeedEvilyes.
16:44.28SpeedEvilWith a GPU that can do 2D/3D acceleration capably, and video decoding too, it's much less of an issue.
16:44.50ScaredyCatmmm.... if it shares the ram, can you poke it ?
16:44.53SpeedEvilBut the 3D acceleration for 02 will likely not be written, and there are performance problems, and it looks like video may not happen either.
16:45.08ScaredyCat:(
16:45.20SpeedEvilIt's just - from a sofftware point of view - with GTA01 - another area of RAM
16:45.51SpeedEvilIt's just that it's got special hardware that reads that area of RAM constantly out to the LCD at the appropriate rate.
16:46.48ScaredyCatright, so why not write directly to that then?
16:46.59ScaredyCator is that what's actually happening
16:47.02SpeedEvilYes
16:47.10SpeedEvilOn 01
16:47.33SpeedEvilOn 02, it's connected via an external bus to the GPU
16:47.46ScaredyCatright. ok now I get it
16:53.40Weiss_SpeedEvil: what performance problems? the 7M/s pipeline is simply too much of a bottleneck to get decent (say, OpenGL) throughput?
16:54.17*** join/#openmoko ecraven (n=nex@plc31-103.linzag.net)
16:56.17SpeedEvilIf you're saying 'blit rectangle from x to y' - then it's completely adequate and very fast.
16:57.08SpeedEvilIf you run up against something that the hardware can't quite do - or has no software for - you're reduced to rendering it on the CPU, and painting it on the framebuffer at 7M/second
16:58.04SpeedEvilWhich - when the whole screen is a over half a meg - can slow things down and make them jerky.
16:59.27*** join/#openmoko wolog (n=wolog@AOrleans-152-1-100-239.w90-21.abo.wanadoo.fr)
16:59.49ScaredyCatso only an issue if you need a really high framerate
16:59.51*** join/#openmoko CVirus (n=GoD@82.201.174.127)
17:00.04ScaredyCatie can it play doom == no
17:00.11ScaredyCat?
17:00.34*** join/#openmoko summatusmentis (n=summatus@umm-yrless170.morris.umn.edu)
17:00.50SpeedEvilWorst case, drop to QVGA and it'll be fine.
17:01.29SpeedEvilAt 30FPS+
17:01.59ScaredyCatwell, we only want 24.5 :)
17:06.24*** join/#openmoko Crfrod (n=Crfrod@88.214.193.26)
17:09.49*** join/#openmoko fsteinel (n=fsteinel@pD9FBBF10.dip.t-dialin.net)
17:12.35*** join/#openmoko abraxa_ (n=abraxa@pD95FD207.dip.t-dialin.net)
17:12.49*** join/#openmoko eikonos (n=eikonos@S0106001c104ae594.gv.shawcable.net)
17:13.34*** join/#openmoko gambler (n=orion@203-217-45-11.dyn.iinet.net.au)
17:13.43*** join/#openmoko Blastur (n=blastur@kr-lun-168-149-233-83.3.cust.bredband2.com)
17:14.00*** join/#openmoko MetaMorfoziS (n=avr@3e70d12b.adsl.enternet.hu)
17:18.42*** join/#openmoko peeps[work] (n=peeps@bwext.kpimdp.com)
17:18.56peeps[work]what's the color depth of the GTA02 screen?
17:19.12peeps[work]didn't see it on the wiki
17:19.18SpeedEvil17 bits, same as GTA01
17:19.20SpeedEvil16
17:20.29jmichelScaredyCat: Thanks now my image was able to build
17:20.40ScaredyCat:D
17:20.51peeps[work]hmm, i just read that the bus to the graphics chip has only 7MB/s bus on GTA02.  this means at 640x480x2 you get about 13 fps max?
17:21.26peeps[work]i mean 11
17:21.33jmichelScaredyCat: But I need the source for the kernel and it seems that there is no more INHERIT += "rm_work" in the config that I can comment to keep the downloaded source
17:21.37joschpeeps[work], hush! glamo bus performance is a forbidden word here!
17:21.56*** join/#openmoko goxboxlive (n=goxboxli@208.84-48-176.nextgentel.com)
17:22.28ScaredyCatif it's not there jmichel it shouldn;t clean it out..
17:22.34*** join/#openmoko wibbit (n=douglasf@host-84-9-13-237.dslgb.com)
17:22.37ScaredyCatyou should still have it
17:22.54wibbitHello all
17:22.56peeps[work]but 11fps makes baby mokoninja cry
17:23.00SpeedEvilpeeps[work]: about that.
17:23.21SpeedEvilpeeps[work]: QVGA is better - and if you can do some of the work locally, that's also better
17:23.26SpeedEvil(on the gamo)
17:23.52peeps[work]what do you mean "do some of the work locally"?
17:24.07ScaredyCatyou have to draw it on paper
17:24.12wibbitAny know of any one who's tested the freerunner (or gta02) in Russia?
17:24.18jmichelScaredyCat: Shouldn't it be in build/tmp/work/om-gta01-angstrom-linux-gnueabi/linux-openmoko-1_2.6.24+git20080423-r0/ because it is not there
17:24.36SpeedEvilpeeps[work]: if it's simple 2D manipulation that can be done on the glamo.
17:27.18ScaredyCat..
17:27.24ScaredyCatmm I have it jmichel
17:27.27*** join/#openmoko doc|work (n=doc@gentoo/contributor/doc-007)
17:27.28ScaredyCatbuild/tmp/work/om-gta01-angstrom-linux-gnueabi/linux-openmoko-1_2.6.24+git20080423-r0
17:27.45ScaredyCatthe source is in the git dir
17:28.48jmichelno git dir for me :(
17:29.36*** join/#openmoko SirBob1701 (n=mcginley@139.84.102.34)
17:29.39ScaredyCat:o
17:30.23*** join/#openmoko Sup3rkiddo (n=sudharsh@unaffiliated/sudharsh)
17:30.47jmichelcould the rm_work variable be somewhere else than local/conf/site.conf ?
17:31.24ScaredyCatbuild/conf/
17:31.45jmichelok I see
17:31.53ScaredyCatlocal.conf
17:31.53jmichelsorry that was my mistake
17:31.55ScaredyCatin there
17:31.57ScaredyCattry that
17:31.58jmichelthanks
17:39.23*** join/#openmoko Marex (n=marex@vasut.kolej.mff.cuni.cz)
17:40.58*** join/#openmoko heikkit_ (n=chatzill@c-67-188-122-139.hsd1.ca.comcast.net)
17:42.12*** join/#openmoko nnpiggy (n=nnpiggy@209.195.169.219)
17:42.54*** join/#openmoko zell1983 (n=zell1983@host83-177-dynamic.30-79-r.retail.telecomitalia.it)
17:46.43cb22_ba doink a doink doink
17:50.02*** part/#openmoko jeffdameth (n=jeff@host-091-096-147-184.ewe-ip-backbone.de)
17:51.24cb22_is that 7mb/s read / write shared or write only?
17:53.55*** join/#openmoko miip (n=miip@p54A55D8B.dip.t-dialin.net)
17:55.04*** join/#openmoko eikonos (n=eikonos@S0106001c104ae594.gv.shawcable.net)
17:55.33*** join/#openmoko rcxdude (n=rcxdude@host86-155-197-165.range86-155.btcentralplus.com)
17:56.10*** join/#openmoko caratorn (n=aratorn@tui75-3-88-168-237-15.fbx.proxad.net)
17:58.00*** join/#openmoko crunsher (n=crunsher@p54B8F950.dip.t-dialin.net)
17:58.20*** part/#openmoko crunsher (n=crunsher@p54B8F950.dip.t-dialin.net)
17:58.34*** part/#openmoko zell1983 (n=zell1983@host83-177-dynamic.30-79-r.retail.telecomitalia.it)
17:58.56*** part/#openmoko mboldisc (n=mike@c-66-41-225-167.hsd1.mn.comcast.net)
18:02.07*** join/#openmoko fulgas424 (n=fn@a83-132-24-119.cpe.netcabo.pt)
18:05.42*** join/#openmoko Fradeve (n=fradeve@87.13.132.151)
18:05.55*** join/#openmoko Tob2 (n=tobi@pD9E87CD9.dip.t-dialin.net)
18:07.28*** join/#openmoko MichaelShiloh (n=chatzill@76.208.209.165)
18:08.56*** join/#openmoko grummel (n=Grummel@2a01:198:21d:0:29:dfe9:1217:9daf)
18:11.28*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
18:13.36*** join/#openmoko ccube (n=ccube@ssh.ccube.de)
18:16.09*** join/#openmoko `pwgen` (n=ew@port-92-193-112-200.dynamic.qsc.de)
18:18.55*** join/#openmoko ewon (n=ewan@skynet.skynet.ie)
18:24.52*** join/#openmoko LetoT1 (n=paul@bofh.xelerance.com)
18:25.54*** join/#openmoko Mathiasdm (n=Mathias@vpnc105.ugent.be)
18:28.43*** join/#openmoko wasanderes (n=chatzill@p4FD3EF20.dip.t-dialin.net)
18:31.04*** join/#openmoko mortenlysgaard (n=mortenly@85.221.51.109)
18:31.55*** join/#openmoko quicksand (i=3f51a178@gateway/web/ajax/mibbit.com/x-b7878ba308116a25)
18:35.04*** join/#openmoko mhymn (n=mhymn@unaffiliated/mhymn)
18:37.56*** part/#openmoko mhymn (n=mhymn@unaffiliated/mhymn)
18:38.33*** join/#openmoko rd_ (n=dr@vnsecurity.net)
18:49.01*** join/#openmoko pH5 (n=ph5@e178208112.adsl.alicedsl.de)
18:51.28*** join/#openmoko Varox_NB (n=doug@p4FD44090.dip.t-dialin.net)
18:53.14*** join/#openmoko ahbritto (n=guest@adsl-69-104-245-232.dsl.pltn13.pacbell.net)
18:54.34*** join/#openmoko baze (n=baze@92.228.15.245)
18:58.56*** join/#openmoko adjaxio (n=adjaxio@lns-bzn-49f-81-56-215-221.adsl.proxad.net)
19:01.11*** join/#openmoko lu_zero (n=lu_zero@151.57.19.50)
19:02.26*** join/#openmoko pvborza (n=pvborza@89.123.76.12)
19:07.08*** join/#openmoko christooss (n=matic@89-212-20-253.dynamic.dsl.t-2.net)
19:09.05*** join/#openmoko guillaum1 (n=Guillaum@AMontsouris-153-1-75-26.w90-2.abo.wanadoo.fr)
19:09.37*** join/#openmoko geaaru__ (n=geaaru@host68-212-dynamic.17-79-r.retail.telecomitalia.it)
19:12.36*** join/#openmoko jorgenpt (n=jorgenpt@ip6.tjer.no)
19:22.32*** join/#openmoko norro_ (n=norro@e182045199.adsl.alicedsl.de)
19:24.00*** join/#openmoko ajbrun (n=ajbrun@host86-153-109-113.range86-153.btcentralplus.com)
19:26.09*** join/#openmoko Bubbi (i=Bubbi@90.184.128.67)
19:30.31*** join/#openmoko jserv--- (n=jserv@61-230-51-56.dynamic.hinet.net)
19:34.10*** join/#openmoko d1 (n=dr@vnsecurity.net)
19:38.45*** join/#openmoko Grummel69 (n=Grummel@2a01:198:21d:0:29:dfe9:1217:9daf)
19:39.02*** join/#openmoko Mathiasdm2 (n=Mathias@vpnc105.ugent.be)
19:39.45*** join/#openmoko d1 (n=dr@vnsecurity.net)
19:41.20*** join/#openmoko emonkey (n=emonkey@ubuntu/member/emonkey)
19:43.46*** join/#openmoko bricode (n=bricode@201.198.2.17)
19:43.47*** join/#openmoko rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
19:46.42*** join/#openmoko pmw (n=pmw@m461336d0.tmodns.net)
19:48.17*** join/#openmoko baze (n=baze@92.228.15.245)
19:51.06*** part/#openmoko pvborza (n=pvborza@89.123.76.12)
19:52.49*** join/#openmoko fgau (n=fgau@pD95395A3.dip0.t-ipconnect.de)
19:54.36*** join/#openmoko rd_ (n=dr@vnsecurity.net)
19:58.12bricodeAny hints as to how to get the u-boot menu? I've tried all combinations of the aux key and power key, but the menu never displays.
19:58.31ahvenhold down aux and press power?
19:58.32bricodeGTA02v3 (as reported by software) GTA02v4 as printed on the PCB.
19:59.14bricodeahven: Tried that. Holding for 4 seconds. Then 10. Doesn't work.
19:59.17ahvenhold down aux and press and hold power until menu appears*
19:59.24ahvenit doesn't turn on at all?
19:59.53bricodeNot while the aux button is held down.
20:00.05ahventime doesn't matter, only the fact that it must be pressed down whilst holding down power
20:00.07bricodeJust pressing the power button it will boot.
20:00.42ahvenis the aux functioning as should with the software?
20:00.57bricodeYes.
20:01.19ahvenstrange
20:01.27bricodeYeah.
20:10.10*** join/#openmoko mortenlysgaard (n=mortenly@85.221.51.109)
20:13.51*** join/#openmoko malik1972 (n=malik197@e182058132.adsl.alicedsl.de)
20:14.07*** join/#openmoko t_s_o (n=tso@129.84-49-131.nextgentel.com)
20:15.52*** part/#openmoko malik1972 (n=malik197@e182058132.adsl.alicedsl.de)
20:16.22bricodeIs there any way to force a new bootloader (without a debug board)?
20:16.40bricodeI keep getting  "File is not targeted for use by this device" errors with dfu-util.
20:20.01*** join/#openmoko wasanderes (n=chatzill@p4FD3EF20.dip.t-dialin.net)
20:24.11mwesterbricode:  whatever it is you are doing, without a debug board you are almost certainly in grave danger of bricking the device.
20:25.23bricodemwester: Yep. I realize that. I'm already well on my way. Still boots up, but can't mount mtdblock4.
20:31.04joschMichaelShiloh, hi! did you receive my email concerning the camisole? :-)
20:42.26quicksandSorry josch, He's Just Not That Into You.
20:42.36quicksand;-)
20:42.40joschnooooo!!
20:42.44josch:'(
20:42.53joschMichaelShiloh, dont do this to me!
20:43.47MichaelShilohhi josch, sorry, i wasn't watching irc. i don't think i saw any camisole email. can you resend? should i ask?
20:43.56joschdarn
20:44.12joschi sent you an email concerning my tshirt for community member of the week ^^
20:46.27joschMichaelShiloh, did you receive it? it had the subject "Community member of the week price"
20:46.50*** join/#openmoko broedje (n=hellvis@92.116.217.66)
20:47.11Spydonthat sounds like a spam subject ^^
20:47.27josch-___-
20:47.28I-MODlol, you're right. it does
20:47.30MichaelShilohoh, yes, i did receive that. sorry - i thought i had replied. i have not yet ordered it, but will do so shortly. i aplogize for the delay.
20:47.31tcMichaelShiloh: Hi Micheal, I asked on the community list a few days ago if some GTA02v5's will ship and if so will the power consumption be the same as v6? I really think it needs some clarification, can you help?
20:47.40joschMichaelShiloh, ah great
20:47.54doc|worktc that's been answered on the list
20:47.59joschMichaelShiloh, would be nice if it would arrive by the end of next week - is this possible?
20:48.28tcdoc|work: Are you referring to the email by Tony?
20:48.31MichaelShilohjosch: yes, i can order it today or tomorrow, should get there end of next week. i'll rush the shipping.
20:48.57doc|worktc I'm not sure exactly, I just thought I read that all phones would have the problem fixed
20:48.59joschMichaelShiloh, thank you very much!!!
20:50.10tcdoc|work: I've been following it on the list and I cannot find a conclusive answer at all
20:50.46doc|worktc is it a big deal really? it's only when the led is actually lit anyway
20:51.21*** join/#openmoko zedstar (n=john@82-44-200-69.cable.ubr08.haye.blueyonder.co.uk)
20:52.15tcdoc|work: No, I don't think it's that much of a big deal but if it does affect power consumption it would be nice to have an answer
20:52.51*** join/#openmoko heikkit_ (n=chatzill@c-67-188-122-139.hsd1.ca.comcast.net)
20:54.05ScaredyCathehehe.. walked into that one MichaelShiloh .. :)
20:54.24tcsorry :)
20:54.40joschMichaelShiloh, sent you another mail with a new shipping address for next week
20:55.11ScaredyCatstabs sipgate
20:59.02tomjoadtc: What is wrong with the explanation from Tony?
21:00.33tctomjoad: "A5 or A6 *should* all apply the LED transistor change"
21:01.46tctomjoad: The word should is a concern of mine
21:06.25tomjoadtc: yeah, I see what you're saying. I can't decipher the wiki page he linked to either as to the change being applied to A5
21:10.16tctomjoad: Yeah, that's why I would like an official response from Steve or Micheal
21:11.16tomjoadtc: I agree i would like to see that too. or atleast more of a definitive, "yes the A5 has the transistor fix"
21:11.50tomjoadtc: though I have to admit I'll be buying in the first batch eitherway
21:12.30mjrI think it's nitpicking to be concerned about it, though one agress it should be further made absolutely clear before sales
21:13.21mjrAs to the question of v5's power consumption vs. v6, it's pretty clear it's not the same. The wiki mentions at least a 1 mA change not applied in v5 :]
21:14.45tcmjr: I think it's nit picking too, but the longer the question goes unanswered the more concerned I am getting
21:15.26mjrbasically I think it has been answered
21:15.29*** join/#openmoko paul0 (n=paulo@200-102-50-204.fnsce701.dsl.brasiltelecom.net.br)
21:15.46mjrand it's nitpicking to get concerned for not having it hammered into your skull
21:17.57tcI just don't think leaving it with a "should" is the greatest idea.
21:18.18anrpi think what he's trying to say is that he'd be happier if he didn't even know it was a problem
21:18.22anrp:\
21:18.44*** join/#openmoko geaaru (n=geaaru@87.14.206.193)
21:18.49mjryea
21:18.50tcanrp: I think you're right :/
21:19.28tomjoadI'm still concerned about the GSM firmware working with all AT&T sim cards
21:20.10tomjoadi sent an email to the ml and got one response but it was not somebody with an OM email so I assume they were just guessing
21:20.51joschMichaelShiloh, could you drop me a message via irc when you manage to order it? did you receive my email with the changed shipping address?
21:20.58*** join/#openmoko Khem (n=Khem@71.146.20.69)
21:21.25tctomjoad: are you worried you will get a contract and the sim not working?
21:22.12tomjoadtc: I am actually already with AT&T and have an old sim but received a new sim that is on the list of non-working sims
21:22.41tomjoadtc: i would like to start using the new sim but am afraid to incase the new one doesn't work with the FR
21:23.15tcah I see :/
21:23.31tomjoadtc: I guess I'll just stick with the old one
21:25.00*** join/#openmoko j_ack (n=j_ack@dsbg-4db7b0c9.pool.einsundeins.de)
21:27.19MichaelShilohjosch: got it. will ship to new address. and i will send you email w/ tracking number when i order it.
21:27.20*** join/#openmoko _rob (n=rob@85.233.59.8.static.cablesurf.de)
21:27.23*** join/#openmoko Demitar (n=demitar@h-2-44.A146.cust.bahnhof.se)
21:28.24*** join/#openmoko Demitar_ (n=demitar@h-2-44.A146.cust.bahnhof.se)
21:30.01*** join/#openmoko bmk789 (n=bmk789@c-98-223-16-230.hsd1.in.comcast.net)
21:31.07bricodeMichaelShiloh: Do you guys have debug boards in stock these days for gta02?
21:32.47broedjeany repositories that i could put in the ipkg app? i have the late march firmware
21:33.59broedjedoes alternate mean.... flash anything you like, as long it is compatible? or is there a file existing with -alternate suffix?
21:34.25MichaelShilohbricode: good question. i think not yet. i will ask. ping me on the kernel list in a few days if you don't hear back.
21:36.03bricodeMichaelShiloh: Cool. Thanks.
21:36.43emdetealphaone: query..?
21:38.22*** join/#openmoko unarzna (i=hk69690@node1.cluster.cs.uta.fi)
21:40.05*** join/#openmoko christian (n=christia@p5B16EDDF.dip.t-dialin.net)
21:45.05*** join/#openmoko krau (n=cktakaha@200.184.118.132)
21:46.18*** join/#openmoko rtp (n=rtp@sat78-7-88-166-121-96.fbx.proxad.net)
21:47.09*** join/#openmoko bmk789_ (n=bmk789@c-98-223-16-230.hsd1.in.comcast.net)
21:51.54*** join/#openmoko polz_ (n=polz@cpe-213-157-235-31.dynamic.amis.net)
21:52.37*** join/#openmoko prpplague (n=dave@mail.americanmicrosystems.com)
21:53.04prpplagueanyone know if the neo1973 support in qemu is being pushed upstream to qemu main tree?
21:53.42thosprpplague, ask balrog-kun
21:54.14prpplaguethos: ok thanks
21:54.33thosprpplague, he wrote it :-)
21:55.10prpplaguei thought andrew with o-hand.com did most of the core s3c24xx support
21:56.40*** join/#openmoko sandsmark (i=sandsmar@cassarossa.samfundet.no)
21:56.56sandsmarkif I install qtopia on the freerunner, is any gtk-stuff needed?
21:57.16balrog-kunprpplague: yes, it's planned
21:57.19thosprpplague, that's the same person
21:57.40prpplagueahh
21:57.55balrog-kunprpplague: there's so much higher priority stuff to do before that though :(
21:58.16prpplaguebalrog-kun: is there seperate patches for adding s3c24xx support and adding neo1973?
21:58.59balrog-kunprpplague: nope, currently it's not split into patches, just a svn tree
21:59.01*** join/#openmoko polz__ (n=polz@cpe-213-157-235-31.dynamic.amis.net)
21:59.25prpplaguebalrog-kun: ahh ok
21:59.41*** join/#openmoko aloril_ (n=aloril@h13460.gprs.dnafinland.fi)
22:01.01balrog-kunprpplague: are you specifically interested in s3c24xx emulation?
22:01.06*** join/#openmoko ruoso (n=ruoso@85.138.47.186)
22:01.22prpplaguebalrog-kun: yea, thats mainly what i'm interested
22:02.10balrog-kunif there was a machine other than neo1973 using the s3c24xx code then i could even go over this weekend and merge the core stuff
22:02.25balrog-kunthis part is rather clean and upstreamable
22:02.51prpplaguehttp://www.elinux.org/Hammer_Board
22:02.57prpplaguethats where i'm starting
22:03.12prpplaguei'll be adding a 2440 device as well
22:03.39prpplaguehttp://www.elinux.org/Nail_Board
22:04.29balrog-kunprpplague: that's very neat hardware
22:04.42*** join/#openmoko fix (n=fix@78-23-85-249.access.telenet.be)
22:04.43prpplaguebalrog-kun: thanks
22:05.21balrog-kunprpplague: imho it should be safe for a person to develop against the qemu-neo1973 tree their own emulator, i think there's somene already doing that (though their tree isn't public)
22:05.41*** join/#openmoko renatofilho^_ (n=renato@200.184.118.132)
22:05.52prpplaguebalrog-kun: yea i did a diff, looks pretty straight forward
22:06.32prpplaguebalrog-kun: i'll be tinkering with it over the next couple of weeks, any problems pestering you on this channel if i have any questions?
22:07.15balrog-kunprpplague: nope, pester me any time, i just may be a bit slow ansering some days
22:07.17*** join/#openmoko lrg (n=liam@lrg2.demon.co.uk)
22:07.30prpplaguebalrog-kun: np, i'm sure mallum is a slave driver
22:08.28balrog-kuni can also merge patches from people into qemu-neo1973 tree and if we reach something usable i can merge it upstream directly together with the rest of s3c24xx code
22:08.43balrog-kunit's just that if i upstreamed that now there would be no machine code using it
22:08.53balrog-kunprpplague: no, quite the opposite :)
22:09.06prpplaguebalrog-kun: hehe
22:09.06balrog-kunit's my university that's my slave driver :(
22:09.26prpplaguebalrog-kun: ok, i'll do some testing and get back with you about some patches
22:09.34SpeedEvilrmmod slave
22:10.18prpplaguebalrog-kun: thanks and later
22:12.39*** join/#openmoko TAsn (n=TAsn@89.1.0.74.dynamic.barak-online.net)
22:12.59ljpsandsmark: no gtk needed with qtopia
22:14.39sandsmarkok, the anti-qtopia-rant on the wiki was a bit misleading
22:15.07raboofqtopia doesn't even need X, iirc, does it? or has that changed?
22:15.27ljpno x needed
22:15.44ljpanti qtopia rant?
22:15.50sandsmarkhttp://wiki.openmoko.org/wiki/Why_Not_QT
22:15.54raboofdoes that also mean you can't run X apps when you chose qtopia? or can they live together?
22:16.13ljpthat does mean no x apps too
22:16.54sandsmarkbah, who needs X, when you have qtopia
22:17.17sandsmarkwants to port kdelibs and amarok ^_^
22:17.20mjrOM is apparently porting (with some pains ;] ) qtopia on X11 to be able to run those apps alongside the rest
22:17.27ljpactually gtk apps use more memory than qtopia apps
22:17.37sandsmarkljp: indeed
22:17.51sandsmarkljp: but that wiki page was misleading, because it compared qt + gtk to just gtk
22:18.33mjryes, and that's because OM is (well, at least was, dunno nowadays with the E) gtk-based
22:19.05mjrit's not misleading, you're just trying to read it in a context it was not written for
22:19.25ljpits not misleading, its just plain wrong
22:19.34ljpespecially about memory constraints
22:20.04ljpqtopia takes less space in flash and has more functionality than the gtk stuff
22:20.28ljpif you include x and all gtk dependencies, daemons, etc
22:20.57mjrljp, congratulations, thanks for demonstrating yet again that you lack reading comprehension skills and are simply droning on about the wonders of qtopia whenever you get the chance
22:21.06ljppff
22:21.15ljpprove me wring
22:21.15ljpwrong
22:21.16raboofafaics the page tells you why not to use QT if you stick to the existing openmoko framework (which includes X and GTK)
22:21.42mjrindeed what raboof said
22:21.42raboofit doesn't seem to be referring to ripping out all the X and GTK stuff and replacing the entire platform with qtopia
22:21.54mjrindeed it isn't referring to that
22:22.27ljp"
22:22.29mjrand it, methinks, makes it _very_ clear
22:22.32raboof(key words in first paragraph: "application developers", not platform developers)
22:22.35*** join/#openmoko polz (n=polz@cpe-213-157-235-31.dynamic.amis.net)
22:22.42ljp"OpenMoko is a distribution designed around GTK+2 and not Qt."
22:22.52ljppretty much seems to sum up all the bias
22:23.12raboofbias? looks like an undeniable fact to me.
22:23.13mjrit's not bias, it's a fucking statement of fact
22:23.41mjr(forgetting recent movement toward perhaps something raster-based...)
22:24.02ljpthis seems to rant that because it was first conceived for gtk, nothing should ever change
22:24.52mjrNo, you moronic corporate drone. It says that if you have a gtk-based platform, you incure less overhead and are more consistent if you use GTK for your apps. It says no more, and no less.
22:24.56ljplook and feel is wrong, as qt can have the same look, as we can tie into the glib event loop. look at distributions that do this
22:25.13ljpat least I dont call anyone names to try and prove a point
22:25.25mjrthat also was a statement of fact
22:25.32ljpppfft
22:25.56SpeedEvilhands out pugel sticks.
22:26.33mjrI understand how some facts may be unpleasant to hear.
22:26.33ljpcalling someone names ike that just proves you are being childish and cannot come up with good enough reasons to back up your side of the argument
22:26.33raboofljp: indeed the page looks like it's intended for application developers targeting the *current* openmoko platform, not a theoretical QT-based platform
22:26.40mjrof course, you forget all about me providing the actual reasons why you're being a moronic corporate drone right after saying you are.
22:27.28ljpfuk off
22:28.11mjryou're purposefully twisting the wiki page to suit your blind "qtopia everywhere" agenda, completely ignoring any sanity in interpreting what the page is actually trying to say
22:28.33raboofljp: as for the look and feel: the page doesn't say it's impossible for QT to have the same look and feel, but that making that happen will be quite a bit of work.
22:28.38raboofljp: sounds reasonable to me, too
22:29.14ljpwell, seeing as they changed directions a few times already, it doesnt reallt matter
22:29.44raboofljp: good. then why all the discussion? :)
22:29.51ljpopenmoko is about freedom, anyway
22:30.27raboofagreed entirely, the work being done to bring qtopia to the openmoko hardware is really interesting
22:30.30mjrHell, calling the wiki page an (implicitly anti-qtopia) rant even when it explicitly says that _on a qtopia platform_ you should likewise use qtopia and stay away from gtk, now that is pure fanatical blindness to the extreme
22:30.39ljpraboof: because that wiki page only presents one persons view and one side
22:31.03ljpraboof: nokia will be doing almost the same with maemo and bringing qt to that platform as well
22:31.49raboofljp: I think I responded to your statements about that wikipage above, so you won't be surprised I think the wikipage seems mostly correct to me
22:32.04*** join/#openmoko prpplague (n=dave123_@ppp-70-244-166-139.dsl.rcsntx.swbell.net)
22:32.27mjrNow, I await the "good enough reasons" to back up ljp's "fuk off" side of the argument.
22:32.40raboofand does *not* say bringing qtopia to the openmoko hardware is a bad idea. it just says writing qt-based *applications* for the gtk-based openmoko framework is a bad idea.
22:32.48rtmmjr & ljp: You're discussing the "Why Not GT" page, right?
22:32.55mjrrtm, QT, yes
22:33.03rtmoops QT, not GT
22:33.16doc|workwhy not fluxbox?! why?! WHY?
22:33.25doc|workstabs randomly due to pointless discussions
22:33.27mjrrtm, he seems to think it's a biased rant because it doesn't say "YES, you should code in Qtopia no matter what the underlying platform uses"
22:33.59mjrI on the other hand think he's a moron because of this
22:34.42raboofjust tries to point out where ljp seems to misread the page, and gets ignored completely :)
22:34.43mjrthat, I think, summarizes the different points here pretty well
22:35.00mjrraboof, oh, I'm with you there
22:35.01ljpi am not ignoring you
22:35.06rtmGosh - that page seems pretty reasonable to me.
22:35.24alphaonepoints to http://en.wikipedia.org/wiki/Agree_to_disagree
22:35.29raboofljp: ok, i was being a bit dramatic :)
22:35.37mjrraboof, and yes, he's too blind to see it. I think that may be due to "Stock option blindness"
22:35.42ljpproblem is, neo is not exactly memory constrained nor an embedded device
22:36.04alphaoneljp: I wouldn't actually call it a problem :-)
22:36.19SpeedEvilI'd disagree about embedded.
22:36.20*** join/#openmoko polz_ (n=polz@cpe-213-157-235-31.dynamic.amis.net)
22:36.27ljpalphaone: no, but some people seem to mistake this anyway
22:36.44mjrljp, I see, you lost that discussion so you're trying to frame it into a new one.
22:36.51ljpso my computer 10 years ago is embedded?
22:36.59mjrClever trolling (!) tactic
22:37.08doc|workmine is, in the bottom of a landfill somewhere
22:37.16ljpi still have 20 MB hard disks around
22:37.29SpeedEvilljp: no - but because your washing machine - for example - now has more power than your first computer, that does not make it not embedded.
22:37.47rtmEven though the neo has memory comparable to a 10 year old PC, it has a lot more constraints, particularly with power usage.
22:37.53doc|workcan we install qt on a washing machine?
22:38.03ljpa washing machine is embedded because it has one purpose only
22:38.13ljpdoc|work: why not!
22:38.22raboofwho cares about the definitions of 'memory constrained' and 'embedded'? the definitions used usually seem to be either irrelevant or clear from context...
22:38.26doc|workljp: because it's pointless!
22:38.29doc|work;)
22:38.30*** join/#openmoko TimRiker (n=timr@rikers.org)
22:38.39mjrdoc|work, indeed you should do so and only code in qtopia for it, otherwise you're "biased" and any reasons you might give for your decisions are "rants"
22:38.45ljpno its not, it would provde and very easy to develop and functional ui
22:38.46doc|work;)
22:39.06doc|workljp: except.... it's a fucking washing machine. :)
22:39.08ljpqt runs on some volvo buses
22:39.29doc|workqt there are also airbags on buses, should we put airbags onto washing machines too :)
22:39.35doc|worker, ljp :)
22:39.37rtmOM runs on some buses when I commute to work.
22:39.39ljpprobably.
22:39.57SpeedEvildoc|work: remove the explosive capsule first, and use extra fabric software, and wash on a low-temp cycle.
22:40.14doc|workawww, no boom? :(
22:40.30ljpairbags deply when it senses a 2 year old toddler nearby
22:40.30*** join/#openmoko moko-bunny (n=reik@CPE-76-178-148-218.natnow.res.rr.com)
22:40.34ljpdeploy
22:41.23doc|workhaha, best homemade video ever. you see a child waddling across the kitchen floor, next thing *bang* kid is flying through the air heading for the wall towards the back of the room
22:41.34doc|work*smack*
22:42.53*** join/#openmoko tharvey (n=tharvey@adsl-76-205-222-173.dsl.snlo01.sbcglobal.net)
22:44.09ljpgetting back to that wiki page. I think its admirable that openmoko wants to use multiple toolkits
22:44.45tharveyanyone know what the state of the ar6k driver is in openmoko?
22:44.48ljpno where have I seen a statement about the visio for openmoko limiting itself to gtk. it wants to create an _open_ phone
22:45.03ljpopen means just that - open to new things
22:45.39ljpsome people cannot handle that qtopia runs better on the phone
22:45.46bricodewonders where the closes debug board is to him.
22:45.51SpeedEvilljp: in some ways - from my perspective - openmmoko is two seperate aims. A) Open hardware. B) An open software stack.
22:46.12mjrljp, who are these people?
22:46.31SpeedEvilljp: the primary aim of FIC in supporting the project is not to develop a cool OS. It's to develop software that's free to tehm, that they can use on phones to sell them direct to end-users.
22:46.42SpeedEvilbricode
22:46.47SpeedEvilbricode: lat/lon?
22:47.28bricodeSpeedEvil: Costa Rica?
22:47.36SpeedEvilHmm.
22:47.39SpeedEvilProlly not me then.
22:48.03bricodeToronto in a couple of weeks...
22:48.13mjrpersonally couldn't care less how well qtopia runs, so I handle it just fine. The main reason for not caring is, of course, the suboptimal "openness to new things" of the qtopia stack :]
22:49.19SpeedEvilis about 10000Km from bricode.
22:49.34bricodeSpeedEvil: Well, thanks for looking that up.
22:49.53SpeedEvilbricode: you've bricked yours?
22:49.55*** join/#openmoko liberfiasco (n=libervis@78-0-71-51.adsl.net.t-com.hr)
22:51.06*** part/#openmoko guillaum1 (n=Guillaum@AMontsouris-153-1-75-26.w90-2.abo.wanadoo.fr)
22:51.22*** join/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
22:51.24*** join/#openmoko paul0 (n=paulo@201-24-117-16.fnsce701.dsl.brasiltelecom.net.br)
22:52.26*** join/#openmoko jeffdameth (n=jeff@host-091-096-147-184.ewe-ip-backbone.de)
22:52.36ljpSpeedEvil: yes, but the software must also work. qtopia provides all that. they just need to abide by the GPL
22:54.03Mononokesilently points at http://zecke.blogspot.com/2008/04/slowly-getting-frustrated-with-qtopia.html
22:54.45bricodeSpeedEvil: Yep. It was a slow process where it was just a corrupt filesystem, but now I've borked everything such that even dfu-util doesn't work.
22:55.08*** join/#openmoko morricone (n=foobar@dslb-084-057-171-203.pools.arcor-ip.net)
22:55.39SpeedEvilbricode: does it not boot at all now?
22:56.02SpeedEvilbricode: And are you sure it's not battery flat issues?
22:56.41ljpMononoke: that is one persons subjective opinion. I know of 40 developers who disagree
22:56.58bricodeSpeedEvil: Nope. Just turns the backlight on (battery still works).
22:57.44SpeedEvilbricode: and you get nothing showing up on lsusb?
22:57.48SpeedEvil:/
22:57.57SpeedEvilbricode: sounds bricked then.
22:58.43bricodeSpeedEvil: dfu-util -s section -R -D file doesn't work anymore, but lsusb does show it being there.
22:59.14*** part/#openmoko caratorn (n=aratorn@tui75-3-88-168-237-15.fbx.proxad.net)
22:59.35SpeedEvilCan you get into the u-boot bootloader with ttyACM?
22:59.42ewonbest debian bug EVAR: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477454
22:59.54SpeedEvilUSB serial IOW
23:00.26bricodeSpeedEvil: Nope. Couldn't do that from the start. That's why I tried this whole u-boot upgrade process. The phone I have is a bit of a mutt.
23:00.58SpeedEvilbricode: was this a purchased phone - or an early version?
23:01.29bricodeSpeedEvil: How's this: gta01 software with gta02v3 bootloader on a gta02v4 pcb. It's an early version.
23:02.21SpeedEvilAh
23:02.32bricodeSpeedEvil: Yeah. Debugboard time.
23:02.59SpeedEvilI know there on the GTA02 a boot flash that can recover things. I don't know if it's been implemented.
23:04.50bricodeSpeedEvil: Considering that phone was obtained in January, it's got some crusty code on it.
23:04.56SpeedEvilYeah.
23:05.48ewonwho did you sleep with to get a GTA02?
23:06.07bricodeSpeedEvil: I can still dump stuff into RAM. Is there a way to pause the processor (like in JTAG) through the USB?
23:06.12bricodeewon: The right people.
23:06.26mjrI didn't know you could get a GTA02 by sleeping with someone? Who?
23:06.39*** join/#openmoko wolog (n=wolog@AOrleans-152-1-13-161.w90-21.abo.wanadoo.fr)
23:06.40bricodeewon: Sadly the right people didn't also include a debug board with the phone.
23:07.16SpeedEvilbricode: yes - as I understand it - if you can get to u-boot - you can get into the bootloader serial console over USB.
23:07.39SpeedEvilbricode: howevfer, this might not be the case I suppose in your hardware.
23:07.59SpeedEvilbricode: anyway - find yourself in scotland, and you can use my debug board.
23:08.29*** join/#openmoko retracile_ (n=eli@76-204-213-211.lightspeed.allntx.sbcglobal.net)
23:08.48bricodeSpeedEvil: Thanks for the offer.
23:09.01*** join/#openmoko liberfiasco (n=libervis@78-0-71-51.adsl.net.t-com.hr)
23:10.03*** join/#openmoko polz_ (n=polz@cpe-213-157-235-31.dynamic.amis.net)
23:10.43SpeedEvilbricode: to check - you know how to get to u-boot via tty-ACM - and it just doesn't work?
23:11.42*** join/#openmoko polz__ (n=polz@cpe-212-18-59-51.dynamic.amis.net)
23:11.51bricodeSpeedEvil: Tried both cu -l /dev/ttyACM0 (properly chown'd) and neocon. No dice.
23:12.10bricodeSpeedEvil: Even cat doesn't give me any love.
23:13.08SpeedEvildo you get the ACM device?
23:13.14SpeedEvilIt ust doesn't respond?
23:13.38quicksandWhat are the vid/pid you see for the device in lsusb?
23:13.58bricodeYep. ACM device, doesn't respond.
23:14.23bricodequicksand: oldskool 1457:5119
23:16.41quicksandHmm, that's what dfu-util would be looking for, so I'm out of ideas.  (On my GTA01 at least -- dunno if GTA02 is different)
23:24.51bricodeWell, thanks for ideas guys.
23:26.33*** join/#openmoko MichaelShiloh (n=chatzill@76.208.209.165)
23:27.04*** part/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
23:27.15*** join/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
23:28.34*** join/#openmoko christooss (n=matic@84-255-246-158.static.t-2.net)
23:30.08*** part/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
23:30.35*** join/#openmoko freebzh_jabber (n=freebzh_@80.248.214.43)
23:39.08*** join/#openmoko christooss (n=matic@84-255-246-158.static.t-2.net)
23:41.19*** join/#openmoko eikonos (n=eikonos@S0106001c104ae594.gv.shawcable.net)
23:42.45*** join/#openmoko duffyd (n=tim@202.74.204.60)
23:47.14duffydhi ScaredyCat, how do your images match up with Kevin Dean's? Are they dated the same?
23:47.20duffydprobably stupid question ;)
23:52.02*** join/#openmoko peter__b (n=biertrin@p54979CF9.dip0.t-ipconnect.de)

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