| 00:17.48 | *** join/#openezx Fry-kun (n=kostya@h-67-100-89-239.snfccasy.covad.net) |
| 00:17.55 | Fry-kun | well, this is interesting |
| 00:18.09 | Fry-kun | now have a different error |
| 00:20.18 | *** join/#openezx AlexZhang (n=alex@218.17.81.173) |
| 00:32.10 | *** part/#openezx AlexZhang (n=alex@218.17.81.173) |
| 00:46.16 | Fry-kun | oops |
| 00:46.35 | Fry-kun | should've asked Alex to help me |
| 00:46.39 | Fry-kun | :)p |
| 01:43.57 | *** join/#openezx AlexZhang (n=alex@121.35.124.27) |
| 01:47.01 | Fry-kun | hi there |
| 01:47.18 | Fry-kun | , Alex |
| 02:11.24 | *** join/#openezx AlexZhang (n=alex@121.35.124.27) |
| 02:17.38 | *** join/#openezx AlexZhan1 (n=alex@121.35.124.27) |
| 02:34.38 | *** join/#openezx AlexZhang (n=alex@121.35.124.27) |
| 04:05.50 | Fry-kun | oookay, this is really weird |
| 04:07.43 | Fry-kun | running once: failed |
| 04:07.50 | Fry-kun | running 2-3 more times: failed |
| 04:08.04 | Fry-kun | running 4th time: spike out cpu for a minute, then failed |
| 04:08.25 | Fry-kun | running 5th time: definitely doing something (cpu spiking but didn't fail yet) |
| 04:14.14 | Fry-kun | running the command line by hand gives me different crashes, too |
| 04:14.18 | Fry-kun | it's not consistent o_O |
| 04:14.36 | Fry-kun | what's up with all this cross-compilation and bootstrapping? |
| 05:11.05 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 05:32.54 | Fry-kun | *yawn* |
| 05:33.44 | Fry-kun | 'nite all |
| 05:33.50 | *** part/#openezx Fry-kun (n=kostya@h-67-100-89-239.snfccasy.covad.net) |
| 05:52.55 | *** join/#openezx AlexZhang (n=alex@121.35.121.236) |
| 06:35.29 | *** join/#openezx dion (n=dion@inhex.net) |
| 07:19.58 | *** join/#openezx LuitvD (n=luitvd@beigetower/luitvd) |
| 07:37.32 | *** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 07:37.37 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 08:33.22 | *** join/#openezx |dion| (n=dion@inhex.net) |
| 08:42.03 | *** join/#openezx AlexZhang (n=alex@121.35.121.236) |
| 09:34.24 | *** join/#openezx is_null (n=james@82.240.220.118) |
| 09:41.02 | is_null | hello everybody, you can remove the vapourware from imcosys on page http://wiki.openezx.org/Other_Linux_Phones, i ordered it a year ago and the seller keeps telling me that he will contact me as soon as he gets my device |
| 09:47.58 | stefan_schmidt | is_null: It's a wiki. Just add this as comment. :) |
| 09:50.15 | is_null | stefan_schmidt: i know but i don't have access as guest |
| 09:50.50 | stefan_schmidt | is_null: Make a account? |
| 09:51.53 | stefan_schmidt | is_null: Do it yourself or hope I remember it later today. :) |
| 09:54.12 | webmind | making an account is quite easy :) |
| 11:39.17 | *** join/#openezx koen (n=koen@dominion.kabel.utwente.nl) |
| 13:44.25 | *** join/#openezx drath_ (n=vmaster@p5B07CC05.dip.t-dialin.net) |
| 13:55.56 | *** join/#openezx AlexZhang (n=alex@121.34.175.52) |
| 14:04.46 | *** part/#openezx AlexZhang (n=alex@121.34.175.52) |
| 15:47.08 | *** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 15:55.32 | *** join/#openezx ao2 (n=none0@host14-142-dynamic.9-79-r.retail.telecomitalia.it) |
| 15:59.07 | *** join/#openezx dion (n=dion@inhex.net) |
| 16:07.23 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 16:41.34 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 17:19.17 | *** join/#openezx Fry-kun (n=kostya@h-66-166-233-66.snvacaid.covad.net) |
| 17:20.09 | Fry-kun | 'ello there |
| 17:41.27 | Fry-kun | anyone awake? |
| 17:46.25 | SuN | Not really. |
| 17:46.33 | Fry-kun | :) |
| 17:46.42 | Fry-kun | hi |
| 17:46.51 | SuN | I'm just saying something so you know it's not your connection or anything :) |
| 17:46.53 | SuN | Hi! |
| 17:46.56 | Fry-kun | I'm a newbie |
| 17:47.02 | Fry-kun | Konstantin on the mailing list |
| 17:47.23 | SuN | Ahh ok, I saw your mails. |
| 17:47.36 | Fry-kun | still trying to compile OE |
| 17:47.57 | Fry-kun | if you have any suggestions, i'd appreciate them ;) |
| 17:48.15 | SuN | Not really, I'm an OE-newbie myself. |
| 17:48.21 | Fry-kun | ah ic |
| 17:48.30 | Fry-kun | have you been able to build it, at least? |
| 17:48.50 | SuN | Yes, but about 2 years ago, for a Zaurus :) |
| 17:49.05 | Fry-kun | ..and you call yourself a newbie after 2 years |
| 17:49.09 | Fry-kun | i see :] |
| 17:49.21 | SuN | Well, I never got into it. |
| 17:49.27 | Fry-kun | ah, okay |
| 17:49.46 | Fry-kun | so what rekindled your interest? |
| 17:50.06 | Fry-kun | new hardware? |
| 17:50.18 | Fry-kun | I'm interested in A1200 MING, personally |
| 17:50.26 | SuN | I have an E6 |
| 17:50.33 | Fry-kun | awesome phone, except the proprietary crapola software |
| 17:50.40 | SuN | And I have an E680 as well. |
| 17:50.51 | SuN | Well, the software isn't all bad, considering the alternatives :) |
| 17:51.07 | Fry-kun | what's e6 |
| 17:51.26 | Fry-kun | e680 looks nice |
| 17:51.35 | SuN | The new ROKR, it's somewhat similar to the A1200, software-wise (same platform), but it's a candy bar-style. |
| 17:51.36 | Fry-kun | i prefer clamshell form factor, though |
| 17:52.02 | Fry-kun | http://www.phonescoop.com/phones/phone.php?p=491 <- i'm looking at e680 |
| 17:52.07 | Fry-kun | but can't find e6 |
| 17:52.14 | SuN | In a few words, the E6 is basically an improved A1200-E680 hybrid :) |
| 17:52.21 | Fry-kun | ooh |
| 17:52.24 | Fry-kun | neat |
| 17:52.49 | SuN | The form factor is the same as E680, but it's much thinner, has a 2MP camera and a 3.5inch headphone jack. |
| 17:52.57 | Fry-kun | wow |
| 17:53.08 | Fry-kun | so it's meant to be an ipod killer? :D |
| 17:53.17 | SuN | More or less, yeah. |
| 17:53.19 | Fry-kun | usually 2.5mm is all you get with a cell phone |
| 17:53.29 | Fry-kun | btw, a1200 comes with a stereo 2.5mm connection |
| 17:53.40 | SuN | Yep, a real pity. I had to use an ugly convertor with my E680./ |
| 17:54.17 | SuN | Now I can plug it straight in. |
| 17:54.17 | Fry-kun | neat |
| 17:54.17 | Fry-kun | but then.. it probably has bluetooth anyway, right? |
| 17:54.19 | SuN | That was one of the main incentives for me to get the phone, since it's fairly similar to the E680 and I already had that. |
| 17:54.21 | Fry-kun | so why use wires |
| 17:54.25 | SuN | Yep, A2DP |
| 17:54.36 | Fry-kun | so now you want to liberate your e680? |
| 17:54.45 | Fry-kun | that why you're trying openezx? |
| 17:54.57 | Fry-kun | since you'll be using your e6 for primary instead |
| 17:55.06 | Fry-kun | oops, brb |
| 17:56.03 | SuN | Well I've been here for 2 years already, but I've mainly been waiting since I don't know much about kernel hacking and there's not much to do in userland-terms at the moment, because the basics aren't finished yet so there's no way of knowing what it should interface to |
| 17:58.35 | SuN | Plus everyone's waiting for what openmoko brings in terms of user interfaces, anything done independently from that is somewhat doomed to obsoletion before it's even released. |
| 18:04.03 | Fry-kun | back |
| 18:04.24 | Fry-kun | hm, interesting |
| 18:04.27 | Fry-kun | what's openmoko |
| 18:04.43 | SuN | http://openmoko.org/ |
| 18:05.13 | Fry-kun | does it include the kernels/etc? |
| 18:05.23 | Fry-kun | or will it run on top of OpenEZX? |
| 18:06.11 | SuN | It's OE-based. |
| 18:07.05 | SuN | So basically there are device-specifics and the rest of the apps, which will ultimately be offered in an openezx flavor, I assume. |
| 18:07.10 | Fry-kun | so basically EZX is a competitor?.. |
| 18:07.25 | SuN | Not really, EZX is a different layer, more or less. |
| 18:07.43 | SuN | Parts of openmoko will be integrated into EZX, I imagine. |
| 18:07.45 | Fry-kun | right, that's what i was asking - does it run on top of EZX |
| 18:07.50 | Fry-kun | ah i see |
| 18:08.01 | SuN | Well, it depends on your definition of EZX. |
| 18:08.12 | Fry-kun | it's a bit confusing - there's OpenEmbedded and OpenEZX (both can be called OE) |
| 18:08.15 | Fry-kun | -_- |
| 18:08.26 | SuN | In terms of Motorola EZX, probably not, since it will most likely be discarded. |
| 18:08.40 | SuN | And openezx in its current form is more or less a stub. |
| 18:08.55 | Fry-kun | wait, motorola ezx? what's that? |
| 18:09.08 | Fry-kun | lol looks like i jumped in without looking ahead |
| 18:09.13 | SuN | The kernel patches will either go mainstream of become deviceisms in OpenEmbedded (which is the only thing I'll call OE). |
| 18:09.34 | Fry-kun | ah, i see |
| 18:09.37 | SuN | Motorola EZX is what the phones currently ship with. |
| 18:09.48 | SuN | Montavista Linux + QTe + lots of Motorola crap. |
| 18:09.50 | Fry-kun | okay |
| 18:10.01 | Fry-kun | what does "ezx" stand for? |
| 18:10.04 | Fry-kun | out of curiosity |
| 18:10.27 | SuN | I think only Motorola knows :) |
| 18:10.34 | Fry-kun | aaah |
| 18:10.36 | Fry-kun | gotcha |
| 18:12.01 | Fry-kun | in that case, i wonder where i would be most useful - in terms of speeding up the release of a firmware replacement for a1200 |
| 18:12.29 | Fry-kun | i'm guessing that openmoko is doing well in terms of userland, but a1200 has barely any hardware support |
| 18:12.39 | SuN | Probably kernel driver programming... though I'm not very much into the details. |
| 18:13.05 | SuN | Yep, there needs to be sufficient kernel support before anyone can even think about getting openmoko working. |
| 18:13.06 | Fry-kun | if that's so, then devs in openezx are needed more than openmoko |
| 18:13.23 | Fry-kun | but as soon as there's kernel support, openmoko should just run, right? |
| 18:13.27 | Fry-kun | more or less :) |
| 18:13.36 | Fry-kun | probably less than more... |
| 18:13.45 | Fry-kun | but would be much closer |
| 18:13.46 | Fry-kun | hehe |
| 18:13.48 | SuN | More or less, yes. Bar some glue between the drivers and openmoko, but that should be fairly trivial. |
| 18:14.07 | Fry-kun | gotcha |
| 18:14.59 | SuN | And then stuff needs to get rearranged to run on 320x240 but that is just a lot of work, not very challenging, as opposed to say, baseband processor -> app processor communication, etc. |
| 18:15.22 | Fry-kun | right.. |
| 18:15.27 | SuN | And there's room for alternatives, I can imagine a basic GPE environment with a few specific apps will do the trick for Motorola phones as well. |
| 18:16.03 | SuN | Very crudely put, it doesn't consist of a lot more than a dialer, phonebook and sms text app. |
| 18:16.36 | Fry-kun | yeah, reading their availability page now - that's about what it says |
| 18:18.00 | SuN | The gsmlib will be a large part, and it's probably what an openezx kernel should communicate with as well, but since there's (AFAIK) no standard yet, things are hard to implement. |
| 18:18.34 | SuN | But don't trust me on the real status, I'm sort of out of the loop :) |
| 18:18.57 | Fry-kun | gotcha |
| 18:23.24 | SuN | It's just that I'm occasionally the only person available to talk, and that's pretty much all I can do at this point. |
| 18:23.36 | SuN | (I'm not even officially involved) |
| 18:23.48 | Fry-kun | that's cool, at least you cleared up some stuff for me |
| 18:23.54 | Fry-kun | i'm very confused normally :) |
| 18:24.08 | SuN | :) understandable, there's quite a lot going on here. |
| 18:24.44 | SuN | More than a wiki could cover, for instance. Even if it were regularly maintained (or if things were moving slow enough for that to be possible, that is). |
| 18:25.02 | Fry-kun | haha, yeah |
| 18:40.58 | *** part/#openezx Fry-kun (n=kostya@h-66-166-233-66.snvacaid.covad.net) |
| 19:43.59 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 20:33.18 | *** join/#openezx CIA-24 (n=CIA@208.69.182.149) |
| 20:33.57 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 20:48.07 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 20:58.02 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 21:26.48 | *** join/#openezx goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com) |
| 21:29.37 | *** join/#openezx dion (n=dion@inhex.net) |