Re: WLAN: known issues and how to help

2008-12-01 Thread Werner Almesberger
Philip Rhoades wrote: > out a few days ago. The first attempt only lasted a few hours but the > most recent one lasted 16.5 hours before I had to stop it! Is SHR an > older OS but more worked on ie less bugs? Interesting ! I don't know if SHR is doing anything differently or if this was just

Re: WLAN: known issues and how to help

2008-12-01 Thread Werner Almesberger
Stefan Monnier wrote: > just keeps returning the same old data. To some extent, it seems the > rest is still usable (e.g. if I go back to where that list was valid, > wpa-supplicant seems to be able to associate with my network again, You mean that you can re-associate with the original AP but wi

Re: WLAN: known issues and how to help

2008-12-01 Thread Philip Rhoades
Werner, I have been testing nearly all the distributions and have never been able to keep a WLAN connection going for more than 5.5 hours (just a simple script pinging every two minutes). I had not looked at SHR before because I thought it might not suit me but I decided to try it out a few d

Re: Openmoko Bug #2146: Freerunner will not charge when booted from USB (git andy-tracking)

2008-12-01 Thread Openmoko Public Trac
#2146: Freerunner will not charge when booted from USB (git andy-tracking) --+- Reporter: nicolas.dufresne | Owner: openmoko-devel Type: defect| Status: new Priority: normal

Re: Openmoko Bug #2146: Freerunner will not charge when booted from USB (git andy-tracking)

2008-12-01 Thread Openmoko Public Trac
#2146: Freerunner will not charge when booted from USB (git andy-tracking) --+- Reporter: nicolas.dufresne | Owner: openmoko-devel Type: defect| Status: new Priority: normal

Re: Openmoko Bug #2146: Freerunner will not charge when booted from USB (git andy-tracking)

2008-12-01 Thread Openmoko Public Trac
#2146: Freerunner will not charge when booted from USB (git andy-tracking) --+- Reporter: nicolas.dufresne | Owner: openmoko-devel Type: defect| Status: new Priority: normal

Re: Openmoko Bug #1841: white screen of death (WSOD) after resume

2008-12-01 Thread Openmoko Public Trac
#1841: white screen of death (WSOD) after resume ---+ Reporter: Rorschach | Owner: openmoko-devel Type: defect | Status: new Priority: highest| Milestone: Co

Community update, Dec. 1st, 2008

2008-12-01 Thread Minh Ha Duong
Dear friends, Good evening/day/afternoon (whatever your TZ is). This is our sixth "community community update". Congratulations to Valério, he won the first 24h-coding prize at Sapo Codebits by turning freerunner in a mouse and gamepad using the accelerometers. Code will be merged with ReMoko.

Re: WLAN: known issues and how to help

2008-12-01 Thread Stefan Monnier
> #1929 WLAN gets stuck after a while with ar6000_ioctl_giwscan() > complaining (= #1285 ?) I'm not sure if that's the one, but I consistently have to reboot my FR in order to associate to a new network: after a while, "iwlist scan" just keeps returning the same old data. To some extent

Re: "X--tag=CC: command not found"

2008-12-01 Thread Joseph Reeves
Many thanks Ludwig, that worked as planned :-) Joseph 2008/12/1 Ludwig <[EMAIL PROTECTED]>: > > I have just run into the same issue on Ubuntu 8.10 > > It seems to be that 8.10 has an incompatible version of libtools (i.e > version 2.24), while the scripts work only with 1.5 (or so). > > I got f

Re: "X--tag=CC: command not found"

2008-12-01 Thread Ludwig
I have just run into the same issue on Ubuntu 8.10 It seems to be that 8.10 has an incompatible version of libtools (i.e version 2.24), while the scripts work only with 1.5 (or so). I got further by uninstalling libtool 2, then installing libtool 1.5.26: sudo apt-get remove libtool wget http:/

Re: Openmoko Bug #2148: [2009.11 testing] Settings application fails to open

2008-12-01 Thread Openmoko Public Trac
#2148: [2009.11 testing] Settings application fails to open -+-- Reporter: iknowjoseph | Owner: openmoko-devel Type: defect | Status: new Priority: normal | Milestone:

Re: GL|ES Mesa and DRI

2008-12-01 Thread Andreas Pokorny
Hi, 2008/12/1 Thomas White <[EMAIL PROTECTED]>: > Absolutely. In fact, I don't see any reason not to go the "whole hog" > and use the DRI infrastructure proper, which should make this a lot > easier. Yesterday I started looking at and building the generic drm code, to understand what it does, an

Re: Openmoko Bug #2148: [2009.11 testing] Settings application fails to open

2008-12-01 Thread Openmoko Public Trac
#2148: [2009.11 testing] Settings application fails to open -+-- Reporter: iknowjoseph | Owner: openmoko-devel Type: defect | Status: new Priority: normal | Milestone:

Re: Openmoko Bug #2148: [2009.11 testing] Settings application fails to open

2008-12-01 Thread Openmoko Public Trac
#2148: [2009.11 testing] Settings application fails to open -+-- Reporter: iknowjoseph | Owner: openmoko-devel Type: defect | Status: new Priority: normal | Milestone:

Openmoko Bug #2148: [2009.11 testing] Settings application fails to open

2008-12-01 Thread Openmoko Public Trac
#2148: [2009.11 testing] Settings application fails to open -+-- Reporter: iknowjoseph | Owner: openmoko-devel Type: defect | Status: new Priority: normal | Milestone:

Re: Openmoko Bug #2146: Freerunner will not charge when booted from USB (git andy-tracking)

2008-12-01 Thread Openmoko Public Trac
#2146: Freerunner will not charge when booted from USB (git andy-tracking) --+- Reporter: nicolas.dufresne | Owner: openmoko-devel Type: defect| Status: new Priority: normal

Re: GL|ES Mesa and DRI

2008-12-01 Thread Thomas White
"Andreas Pokorny" <[EMAIL PROTECTED]> wrote: > Please correct me if I am going into the wrong direction. I believe > we need a DRM like kernel module that manages memory and rendering > states and handles context switches Absolutely. In fact, I don't see any reason not to go the "whole hog" and

Re: Openmoko Bug #2146: Freerunner will not charge when booted from USB (git andy-tracking)

2008-12-01 Thread Openmoko Public Trac
#2146: Freerunner will not charge when booted from USB (git andy-tracking) --+- Reporter: nicolas.dufresne | Owner: openmoko-devel Type: defect| Status: new Priority: normal