Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2185: AUX button makes interrupt storm
(Openmoko Public Trac)
2. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
3. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
4. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
--- Begin Message ---
#2185: AUX button makes interrupt storm
---------------------+------------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.9-dev
Severity: normal | Keywords: AUX button interrupts
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by arhuaco):
vnevoa:
This kernel should fix AUX bouncing. It would be nice if you can confirm
so that we can trust the patch.
http://wiki.emqbit.com/tmp/uImage-moredrivers-GTA02_andy-
tracking_b6d1b1c2788c5903.bin
Once we know this problem is solved we'll check the power button issue.
It is solved for me but your problem was more serious.
Best regards.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2185#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
Reporter: Defiant | Owner: hardware
Type: defect | Status: closed
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: debian event2 event3 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
-------------------------------------+--------------------------------------
Comment(by SimonKagstrom):
A general comment first: Thanks to all for the testing and experiments,
the messages here have been very clear and to the point!
Johannes: 100 interrupts per second sounds right when the threshold is 0
(so that new datums is signalled by the interrupt) - the data rate is set
to 100Hz by default. With threshold 0, the interrupt rate should not
change depending on if the device is shaken or not - it always interrupts
at each datum in that case.
As for your earlier test: The interrupt is only enabled when the device
file is opened - so if I understand that test correct, you are closing the
device during the sleep and in that case the interrupt stream should stop.
DigitalPioneer: Your first problem certainly sounds like the original
issue, but as for the screen corruption I have no idea :-). To me it
sounds like a more general problem. Andy: Could it have something to do
with the "manual" bitbang used by the accelerometer code? (I'm thinking if
it can somehow interfer with the Glamo).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
Reporter: Defiant | Owner: hardware
Type: defect | Status: closed
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: debian event2 event3 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
-------------------------------------+--------------------------------------
Comment(by SimonKagstrom):
I should also add that I've tried the accelerometers with uImage-
moredrivers-GTA02_andy-tracking_e142549d884a17b8.bin, and everything seem
to work fine for me. I ran the python test script from the wiki page with
and without thresholds, and the device reacts as expected. I've not seen
any "display crash" (although E crashed a few times during the test, but I
see that always :-) ).
I'm using Om2008.12.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
-------------------------------------+--------------------------------------
Reporter: Defiant | Owner: hardware
Type: defect | Status: closed
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: debian event2 event3 | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
-------------------------------------+--------------------------------------
Comment(by Defiant):
I had the display problem after waking up from suspend the current andy
tracking.
Also with the andy tracking powering bluetooth on/off is not visible in
dbus (probably because of an other dbus path, not sure)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
