-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I'm just adding some patches and doing some cleaning on it, I'll update
| the moredrivers kernels at http://people.openmoko.org/andy when I
| checked we didn't break the threshold stuff.
|
| Thanks, in the
QI
Make sure you have the rw in there, and the /boot/append-GTA02 is in
the partition with the rootfs. Try adding a space before the rw in case
I mangled it with recent changes.
It's a bug I think if the rootfs does not remount root rw.
the same failed to set owner root for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| QI
|
| Make sure you have the rw in there, and the /boot/append-GTA02 is in
| the partition with the rootfs. Try adding a space before the rw in case
| I mangled it with recent changes.
|
| It's a bug I
If you come up in NOR U-Boot it doesn't seem to impact NAND environment,
no idea why but nothing can be done about it now.
So if that's the case try whatever dance of death needed to get a
console on NAND U-Boot and do the same there.
After using the devirginator the same procedure worked.
I'm just adding some patches and doing some cleaning on it, I'll update
the moredrivers kernels at http://people.openmoko.org/andy when I
checked we didn't break the threshold stuff.
Thanks, in the moredrivers kernel the accs are working now. But now I have the
following problems.
When I use
On Wednesday 04 February 2009, Michael Tansella wrote:
ifconfig usb0 192.168.0.202 netmask 255.255.255.0 up
Finally this made my day. I never had to do that before.
Assuming MS5 is similar to recent SHR this is because connman is taking over
management of the network interfaces, and trying
This is reminding me of a problem we have with level interrupts on
pcf50633 new driver, we also get twice the same interrupt there although
the density of interrupts is so low and logically it cannot get confused
so it doesn't make trouble.
We also changed lis302dl to use level interrupts so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This is reminding me of a problem we have with level interrupts on
| pcf50633 new driver, we also get twice the same interrupt there although
| the density of interrupts is so low and logically it cannot
Send a bug report in Trac about it.
There is a quick workaround for this that can be done I believe.
-Andy
Thank You very much
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Tue, 3 Feb 2009 11:53:15 +0100
Michael Tansella michael-tanse...@gmx.de wrote:
There is a quick workaround for this that can be done I believe.
Any hint where I can find this workaround, then I'll post it to the
wiki?
The fix should now be in the latest andy-tracking kernel:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| There is a quick workaround for this that can be done I believe.
|
| Any hint where I can find this workaround, then I'll post it to the wiki?
I'm just adding some patches and doing some cleaning on it,
Very nice
thanks
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
There is a quick workaround for this that can be done I believe.
Any hint where I can find this workaround, then I'll post it to the wiki?
Greets
Michael
___
Openmoko community mailing list
community@lists.openmoko.org
are you sure this isn't just the synchronization events?
For me the problem looks like this.
|type| |code| |-value-|
0006 - Seperator time 1
0006 0002 0048 - Value X1
0006 0002 0001 0024 - Value Y1
0006 0002 0002 0396 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| are you sure this isn't just the synchronization events?
|
| For me the problem looks like this.
|
| |type| |code| |-value-|
| 0006 - Seperator time 1
| 0006 0002
On Sat, 24 Jan 2009 10:35:14 +0100
Michael Tansella michael-tanse...@gmx.de wrote:
When I read out the Acc values I get strange values. I set the device
to 100 Hz that means I should get one (3D) value every 10 ms but I
get two even with a different time stamp whitch differs round about
0.4
Could you test to set the threshold value to something low, e.g., 18 or
so? Also check the threshold file afterward you've set it so that it's
not zero, values which are too low to be represented by the threshold
code get rounded down.
HI,
I made a mistake. I do not really get two different
On Sat, 24 Jan 2009 17:21:09 +0100
Michael Tansella michael-tanse...@gmx.de wrote:
I made a mistake. I do not really get two different values I get
twice the same (3D) value but a different timestamp (see below). But
anyway this is not correct. I don't want to set a threshold, because
I need
18 matches
Mail list logo
