Re: debian on neo1973: ogpsd failing?
ok, found it copied /usr/share/doc/fso-frameworkd/examples/frameworkd.conf to /etc and then modified the ogpsd section: [ogpsd] device = NMEADevice channel = FileChannel path = /tmp/nmeaNP log_level = INFO the debian neo1973 page can't be modified, but this would be very useful info on it. Brad but gpspipe (talking to fso-gpsd) is not getting any of this. I believe this means that ogpsd is failing to send dbus messages for the current fix. What should I do to make ogpsd work? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Community update
Hello everybody, and welcome to the Openmoko Community Newsletter, for the November 3th to November 16th timespan. During these two weeks, we had FSO milestone IV and a testing SHR image released. Openmoko pulled the download server offline due to an mp3 copyright issue, they are rebuilding everything without any questionable codecs. Werner announced a firmware update for the GSM chip that will allow 3G chips compatibility. And there is movement again towards a better driver for the glamo graphic chip. Contents [hide] * 1 Distributions * 2 Applications * 3 Infrastructure: X and OE * 4 Kernel * 5 Hardware [edit] Distributions FSO team released Milestone IV 'Homework', see the OpenmokoFramework/Status Update 5. To accomodate the forthcoming release of other FSO API consumers like paroli or the SHR phone stack, three FSO-compliant images are build and released now: 1. fso-console-image: minimal system with frameworkd, no user interface manager. 2. fso-illume-image: everything in console-image plus X-Window, plus Enlightenment plus Illume window manager. 3. fso-image: everything in illume-image plus Zhone. Can be used for phone calls. Like previous milestones. But Zhone is going to be faded out. Debian: Joachim announced that the preferred installer script is now the one in the git. The old URL does redirect to it. Thanks mostly to Luca “Gismo” Capello’s great work, recent improvements include: 1. The use of the general auto-login script “nodm” instead of zhone-session. Session configuration can now be done by modifying /root/.xsession. 2. Device independent frameworkd and accompanying configuration packages. If apt-get upgrade breaks your FreeRunner, try to run apt-get install fso-config-gta02. 3. openmoko-panel-plugin installed by default (running in trayer), to provide keyboard toggle and device control. 4. The use of the packaged kernel instead of wget/tar. To get this going, run apt-get install linux-image-2.6.24-openmoko-gta02 SHR is getting closer to a first milestone release. According to BillK and others who kindly tested the latest version, the ergonomy feels generally better than other distros. But its early days yet, if you need a phone use 2008.9. Julien Cassignol invites the braves out here to install a preview SHR-testing (wiki help) and join the Internet Relay Chat on #openmoko-cdevel on FreeNode. FDOM is considering wether to move to OpenEmbeded, as this would solve the source redistribution issue nicely. On November 12th, http://downloads.openmoko.org/releases/ were taken offline due to the discovery of an MP3 licensing issue. Openmoko collaborates with the Software Freedom Law Center in New York on this kind of issues. [edit] Applications Aapo compiled a newer version of Numptyphysics package on Debian, which can be played landscaped, without keyboard and it uses same datafiles than any other numptyphysics-port is at: http://www.opkg.org/package_3.html. Signal Applications To Any (Audio) Network, or, ehm, SATAN, was born... This is a tracker to create simple music, or just jam on the train, bus or café. Debian users rejoice: openmoko-panel-plugin reaches 0.5. Show and modify you the state of the hardware in you FreeRunner(i.e. gsm, gps ...) with any gtk based windowmanager (i.e. xfce). (thread, download). Centerim, a terminal-based instant messager, ported on the freerunner (package, port page) In the wiki, the Applications and Distributions pages were revised. We are having trouble with an engine extention that eats up whitespace, the workaround is to wrap pre formatted text in pre tags. The thematic List of X applications pages are going away, we want to keep just one big directory style application linkfarm. The idea is that presenting applications in organized ways is better done by http://opkg.org . This directory already has 45 entries, please register and go populate it. [edit] Infrastructure: X and OE Reports from the optimization team have been landing weekly. They include patches to fix ticket 1884 ([suspend/resume] if press power batton right after suspend, the device won't wake up) and patches to improve the network registering time. The openmoko-mediaplayer2: dependency on pulseaudio was removed to use alsa instead. And various utilities should appear shortly in the distributions, including telnet, wget, tcptraceroute, wmiconfig, a bunch of X system fonts and more. The lack of GLamo OpenGL is still a major dark hole on the FreeRunner's phone liberation front. Hacker culture factoid: did you know that as a software project X is older and about as large as the kernel with a penguin on it, but has an order of magnitude less contributors to it ? Wolfgang from Openmoko wrote: If someone wants to seriously develop for the glamo, please get in touch with me and we will find a legally correct way to extend the smedia documentation to you. In fact we have done that in a few
Results of WSOD (unofficial) survey question
Hi, As promised, here are the results after a week. I received only 11 results so they are hardly meaningful. Here is the break down anyway: 2 - Dropped with no effect on functionality 5 - WSOD Out of the Box (i.e. never dropped) 1 - Dropped with no effect for a while, then regular WSODs 3 - WSODs experienced, but not stated if dropped or not. As a side note, 2 people reported WSODs under other distros but not FDOM, 1 person reported WSODs under other distros but not Qtopia. In the interests of brevity, I did not mention that Harald had done some work, and that Andy was trying to find a way to work around the issue regardless of the cause. Thanks Andy, I didn't mean to undermine you or your work - sorry. I admire your persistence even though only a relatively small number of devices are affected. The behaviour changes with temperate are interesting, but I'm not sure if they mean anything, and one person said that it had no effect in their case. grslmpf mentioned that resistors could be an issue, and I agree that it possible that cumulative variance of the properties passive components _might_ lead to this problem, but that is something that I may experiment with _after_ a work-around (such as Andy's reset trick) is found. Passive device variance may also explain the difference in symptom onset times, which is 15 - 20 minutes for me but 1 - 2 minutes for others. I'm also not sure how temperture affects the properties of passives though - maybe there is a correlation? Have fun, Greg. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
On Mon, 17 Nov 2008 13:54:55 +0800 John Lee [EMAIL PROTECTED] babbled: On Sun, Nov 16, 2008 at 10:05:16AM +1100, Carsten Haitzler wrote: x's internals are definitely up for improvement - callium3d is there to try and fix this by providing a better more organised and better accelerated driver layer - but again - they aren't going to replace x... just clean up internals. what it means is - the rest of us can continue happily writing x apps and just wait for an improvement to pop out the pipeline. indeed x's internal acceleration layer could be improved. it has in the past (especially with xaa) proved an impediment if you have to code AT the driver layer. as such - x was originally designs (as a system - not specifically the xorg tree etc.) to allow full freedom to implement the internals of x any way you like - so as such if you wanted to spend the effort x could accelerate just about everything as long as hardware can do it, somehow - but the points at which that acceleration knowledge need to go into might be much higher up than xaa/exa. you'd have to write a forked x with all sorts of hooks higher up. - but it's possible... and then x client work as they always did - and get more use of the hardware :) MicroXwin ? http://www.microxwin.com/ MicroXwin is binary compatible to the Xlib API. However it is niether client server nor network oriented. Graphics operations are implemented in the linux kernel via a kernel module. An open source Xlib library sends graphics commands to the kernel. There is no network overhead and no context switch from X client to X server. This makes our solution smaller and faster than traditional X Windows. as such - context switching doesn't happen as often as people think.. if you write good x code - its' buffered. but as such this is an interesting solution - that is linux specific. not sure if it handles everything (window management, and not to mention enough of the modern extensions), but for gta03 (as this is framebuffer based) this could be a definite option. i'd say it'd be worth exploring. keeps compatibility AND should give you some speedup. not sure just how much day to day though. but the license seems... opaque - no idea what it is but it looks closed. but as such this would be another valid way of doing things with x. as such x apps just should avoid round-trip calls to x, so while they run they can do all their gfx ops WITHOUT a single round trip (thus no cache flush) and they only flush on final draw of everything - so just once per frame really (for the app). -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, 17 Nov 2008 02:40:19 -0500 Lally Singh [EMAIL PROTECTED] babbled: Well then, Therein lies the question, how long is OM going to be using the Glamo? There's apparently some real potential in the device, but that's really measured as much by the chip's relevance as its functionality. this is the problem. glamo is not used anywhere else on any linux/x running devices. it's a one-shot wonder so far in the gta02. as best i know there are no plans to use it again. it's an end-of-life chip anyway - it's old and has been out for a long time so even if you wanted to - it may not be available anymore in the near future (unknown - but likely scenario). in the end - you need to weigh up effort vs. return on effort. the glamo itself actually is quite limited. trust me. when i first just read the bullet point featurelist i too was excited... then i actually read all the nitty details and the gotchas, the only in this situation, only with these inputs or outputs or only within these parameters and my excitements dwindled very quickly. you'll have to jump through some nasty hoops just to get a bit more accel - and as i made a bet long ago, and i still stand by it. you'll spend a lot of code doing a lot of acceleration and you will actually... not be faster. for most things. the only thing that has anything of vague interest is opengl-es - and even then here are some bullet points for limitations: 1. 256x256 max texture size (for vga and 2d this is just appaling in this day and age) 2. max output buffer 511x511 (that means... qvga boys. and right now.. qvga doesn't even work as the pixel timings aren't right). 3. no render-to-texture 4. texture uploads are slow (7m/sec) combined with only 8m video ram 5. if you saw the 3d docs... they are scant at best (register names pretty much) and not much else. now add to this having to merge it with 2d (texture allocation shared with pixmap), the only thing i see gl being useful for is some limited 3d games that are fullscreen (drop to qvga). qvga on the lcd actually looks rather awful (very blocky) as well... i'm not saying don't do it. i'm saying you need to look at what you have, the effort needed, the return on effort, the results, and the future. The GTA02's been on the brink of obsolescence since the day it was introduced. It can't even take most modern (3G) SIMs. If the Glamo (or something compatible) is going to be around for a while, either in a long production life of the GTA02, or in newer phones, then all this makes sound engineering sense to work on. Otherwise, I have real doubts about the longevity of a software project aggressive enough to attempt major work (e.g. accellerated OpenGL) on this chip. Lots of open source projects start off with a bang of enthusiasm, and die with a whimper. If the chip's gone in a few months, I don't think we'll see the project survive. Hence, my earlier suggestion on just using the acceleration for some Gtk operations. Small, effective changes. Get that done to make the device feel responsive. If someone wants to do the big OpenGL implementation later, fine, use this Gtk work as a sandbox for getting a feel for the device. this is the thing.. the drvier is ALREADY doing this. i repeat this ad-nauseum. the acceleration is the same u get in the nv driver or you saw a few years back in the i8xx drivers etc. you get blit and fill accelerated (the most common x ops). xvideo is accelerated. the only thing not is anti-aliases font drawing and as such the glamo doesnt support this fully - u need to do some hacks to pretend it will (like expand fonts to ARGB32 in software) and from the look of it the expansion and then upload of pixels will likely net you zero speedup as this extra cost will negate the speedups you get. imho glamo is right now about as fast as u'll ever likely see it (imho). you can go sink a mountain of work and as per the example above.. see no return. the ONLY thing that i can see it might be worth it is opengl - and even then its a very weak opengl accelerator with lots of gotchas. all of the above of course is in my opinion. it's based from years of doing graphics - software and hardware and with x, and having read all of the glamo docs. the original hope was to do the most urgent acceleration that can be done cleanly and get 90% done (which is where it is at), and then open the docs so people can tweak - thats the point of an open device. openmoko can't go supporting some ancient device forever and ever - in 3 years will people still be demanding updates and support? thats the point of it being open - you can support yourselves via community. the problem is the fact that the docs are not open to allow this to happen so there is a problem here. i know so many of you are all excited over Accelerating glamo - it's already done (for 2d) as much as is probably practical for x11 that will get you speedups. 3d is possible but with a hefty list of limitations and a lot of
Re: [Om2008.9] How to power off Wifi?
El día Sunday, November 16, 2008 a las 01:49:57AM +0100, Minh Ha Duong escribió: Le samedi 15 novembre 2008, Matthias Apitz a écrit : I don't know if it reduces the drawing of power (btw: what is the easiest method to measure it? pulling out the battery and measure the power consumption via the cable?); I would use something like the attached battery.py script to measure power. Minh Thanks for this; I have had an older version without the detailed information about power drain and so; It is a bit tricky to use such a Python tool to measure things because it has to much effect in the power consumption by its own; maybe I will just collect in the future the data from the /sys/... files and draw the figured later based on them; for now I've tested it with your battery.py, here are the numbers: 181 mA -- nearly empty FR (only battery.py and Terminal running) 231 mA -- after launch of GPSD 183 mA -- after stop of GPSD 189-232 mA -- after Wifi-up with, running 'ping' through eth0 184-186 mA -- after Wifi-down For me this reads that the Wifi chip is already powered-up on boot; the diff between before (181) and after using it (184-186) is not very big; right? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
2008/11/14 Gothnet [EMAIL PROTECTED]: It really needs work on the basics. I mean, responsiveness is not there, interface is dodgy (the end call button being in the same spot as the accept call button, and being unresponsive, made me hang up s many calls). Echo on calls, battery life... These are all small issues as such, as they are all on the software side and many have been either fixed or are different on different distributions (you don't need to use Openmoko's distribution - you can use Debian, Qt Extended, SHR, ...). You will find echo fixed in Openmoko's 2008.11 release, if you keep using the Openmoko distro, and responsiveness and touch screen usability will also improve with 2008.11 release. End call / accept call stuff are just UI things, easy to fix, but maybe you should file a bug report about it since otherwise no-one might notice. The buzzing issue is the only real, serious issue. Also, I know everyone loves X, but is it really the best choice for a low powered device that needs a responsive UI? Yes :) Any unresponsiveness in the UI is not because of the X. I think maybe I had the wrong impression about the state of the software when I bought it. Probably. It's not a phone product yet, it's a phone in development. From your point of view I can understand the frustration with the other issues, but for me they are just a few things to work on / test fixes. The buzzing / hw issue is really the only thing I'm worried about, since it needs to be fixed and there is no known software fix for it yet. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
2008/11/17 Lally Singh [EMAIL PROTECTED]: $400 for a phone is a reasonable investment. But months of work in one's spare time is much bigger. Before anyone commits to a large-scale project, I think it's fair to ask OM what their plans are with this chip. Hey people, please don't underestimate the general willingness to hack stuff :) Most of us don't think about value-for-money, sensibility or other minor aspects. Coding is fun! That's why we have accelerometer-controlled Doom working fluently before phone calls, and I think it's great ;) So I don't think there's any value discussing how sensible / meaningful / valuable doing OpenGL support would be. If there are people interested, that's great and it's not cutting anything away from somewhere else. Volunteer people need to do what they like to do, not what's the most sensible product-wise. And we already have eg. partial MPEG4 hw decoding using Glamo, imagine if the developer of that would have been told don't waste your time on something like that. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
About the buzzin issue, I would like to be sure : is it or is it not hardware related ? I heard about a soldering fix of one electronic component which could get rid of the interferences... Has anyone more information ? Kimaidou 2008/11/17 Timo Jyrinki [EMAIL PROTECTED] 2008/11/14 Gothnet [EMAIL PROTECTED]: It really needs work on the basics. I mean, responsiveness is not there, interface is dodgy (the end call button being in the same spot as the accept call button, and being unresponsive, made me hang up s many calls). Echo on calls, battery life... These are all small issues as such, as they are all on the software side and many have been either fixed or are different on different distributions (you don't need to use Openmoko's distribution - you can use Debian, Qt Extended, SHR, ...). You will find echo fixed in Openmoko's 2008.11 release, if you keep using the Openmoko distro, and responsiveness and touch screen usability will also improve with 2008.11 release. End call / accept call stuff are just UI things, easy to fix, but maybe you should file a bug report about it since otherwise no-one might notice. The buzzing issue is the only real, serious issue. Also, I know everyone loves X, but is it really the best choice for a low powered device that needs a responsive UI? Yes :) Any unresponsiveness in the UI is not because of the X. I think maybe I had the wrong impression about the state of the software when I bought it. Probably. It's not a phone product yet, it's a phone in development. From your point of view I can understand the frustration with the other issues, but for me they are just a few things to work on / test fixes. The buzzing / hw issue is really the only thing I'm worried about, since it needs to be fixed and there is no known software fix for it yet. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: (Debian) IceWm running!
Davide Scaini [EMAIL PROTECTED] writes: using xrandr i have a strange behaviour... after restoring previous orientation I have very big fonts... why? and how to fix that? It's a known bug. http://bugs.debian.org/xserver-xglamo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, Nov 17, 2008 at 5:52 AM, Timo Jyrinki [EMAIL PROTECTED]wrote: Coding is fun! That's why we have accelerometer-controlled Doom working fluently before phone calls, and I think it's great ;) I'm just starting my day here on the East coast of the U.S.. I'm confident what you just wrote will be the funniest thing I encounter all day. -Charles Pax ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] How to power off Wifi?
I guess that's right. I have similar readings myself. On Mon, Nov 17, 2008 at 3:57 PM, Matthias Apitz [EMAIL PROTECTED] wrote: El día Sunday, November 16, 2008 a las 01:49:57AM +0100, Minh Ha Duong escribió: Le samedi 15 novembre 2008, Matthias Apitz a écrit : I don't know if it reduces the drawing of power (btw: what is the easiest method to measure it? pulling out the battery and measure the power consumption via the cable?); I would use something like the attached battery.py script to measure power. Minh Thanks for this; I have had an older version without the detailed information about power drain and so; It is a bit tricky to use such a Python tool to measure things because it has to much effect in the power consumption by its own; maybe I will just collect in the future the data from the /sys/... files and draw the figured later based on them; for now I've tested it with your battery.py, here are the numbers: 181 mA -- nearly empty FR (only battery.py and Terminal running) 231 mA -- after launch of GPSD 183 mA -- after stop of GPSD 189-232 mA -- after Wifi-up with, running 'ping' through eth0 184-186 mA -- after Wifi-down For me this reads that the Wifi chip is already powered-up on boot; the diff between before (181) and after using it (184-186) is not very big; right? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Sun, Nov 16, 2008 at 4:34 PM, Andy Green [EMAIL PROTECTED] wrote: | FWIW I talked this over with an experienced 3D guy recently about | something related and he was all in favour of discarding the kdrive | implementation and making a pure xorg one as a way forward: he told that | kdrive itself was long dead. I also know that XGlamo is not that great | Just fair warning here. As I don't think OM will use the Glamo in | future devices, doing the right thing isn't as critical as normal | software projects. Spend the energy making the best performing, most | functional implementation possible. If that goal's met, *then* go | back and shove it into Xorg. We don't plan to use Glamo at the moment, but we do seem to be planning and are working twoards using xorg everywhere. It makes sense to have a consistent strategy for it across all the devices using the best solution. More developers are likely to want to expend effort to get experience with xorg / GLX type solution than known-deprecated kdrive / lashup implementation. If you look at GTA01 experience, that is still a living device running current rootfs, we can expect GTA02 to have similar long life, we should also make architectural decisions with that in mind I think. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkhT3MACgkQOjLpvpq7dMp8BACffuMTO4LWmoPpsIkqKoI4cCIO 35gAoICe9V8TsLesAtddradgxsOsrdsY =H9Ot -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
Le lundi 17 novembre 2008, kimaidou a écrit : About the buzzin issue, I would like to be sure : is it or is it not hardware related ? I heard about a soldering fix of one electronic component which could get rid of the interferences... Has anyone more information ? It is hardware related and discussed on the Hardware mailing list: http://lists.openmoko.org/pipermail/hardware/ Check September, October... it is about half of the traffic there. Minh -- Minh HA DUONG, Chargé de Recherche, CNRS CIRED, Centre International de Recherches sur l'Environnement et le Développement http://minh.haduong.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
2008/11/17 The Rasterman Carsten Haitzler [EMAIL PROTECTED] [...] this is the thing.. the drvier is ALREADY doing this. i repeat this ad-nauseum. the acceleration is the same u get in the nv driver or you saw a few years back in the i8xx drivers etc. you get blit and fill accelerated (the most common x ops). xvideo is accelerated. the only thing not is anti-aliases font drawing and as such the glamo doesnt support this fully - u need to do some hacks to pretend it will (like expand fonts to ARGB32 in software) and from the look of it the expansion and then upload of pixels will likely net you zero speedup as this extra cost will negate the speedups you get. imho glamo is right now about as fast as u'll ever likely see it (imho). you can go sink a mountain of work and as per the example above.. see no return. the ONLY thing that i can see it might be worth it is opengl - and even then its a very weak opengl accelerator with lots of gotchas. all of the above of course is in my opinion. it's based from years of doing graphics - software and hardware and with x, and having read all of the glamo docs. Hi Raster! before reading this post I supposed that 2d acceleration was very partially implemented. This cames out for example because I never see a smooth scroll on the device. So what is the reason for this? glamo? 2d acceleration driver? poor graphics toolkit? Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
How to use links-x11?
Hello! I'm using shr image, and I've installed links-x11 from http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/ But when I try to run it with links I get Illegal instruction all the time. Do I need to install something else? Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] How to power off Wifi?
Matthias Apitz wrote: for now I've tested it with your battery.py, here are the numbers: 181 mA -- nearly empty FR (only battery.py and Terminal running) 231 mA -- after launch of GPSD 183 mA -- after stop of GPSD 189-232 mA -- after Wifi-up with, running 'ping' through eth0 184-186 mA -- after Wifi-down For me this reads that the Wifi chip is already powered-up on boot; the diff between before (181) and after using it (184-186) is not very big; right? What do you mean for Wifi-down? Using ifconfig (ifdown) or using the wmiconfig tool? BTW the major wifi power consumption, if it has been turned on, happens while the phone is suspended. Sometimes I've left my phone in suspend with full battery and wifi on (I mean, after I disassociated it from an AP) and in few hours the battery was drained... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Will there be a hardware revision for the buzzing issue?
Hi all, I'm about to buy an openmoko, as I finally have some time and cash. However, my understanding is that the latest phones for sale have a buzzing issue and its confirmed to be hardware related. Will there be a hardware revision? Or I'm a stuck using a soldering iron and new parts to fix it? Please correct me if I'm misinformed. - R ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] How to power off Wifi?
El día Monday, November 17, 2008 a las 03:19:32PM +0100, Marco Trevisan (Treviño) escribió: Matthias Apitz wrote: for now I've tested it with your battery.py, here are the numbers: 181 mA -- nearly empty FR (only battery.py and Terminal running) 231 mA -- after launch of GPSD 183 mA -- after stop of GPSD 189-232 mA -- after Wifi-up with, running 'ping' through eth0 184-186 mA -- after Wifi-down For me this reads that the Wifi chip is already powered-up on boot; the diff between before (181) and after using it (184-186) is not very big; right? What do you mean for Wifi-down? Using ifconfig (ifdown) or using the wmiconfig tool? I don't use the 'wmiconfig tool'; I have two desktop application templates which toggle an desktop icon between UP and DOWN and in which a sequence of commands are fired up to bring Wifi UP or DOWN; this works *very* reliable in the sense of bringing Wifi UP or DOWN, associating, getting IP via DHCP and so on; BTW the major wifi power consumption, if it has been turned on, happens while the phone is suspended. Sometimes I've left my phone in suspend with full battery and wifi on (I mean, after I disassociated it from an AP) and in few hours the battery was drained... I can't comment on this because I don't use suspend mode; maybe one could measure the drain of power with a special USB cable while the battery is pulled out... matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ A computer is like an air conditioner, it stops working when you open Windows Una computadora es como aire acondicionado, deja de funcionar si abres Windows [Desktop Entry] Encoding=UTF-8 Name=WifiDisc Comment=Bring Wifi down with ifdown eth0 Exec=xterm -e ifdown eth0 ; sleep 5 ; cp /usr/share/applications/Wifi-up.desktop.tmpl /usr/share/applications/Wifi.desktop Icon=wifiOff Terminal=false Type=Application Categories=Application;Utilities; SingleInstance=true StartupNotify=true [Desktop Entry] Encoding=UTF-8 Name=WifiCon Comment=Bring Wifi up with ifup eth0 Exec=xterm -e ifdown eth0 ; iwconfig eth0 txpower auto channel 1 ; killall wpa_supplicant ; killall udhcp ; ifup eth0 ; sleep 20 ; cp /usr/share/applications/Wifi-down.desktop.tmpl /usr/share/applications/Wifi.desktop Icon=wifi Terminal=false Type=Application Categories=Application;Utilities; SingleInstance=true StartupNotify=true ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FDOM] Ye olde no sound after resume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I installed FDOM 20081023 but there is no sound. | | Any idea? If you are booting from Qi, you need a version from yesterday or later to get audio working. http://people.openmoko.org/andy has binaries for Qi and stable-tracking kernels. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkhgugACgkQOjLpvpq7dMrUQwCfQCKlwZDEL2/8AQnPG2WBS96i sAEAoJO08F3BWOUMVkELB8tGNgtfpMmN =IEFR -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GPRS Issues - Related to infamous 'buzz'?
I just had the same problem. I configured GPRS connection on QT Extended 4.4.2. And tried the connection - it worked without any problems. Then I disconnected from GPRS and about 10 minutes after that someone called me. When I answered the call a very loud sound started to play. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, 17 Nov 2008 14:30:31 +0100 Nicola Mfb [EMAIL PROTECTED] babbled: Hi Raster! before reading this post I supposed that 2d acceleration was very partially implemented. This cames out for example because I never see a smooth scroll on the device. So what is the reason for this? glamo? 2d acceleration driver? poor graphics toolkit? depends on the toolkit and how ti does it. efl doesn't use any blitting at all for scrolling. it's a redraw - thus a re-compute of pixels and write to screen. i won't go into the details why - but they are complex. glamo can't do enough to cover the accelerated paths (xrender for example) so you get s a software re-compute. no - it's not possible to do a scroll (via blit) as you have alpha channels, layered objects etc. etc. - just trust me in that the cost of trying to figure out a blit - if it is possible is probably much higher than the cost of just doing a redraw in almost all cases - the upload speed of the glamo is so low though that it may just be worth it... but i don't intend to bother as the glamo on the freerunner is a complete anomaly in terms of performance and i have other much better and more important platforms to support as well :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
So far, on the FR, I remain to be convinced that the use of X is the critical performance issue. In any event, the main issue with optimization efforts is whether they can proceed faster than the introduction of better hardware. If a 400 Mhz machine is too slow, will a 1 Ghz machine be fast enough? Will anything be fast enough? Apparently, from the history of desktops, the answer is no! My own experiments with the FR lead me to believe that memory access and peripheral access are more significant than X performance, but I have yet to do the tests and the math. Carsten Haitzler (The Rasterman) wrote: On Mon, 17 Nov 2008 13:54:55 +0800 John Lee [EMAIL PROTECTED] babbled: On Sun, Nov 16, 2008 at 10:05:16AM +1100, Carsten Haitzler wrote: x's internals are definitely up for improvement - callium3d is there to try and fix this by providing a better more organised and better accelerated driver layer - but again - they aren't going to replace x... just clean up internals. what it means is - the rest of us can continue happily writing x apps and just wait for an improvement to pop out the pipeline. indeed x's internal acceleration layer could be improved. it has in the past (especially with xaa) proved an impediment if you have to code AT the driver layer. as such - x was originally designs (as a system - not specifically the xorg tree etc.) to allow full freedom to implement the internals of x any way you like - so as such if you wanted to spend the effort x could accelerate just about everything as long as hardware can do it, somehow - but the points at which that acceleration knowledge need to go into might be much higher up than xaa/exa. you'd have to write a forked x with all sorts of hooks higher up. - but it's possible... and then x client work as they always did - and get more use of the hardware :) MicroXwin ? http://www.microxwin.com/ MicroXwin is binary compatible to the Xlib API. However it is niether client server nor network oriented. Graphics operations are implemented in the linux kernel via a kernel module. An open source Xlib library sends graphics commands to the kernel. There is no network overhead and no context switch from X client to X server. This makes our solution smaller and faster than traditional X Windows. as such - context switching doesn't happen as often as people think.. if you write good x code - its' buffered. but as such this is an interesting solution - that is linux specific. not sure if it handles everything (window management, and not to mention enough of the modern extensions), but for gta03 (as this is framebuffer based) this could be a definite option. i'd say it'd be worth exploring. keeps compatibility AND should give you some speedup. not sure just how much day to day though. but the license seems... opaque - no idea what it is but it looks closed. but as such this would be another valid way of doing things with x. as such x apps just should avoid round-trip calls to x, so while they run they can do all their gfx ops WITHOUT a single round trip (thus no cache flush) and they only flush on final draw of everything - so just once per frame really (for the app). -- Iain B. Findleton Tel: 514-457-0744 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
On Mon, Nov 17, 2008 at 7:46 AM, kimaidou [EMAIL PROTECTED] wrote: Ok thanks, I have just read the hundreds if topics on it... the problem is I am no electronicien so I did not understand if a workaround has been found : I read about soldering, sticky tape. If there is a workaround, is there a webpage with clear instructions ? (by clear I mean for non-elecronician guy). Is it doable by a anybody or do we need special devices/skills It does require special skills and tools. If the posts in the hardware list were not enough for you to see the fix then you shouldn't attempt it. Angus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
It does require special skills and tools. If the posts in the hardware list were not enough for you to see the fix then you shouldn't attempt it. Angus Hum Sorry to ask again, but.. A solution has been found ? Or this solderings and pin things are for tests purposes only ? If the solution is ok, * I know some electronician guys, but they would need proper schemes (not pictures). * or I can send back my FR and try to ask my provider to repair it ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Qt extended] Default input method
Does someone know if there's a way to set the default input method? I really can't use handwriting and I really like the predictive keyboard, is it necessary to select my favourite input method everytime qtextended starts? -- View this message in context: http://n2.nabble.com/-Qt-extended--Default-input-method-tp1510183p1510183.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
What theme is this?
Hi! I found this image on scap.linuxtogo.org http://scap.linuxtogo.org/files/cb247f8d70308d5fec6a479c329e75f3.png There are also some other themes. Where I can download it? Who is making it? Thanks. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Host resolving errors during opkg install
HI there, trying to download packages during opkg install curently fails on my newly installed FR. opkg update works fine, but then, I get [EMAIL PROTECTED]:~# opkg install classpath Installing classpath (0.97.2-r4) to root... Downloading http://downloads.openmoko.org/repository/testing/armv4t/classpath_0.97.2-r4_armv4t.opk Collected errors: * Failed to download http://downloads.openmoko.org/repository/testing/armv4t/classpath_0.97.2-r4_armv4t.opk, error 0 * Failed to download classpath. Perhaps you need to run 'opkg update'? [EMAIL PROTECTED]:~# wget http://downloads.openmoko.org/repository/testing/armv4t/c lasspath_0.97.2-r4_armv4t.opk wget: bad address 'downloads.openmoko.org' [EMAIL PROTECTED]:~# ping download.openmoko.org ping: bad address 'download.openmoko.org' [EMAIL PROTECTED]:~# ping www.kth.se PING www.kth.se (130.237.32.143): 56 data bytes 64 bytes from 130.237.32.143: seq=0 ttl=56 time=13.965 ms 64 bytes from 130.237.32.143: seq=1 ttl=56 time=13.513 ms --- www.kth.se ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 13.513/13.739/13.965 ms So, ping does not work, wget does not work, but to other hosts things seems to be better. Any hints? Cheers /peter http://www.oredev.se - Be there or be gone. GTalk:neubauer.peter Skypepeter.neubauer ICQ18762544 Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org- New Energy for Java - Domain Driven Development. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
I have implemented an image display script on the FR that demonstrates smooth scroll in the form of dragging the image about the screen. Works for fairly large images (colour weather maps of North America). The application uses the FLTK tool kit with double buffering through X. Nicola Mfb wrote: 2008/11/17 The Rasterman Carsten Haitzler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [...] this is the thing.. the drvier is ALREADY doing this. i repeat this ad-nauseum. the acceleration is the same u get in the nv driver or you saw a few years back in the i8xx drivers etc. you get blit and fill accelerated (the most common x ops). xvideo is accelerated. the only thing not is anti-aliases font drawing and as such the glamo doesnt support this fully - u need to do some hacks to pretend it will (like expand fonts to ARGB32 in software) and from the look of it the expansion and then upload of pixels will likely net you zero speedup as this extra cost will negate the speedups you get. imho glamo is right now about as fast as u'll ever likely see it (imho). you can go sink a mountain of work and as per the example above.. see no return. the ONLY thing that i can see it might be worth it is opengl - and even then its a very weak opengl accelerator with lots of gotchas. all of the above of course is in my opinion. it's based from years of doing graphics - software and hardware and with x, and having read all of the glamo docs. Hi Raster! before reading this post I supposed that 2d acceleration was very partially implemented. This cames out for example because I never see a smooth scroll on the device. So what is the reason for this? glamo? 2d acceleration driver? poor graphics toolkit? Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Iain B. Findleton Tel: 514-457-0744 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Toolchain opkg postinst Error
Hi, my qt4 Libs are not installed correctly in toolchain since the update of the angström Repository, when I try to reinstall them I get the following error [EMAIL PROTECTED]:/usr/local/openmoko/arm/bin# opkg-target -force-reinstall install libqtcore4 Reinstalling libqtcore4 (4.4.3-r1.1) on root... Downloading http://www.angstrom- distribution.org/feeds/2008/ipk/glibc/armv4t/base/libqtcore4_4.4.3- r1.1_armv4t.ipk Configuring libqtcore4 (offline root mode: not running libqtcore4.postinst) [EMAIL PROTECTED]:/usr/local/openmoko/arm/bin# Any idea what this error message means? Greets Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What theme is this?
Leonti Bielski wrote: Hi! I found this image on scap.linuxtogo.org http://scap.linuxtogo.org/files/cb247f8d70308d5fec6a479c329e75f3.png There are also some other themes. Where I can download it? Who is making it? Thanks. Leonti I agree it looks nice. And as we are on this topic. I think this theme http://scap.linuxtogo.org/files/4dc340d6661464ca15a0789011cdd3c6.png is ingenious! I never liked the grey theme. Bright colours on black are the way to go. -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
If we work on having x.org server working on the FR, wouldn't that help for whatever comes next?. At least we would have some working knowledge on how to develop drivers for X, and a team of programmers with ample knowledge on all things regarding the x.org Server. I mean, the thing is modularized. Is it not simpler to just replace the glamo driver with the [whatever\] driver? On Mon, Nov 17, 2008 at 11:48 AM, Iain B. Findleton [EMAIL PROTECTED] wrote: I have implemented an image display script on the FR that demonstrates smooth scroll in the form of dragging the image about the screen. Works for fairly large images (colour weather maps of North America). The application uses the FLTK tool kit with double buffering through X. Nicola Mfb wrote: 2008/11/17 The Rasterman Carsten Haitzler [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [...] this is the thing.. the drvier is ALREADY doing this. i repeat this ad-nauseum. the acceleration is the same u get in the nv driver or you saw a few years back in the i8xx drivers etc. you get blit and fill accelerated (the most common x ops). xvideo is accelerated. the only thing not is anti-aliases font drawing and as such the glamo doesnt support this fully - u need to do some hacks to pretend it will (like expand fonts to ARGB32 in software) and from the look of it the expansion and then upload of pixels will likely net you zero speedup as this extra cost will negate the speedups you get. imho glamo is right now about as fast as u'll ever likely see it (imho). you can go sink a mountain of work and as per the example above.. see no return. the ONLY thing that i can see it might be worth it is opengl - and even then its a very weak opengl accelerator with lots of gotchas. all of the above of course is in my opinion. it's based from years of doing graphics - software and hardware and with x, and having read all of the glamo docs. Hi Raster! before reading this post I supposed that 2d acceleration was very partially implemented. This cames out for example because I never see a smooth scroll on the device. So what is the reason for this? glamo? 2d acceleration driver? poor graphics toolkit? Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Iain B. Findleton Tel: 514-457-0744 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
fennec -force-depends doesn't help
Hi! I'm trying to install fennec on my beloved Neo. I have added angstrom-distribution.org feed and try to do opkg install fennec It give me gtk eror similar to this one http://lists.openmoko.org/pipermail/device-owners/2007-November/000759.html So I tried 'opkg install fennec -force-depends' but it gives me the same error. Isn't -force-depends supposed to solve this kind of problems? Thanks. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Host resolving errors during opkg install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 17 Nov 2008 17:45:45 +0100 Peter Neubauer [EMAIL PROTECTED] mentioned: HI there, trying to download packages during opkg install curently fails on my newly installed FR. opkg update works fine, but then, I get [EMAIL PROTECTED]:~# opkg install classpath Installing classpath (0.97.2-r4) to root... Downloading http://downloads.openmoko.org/repository/testing/armv4t/classpath_0.97.2-r4_armv4t.opk Collected errors: * Failed to download http://downloads.openmoko.org/repository/testing/armv4t/classpath_0.97.2-r4_armv4t.opk, error 0 * Failed to download classpath. Perhaps you need to run 'opkg update'? [EMAIL PROTECTED]:~# wget http://downloads.openmoko.org/repository/testing/armv4t/c lasspath_0.97.2-r4_armv4t.opk wget: bad address 'downloads.openmoko.org' [EMAIL PROTECTED]:~# ping download.openmoko.org ping: bad address 'download.openmoko.org' [EMAIL PROTECTED]:~# ping www.kth.se PING www.kth.se (130.237.32.143): 56 data bytes 64 bytes from 130.237.32.143: seq=0 ttl=56 time=13.965 ms 64 bytes from 130.237.32.143: seq=1 ttl=56 time=13.513 ms --- www.kth.se ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 13.513/13.739/13.965 ms I think the host should be downloads.openmoko.org, not *download*. - -- Stanislav Sedov ST4096-RIPE -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkho5oACgkQK/VZk+smlYHgOwCfSn5ZS7IafyhVaSNawKpRm/Z2 IiYAn0yepuEDyPe+nOGBZiv7EhGfNkfq =9hSg -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, 2008-11-17 at 11:58 -0500, Aliner wrote: If we work on having x.org server working on the FR, wouldn't that help for whatever comes next?. At least we would have some working knowledge on how to develop drivers for X, and a team of programmers with ample knowledge on all things regarding the x.org Server. I mean, the thing is modularized. Is it not simpler to just replace the glamo driver with the [whatever\] driver? Basically yes, the advantages of Xorg are active development and familiarity with developers as comapred to kdrive based stuff. At the moment Xorg with tslib/fbdev drivers works well on GTA02 my task now is to make a glamo driver for Xorg based on the Xglamo code. Graeme ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, Nov 17, 2008 at 12:06 PM, Graeme Gregory [EMAIL PROTECTED]wrote: On Mon, 2008-11-17 at 11:58 -0500, Aliner wrote: If we work on having x.org server working on the FR, wouldn't that help for whatever comes next?. At least we would have some working knowledge on how to develop drivers for X, and a team of programmers with ample knowledge on all things regarding the x.org Server. I mean, the thing is modularized. Is it not simpler to just replace the glamo driver with the [whatever\] driver? Basically yes, the advantages of Xorg are active development and familiarity with developers as comapred to kdrive based stuff. At the moment Xorg with tslib/fbdev drivers works well on GTA02 my task now is to make a glamo driver for Xorg based on the Xglamo code. Do you have the instructions to build Xorg with the toolchain? Graeme ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, 2008-11-17 at 12:12 -0500, Aliner wrote: On Mon, Nov 17, 2008 at 12:06 PM, Graeme Gregory [EMAIL PROTECTED] wrote: On Mon, 2008-11-17 at 11:58 -0500, Aliner wrote: If we work on having x.org server working on the FR, wouldn't that help for whatever comes next?. At least we would have some working knowledge on how to develop drivers for X, and a team of programmers with ample knowledge on all things regarding the x.org Server. I mean, the thing is modularized. Is it not simpler to just replace the glamo driver with the [whatever\] driver? Basically yes, the advantages of Xorg are active development and familiarity with developers as comapred to kdrive based stuff. At the moment Xorg with tslib/fbdev drivers works well on GTA02 my task now is to make a glamo driver for Xorg based on the Xglamo code. Do you have the instructions to build Xorg with the toolchain? No, Im an OE guy so I use OE as my toolchain. Graeme ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Mon, Nov 17, 2008 at 6:12 PM, Aliner [EMAIL PROTECTED] wrote: On Mon, Nov 17, 2008 at 12:06 PM, Graeme Gregory [EMAIL PROTECTED]wrote: On Mon, 2008-11-17 at 11:58 -0500, Aliner wrote: If we work on having x.org server working on the FR, wouldn't that help for whatever comes next?. At least we would have some working knowledge on how to develop drivers for X, and a team of programmers with ample knowledge on all things regarding the x.org Server. I mean, the thing is modularized. Is it not simpler to just replace the glamo driver with the [whatever\] driver? Basically yes, the advantages of Xorg are active development and familiarity with developers as comapred to kdrive based stuff. At the moment Xorg with tslib/fbdev drivers works well on GTA02 my task now is to make a glamo driver for Xorg based on the Xglamo code. Do you have the instructions to build Xorg with the toolchain? Graeme ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community I thought Debian on the FR started with X by default? Testing that would give you a quick comparison if you didn't feel like building X. Also, kdrive is part of Xorg now, so you just simply pass it the --enable-kdrive flag at compile time according to information at freedesktop.org [1]. -Jacob [1] http://www.freedesktop.org/wiki/Software/Xserver ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[2008.x] Settings app not working
November 1st I upgraded from 2008.9 stable to 2008.x testing, using opkg update opkg upgrade. This broke the settings applications which no longer starts. I have just now updated and upgraded again to see if there would be a fix in the repository without any luck. I have also searched google and the mailing lists without finding anything relevant. This is the bug #2088 ( http://docs.openmoko.org/trac/ticket/2088 ), in which I have also pasted the backtrace. Apparently the bug has been resolved, but I can not find out how to apply this fix. The backtrace is: [EMAIL PROTECTED]:~# exposure.py -f run Traceback (most recent call last): File /usr/bin/exposure.py, line 304, in module import etk File /usr/lib/python2.5/site-packages/etk/__init__.py, line 1, in module from core import * File /usr/lib/python2.5/site-packages/etk/core.py, line 1, in module import c_etk ImportError: /usr/lib/python2.5/site-packages/etk/c_etk.so: undefined symbol: evas_list_append Does anybody know how to fix this? Am I the only one getting this error? It seems I have some incompatible packages. How can I find out which ones? Any help would be greatly appreciated. Kind Regards, pooze! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fennec -force-depends doesn't help
Hi Leonti, To get this to work, you will need to do a: opkg install gtk+ -force-overwrite Depending on the distro that you are using, you may experience some glitching in graphics after the install. I have installed fennec before and it is unbearably slow but there may have been updates recently that improve performance. Cheers, Andrew Leonti Bielski wrote: Hi! I'm trying to install fennec on my beloved Neo. I have added angstrom-distribution.org feed and try to do opkg install fennec It give me gtk eror similar to this one http://lists.openmoko.org/pipermail/device-owners/2007-November/000759.html So I tried 'opkg install fennec -force-depends' but it gives me the same error. Isn't -force-depends supposed to solve this kind of problems? Thanks. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Will there be a hardware revision for the buzzing issue?
Hello! Yes, this is hardware issue, and it's fixable. Right now openmoko folks are testing the solution which fixes this issue. As far as I understood it will make it to new hardware revision, but it's going to take a while - they have to test it first to be sure it's not causing new problems. But it doesn't mean if you buy your phone now it will have this problem - it depends a lot on operator, frequency and other stuff - some people have it, some just reading mailing lists and wondering what is this buzzing issue :) But in your place I would wait a little to don't have to solder it yourself. Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
Iain B. Findleton wrote: the main issue with optimization efforts is whether they can proceed faster than the introduction of better hardware. If a 400 Mhz machine is too slow, will a 1 Ghz machine be fast enough? Will anything be fast enough? Apparently, from the history of desktops, the answer is no! Having seen the way the device responds under android compared to the way it responds under OM2008, I'd say they have a way to go on current hardware. I guess I'll try OM2008.11 at some point and see if that's caught up. -- View this message in context: http://n2.nabble.com/The-forbidden-topic%3A-Glamo-OpenGL-tp1495995p1510628.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Qt extended] Default input method
Dareus wrote: Does someone know if there's a way to set the default input method? I really can't use handwriting and I really like the predictive keyboard, is it necessary to select my favourite input method everytime qtextended starts? theoretically, it already has a default keyboard, which is already set to the predictive keyboard. Known bug. You can delete the handwriting plugin: /opt/Trolltech/Qtopia/plugins/inputmethods/libpkim.so -- Lorn 'ljp' Potter Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The forbidden topic: Glamo OpenGL
Minh Ha Duong [EMAIL PROTECTED] writes: I hope the software stack becomes less of a joke in time for GTA03 or it'll be hard to get much new customers... Actually I have never read any jokes about the software stack. But it is a sign of good mental health when a community is able to make fun of itself. Besides, where else would one share jokes about Openmoko ? Open fire ! Ok I will bite :) Q: Why did OM cross the road? A: To get to another toolkit :) Q: How many OM devs does it take to change a lightbulb? A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :) Please not this is not a cue for a thread on lightbulb analogies :) Q: What is the difference between a professional photographer and OM user? A: The OM user has to flash more often :) Q: Why did the OM newbie log onto #openmoko? A: Because they had not read: a) the wiki and b) the topic As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin. I will be here all week, try the salad :) Regards (apologies for posting via gmane moving e-mail around) Tig ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What theme is this?
Tilman Baumann wrote: Leonti Bielski wrote: Hi! I found this image on scap.linuxtogo.org http://scap.linuxtogo.org/files/cb247f8d70308d5fec6a479c329e75f3.png There are also some other themes. Where I can download it? Who is making it? Thanks. Leonti I agree it looks nice. And as we are on this topic. I think this theme http://scap.linuxtogo.org/files/4dc340d6661464ca15a0789011cdd3c6.png is ingenious! I never liked the grey theme. Bright colours on black are the way to go. Of course it's a matter of taste. But I also like the black and white theme much more that the colourful theme. They give me a more professional feeling. I'm also interested in where it can be downloaded. Regards, Joop. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What theme is this?
I think hire did create the colorful theme. You should be able to catch him in #openmoko-cdevel Richard ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian on neo1973: ogpsd failing?
Daniel I tried this, but now I get no fix. gpspipe -r prints out a dump with no coordinates. The fso(?) gps gui shows no coordinates and tangogps doesn't have coordinates. gllin is not started automatically, but if I do start it manually with /etc/init.d/gllin start, it runs but nothing changes. I'm not sure how to test to see where things are breaking. gllin doesn't have the /tmp/nmeaNP stuff now, so I'm not sure how to check to see if gllin sees a fix. Is this version using a using a tcp port? Brad This will not survive suspend, though. Better to install gllin version 1.1 (if you have /tmp/nmeaNP you are still using version 1.0), available at http://3rdparty.downloads.openmoko.org/gllin/download/gllin_1.1+r931-r0_om-gta01.ipk (click-through license). Then change frameworkd.conf to read: [ogpsd] device = NMEADevice channel = GllinChannel path = /etc/init.d/gllin -- Brad Midgley ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android open sourced
A new rootfs has been released. http://people.openmoko.org/sean_mcneil/ -- View this message in context: http://n2.nabble.com/Android-open-sourced-tp1359949p1511876.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Sean Moss-Pultz @ BALUG Tomorrow
Hi Folks: Just a quick note to let the OpenMoko community know that Sean Moss-Pultz will be speaking at BALUG tomorrow night in San Francisco. We're expecting a great crowd, so if you'd like to join us please RSVP: RSVP at balug.org **Why RSVP??** Well, don't worry we won't turn you away, but the RSVPs really help the Four Seas Restaurant plan the meal and they ensure that we're able to eat upstairs in the private banquet room. Meeting Details... 6:30pm November 18th, 2008 (Tomorrow) Four Seas Restaurant 731 Grant Ave. San Francisco, CA 94108 Easy $5 PARKING: Portsmouth Square Garage at 733 Kearny Cost: The meetings are always free, but dinner is $13 -- Andrew Fife Untangle - The Open Source Network Gateway www.untangle.com/download 650.425.3327 desk 415.806.6028 cell ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android open sourced
anyone knows where is the changelog for this new image? i couldn't find it anywhere. abatrour escribió: A new rootfs has been released. http://people.openmoko.org/sean_mcneil/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android open sourced
Hi, I flashed this new image and it doesn't boot anymore. Tried with the same SD card as before, deleted the old files from the ext3 partition, and nothing. All I see is a black screen. On Tue, Nov 18, 2008 at 12:47 AM, Tomas Riveros Schober [EMAIL PROTECTED]wrote: anyone knows where is the changelog for this new image? i couldn't find it anywhere. abatrour escribió: A new rootfs has been released. http://people.openmoko.org/sean_mcneil/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fennec -force-depends doesn't help
Leonti Bielski wrote: Hi! I'm trying to install fennec on my beloved Neo. I have added angstrom-distribution.org feed and try to do opkg install fennec It give me gtk eror similar to this one http://lists.openmoko.org/pipermail/device-owners/2007-November/000759.html Download the ipk file, extract it somewhere with dpkg -x fennec*.ipk .; then copy your ./usr/lib/fennec to the phone and run it from there... This works without any opkg trick... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.x] Settings app not working
On Tuesday 18 November 2008 01:40:42 Ivar Mossin wrote: November 1st I upgraded from 2008.9 stable to 2008.x testing, using opkg update opkg upgrade. This broke the settings applications which no longer starts. I have just now updated and upgraded again to see if there would be a fix in the repository without any luck. May be the upgrade path is broken ? Did you try to install the latest testing image ? If that does not help we can reopen the bug ... Marek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android open sourced
I flashed this new image and it doesn't boot anymore. Tried with the same SD card as before, deleted the old files from the ext3 partition, and nothing. All I see is a black screen. the same for me. the partition get's mounted and some data written on it but the screen stays black... i get ping responses. -- Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Android open sourced
On Tue, 18 Nov 2008 06:35:27 +0100 Petr Vanek [EMAIL PROTECTED] (PV) wrote: I flashed this new image and it doesn't boot anymore. Tried with the same SD card as before, deleted the old files from the ext3 partition, and nothing. All I see is a black screen. the same for me. the partition get's mounted and some data written on it but the screen stays black... i get ping responses. the image is gone from the url now. i guess some rework is being done. Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
MP2/MP3-free image based on Om2008.9
Dear Community; We are glad to announce that we have a mp3-free image based on Om2008.9 in place. The link to this image is http://downloads.openmoko.org/releases/Om2008.9/ . Again, any thoughts and feedbacks are welcome and appreciated. Thank you all and Best Regards. Ray Chao Openmoko System Admim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
