On 3 Apr 2008, at 17:58, Andy Green wrote:
neod has them both open, but the input subsystem should be okay with
that and you having them too. I think you need to make sure you have a
real recent kernel with the patch to improve locking for the service
routine.
Before I tried the test, I re-f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Tue, 2008-04-01 at 21:37 +0200, Michael 'Mickey' Lauer wrote:
|> Hi guys,
|>
|> just got around to testing one (the 2nd one seems broken or unaccessible
|> on my prototypes) of the Neo FreeRunner accelle
On Tue, 2008-04-01 at 21:37 +0200, Michael 'Mickey' Lauer wrote:
> Hi guys,
>
> just got around to testing one (the 2nd one seems broken or unaccessible
> on my prototypes) of the Neo FreeRunner accellerometers.
Both seem to work on my prototype (GTA02v5), as long as X isn't running.
If I start m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I notice you mention only one chip is currently working as isr source.
| But isn't there two independently configurable pins connected to irqs
| from that one chip? I didn't dig into the schematic, not su
TECTED] On Behalf Of Michael
'Mickey' Lauer
Sent: Thursday, April 03, 2008 10:08 AM
To: Andy Green
Cc: List for Openmoko community discussion;
[EMAIL PROTECTED]
Subject: Re: accellerometer test
> It seems to me there is basically one number you can set, and then you
> can decide if
> |> So you can almost get what you are looking for, just that there is only
> |> one number allowed.
> |
> | Excellent! When do you have time to give that a go? :)
>
> Right now... to be clear we talk about wake CPU from suspend with this?
100%, yeah.
> Also is
>
> http://bugzilla.openmoko.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> It seems to me there is basically one number you can set, and then you
|> can decide if X, Y and/or Z go above or below that number makes an
|> interrupt. It looks like this number is absolute, ie, if you
> It seems to me there is basically one number you can set, and then you
> can decide if X, Y and/or Z go above or below that number makes an
> interrupt. It looks like this number is absolute, ie, if you set it to
> 5 then going above or below 5 x 18mG "in + or -" will trigger it.
>
> So you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Am Donnerstag, den 03.04.2008, 09:57 +0100 schrieb Andy Green:
|> We can wake up from one of the accelerometers and not the other -- which
|> is likely okay for real use -- but there is no driver support or
Am Donnerstag, den 03.04.2008, 09:57 +0100 schrieb Andy Green:
> We can wake up from one of the accelerometers and not the other -- which
> is likely okay for real use -- but there is no driver support or API to
> enable or disable it yet. I guess it can just expose something in /sys.
Agreed. Can
Am Donnerstag, den 03.04.2008, 09:57 +0100 schrieb Andy Green:
> Sounds good. I am curious about what happens if you take that app for a
> ride in your car. What does it show after you accelerated to cruising
> speed and just go constantly along with it sat on the passenger seat?
If it stops to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi guys,
|
| just got around to testing one (the 2nd one seems broken or unaccessible
| on my prototypes) of the Neo FreeRunner accellerometers.
|
| Apart from a bit of jitter, I think its pretty accurate -
Hi guys,
just got around to testing one (the 2nd one seems broken or unaccessible
on my prototypes) of the Neo FreeRunner accellerometers.
Apart from a bit of jitter, I think its pretty accurate -- I'm very
satisfied with the performance. We can detect lots of different
orientations, including (t
13 matches
Mail list logo
