irclog2html for #openmoko on 20070202

00:05.29*** join/#openmoko rwhitby (n=rwhitby@nslu2-linux/rwhitby)
00:09.29*** join/#openmoko DukeOfURL (n=chatzill@vc7-1-39.dsl.netrack.net)
00:09.37*** join/#openmoko MetaBookfoziS (n=sajt@3e70c809.adsl.enternet.hu)
00:10.29*** part/#openmoko dougt (n=chatzill@gw-public.office.mozilla.org)
00:21.29*** join/#openmoko rwhitby-away (n=rwhitby@nslu2-linux/rwhitby)
00:29.53*** join/#openmoko duffyd (n=tim@60-234-239-189.bitstream.orcon.net.nz)
00:31.51duffydbtw, are there many taiwanese developers on this channel?
00:32.26duffydjust curious as we're going to Taiwan in May and was wondering if I'll have a better chance of buying an openmoko there
00:33.16DukeOfURLDoes anyone have experience with a GSM gateway?  http://www.2n.cz/products/gsm_gateways.html
00:50.27*** join/#openmoko voodoosmurf (n=voodoosm@209.168.162.146)
00:51.36duffydwell, I'm just guessing from the fact that FIC is a Taiwanese company that there must be quite a few Taiwanese developers here :-)
00:51.45duffydthat makes me feel happy
00:52.02voodoosmurfI didn't think anyone was in here
00:52.25duffydvoodoosmurf: :-)
00:52.32duffydcool name btw ;-)
00:52.36voodoosmurfthx :)
00:52.41newmedianWe're just the ghosts in the machine.
00:52.46voodoosmurfheh
00:52.51duffydyeah
00:53.04duffydwell it's about 10am in Taiwan
00:53.15duffydwell actually 9am
00:53.37voodoosmurfit's....  8 here on the east coast in the us
00:53.39voodoosmurfpm
00:53.56newmedianI think it tends to be busier "earlier" in the day. (It's 00:54 UTC)
00:54.16voodoosmurfyea, prob so...   there a lot of developers that hang around in here?
00:54.24duffydok
00:54.38duffydsorry that was a question ;-)
00:54.42voodoosmurfheh
00:55.05newmedianI've seen a few from the Planet here, but I've not been around long enough to identify everyone.
00:55.26voodoosmurfeither of you know when this phone is goin to go on sale?
00:55.38newmedian3/11/2007
00:55.45DukeOfURLcounter
00:55.45alorila week, 3 days 05:04:14 (10.21 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 3 days (38.21 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 3 days (222.21 days) for mass market (2007-09-11): see topic for more info
00:57.27duffydaloril: wow :-)
00:58.46duffydI'll be in Taiwan when they go on sale :-)
00:58.49duffydyay
01:00.25DukeOfURLMy chatzilla shows ~200 people on the channel.  How do I tell who is actually signed in?
01:01.06voodoosmurfhmmm...
01:01.21parag0nuse a proper irc client? most of them have userlists
01:01.43DukeOfURLchatzilla isn't "proper"?
01:01.49duffydwonder where Sean Moss-Pultz lives?
01:01.52duffydUS or Taiwan?
01:05.12DukeOfURLduffyd: how many hours from NZ to TW?
01:06.20duffydwell I've got a stopover in Sydney so from Sydney is 8 hours 15 mins
01:07.00DukeOfURLLA to Sydney is 14+ hours.  
01:07.20DukeOfURLBig ocean
01:08.05duffydyeah :-)
01:08.21*** join/#openmoko bkuhn (n=bkuhn@atheist.ebb.org)
01:08.31duffydDukeOfURL: what do you do for a living?
01:08.52DukeOfURLVoip telephone systems for small business
01:09.04DukeOfURLAsterisk
01:09.13DukeOfURLYou?
01:10.04duffydPlone developer
01:10.10duffydi.e. plone.org
01:10.37duffydDukeOfURL: interesting job, though - I can tell why you have come here ;-)
01:10.47duffydyour job is interesting that is ;-)
01:11.06duffydI do use Asterisk personally - great platform
01:11.08newmedianAsterisk integration with OpenMoko would be good.
01:12.11duffydnewmedian: yeah :-)
01:12.25voodoosmurfAsterisk?
01:12.33duffydasterisk.org (iirc)
01:12.40DukeOfURLI'm wondering about running Asterisk in the Neo...
01:12.42duffydvoip pabx
01:12.58duffydin the Neo?
01:12.59duffydwow
01:14.17DukeOfURLThat's why I asked if anyone had experience with a GSM gateway.
01:14.53DukeOfURLmobile to mobile calls on Cingular are free.  SIM in the Neo, SIM in the gateway, controlled by an Asterisk system.
01:14.57newmedianThe first version of the phone .. does not have Wifi, right?
01:15.04DukeOfURLDoes not
01:15.13newmedianUnfortunately.
01:15.39duffydshame
01:15.49newmedianEspecially since GPRS is $$$$ in Canada.
01:15.59DukeOfURLAm looking at establishing a modem (FSK) connection over the GSM connection...
01:16.24newmedianTDD?
01:16.29DukeOfURLYes
01:16.38newmedianInteresting.
01:26.41*** join/#openmoko parag0n (n=parag0n@popeshoe.gotadsl.co.uk)
01:38.59*** join/#openmoko mtm2 (i=mtm@nat/google/x-6230a3c0b5e0570f)
02:00.27*** join/#openmoko orospakr__ (n=orospakr@bas11-ottawa23-1128668517.dsl.bell.ca)
02:14.22*** join/#openmoko xerom (n=jack@81.193.130.125)
02:21.55*** join/#openmoko wiml (n=wiml@underhill.hhhh.org)
02:33.33*** join/#openmoko Marex (n=Marex@85.132.236.161)
03:31.14*** join/#openmoko romulus_ (n=romulus@S0106000625a403af.vc.shawcable.net)
03:41.07*** join/#openmoko romulus_ (n=romulus@S0106000625a403af.vc.shawcable.net)
03:47.48*** join/#openmoko ChanServ (ChanServ@services.)
03:47.49*** mode/#openmoko [+o ChanServ] by irc.freenode.net
03:50.37alorilcounter
03:50.38alorila week, 3 days 02:09:22 (10.09 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 3 days (38.09 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 3 days (222.09 days) for mass market (2007-09-11): see topic for more info
04:03.28*** join/#openmoko rwhitby (n=rwhitby@nslu2-linux/rwhitby)
04:13.01*** join/#openmoko rwhitby (n=rwhitby@nslu2-linux/rwhitby)
04:27.22*** join/#openmoko thedaniel (n=daniel@netblock-68-183-179-95.dslextreme.com)
04:32.16*** join/#openmoko bluelightning_ (n=blueligh@125-237-70-10.jetstream.xtra.co.nz)
04:33.40alorilcounter
04:33.40alorila week, 3 days 01:26:20 (10.060 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 3 days (38.060 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 3 days (222.060 days) for mass market (2007-09-11): see topic for more info
04:33.50LoRezdamn that's annoying.
04:34.17Agrajag-i reckon
04:34.41alorilLoRez: hehe, I changed it slightly again ;-)
04:44.57*** join/#openmoko bluelightning1 (n=blueligh@222-155-156-197.jetstream.xtra.co.nz)
04:51.24*** join/#openmoko cying (n=cying@adsl-75-18-222-151.dsl.pltn13.sbcglobal.net)
04:51.35cyingany openmoko team folks around?
04:58.52*** join/#openmoko eikonos (n=eikonos@S0106001310d36705.gv.shawcable.net)
05:04.40wiml*crickets*
05:17.55*** join/#openmoko gambler (n=orion@203-206-86-98.dyn.iinet.net.au)
05:21.47*** join/#openmoko dilinger (n=dilinger@c-65-96-191-108.hsd1.ma.comcast.net)
05:40.44*** join/#openmoko nh_work (n=nh@aurora.msi.umn.edu)
05:48.29*** join/#openmoko friedel (n=fwolff@dsl-242-233-175.telkomadsl.co.za)
05:59.26*** join/#openmoko bomanizer (n=janne@a88-112-208-94.elisa-laajakaista.fi)
06:17.32*** join/#openmoko eikowerk (n=eikonos@S0106001310d36705.gv.shawcable.net)
06:20.01*** join/#openmoko jouka (n=a@90-227-24-249-no68.tbcn.telia.com)
06:21.09*** part/#openmoko duffyd (n=tim@60-234-239-189.bitstream.orcon.net.nz)
06:27.20*** join/#openmoko MDK (n=mdk@cs181209253.pp.htv.fi)
06:29.26*** join/#openmoko koen|gprs (n=koen@212.41.157.237)
06:44.22koen|gprscounter
06:44.23alorila week, 2 days 23:15:37 (9.969 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.969 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.969 days) for mass market (2007-09-11): see topic for more info
07:00.58CMaloril: That google video of Bob Brodersens lecture was interesting, thanks :)
07:08.57*** join/#openmoko friedel (n=fwolff@dsl-242-233-175.telkomadsl.co.za)
07:15.07*** join/#openmoko rob_w (n=rob_w@p549B978C.dip0.t-ipconnect.de)
07:17.43*** join/#openmoko vgeorgescu (n=vgeorges@86.107.206.167)
07:26.15*** join/#openmoko buz (n=buz@80-218-148-33.dclient.hispeed.ch)
07:34.42*** join/#openmoko friede1 (n=fwolff@dsl-242-233-175.telkomadsl.co.za)
07:40.42*** join/#openmoko pjz (n=pj@zachs.place.org)
07:49.52*** join/#openmoko ans (n=anselm@pool-71-244-143-4.chi.dsl-w.verizon.net)
07:56.46*** join/#openmoko Eblis (n=Miranda@82.77.126.134)
07:57.57*** join/#openmoko keithp (n=keithp@home.keithp.com)
07:58.00*** join/#openmoko Cockroach- (n=saaskoli@gw.solution.yomi.com)
07:58.30*** join/#openmoko jouka (n=a@90-227-24-249-no68.tbcn.telia.com)
07:59.31*** join/#openmoko borg_ (n=olaf@80.149.17.21)
08:06.28*** join/#openmoko ssvb (n=ssvb@vbaltd.vba.com.by)
08:09.26*** join/#openmoko rob_w|mis (n=rob_w@p549B978C.dip0.t-ipconnect.de)
08:12.08*** join/#openmoko TRIsoft (n=mac@p57A2D155.dip.t-dialin.net)
08:13.05*** join/#openmoko jouka_ (n=a@81-235-183-167-no20.tbcn.telia.com)
08:14.25rob_w|misis that TRIsoft from Trisoft ?
08:14.35*** join/#openmoko TRIsoft_ (n=mac@p57A2CEB2.dip.t-dialin.net)
08:15.28rob_w|misis that TRIsoft_  from Trisoft ?
08:16.06TRIsoft_Yes, it is :-)
08:16.53rob_w|misnice .. how is the Lisa stuff .. is that still alive ?
08:17.36TRIsoft_*lookspuzzled* Lisa stuff ? We're the Zaurus guys...
08:23.58rob_w|misoh ... didn you guys some years back also sell Ipaq`s with the strange lisa linux ?
08:24.01rob_w|missorry then
08:24.14rob_w|misah right ,,i bought my old zaurus back then from you
08:29.55TRIsoft_ah, right. But the Ipaqs came from Lisa Systems in Hamburg.
08:35.45*** join/#openmoko nslu2-log_ (i=slug@nslu2-linux/dyoung)
08:42.07*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
08:50.10*** join/#openmoko zween (n=zween@212-139-182-173.dynamic.dsl.as9105.com)
08:57.23*** join/#openmoko thedaniel (n=daniel@adsl-75-16-79-90.dsl.irvnca.sbcglobal.net)
08:58.59*** join/#openmoko greentux (n=lemke@80.187.130.242)
09:06.38hrw"I'm cuirous too, if we're lucky Marcin or Stefan will have a bit of news that will help us out." - why people on openmoko-community think that I have more about openmoko then they? :D
09:06.43hrwmorning
09:07.00TRIsoftmorning
09:07.23TRIsoftMaybe because you're hanging around here all the time ?
09:09.01hrw25 hits from planet openmoko to my website and it will be top referrer instead of oesf forums
09:09.04hrw;D
09:16.17*** join/#openmoko slava (n=slava@CPE0080ad77a020-CM000e5cdfda14.cpe.net.cable.rogers.com)
09:18.29*** join/#openmoko cyberix (n=cyberix@hoas-fe17dd00-69.dhcp.inet.fi)
09:29.58slavahi all
09:34.58alorilhi slava
09:35.40slavai'm interested in porting my language to the openmoko phone when it becomes available
09:36.16dottedmagslava: language?
09:36.25slavahttp://factorcode.org/
09:38.07alorilslava: to quote koen: Follow the instructions on http://openembedded.org, MACHINE=ep93xx, DISTRO=generic should build compatible binaries.
09:38.31slavaits not as easy as that :)
09:38.31aloriluntil we have source code release, it has some additional stuff but is mostly based on openembedded
09:38.36slavai'm still working on the ARM compiler backend
09:38.40slavashould be done in a few adys
09:38.44*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
09:38.49slavamostly i'm interested in writing libraries for accessing the cellular and gps hardware
09:38.59alorilslava: yeah, I saw, but still.. I guess you eventually need above info
09:39.01hrwah that ep93xx machine ;d
09:39.27alorilah.. in that case you need to wait about 10 days
09:39.29slavawill your arm9 cpu have an fpu?
09:39.29alorilcounter
09:39.29alorila week, 2 days 20:20:30 (9.848 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.848 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.848 days) for mass market (2007-09-11): see topic for more info
09:39.59alorilslava: no: http://www.openmoko.com/press/index.html  -> http://www.samsung.com/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm
09:40.51slavaok thanks
09:42.14alorilqemu is emulator (don't recall  arguments or so, but they have been mentioned in mailing list (I guess searching for qemu at archives should work: http://lists.openmoko.org )
09:42.21aloril)
09:42.54slavai'm running qemu and i also have a gumstix
09:43.28slavai planned on doing an arm port for a while and started a few days ago, then i came across the openmoko
09:46.39slavawill it support GSM or GPRS only?
09:46.40*** join/#openmoko ValiSystM (n=ValiSyst@81.56.207.165)
09:48.30alorilGSM and GPRS only
09:48.41slavais GSM the same thing as GPRS (forgive my ignorance)?
09:49.25madwootano
09:49.25alorilGSM voice, data connections, fax, etc..: GSM is reserved connection
09:50.50alorilGPRS is packet protocol (usually IP)
09:50.54*** join/#openmoko ValiSystM (n=ValiSyst@81.56.207.165)
09:50.57slavaoh, ok
09:53.55*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
09:54.20*** join/#openmoko greentux (n=lemke@ip-217-18-181-130.static.reverse.dsi.net)
10:01.18*** join/#openmoko tr2x (n=alvar@80-218-185-55.dclient.hispeed.ch)
10:02.29Morgretslava:  Hi.  I've just been reading your site.  Interesting.  Like a sort of Lua combined with Smalltalk but with a default set of libraries ...
10:06.36Stephmwmornin'
10:24.01*** join/#openmoko lrg (n=liam@lumison.wolfsonmicro.com)
10:29.08*** join/#openmoko aloril2 (n=aloril@kaar72.airix.fi)
10:30.41*** join/#openmoko amarsh04 (n=amarsh04@138.217.208.105)
10:32.07*** join/#openmoko Rac0r (n=Rac0r@p5081D332.dip.t-dialin.net)
10:40.54Morgretslava: where's the source code to the various images?  I've got 'f' compiled, but I'm not going to run it on an unknown binary image.
10:41.15slavathe images are built from the source code in the distribution
10:41.22slavayou need a working factor build new images
10:41.59MorgretDoes "a working factor" mean a working 'f'?
10:42.13slavano, it means a f plus bootstrapped factor.image
10:43.14MorgretBut factor.image* are binaries.  I want the source code of one.  Can't start with a binary to generate a binary. :-)  That's what killed Smalltalk.
10:43.39slavathe factor.image and boot.image.* are generated from source. but the parser/compiler is written in factor
10:43.50slavanow do you build gcc without having gcc? :)
10:44.45MorgretUsing an earlier gcc, which is a standalone program.  
10:45.04slavawell, you need factor to build factor
10:45.36slavai think java killed smalltalk, not the nature of the implementation. and javac is written in java, you need sun's jdk installed to compile sun's jdk :)
10:45.40MorgretThe image isn't the equivalent of gcc though.  It's the equivalent of all the runtime libraries dumped together, plus the 'f' that you compile independently.
10:45.49slava'f' isn't part of the image file
10:46.05MorgretI know, I've compiled it.  What is 'f', conceptually?
10:46.21*** join/#openmoko cbx33 (i=c2df514b@gateway/web/cgi-irc/ircatwork.com/x-4902c99349be74b8)
10:46.22slavaits a loader, GC, and interpreter
10:46.35slavawhen you bootstrap, the compiler runs in the interpreter and compiles code in the boot.image to producce a factor.image
10:47.33MorgretOK, I understand that.  Unfortunately, it presents a security problem, because the contents of boot.image are unknown in advance.
10:47.58jouka_java is crappy
10:48.10MorgretIs there a standalone pretty printer at least, so that the contens of the boot.image can be examined?
10:48.15slavaMorgret: the contents of the sources are in a sense unknown too, unless you happen to learn the language and study everything
10:48.32slavathe image format is documented in vm/layout.h; get a hex dump tool and start digging :)
10:49.07slavaa pretty printer would be easy to write, though.
10:49.30MorgretWell, your dev approach has cycles.  Why not use a DAG approach and make the runtime image a composition of more primitive elements each of which can be produced independently?
10:49.46slavabecause that would entail writing large parts in C, such as the parser and core data structures
10:49.47ElrondWhat are you talking about?
10:49.49cbx33hi all
10:49.57cbx33heard about openmoko on lugradio
10:50.06cbx33sounded cool so I thought I'd pop in and say hi
10:50.08MorgretElrond: we're talking about slava's language "factor"
10:50.35slavaMorgret: when one factor image builds another factor image, nothing is 'carried over'. its built up completely from sources
10:50.39Elrondcbx33 - Hi.
10:50.41slavaits just that, eg, the parser is written in factor
10:50.56slavaso 'f' cannot parse sources by itself
10:51.21ElrondHmmm.
10:51.25Morgretslava: yeah, I'm fine with that.  The stumbling block is not being able to see what's inside the pill before you swallow it.
10:51.48cbx33the thought of having linux running on a phone so I can use a bash shell...is just awesome ;)
10:51.50slavawhen you download a piece of software, do you inspect every line of source code for potential vulnerabilities? ;)
10:52.02cbx33slava good point
10:52.15Morgretslava: I don't inspect every last piece of code ... BUT I COULD IF I WISHED.
10:52.56*** join/#openmoko pH5 (n=ph5@e178226191.adsl.alicedsl.de)
10:53.22Morgretslava: your security issue could be addressed simply by providing an image examiner, *not* written in Factor.
10:53.32ElrondRight. One of the ideas of (free) opensource. Reviewability.
10:54.01slavaif somebody wishes to write such a tool, they're free to do so. personally i'm more interested in improving the compiler, libraries, GUI, etc.
10:54.06ElrondHow does one bootstrap factor on a plain box?
10:54.18slavayou use a boot image from the web site
10:54.27Morgretslava: for most languages it's not an issue, because their base code is text.  Here yours is a binary format, so you have an issue.  You ought to find a solution.
10:54.28Elrondaka binary?
10:54.38slavathe image is not the 'base code'.
10:54.43slavathe base code is plain text source.
10:55.25MorgretI've compiled up f.  Now I want another piece of plain text source to start building up a small binary image, compositionally.  Apparently, I can't.
10:55.35slavaright, you can't.
10:55.59Morgretslava: so, Factor has a problem, for anyone who doesn't dismiss security as a valid concern.
10:56.03ElrondHuh. I'm missing something here.
10:56.21slavagcc has the same problem.
10:56.23slavaso does the linux kernel
10:56.26Morgretslava: which is a pity, because I think Factor sounds terrific.
10:57.04Elrondslava - gcc can be compiled using another c compiler.
10:57.16MorgretElrond: yep, good point
10:57.17slavaanybody can implement a new factor compiler
10:57.37Elrondgcc comes in source only. ;)
10:57.55slavathe boot image doesn't even have machine code.
10:58.08slavaits just a serialized object graph of the source code in core/, generated by core/tools/image.factor
10:58.28*** part/#openmoko friedel (n=fwolff@dsl-242-233-175.telkomadsl.co.za)
10:58.33ElrondSo there is some sort of assembler for factor?
10:58.50ElrondWhich converts "bytecode" to machine code?
10:59.00slavawhen you bootstrap, the compiler compiles all library definitions to machine code and saves a factor.image
10:59.04hrwslava: anyway - to get software to openmoko it has to be buildable in a way that if I start from clean dir then I fetch/unpack/patch/configure/compile all dependencies, toolchain and finally package.
10:59.05slavathe compilation step is optional
10:59.26slavaso how do you plan on building gcc?
10:59.58ElrondUsing a cross compiler. :)
11:00.09MorgretYeah, I understand how it hangs together.  Slava, it's cool.  Unfortunately, I can't run it, for the reasons I gave, which is a pity (for me) because I'd like to.  The unknown binary image needs to be composable from smaller visible elements first, or at the very least convertible into a viewable form.
11:00.33slavai'm not pushing for factor to be included with the openmoko distribution, anyway.
11:00.39slavai'm just interested in putting some time into porting it over.
11:00.48dottedmagslava: factor just need the trust path. How did you bootstrapped it from the beginnings?
11:00.59dottedmags/ed//
11:01.08slavait used to be implemented in java, and the java implementation would run entirely from source
11:01.12slavathis was back in 2004
11:01.18Elrondslava - Can you give me a short (three sentence) intro on factor?
11:01.27slavathe first image for the native implementation was generated by the java implementation
11:01.30Morgretfactor.sf.net
11:01.38Elrondahh.
11:02.08dottedmagslava: well, it will enormously helpful if you can restore this implementation which can build at least subset of factor enough to compile full image.
11:02.40slavathe java implementation is too out of date now. i haven't worked on it for 3 years
11:03.10MorgretI love the idea behind it.  It's just blocked by a security/trust problem.  You've done a good job building up a bootstrap path, but you need a deconstruct path too.  Security is a concern these days.
11:03.47slavasqueak smalltalk and various lisps such as sbcl follow a similar approach
11:04.17MorgretI know, that's why I chucked out Smalltalk here.  I loved the language.
11:04.20slavai understand security is a concern; are you worried that I could hypothetically be inserting backdoors into the boot image?
11:04.33slavaor that the boot images on the web site are comporomised?
11:04.48Morgretslava: not worried about you personally.  But one needs to be consistent.
11:06.37MorgretI especially love Factor's philosophy of "If you can't understand the stack, your code segment is too long".
11:06.47ElrondYep, web site compromises weren't too uncommon in the old days. ;)
11:08.23*** join/#openmoko mikesh (n=mikesh@x133.net.upc.cz)
11:09.37slavai guess you're ruling out anything other than gcc, and a handful of scripting languages
11:09.41slavafor your own use
11:10.06*** join/#openmoko morricone (i=foobar@dslb-084-057-156-217.pools.arcor-ip.net)
11:11.08MorgretJust an image walker would probably be enough to provide the trust, as long as the image structure is defined and can't contain hidden inserts.  I don't think recreating an alternative implementation is viable.
11:11.37ElrondRight.
11:12.29ElrondI still haven't really gotten the runtime model...
11:12.55slavaits something i'll keep in mind for the future. i don't have a lot of time or resources right now.
11:14.05*** join/#openmoko hipitihop (n=hipitiho@c211-30-214-40.belrs1.nsw.optusnet.com.au)
11:14.48*** part/#openmoko hipitihop (n=hipitiho@c211-30-214-40.belrs1.nsw.optusnet.com.au)
11:15.14slavaElrond: the part written in C is an executable named 'f'; when you run it, it loads an image into memory and relocates it to its final address. this becomes the heap
11:15.44slavathe heap holds data and code and is managed by a garbage collector and can be saved back to disk at any time
11:15.57slavayou can also generate a new image from scratch, instead of taking a snapshot of the current heap
11:16.15slavawhere 'from scratch' means running a program inside your image which loads all the sources and serializes them in the correct format
11:16.52ElrondAhhh.
11:17.06ElrondSo how do you port to a new CPU?
11:17.36slavathe C part has an interpreter, which is trivial to port.
11:17.46slavato get the interpreter running, i emit a boot image with the correct word size and endianness.
11:17.53slavathen i port the compiler
11:18.27Morgretslave: You're porting the compiler from its binary.
11:18.41ElrondSo the boot images aren't really CPU dependent, but only word size / endianness dependent?
11:18.45*** join/#openmoko aloril2 (n=aloril@kaar72.airix.fi)
11:18.58slavaElrond: right.
11:19.18slavathe files on the web site have cpu extensions because the relevant compiler backend is pre-loaded
11:19.25slavabut one can do ./f boot.image.x86 -no-compile on an ARM, for instance
11:20.00ElrondSo you really could put a boot.image.32bit-little-endian up?
11:20.07slavayes
11:20.24slavai could also create minimal boot images without any libraries other than the bare minimum to load other libraries.
11:20.26ElrondAnd the c runtime has an interpreter for that?
11:20.28slavathis is very easy and i've done it before, just for fun
11:20.44slavaElrond: yes
11:20.56ElrondAhh.
11:21.11ElrondIt reminds me a bit of the labview runtime model. ;)
11:21.33Morgretslava: given such a barebones image, how would it be extended?  I ask, because it it can then you have a means of growing your image compositionally, instead of used an opaque lump.
11:21.50slavayou can load new code into a factor instance at any time.
11:22.08slavai'm doing this as we speak, testing bits of the ARM compiler, changing the source, and reloading it, without shutting down and restarting the environment.
11:23.09ElrondSo there could be a minimal image, which only has the parser in it, and enough to parse/extend itself?
11:23.11Morgretslava: there's your solution then -- defactor everything into individual uncoupled images, write an image walker to display what' inside of each.  Then let images grow by composition of only those parts needed.
11:23.16Eblisdoes anyone have the possibility to test Mono on an arm cpu ?
11:23.33slavaElrond: yes
11:23.40slavai've built such an image, its around 500kb
11:24.06ElrondThat, and a image-pretty-printer would make Morgret happy. :)
11:25.25ElrondOne could then compare the pretty printed with the shipped sources and say "Okay, there are no easter eggs in the image. I'm happy."
11:25.41MorgretHehe.  Well I love the idea behind the language.  Just got a security concern here, and it's a concern that everybody else *should* have too, although of course that's for them to decide.
11:26.07slavaElrond: dumping the image won't give a byte for byte reproduction of the source
11:26.22slavait is possible to reconstruct source from the image -- you can use the 'see' function inside factor to do that
11:26.29Elrondslava - Yes. But a structural. The rest is Morgret's problem. ;)
11:26.31slavahowever you don't get the same whitespace, etc
11:26.41slavaand comments are lost
11:27.00ElrondYeah, yeah.
11:27.23ElrondHow hard would it be to write see as a standalone program in *any* other language?
11:27.34Elronds/see/"see"/
11:27.43slava'see' isn't an image dumper, its a function which takes a function as as parameter and shows its source
11:27.48slavabut to answer your question, not very hard
11:28.13Morgretslava: how come that comments would be lost?  The image contains the full source as I understand it, but fully tokenized.  This must contain the comments too, surely.
11:28.24slavano it doesn't contain the full source.
11:28.32ElrondWell, that tool could be extended to recursively walk all functions, that are referenced from the main entry function.
11:28.35Morgretslava: so where is the source?
11:28.40slavathe source is in text files
11:29.14ElrondMorgret - The images on the web site are pre-compiled. ;)
11:29.16MorgretSo ... we *do* have source for the image?
11:29.21ElrondYes.
11:29.26slavayes, but you need to run an image to produce a new image.
11:29.29ElrondBut you can't compile them on a bare system.
11:29.50ElrondUnless you write a compiler in some other language.
11:30.11ElrondSo you have two options:
11:30.22Elrond- Either write a pretty printer and compare with shipped sources.
11:30.31Elrond- Or write another compiler.
11:31.51*** join/#openmoko chrustinho (n=christop@p57B000D8.dip0.t-ipconnect.de)
11:33.46MorgretIt needs addressing, slava.  You see, if this ever became popular, and virus/malware/spyware/crapware/crime writers ever discovered it ... it would be absolutely end of story.  No means of verifying what one has running locally.
11:34.52ElrondMorgret - Well, except for the boot-strapping issue, you can verify all sources.
11:34.55slavahave any crapware writers discovered squeak and managed to inject malicious code into the base system?
11:35.15Morgretslava: you know that's a logical fallacy :-)
11:35.21ElrondMorgret - So slava has a little point in pointing us at gcc:  How did you install the box you're sitting front of? ;o)
11:36.17slavaMorgret: yeah, but its 6:30am and i got sucked into a long, drawn out discussion on irc. and my development is proceeding slowly because qemu isn't a speed demon. :)
11:36.20slavatakes a long time to run tests
11:36.58Elrond;)
11:37.07Elrondcounter
11:37.07alorila week, 2 days 18:22:52 (9.766 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.766 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.766 days) for mass market (2007-09-11): see topic for more info
11:40.09slavai need to reflash my gumstix. qemu is far too slow
11:40.17*** join/#openmoko buz (n=buz@80-218-148-33.dclient.hispeed.ch)
11:43.45*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
11:47.56*** part/#openmoko steveb (i=steve@about/uk/perfect)
11:58.58*** join/#openmoko zween (n=zween@212-139-182-173.dynamic.dsl.as9105.com)
12:17.09*** join/#openmoko zipola (n=zipola@zip.kortex.jyu.fi)
12:25.56*** join/#openmoko Ryushin (i=proxy@windwalker.openinnovations.com)
12:33.05*** join/#openmoko tr2x (n=alvar@80-218-185-55.dclient.hispeed.ch)
12:42.38*** join/#openmoko l4rs (n=laprican@hsiproxy.astra-net.com)
12:48.11*** join/#openmoko PierreTramo (n=gcarrier@88.191.20.33)
12:50.09*** join/#openmoko daxxar (i=daxxar@daxxar.com)
13:18.36*** join/#openmoko nnpiggy (n=nnpiggy@24.crcr10.xdsl.nauticom.net)
13:24.51*** join/#openmoko jeddy3 (n=mattiast@gw.sbg.se)
13:28.43*** join/#openmoko zween (n=zween@212-139-182-173.dynamic.dsl.as9105.com)
13:35.05*** join/#openmoko nnpiggy (n=nnpiggy@24.crcr10.xdsl.nauticom.net)
13:35.10buzcan one use udp to send packets to GRPS phones?
13:35.31*** join/#openmoko [g2] (n=g2@nslu2-linux/g2)
13:35.39buzor is that prevented by nat?
13:37.46*** join/#openmoko eikonos (n=eikonos@S0106001310d36705.gv.shawcable.net)
13:38.37Stephmwbuz: it's operator-specific
13:38.58Stephmwbuz: Orange-France, for instance, allowed such stuff in 2005... whether that's still the case though...
13:39.07buzim wondering how much traffic jabber on grps would ause
13:39.15buzto be just online 16h a day
13:39.29buzmessages would obviously be on top of that
13:40.56buzi guess it would depend on the timeout of a tcp connection first and foremost
13:42.45*** join/#openmoko libervisco (n=libervis@tuxhacker/libervis)
13:43.52buzhttp://www.freesoft.org/CIE/RFC/1122/114.htm
13:44.03buzmhh does that mean a sane NAT server would hold open TCP for at least 2 hours?
13:44.58buzmaybe i should go dig for my good old tcp ip illustrated
13:45.35*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
13:54.34Elrondbuz - Straight TCP should have NO timeout.
13:55.18MorgretTCP sessions don't break *EVER* on principle, but a timeout can be specified in socket options.  Unfortunately quite a while back networking libraries and/or TCP stacks started making non-inifinite timeout the default socket option for TCP, as a result of which TCP is nowadays flakey by design, for the simple pragmatic reason of self-cleanup of old sessions.
13:55.20ElrondOf course, many people enable keep-alive, or something alike in the application layer.
13:55.36SpeedEvilIsn't the max timeout 10 hours?
13:55.45MorgretOnly in the socket options
13:56.03SpeedEvilAh - I'm probably thinking of max RTT
13:56.16MorgretTCP used to be 100% reliable ... no breakage ever, regardless of how long you were at max retransmission interval.
13:56.41SpeedEvilI mean, it fails in terms of bandwidth use if the link you are on exceeds 10 hours RTT
13:56.45MorgretBut that was back in the old days, before the socket options thing.
13:57.13SpeedEvilBecause it can't back off far enough adn will always retransmit packets.
13:57.24MorgretYeah, but only as a socket option.
13:58.17SpeedEvilI mean the RTT counter only goes up to 10 hours - it's impossible in tcp/ip to have a longer one.
13:58.22MorgretCleanup of effectively dead streams used to be considered an application problem.  In practice it no longer is, because long-dead streams will self-break.  It's bad on principle, but good in practice.
13:58.44SpeedEvilThis is only generally a problem for ip-via-mail, or space apps though.
14:00.30Stephmwbuz: FWIW, current phone IM clients for multi-protocols tend to use a proxy host
14:00.35MorgretIt's also a problem for covert communications, using very low bandwidth covert channels.
14:00.42Stephmwbuz: specifically to reduce traffic
14:01.26SpeedEvilIt'd be nice if there was some way to authenticate packets. A router for a host will only accept packets with a given signature, which is revokable, and many signatures per host are possible. (say  256)
14:01.39MorgretSo I'm guessing the spooks don't use TCP anyone.  It's actually a good concept to have a fully reliable, non-breaking stream capability, decoupled from data rate.
14:01.47SpeedEvilYeah.
14:02.05SpeedEvilOr just tweak the rtt algorithm on stuff you're using to alter the RTT algorithm.
14:02.28SpeedEvilI did that once - to limit backoff to 1 second, when I was having trouble with packet loss.
14:03.41MorgretWell you can always set your comms app socket options to 0, and TCP will remain retrying forever.  But you can't use default comms apps for it anymore, as they'll use default socket settings.
14:04.51MorgretAfter all, TCP only really exists at the two endpoints.  For everyone else in between, they're just IP datagrams, nothing to break :P
14:05.23ElrondUnless the boxes in between are "smart" ;o)
14:05.48MorgretYeah, they could send a reset back.
14:06.42MorgretIt's one of the problems with stateful inspection in firewalls ... effectively they encode networking *policy*.  It's not particularly good, just pragmatic.
14:07.12*** join/#openmoko terrex (n=terrex@84-122-63-17.onocable.ono.com)
14:07.15ElrondRight.
14:08.32nnpiggySpeedEvil, your revokable packet signature exists as part of IPSec.
14:09.49SpeedEvil:)
14:10.22nnpiggy:-)
14:10.26Elrondnnpiggy - Do you have any experience with ipsec? Is it still a nighmare to setup?
14:10.33MorgretInterestingly, socket timeouts will raise there head again as soon as the Internet starts getting connected to the planets ;-)
14:10.50Morgrettheir*
14:10.57ElrondMorgret - *biggrin
14:10.58Elrond*
14:11.08Elrondssh will be fun. ;o)
14:11.29nnpiggyhttp://www.ipnsig.org/
14:11.31SpeedEvilYeah - the moon isn't so bad.
14:11.43nnpiggyYes, IPSec is still a pain to set up.
14:12.45nnpiggyAnd ipnsig is not a joke or purely speculative activity...
14:12.47MorgretNeo2050 ... GSM-9.5G using asteroid-belt GPS.
14:13.19ElrondMorgret - *lol* ;)
14:13.27ElrondNeo2010 ;o)
14:13.51MorgretWell you never know, this might be the start of something big ;-)
14:14.44*** join/#openmoko quinton (n=quinton@84-45-151-51.no-dns-yet.enta.net)
14:16.18sannescounter
14:16.18alorila week, 2 days 15:43:41 (9.655 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.655 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.655 days) for mass market (2007-09-11): see topic for more info
14:16.51Elrondless then 10 days and we'll have agpsd in our hands. ;)
14:18.05leventhali'll have to wait a little longer.. i was a bad dev and blew all my money for the month already
14:19.04leventhalhm.. or i could just download the framework and see if the gps data can be simulated.
14:19.26SpeedEvilYou can surely just strap a standard GPS in, or use a simulator.
14:19.32SpeedEvilBTDT.
14:19.38Elrondleventhal - For real hw, people have to wait 10 days + shipping anyways. ;)
14:19.41leventhalsimulator it is
14:19.59SpeedEvil+ shipping + dancing up and down time.
14:20.17*** join/#openmoko Matt_PI_ (n=chatzill@209.198.66.141)
14:20.18buzand looking at the software
14:20.24Elrondobjdump --disassemble-all. ;o)
14:20.31buzi just hope there will a non orange theme
14:20.39SpeedEvilyou get the software when it's shipped.
14:20.44SpeedEvilSo before you get it - prolly
14:21.21Elrondbuz - *duck* Create the theme yourself. ;o)
14:23.21*** join/#openmoko MiniMoose (i=dave@c-24-16-216-41.hsd1.wa.comcast.net)
14:29.02MorgretThe standard theme won't matter until September.  It's only then that it needs to sell on the basis of looks.
14:29.35MorgretI bet there will be 100 themes before then ;-)
14:29.48aloril2slava: you need to get factor included in Fedora, Debian, etc.: then its in same situation as gcc ;-) (no need for images, just use system suplied factor compiler)
14:30.33*** join/#openmoko prpplague (n=dave@65.71.224.163)
14:30.54Elrondaloril2 - hehe ;)
14:31.01Morgretaloril2: yep, trust by association is also valid trust.  However, that doesn't make the problem of hacks go away.  If your image is compromised, you need some way of cleaning it without running it.
14:31.06ElrondMorgret - Only 100? ;)
14:31.36MorgretElrond: hehe, OK, as many these as there are people ;-)
14:31.46Morgrets/these/themes/
14:33.16*** join/#openmoko Tantalum (n=Nabil@h-68-167-55-145.mclnva23.covad.net)
14:33.36*** join/#openmoko Any_Key (n=Any_Key@sedova.highlink.ru)
14:34.22TantalumHi I was just on the openmoko website but it doesnt have alot of usefull info... what exactly is openmoko?
14:35.11MorgretIt's the same thing as having a compromised root volume.  The first thing you do is turn off the power switch, no waiting, no clean shutdown, just BANG, off.  Then you bring up another box and mount the old root elsewhere, and start poking.
14:35.57zipolaTantalum: Did you check http://openmoko.com/press/index.html ?
14:36.36*** join/#openmoko dneary (n=dneary@251.9.39-62.rev.gaoland.net)
14:37.39Tantalumcool I'v heard about that, I remember the pictures.
14:38.48buzif your / is compromised and you're not into investigating it, you simply nuke it booting froma livecd
14:39.03TantalumI tried google but there doesnt seem to be much in the way of documentation other then the spec sheet ;-(
14:39.39*** join/#openmoko AggroNinja_ (i=chatzill@nat/redhat/x-1faefc0710f4e800)
14:40.20zipolaTantalum: Look at http://lists.openmoko.org/pipermail/announce/2007-January/000000.html
14:41.44TantalumI need a login for the openmoko wiki?!
14:42.06CMcounter
14:42.07alorila week, 2 days 15:17:53 (9.637 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.637 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.637 days) for mass market (2007-09-11): see topic for more info
14:42.14SpeedEvilThere is currently very little info out there.
14:42.27SpeedEvilOther than the spec sheet, and that derived from it.
14:42.28CMTantalum: The wiki and more will open in about a week :)
14:42.33SpeedEvilThe official wiki is not open
14:42.36SpeedEvilyet
14:42.54buzi wished release would be delayed until 19th
14:43.00buzthats when my last exam takes place
14:43.03buzgrmbl
14:43.05CMHehe
14:43.20*** join/#openmoko bmidgley_ (n=bmidgley@c-67-166-71-203.hsd1.ut.comcast.net)
14:43.32*** join/#openmoko srikantux (n=sri@59.92.133.150)
14:43.35Tantalumok... does openmoko work in the us?
14:43.58buzshould
14:44.03buzwith GSM provider anyway
14:45.00Tantalumdamn... Getting GSM here is a pain
14:45.09*** join/#openmoko Jo2 (n=Joe@217-170-144.541110.adsl.tele2.no)
14:45.12bmidgley_tmobile, cingular
14:45.21bmidgley_what's a pain is pay-as-you-go
14:45.33bmidgley_no prepaid data afaict
14:46.07*** join/#openmoko prpplague^2 (n=dave@mailhost.amltd.com)
14:46.09*** join/#openmoko silwol (n=silwol@193.170.134.179)
14:46.41Tantalumyeah but where I live me and every one else uses verizon..... I never use my out of network minuets ;-)
14:46.51SpeedEvilIn the UK - it's not too bad - contract phones - many of - come with a meg of data a month, and 3 pounds ($6) / Mb
14:47.19SpeedEvil3G is a whole nother ballpark of course.
14:47.35bmidgley_yeah I am sticking w verizon but getting prepay for devel
14:47.39SpeedEvilBut AIUI, all the providers require you to have a 3G capable phone.
14:48.03leventhalSE: Yeah, I'm jealous.. GPRS rates in Canada are a ripoff
14:48.39aloril2Tantalum: OpenMoko is OE based Linux distribution for mobile phones that initially runs on Neo1973 phone
14:48.48*** join/#openmoko MetaBookfoziS (n=sajt@3e70c809.adsl.enternet.hu)
14:49.00SpeedEvilFor 3G - IIRC you cang et a gigabyte a month for 40 quid.
14:49.12leventhalFido dropped the unlimited GPRS because $50 was too cheap
14:49.14Sketchthough i'm theoretically not supposed to tether to another device with that ;)
14:49.19leventhalNow it's $50 for 50mb and 0.03/kb after that
14:49.31leventhalRogers has their $100 for 100mb
14:50.01XorAouch, 7.50 UKP for 2Gig here
14:50.04bmidgley_in my area coverage is good enough that I could switch from cdma to gsm
14:50.09aloril2OpenMoko will be released in 10 days, you can order Neo1979 in 40 days
14:50.14bmidgley_but I am used to 3g :(
14:50.19leventhalI'm clinging to my hiptop solely for the data plan
14:50.26leventhalIt's very closed and limited though
14:50.28Sketchi think tmobile is the cheapest for data in the US (dunno if they support 3G though)
14:50.48*** join/#openmoko ans (n=anselm@pool-71-244-143-199.chi.dsl-w.verizon.net)
14:51.27TantalumI dont think they do
14:52.05leventhalOh wtf.. fido dropped all of their data plans except the 2mb for $5 plan
14:53.00leventhalWhich is idential to the rogers plan
14:53.16TantalumThanks every one for the info..... I'll probably be back when the phone is released and if I get one
14:53.57*** join/#openmoko MeTa (n=sajt@3e70c809.adsl.enternet.hu)
14:54.48bmidgley_tmobile has edge at least
14:56.04Clintt-mobile and cingular both have edge
14:56.09Clintin many areas
14:56.44buzneo doesnt have edge
14:57.16Clint2.5-not-edge
14:57.57*** join/#openmoko vetetix (n=vetetix@247.25-218-195.adsl.internet.lu)
14:59.07Sketchcingular also has 3G
14:59.26Sketch(in some areas, of course)
15:02.27*** join/#openmoko bkuhn (n=bkuhn@fsf/member/bkuhn/bkuhn)
15:09.17*** join/#openmoko Matt_PI_ (n=chatzill@209.198.66.141)
15:11.14*** join/#openmoko xerom (n=jack@bl4-131-14.dsl.telepac.pt)
15:27.31aloril2SpeedEvil: why would you need external GPS? Just route chip communication both to binary agpsd and your own agpsd and compre outputs
15:28.16Elrondaloril2 - All of that gets down to reverse engeneering. ;)
15:30.48aloril2Elrond: yup, but no need for external GPS for it
15:32.37MorgretMight not need to reverse engineer.  We'll just have to wait and see whether Sean can open enough of it up.  I think he *wants* to, from reading some of his visionary statements about openness.  Perhaps he can reach agreement with Infineon/GL to release just the basics of the positional data formats.
15:37.28*** join/#openmoko max_azzolini (n=chatzill@89.97.249.67)
15:38.48buzsomehow i doubt it
15:38.58buzfrom what i understand, most of the work is done in software with GL chips
15:39.11buzand i dont think they will want to give their crown jewels away
15:40.16SpeedEvilaloril: I was assuming that the context was for devs without physical devices.
15:40.34*** join/#openmoko quinton (n=quinton@84-45-151-51.no-dns-yet.enta.net)
15:41.28SpeedEvilThe crown jewels however isn't involved in the output of the hardware.
15:41.44SpeedEvilThat's probably pretty simple and relatively irrelevant.
15:41.46*** join/#openmoko max_azzolini_ (n=chatzill@89.97.249.67)
15:42.08MorgretSpeedEvil: agree
15:43.30SpeedEvilIt's the converting, filtering, ...
15:44.18*** part/#openmoko lamby_ (n=lamby@compsoc.sunion.warwick.ac.uk)
15:44.29MorgretI bet that's true for the interfaces to nVidia's and ATI's graphics cards too, and that opening those interfaces would have no commercial impact whatsoever.  They just want the control.  In this GPS case it's even more-so.
15:46.01SpeedEvilI think the thinking is that in the graphics case, the worry is that someone will take the detailed hardware specs and clone.
15:46.01SpeedEvilProbably also there are horrible IP risks.
15:49.50XorAhaving worked in a gfx chip manufacturer the number 1 reason for no open specs is they expose bugs in the chips, your competitor then does "demos" that expose those bugs
15:49.51hadaraanyone who has capability of actually cloning the hardware will probably have no problem doing so without the hardware interface specs
15:50.10XorAbut work perfectly on their chips
15:50.38XorAPHB's who are involved in buying depts dont know technicall details, they can just tell perfectly rendered boobs from ones with flaws
15:56.51aloril2SpeedEvil: agree about crown jewel, but if you know chip protocol  then you can feed it to existing GPL implementation
15:57.11SpeedEvilYeah - then tweak that.
15:57.42SpeedEvilNope.
15:58.03*** join/#openmoko quinton (n=quinton@84-45-151-51.no-dns-yet.enta.net)
16:04.45MorgretWell if the competition can find your bugs for you, that's a bonus :-)
16:05.48hrwhi
16:06.00SpeedEvilNot if they are hardware, and would cost you tens of millions to fix.
16:06.18SpeedEvilAnd they can be exposed by competitors in shipped product.
16:06.35MorgretNah, it all goes through your driver ... easy to fix.
16:06.55aloril2SpeedEvil: bundled agpsd can have those ITAR limitations regardless whether proprietary binary is used or one compiled from GPL sources. Neither ase changes availability of GPL sources ;-)
16:07.06MorgretAnd so it should be.  Covering up bugs is a mark of incompetence, not engineering.
16:07.30nbdITAR limitations?
16:07.37SpeedEvilBasically:
16:07.51SpeedEvilGPS that can report speeds over 1000 knots and 60000 feet are a munition.
16:07.57SpeedEvilAs defined in the ITAR regulations.
16:08.09MorgretSpeedEvil: can the Hammerhead?
16:08.12SpeedEvilYou need a special licences to import or export them.
16:08.19nbdah
16:08.24SpeedEvilThe hammerhead basically can - however, it's half of the story.
16:08.34SpeedEvilThe hammerhead outputs uncooked data.
16:08.43SpeedEvilThe gpsd cooks it and produces a position.
16:09.12SpeedEvilIt's pretty clear that if you sell the device with an unlimited gpsd that it is in fact subject to the ITAR regs - which means basically it can't be sold.
16:09.47MorgretWell if the Hammerhead is a munition and is being distributed to hundreds of thousands of consumers worldwide, then Infineon/GL are idiots.
16:09.48SpeedEvilIt's as I understand it not been tested in law if an easy to alter source gpsd that has the limits imposed is allowed.
16:09.53SpeedEvilNo.
16:10.19SpeedEvilIt's only a munition when it's combined into hardware + software that reports positions over the limits.
16:10.45SpeedEvilAnd it's the manufacturer of the units problems, not infinieons.
16:11.03MorgretWell in that case the Hammerhead isn't a munion when it's standalone.  Simply logic.  So, let's have the documentation. ;-)
16:11.45SpeedEvilNo, it's not. However, it's possible a court could rule - pushed by apple - that an open source gpsd makes the neo a munition.
16:11.45Morgrets/munion/munition/
16:12.31MorgretSpeedEvil: I think you aren't using enough layers of speculation.  How about another 10?  That would do it .... ;-)
16:12.52SpeedEvilThe ITAR regs are pretty clear. They are still enforced.
16:12.53MorgretIf ... if ... if ... if ...
16:13.16SpeedEvilIt is totally clear that if you sell the neo with an unlimited GPS that it is a munition. Yes, this is insane.
16:13.35MorgretAnd by the ITAR, you just said the Hammerhead alone isn't a munition.  So they don't apply.  Everything else is speculation about the future.
16:13.37nbdSpeedEvil: well, the chipmaker will also have an interest in not having all of their sold gps chips become munition
16:13.53SpeedEvilThe hammerhead is part of a hardware+software package that makes up the GPS.
16:14.13*** join/#openmoko goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
16:14.17SpeedEvilIt is not a munition unless both parts of that package report positions/speeds outside the limits.
16:14.35SpeedEvilThe hammerhead can - but when tied to software that imposes the limits, it's fine.
16:15.01SpeedEvilThe hammerhead doesn't output a position, it outputs relative speeds of satellites in view.
16:15.18SpeedEvilThe position is generated by the gpsd
16:16.02Sketchsounds like you would be fine if you distribute it with a gpsd that obeys teh limits?  if someone replaces the software to get around the limits, that's their own problem? ;)
16:16.13SpeedEvilProbably.
16:16.27Sketchif it's already being distributed by other vendors with different software, that software could surely be replaced by someone who knows enough...
16:16.57SpeedEvilYes - however essentially all GPSs with flashable firmware are in that boat too.
16:17.16nbdwell, just because something is binary-only doesn't mean it's secret, so that problem exists already
16:17.25nbdit's already replacable
16:17.30MorgretSpeedEvil: I don't know why you're trying to put a damper on GPS in OpenMoko, but it's not helping.  If you think there is an ITAR issue, please take it up with Sean, and let's see if he says "You are forbidden from using the Hammerhead directly."  Without that, it's just negative speculation.
16:17.34nbdfor anyone smart enough to reverse engineer the gpsd
16:17.35SpeedEvilI think it's pretty safe to say you won't get a court to rule that a closed binary+hardware violates ITAR
16:18.34SpeedEvilI am not. I just don't want any trivial way of taking the thing off the shelves, when it goes volume.
16:19.29nbdthis looks like the same old free wifi drivers vs fcc regs discussion
16:19.31MorgretSpeedEvil: Yes you are.  You are saying that we cannot freely program those things FIC presents us in the hardware, and you use some FUD about possible ITAR problems to stop us.  It's very bad.
16:20.39SketchSpeedEvil: yeah, but there are many "closed+binary system" devices which have later had linux installed on them
16:20.56*** join/#openmoko high-rez (i=gus@carrera.bourg.net) [NETSPLIT VICTIM]
16:21.40*** join/#openmoko notsmack (n=notsmack@70-101-76-11.dsl1-field.roc.ny.frontiernet.net)
16:22.14SpeedEvilI want neo to succeed - I want one - well - maybe of v2, I may not have cash for v1. I'm waiting on responses from some people who have worked in this area. Hopefully they may have more insight.
16:22.21Sketchso when someone figures out how to install linux on some random GPS (like the cheap ARM based one I got that runs WinCE, i bet would not be too difficult) that has been on the market a few years, does that make the manuf suddenly liable?
16:22.51SpeedEvilI don't know - it depends on what you can get a court to decide.
16:23.21SpeedEvilI would say almost certainly not, as it's closed, and the person doing it is not doing it with the makers approval.
16:23.28MorgretSpeedEvil:  Good, that sounds progressive.  FUD about possible ITAR problems in the future is in contrast not progressive, it's as negative as all FUD.
16:24.16buzthat sounds about as much as fud as the playstation could be used in missiles stupidity
16:24.37buzpeople who build missiles can get proper gps for it, rest assured
16:24.43SpeedEvilGo and look at the ITAR regs - they do in fact apply.
16:24.48SpeedEvilEven if the GPS is civilian.
16:25.00SpeedEvilIf it can produce positions outside the limits.
16:25.23SpeedEvilAnyway - I'll stop talking of this aspect till I get more info.
16:25.33buzthen put that limits in an open source gpsd as well and it's legal
16:26.21SpeedEvilIMO, that'd be a matter for the courts, as it's essentially a documented 'delimit' switch.
16:26.53SpeedEvilAnyway - on another topic - has it been cleared up if the 'hole' in some of the pictures is a lanyard attach, or a button?
16:27.02buzits a hole
16:27.23SpeedEvil:)
16:27.32aloril2SpeedEvil: I fail to see difference between bundled binary A and binary B both obeying limits
16:27.51SpeedEvilBundled binary B comes with a documented off-switch.
16:27.56SpeedEvil(the source)
16:28.14SpeedEvilI wish LCDs were not so damn fragile.
16:28.39SpeedEvilWorn round the neck, with no cover, I'll break it. :(
16:32.31hadarait's rather unlikely that this kind of logic will hold in court, most of us here can probably reverse engineer the communication protocol in the matter of days without any source whatsoever so the "off switch" in the binary blob case is only marginally harder to find
16:32.31*** join/#openmoko Virtuall (n=virtuall@who.is.virtuall.info)
16:34.58aloril2SpeedEvil: *both* come with off switch: download from net binary C without limits
16:36.13*** join/#openmoko nelt (n=radford@cpe-67-49-92-118.socal.res.rr.com)
16:38.31buzcourts and logic arent exactly close friends though
16:42.55ansI hope I don't get chewed out for this question... I'm not as tech savy as many of you are, but I was wondering I develop in flash and would there be a way to get flashlite on openmoko?
16:43.42*** join/#openmoko l3010o (n=leo@n219079066049.netvigator.com)
16:44.18MorgretI'm not worried about courts here, but about the project being FUD'd out of sight.  FIC is a large company, they have lots of lawyers.  Let them deal with possible ITAR issues please.  We're given an open piece of hardware at the interfaces, and our job here is to improve it with open source work in all areas.
16:46.45Morgretans: anything that you can get to work with OpenEmbedded should work on the Neo.
16:50.55*** join/#openmoko daxxar (i=daxxar@daxxar.com)
17:02.18*** join/#openmoko thedaniel (n=daniel@38.98.1.19)
17:04.03Matt_PI_and why worry about flash  when you can use Moble SVG
17:04.38*** join/#openmoko christoph_ (n=christop@p57B0287E.dip0.t-ipconnect.de)
17:04.57Matt_PI_Mobile SVG
17:05.16Matt_PI_SVG is a open standard
17:06.57Matt_PI_http://mobilemonday-ny.com/
17:09.44*** join/#openmoko rob_w (n=bob@p85.212.132.68.tisdip.tiscali.de)
17:09.54neltso is swf
17:10.23neltbut so far the open source implementations are lagging...
17:13.09*** join/#openmoko tr2x (n=alvar@80-218-185-55.dclient.hispeed.ch)
17:18.16Matt_PI_the SVG guys are moving big time into mobile
17:19.20Matt_PI_and they are working on Joost ....and if you've seen Joost you know it wants to be a Mobile app
17:20.04*** join/#openmoko silwol (n=silwol@193.170.134.179)
17:24.55hadarahmm since when is swf open ? last time I checked it was something like "you can get the specs if you agree not to use them to write flash player."
17:27.48*** join/#openmoko goxboxlive (n=goxboxli@9.80-202-160.nextgentel.com)
17:34.08*** join/#openmoko eikonos (n=eikonos@frrrc01.vic.sfl.net)
17:35.54neltAFAIK that is not the case.  I doubt there would be a GNU flash project if that were the case.
17:36.08*** join/#openmoko MeTa[AwAy] (n=sajt@3e70d936.adsl.enternet.hu)
17:36.26nbdthe gnu project is based on reverse engineering, imho
17:36.27nbdnot on open specs
17:36.58notsmackCan I use the File Format Specification to create a SWF interpreter or player?
17:36.58notsmack<PROTECTED>
17:42.00ElrondNearly as closed as sdal. ;o)
17:52.20*** join/#openmoko pleemans (n=peter@d51A5E76A.access.telenet.be)
17:55.49*** join/#openmoko faded515 (n=faded515@cpc3-hatf4-0-0-cust764.lutn.cable.ntl.com)
18:02.43MorgretAdobe recently announced that they were going to turn over the reigns of PDF to open standards committee, although people say that's because of pressure from MS's document formats.  Well Adobe now own Macromedia, so perhaps flash will one day be properly open.  But yeah, currently it's not.
18:03.25*** join/#openmoko MiniMoose (i=dave@c-24-16-216-41.hsd1.wa.comcast.net)
18:05.11SpeedEvil12/window new
18:05.14SpeedEvilsigh
18:06.48*** join/#openmoko Naked (i=naked@naked.iki.fi)
18:06.48*** join/#openmoko PierreTramo (n=gcarrier@sitlib.org)
18:08.01SpeedEvilTypos still appear.
18:08.08SpeedEvilUnless you go to point+click
18:08.09MorgretTalking of documents ... I wonder what the best ebook/document reader will be for us, given the size of the screen.
18:08.29SpeedEvilI've used xpdf - it's probably not best though.
18:09.03SpeedEvilplus enscript
18:10.36SpeedEvilDo we have an accurate number for the screen dimensions?
18:10.36hrwcu
18:10.45MorgretI wonder if that info is on the xoo template
18:10.52SpeedEvilI suppose it's reasonable to assume that the 2.8" is 4:3
18:10.59SpeedEvilIt looks about tht.
18:11.15*** join/#openmoko den (n=user01@ppp91-76-78-64.pppoe.mtu-net.ru)
18:13.16*** join/#openmoko greentux (n=lemke@195.227.105.180)
18:16.27*** join/#openmoko MiniMoose (i=dave@c-24-16-216-41.hsd1.wa.comcast.net)
18:19.33*** join/#openmoko cdnpen (n=cdnpen@149.99.252.102)
18:25.01*** join/#openmoko cathal (n=cathal@89.100.101.244)
18:25.25*** join/#openmoko koen|gprs (n=koen@dominion.kabel.utwente.nl)
18:25.26*** join/#openmoko Mortimus (n=mortimus@pool-71-250-82-182.nwrknj.east.verizon.net)
18:25.43Mortimuscounter
18:25.43alorila week, 2 days 11:34:16 (9.482 days) for source for *all* developers and devices for selected developers (2007-02-11);  a month, a week, 2 days (37.482 days) for anybody (targeting developers) (preorders: not yet) (2007-03-11);  7 months, a week, 2 days (221.482 days) for mass market (2007-09-11): see topic for more info
18:27.34*** join/#openmoko MiniMoose (i=dave@c-24-16-216-41.hsd1.wa.comcast.net)
18:30.14koen|gprsgood morning all
18:31.07*** join/#openmoko dottedmag (n=mag@dottedmag.net)
18:34.16fluffsright, finally sorted out the hw ecc
18:34.25fluffshttp://www.fluff.org/ben/linux-26/2620/2620-rc6-s3c24xx-nand-hwecc.patch
18:35.24*** join/#openmoko cyphase (n=cyphase@c-71-202-49-23.hsd1.ca.comcast.net)
18:42.54*** join/#openmoko pleemans (n=peter@d51A5E76A.access.telenet.be)
18:52.04*** part/#openmoko Mortimus (n=mortimus@pool-71-250-82-182.nwrknj.east.verizon.net)
18:59.22*** join/#openmoko cdnpng (n=cdnpen@74.210.8.118)
18:59.58*** join/#openmoko vegai (n=vegai@archlinux/trusteduser/vegai)
19:28.24*** part/#openmoko tomjoad4400 (n=tomjoad4@adsl-70-130-201-119.dsl.stlsmo.swbell.net)
19:32.19MorgretCripes, Dell and Intel are in one hell of a heap of costly trouble.  (Slashdot story from Reuters)
19:38.17SpeedEvilWhere do we sign up to get a quarter of a billion to put only intel CPUs into the neo? :)
19:39.08prpplagueSpeedEvil: i think that kind of incentive went away when intel sold its arm dev to marvell
19:46.10*** part/#openmoko _eric (i=eric@gorecki.5stops.com)
19:51.16*** join/#openmoko cathal_ (n=cathal@89.100.101.244)
19:53.04*** join/#openmoko TRIsoft (i=Mac@p57A2996E.dip0.t-ipconnect.de)
19:57.43*** join/#openmoko MacNorth (n=daijobu@c-75-71-250-33.hsd1.co.comcast.net)
20:02.15*** join/#openmoko luca_tgmx (n=luca@87.17.65.93)
20:08.14*** join/#openmoko comicinker (n=simeon@R533e.r.pppool.de)
20:12.08*** join/#openmoko chaoticz (n=leo@213-140-11-133.fastres.net)
20:14.12*** join/#openmoko whitedrought (n=Jeff@70.98.72.130)
20:38.55*** join/#openmoko markit (n=konversa@host119-245-static.72-81-b.business.telecomitalia.it)
20:38.56*** join/#openmoko zween (n=zween@212-139-182-173.dynamic.dsl.as9105.com)
20:39.49*** join/#openmoko zween (n=zween@212-139-182-173.dynamic.dsl.as9105.com)
20:39.54koenhttp://lists.cs.uiuc.edu/pipermail/llvmdev/2007-January/007813.html
20:41.48*** part/#openmoko comicinker (n=simeon@R533e.r.pppool.de)
20:44.55*** part/#openmoko whitedrought (n=Jeff@70.98.72.130)
20:46.06*** join/#openmoko chrustinho (n=christop@p57B0287E.dip0.t-ipconnect.de)
21:01.29*** join/#openmoko lrg (n=liam@lrg.demon.co.uk)
21:02.48Stephmwkoen: J2ME job posting :-) http://tinyurl.com/ypuwwo
21:04.39*** join/#openmoko comicinker (n=simeon@R533e.r.pppool.de)
21:04.50*** part/#openmoko comicinker (n=simeon@R533e.r.pppool.de)
21:07.17*** join/#openmoko ssvb (n=user@87.252.225.64)
21:18.49cyingkoen: ah ha! saw my article didja?
21:24.41CMcying: Did a quick search to see if I could find the article you mentioned, and this is what I got: http://en.wikipedia.org/wiki/Charles_Ying
21:25.05cyingCM: hehe, that's not me :)
21:25.23cyingCM: http://www.satine.org/archives/2007/02/01/connect-the-dots-iphone-graphics-os-x-llvm-arm-and-ruby/
21:25.23CMcying: I kind of guessed that, but it was still funny.. :P
21:25.38CMAh, thanks
21:25.40cyingCM: yea... you would not believe how much crap i get for that
21:26.08cyingCM: "OMG charles i heard you were dating Janice, is that true?"
21:26.16CMHehe
21:27.50*** join/#openmoko _rob (n=rob@ACB6A68B.ipt.aol.com)
21:31.04*** join/#openmoko ninHer (n=ninHer@unaffiliated/ninher)
21:34.45*** join/#openmoko thedaniel_ (n=daniel@38.98.1.19)
21:38.20SpeedEvilI once got invited on an expedition (paid) to the pole, to consult on polar bear mating habits.
21:38.27Polar0.o
21:39.13SpeedEvilI even look sorta-similar.
21:39.28SpeedEvilI suspected they'd have worked out it wasn't me though.
21:39.53cyinghehe
21:46.41MorgretBetter get all the research done before they go extinct :-(
21:48.49noiddThere is no-one else on the web with the same name as me
21:48.55noiddI'm every single web hit baby
21:49.54noiddcat is sitting on my shoulder like a pirate parrot
21:50.02cyingyarrrr
21:50.07SpeedEvilYaaaarr.
21:50.45cyingparley!
21:50.45cyingparley!
21:50.45SpeedEvilYou need to train it to wave a little sabre.
21:51.06MorgretHehe, nice image
21:52.38noiddher body is curled around the back of my neck
21:52.39noiddtoo
21:52.51noiddso, neck warmer
21:52.57MorgretPr0n on OpenMoko!
21:53.22noiddyou can be sure that's comming
21:53.26prpplaguenothing like tamale's made with cat
21:53.28MorgretHehe
21:53.32noiddI do after all live in the worlds fastest growing porn city
21:53.48LittleIdiothmm, two mokos + bluetooth app that syncs them = stereo pron ;)
21:53.49Sketchwhat city is that?
21:53.53CMnoidd: I seem to be the only one with my name on google too :)
21:53.54SpeedEvilLas Vegas?
21:53.55cyingrochester?
21:53.55noiddCharlotte, NC
21:54.02cyingoh right
21:54.04noiddthe buckle of the bible belt
21:54.18mjrI already suggested a porn image (perhaps background), changing according to your location
21:54.47cyingdid they give you a free neo to implement that?
21:54.54mjrno, those bastards
21:55.03SpeedEvilon the neo.
21:55.10mjrSpeedEvil, indeed.
21:55.17SpeedEvilping if someone matching your stated interests is in range.
21:55.37noidddid you get a free greenphone?
21:55.58cyingnot yet
21:56.01LittleIdiotfirst app, i'll write is a rss feed grabber to read the daily news in the subway
21:56.03cyingi've been promised one
21:56.17SpeedEvil:)
21:56.19Stephmwwhat framework is this?
21:56.36cyingme?
21:56.38noidda day after the p0 launch
21:56.39Stephmwyah
21:56.44noiddsomeone is going to sell it,
21:56.58noidd50 people, there has to be at least one person who fancies their chances
21:57.02cyingStephmw: a non sucky next gen UI framework for mobile apps
21:57.04LittleIdioti've just searched for cheap grps rates in germany. there is none :/
21:57.12Stephmwcying: unnamed as yet?
21:57.15cyingStephmw: unnamed
21:57.19LittleIdiotall around 0.2 eur/mb
21:57.27LittleIdioterr, 0.1
21:57.28cyingStephmw: prototype first, then name :)
21:57.47cyingthough if the openmoko folks come up with a VMware simulator image, that might be just as good
21:57.56cyingwith all the tools set up and everything
21:58.32Stephmwkoen: did you check out that link?
21:58.35MorgretGreenphone may end up being just as open, depends.  If it turns out that documented access to the GPS serial port is denied us, then I guess Neo is no more open than the Greenphone.  We'll just have to see.
21:58.36cyingtoolchain setups, linkers, projects
21:58.45cyingso i can just boot, load and start hacking
21:59.01cyingkoen: the setup is the big bugger... it's all about the usability to get the developers in
21:59.02mjrMorgret, "no more"? I beg to differ, even in that case.
21:59.17mjr(as for access to the serial port, it would really boggle me if there wasn't)
21:59.19koenStephmw: heh, another nokia job offer
21:59.31koencying: ehm, a toolchain is not a simulator
22:00.00cyingkoen: well when i run the built executable, i'd want it to come up on screen
22:00.06koencying: it's saddening people keep giving the same answers as you did when I ask what they want to have simulated
22:00.29cyingkoen: oh, well then if you want simulator features:
22:00.32Morgretmjr:  it boggles me too, since the whole point of Neo is openness.  But we'll just have to wait a few days and see, unless Sean speaks up before then.
22:01.07Stephmwkoen: hey, it's the glamorous world of API development :)
22:01.10cyingkoen: emulated screen, touch input, and either build cross binaries or emulate the processor speed
22:01.33cyingkoen: so i can do "hello world" w/o much setup
22:01.40koencying: the only actually useful thing for a simulator would be a gsm module
22:02.13koentelling yourself you need a simulator for 'hello world' is just sad
22:02.34cyingkoen: why? is screen access standardized across all linux distributions?
22:02.41cyingkoen: what do i do to blit to the screen?
22:02.46cyingkoen: and what do i do to get mouse input?
22:02.54mjrcying, Neo will run X
22:03.22koenand looking at the currently available emulators for arm makes wanting one foolish as well
22:03.26cyingmjr: do i learn X to get at the screen buffer?
22:03.30mjrand X is pretty much standardized across most linux distributions; some other embedded ones don't use it, but anyway
22:03.55mjrcying, not really, you should learn SDL instead for things like that
22:04.07SpeedEvilSDL is a layer over X.
22:04.08cyingmjr: and does SDL work with openmoko hardware?
22:04.13cyingahhh
22:04.15SpeedEvilthat is a bit simpler to use.
22:04.27koensdl is a layer over pretty much anything
22:04.27cyingso if i built a SDL codebase, would that just port over to openmoko?
22:04.32SpeedEvilIt brings up a SDL window, and you write to that.
22:04.35CMThe only thing that bothers me is that qemu arm doesn't work well with gcc-4.x.x
22:04.37mjrwell, a layer over X and a whole lot of other stuff; yeah, what koen said
22:04.50CMqemu in general that is..
22:05.20mjrYou probably can kill Neo's X and just use sdl on the framebuffer. Not that I'm suggesting it.
22:05.24cyingmjr: so really, this would be the recommended way to write a openmoko app?
22:05.29koencying: what I'm trying to say is this: "In contrary to other shitty environments, most openmoko stuff doesn't need to be emulated for you to test"
22:05.43mjrcying, it would be if the app in question wants to access a framebufferish thingy
22:05.53*** join/#openmoko stim_ (n=stim@203-206-0-185.dyn.iinet.net.au)
22:05.58mjrif you want widgets and stuff, you use the openmoko libs, based on gtk
22:06.38cyingkoen: what i'm trying to say is that "packaging matters". from my POV, having extensive background in RTOS phone development, but 5 year old UNIX programming background, the less i need to learn to start writing openmoko targetted apps the better
22:06.58koencying: I agree on that
22:06.58cyingmjr: hmmm
22:07.51cyingkoen: from my POV, a VMware image that has linux, a simulator, and the openmoko package all set up in directories and such, with one script you run to get something built, is very very nice
22:08.39cyingmjr: that's good info to know... maybe all i need to get started is just an SDL library
22:09.33koencying: do you *need* a simulator, or do you _think_ you need a simulator?
22:10.39koensince openmoko is a huge break for conventional platforms, conventional paradigms will most likely be invalid
22:11.01cyingkoen: i need something that does this: when i launch ./neosim, i get a window that shows me the openmoko UI and my mouse will do touchscreen-ish things on that UI, built from the same code base
22:11.10CMI guess the "OpenMoko Simulator Howto" page in the official wiki will be a favourite..
22:12.13cyingCM: indeed
22:12.23cyingkoen: but i am curious, why i don't need this
22:12.40cyingkoen: it's just that from my POV, this is what i would want to get started
22:12.46koenyou can get the same using Stefan's Xoo skin
22:12.56koenno need for a simulator
22:12.58koensince
22:13.11koena) nothing available can emulate the cpu properly
22:13.20SpeedEvilI want to know at the moment - does it simply look like a 'normal' X window with normal mouse?
22:13.23koenb) you don't have a 300dpi screen
22:13.31koenc) a mouse isn't a touchscreen
22:13.59cyingwhat does his xoo skin do?
22:14.00SpeedEvilb and c are annoying.
22:14.15SpeedEvila) can sort of be worked round by limiting cpu timeslice.
22:14.17CMcying: It just makes it look a bit like the open moko
22:14.23SpeedEvilYou can at least get pessimistic.
22:14.26cyingCM: "it" ?
22:14.26koenSpeedEvil: nope
22:14.26CMAnd sets the resolution for Xoo correctly
22:14.34CMIt's a png and an xml
22:14.38cyingoh XOO
22:14.47koenSpeedEvil: qemu and armulator don't emulate unaligned access faults for example
22:15.07CMcying: It's on the o-hand page
22:15.08cyingoh see?
22:15.10koenSpeedEvil: so a+b+c make 'simulation' nothing more but a toy
22:15.10noiddxoo is basically a pretty Xnest
22:15.11SpeedEvilI mean _roughly_ - as in 1/bazth of a Pfoo/barGhz
22:15.11cyingthis is what i want
22:15.14noiddafaik
22:15.31SpeedEvilHorribly inaccurate, should be within a factor of 5 though.
22:15.35cyingkoen: i think that can be set
22:15.42cyingkoen: on armulator at least
22:15.51SpeedEvilFor much stuff.
22:16.00koenSpeedEvil: so people that say they *need* a simulator are fooling themselves
22:16.18koenSpeedEvil: or are in for a big surprise when they finally break out the real hardware
22:16.33koen"hey, this screen is smaller than on my CRT"
22:16.47CMHehe
22:17.03koen"performance profiles are completely different, why's that?"
22:17.03cyingkoen: if you're doing serious app development, having a desktop development environment helps a lot
22:17.07SpeedEvilAppropriate prescription glasses, and sitting back can ssort of help.
22:17.09CMBut it's true, I guess the scrollbars and such will look huge on a normal monitor
22:17.10cyingkoen: even if the profiles are different
22:17.23koencying: I didn't say it didn't help
22:18.27koendepending on a simulator is like not taking driving lessons put playing GTA:SA instead
22:18.32cyingkoen: so create a VMware linux distrib bundle with Xoo and openmoko's base system packaged and ready to go
22:18.46koencying: right, that's already available :)
22:18.57cyingkoen: well shit, point me at it!
22:19.53noidddid tha person ever pay up the cash for it koen?
22:19.54koencying: MACHINE=qemuarm in OE generates an environment like that
22:20.12koennoidd: I have no idea what [g2] and hrw agreed on
22:20.25Morgretkoen: can never please everyone.  Half will say this phone is smaller than the xoo image, and half will say this phone is too big. :-)
22:20.49[g2]hey koen
22:20.53*** join/#openmoko zipola (n=zipola@zip.kortex.jyu.fi)
22:21.08cyinggood grief
22:21.15MorgretI couldn't care less what its size is.  It's open.
22:21.19cyingthere's about a 20 step process on the openembedded site
22:22.03noiddg2: did you cough up the cash to hrw in the end? :-)
22:22.06cyingand where is openmoko's core GUI then?
22:22.12cyingis that just OE?
22:22.54[g2]noidd I had talked about a bounty and then I was going to write something up
22:22.54cyingoh
22:22.58cyingthere it is on the home page
22:22.59cyingokay
22:23.09cyingwell a VMware image would help, but i suppose this will do for now
22:23.25[g2]noidd I never wrote anything up, but hrw went ahead and developed something
22:23.53[g2]noidd I haven't tested what hrw created
22:24.49noiddroger that
22:24.54noiddget testing :-)
22:24.57[g2]noidd have you tried it ?
22:25.12*** join/#openmoko newmedian (n=newmedia@TOROON63-1168100004.sdsl.bell.ca)
22:25.42noiddNo, didn't know it was there until a few lines ago
22:26.05[g2]noidd I've been distracted by two issues: 1) ixp4xx stuff, 2) moving my base build environ from edgy to xfce
22:26.50[g2]and 3) a bunch of video/media streaming things
22:27.52*** join/#openmoko quinton (n=quinton@84-45-151-51.no-dns-yet.enta.net)
22:29.44noiddI'm guessing we'll get another mtn feed
22:30.05*** join/#openmoko thedaniel_ (n=daniel@38.98.1.19)
22:31.19*** join/#openmoko bluelightning (n=blueligh@222-155-213-100.jetstream.xtra.co.nz)
22:32.08[g2]noidd dunno, but it was a 4hour+ monotone conversion for that last one I pulled
22:43.42noiddwow
22:48.09newmedianhmm, what's this terminal laying here in the corner for? someone must have lost it.
22:49.09*** join/#openmoko ans (n=anselm@pool-71-244-143-199.chi.dsl-w.verizon.net)
22:56.46*** join/#openmoko bkuhn (n=bkuhn@atheist.ebb.org)
23:28.27CMNice joke, actually: http://degredo.net/
23:43.02*** join/#openmoko cprf (n=rzinkov@oss-staff.rutgers.edu)
23:45.04*** join/#openmoko pr3d4t0r (n=cu4cu4@pdpc/supporter/active/pr3d4t0r)
23:45.06pr3d4t0rGreetings.
23:46.25cprfhowdy
23:46.39cprfis there anyway to play with some emulator of the openmoko
23:46.54cprfto give the feel for the kind of technology it is
23:47.43mjrcounter
23:48.05mjrhmh, the bot is down
23:48.17mjranyway, cprf, in about a week the platform source will be released
23:48.35mjrthat'd be all the "emulator" you'd likely need, except for perhaps some details
23:49.32cprfsweet
23:53.40pr3d4t0rcprf: I read the wiki regarding hardware, etc.  Is there a formal process to get a hold of the hardware?
23:54.10pr3d4t0rcprf: I've led development for commercial mobile applications.  I'm curious about the actual hardware, even if it is in prototype form.
23:54.29pr3d4t0rs/cprf/mjr/
23:54.33pr3d4t0rmjr: ^^^
23:56.09pr3d4t0rmjr: The wiki only says "select developers" - I'm working with a group of people who have interested in the OpenMoko platform and we'd like to evaluate it not only the software/OS but also the hardware.  We're based in San Francisco.
23:56.10mjrI'm not with FIC; anyway, phase 0 where free phones are distributed is decided, phase 1 (wolrdwide sales targeting developers) starts 11th March
23:56.17newmedian(Phones given to select developers on Feb 11, available for sale to developers on Mar 11, and general public in Sept, from my memory of the counter)
23:56.22SpeedEvilanyone can buy one for $350
23:56.24pr3d4t0rmjr: Yes.
23:56.42SpeedEvilThe price 6 months on drom then has not been disclosed AIUI, and will presumably depend on the market then.
23:56.43pr3d4t0rmjr: It's not clear if there is a qualification process for 11.March.
23:56.54mjrand when I say decided I mean they've decided already who gets the phase 0 phones
23:56.56newmedianprobably a valid credit card. ;)
23:57.18mjrpr3d4t0r, going by what they've said on the mailing list, no
23:57.19pr3d4t0rmjr: Phase 1 would be fine with us if we can put acquiring a couple of devices in our dev plan.
23:57.58mjranyone should be able to buy on March, just that they're expected to know they're getting a development device
23:58.18pr3d4t0rmjr: Cool, thanks.
23:58.30slavapr3d4t0r!
23:58.34pr3d4t0rslava!
23:58.46pr3d4t0rslava: What are you doing here?
23:58.53slavapr3d4t0r: i'm interested in the device
23:58.56pr3d4t0rslava: This is the last channel I'd expect to find you at.
23:59.01pr3d4t0rslava: So is my posse.
23:59.56slavapr3d4t0r: i'm porting my stuff to ARM/Linux

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.