On Wed, Feb 4, 2009 at 5:18 AM, Sven Rebhan wrote:
> 2009/2/4 Christopher Friedt :
> Then may I suggest to use Gentoo on the phone!? ;-)
>
> http://overlays.gentoo.org/proj/embedded/browser
> http://gentoo.mindzoo.de/
>
> We are currently working on testing the framework stuff, but cross-compilin
Is this perhaps because the repository is being updated at the same
time, or is there actually a corrupt kernel repository?
$ git clone git://git.openmoko.org/git/kernel.git linux-2.6
Initialized empty Git repository in
/home/cfriedt/openmoko/kernel/linux-2.6/.git/
remote: Generating pack...
remot
Werner,
Werner Almesberger wrote:
> Philip Rhoades wrote:
>> Still using:
>>
>> wlan-trial-20090206.jffs2
>
> If you could give your regular rootfs a try with my kernel, that
> would be great. What I'm interested in now is to confirm if the
> communication breakdown is caused by the assertion.
Marcelo wrote:
> Looking at the diagram "glamo_dri.so" caught my eye. Googling I found
> there's in fact a glamo_dri.c in the Mesa tree. What's the status of
> that? What are the implemented capabilities?
Sounds like you came across the skeleton driver I put there. If that's the
case, it's j
Lars-Peter Clausen writes:
> Could you please try the latest commit. Maybe theres still something
> missing, but at least the system should not crash after suspend, but
> you might get a flickering display.
I also get odd visual artifacts:
http://iki.fi/lindi/openmoko/xf86-video-glamo1.png
___
Hi Mirko,
> we have a bit of a discussion on how to handle an fso crash while paroli
> is running and wanted to put it out there to get your input and ideas.
>
> Quoting:
> > ticket 13 needs testing (what happens if framework crashes during
>
> paroli use, how can we show it to the user? )
The
Lars-Peter Clausen writes:
> Could you please try the latest commit. Maybe theres still something
> missing, but at least the system should not crash after suspend, but
> you might get a flickering display.
commit 8062d7aa7bac7e06c1a00bd88ca78098550606ed
Author: Lars-Peter Clausen
Date: Mon Fe
Philip Rhoades wrote:
> Still using:
>
> wlan-trial-20090206.jffs2
If you could give your regular rootfs a try with my kernel, that
would be great. What I'm interested in now is to confirm if the
communication breakdown is caused by the assertion.
For debugging why my rootfs doesn't work for yo
On Monday 09 February 2009, Daniel Spies wrote:
> Hi,
>
> I am a little bit confused about the FSO distibution. I am trying to
> compile testing branch since January without success. First I got the weird
> localization issue and now other build errors. As far as I could see it
> from bugzilla the
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
On Sun, Feb 8, 2009 at 6:37 PM, Thomas White wrote:
> I hope that's helpful to someone. I'm acutely aware of the steep learning
> curve with this stuff, so I thought I'd help in any way possible.
Looking at the diagram "glamo_dri.so" caught my eye. Googling I found
there's in fact a glamo_dri.
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
Werner,
Werner Almesberger wrote:
> Philip Rhoades wrote:
>> regulator : Unable to get requested regulator
>> SO_3V3sc2440-sdi SO_3V3sc2440-sdi : Regulator for SO_3V3 unavailable
>
> That's expected and harmless.
>
>> Cannot create link /etc/mtab~
>> Perhaps there is a stale lock file?
Hi,
I am a little bit confused about the FSO distibution. I am trying to
compile testing branch since January without success. First I got the weird
localization issue and now other build errors. As far as I could see it
from bugzilla the issues are known and also the build logs on [1] are
failin
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
Lars-Peter Clausen writes:
> Which kernel are you using? With OM2008.9 suspend/resume while having
> a Xorg server running works fine for me.
b8b36e5ec3db71d5 from andy-tracking branch (Jan 7 I think).
___
devel mailing list
devel@lists.openmoko.org
ht
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo Juhani Lindfors wrote:
> Lars-Peter Clausen writes:
>> I havn't looked at suspend/resume yet but once the cmdq has moved
>> to the kernel we should be able to resolve this properly. The
>> Xglamo handles the cmdq differently and very inefficient
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
#2230: Git clone on "kernel.git linux-2.6" fails
-+--
Reporter: doxy2| Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Componen
Mike (mwester) wrote:
> Also, it might be
> that Werner's image assumes that the rootfs is mounted "rw" by the
> kernel; check the uboot boot command options to see if it specified "ro"
> instead.
Naw, I do a remount -n right at the beginning. (Just tested it and
it still works as it should.)
But
Lars-Peter Clausen wrote:
> Thomas, I think it's best if you continue your dri aware version of
> the driver as a branch in [2].
Yep. My dri-aware branch is now available on git.openmoko.org, so
xf86-video-glamo on git.bitwiz.org can now be considered obsolete.
I think my kernel and Mesa stuff
Philip Rhoades wrote:
> regulator : Unable to get requested regulator
> SO_3V3sc2440-sdi SO_3V3sc2440-sdi : Regulator for SO_3V3 unavailable
That's expected and harmless.
> Cannot create link /etc/mtab~
> Perhaps there is a stale lock file?
Hmm, getting weirder and weirder :-(
Which roo
Mike,
Mike (mwester) wrote:
> Philip Rhoades wrote:
> ...
>> before typing "boot" but then I got (it is hard to read):
>>
>>regulator : Unable to get requested regulator
>>SO_3V3sc2440-sdi SO_3V3sc2440-sdi : Regulator for SO_3V3 unavailable
>>Cannot create link /etc/mtab~
>>Perhap
Hi,
we have a bit of a discussion on how to handle an fso crash while paroli
is running and wanted to put it out there to get your input and ideas.
Quoting:
> ticket 13 needs testing (what happens if framework crashes during
paroli use, how can we show it to the user? )
As I wrote in the ti
27 matches
Mail list logo
