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. Openmoko Bug #2145: Debian: Reading of accelerometers broken
(Openmoko Public Trac)
2. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
3. Re: Openmoko Bug #1905: packagekit daemon crashing due to
interactive pacakge install? (Openmoko Public Trac)
4. Re: Openmoko Bug #1192: unknown reason cause TI GSM modem
always return "+CME ERROR: 512" (Openmoko Public Trac)
5. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
6. Re: Openmoko Bug #2145: Debian: Reading of accelerometers
broken (Openmoko Public Trac)
7. Re: Openmoko Bug #2097: [testing image] list in Setting can't
scroll (Openmoko Public Trac)
8. Re: Openmoko Bug #1542: gps does not get fix
(Openmoko Public Trac)
--- Begin Message ---
#2145: Debian: Reading of accelerometers broken
----------------------+-----------------------------------------------------
Reporter: Defiant | Owner: hardware
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Keywords: debian event2 event3
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Running Debian with Kernel 2.6.24-20081103.git7172ec57-1 I have the
following problem reading the accelerometers.
-when the device is lying still /dev/input/event2 and 3 is producing
output
-as soon as the is moved event2 & 3 are no longer producing any output.
-when the device is lying still again the device is producing output
again.
I tested it with a simple
hexdump /dev/input/event2
Some people on #openmoko-debian were able to reproduce this bug.
This problem doesn't occur running the Om2008.9 kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145>
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: new
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Keywords: debian event2 event3
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Changes (by andy):
* cc: [EMAIL PROTECTED] (added)
Comment:
It sounds a great deal like the wrong "polarity" of threshold interrupt is
being selected, ie, interrupt when it's LESS than the threshold rather
than more. lis302dl supports both "polarities".
cc-ing Simon Kagstrom since he wrote the threshold stuff.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1905: packagekit daemon crashing due to interactive pacakge install?
-----------------------+----------------------------------------------------
Reporter: peepsalot | Owner: tick
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: opkg | Version: Om2008.8
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------+----------------------------------------------------
Changes (by tick):
* haspatch: => 0
* component: Installer => opkg
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1905#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1192: unknown reason cause TI GSM modem always return "+CME ERROR: 512"
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: assigned
Priority: high | Milestone:
Component: hardware | Version:
Severity: critical | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-----------------------------------------+----------------------------------
Changes (by joerg):
* cc: [EMAIL PROTECTED] (added)
Comment:
added to CC
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1192#comment:24>
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: new
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Keywords: debian event2 event3
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Comment(by SimonKagstrom):
I checked the source code and it looks correct. In
__enable_data_collection, we do this when enabling the data collection
with a threshold:
__reg_write(lis, LIS302DL_REG_FF_WU_CFG_1,
LIS302DL_FFWUCFG_XHIE | LIS302DL_FFWUCFG_YHIE |
LIS302DL_FFWUCFG_ZHIE);
So it should be "high" events. I also tested on my freerunner on stable-
tracking, and for me it appears to work fine (although it's input devices
3 and 4 here). It's quiet when flat on the table, but as I pick it up,
data starts flowing.
I set the threshold to 100.
// Simon
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:2>
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: new
Priority: normal | Milestone:
Component: hardware | Version: unspecified
Severity: normal | Keywords: debian event2 event3
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
----------------------+-----------------------------------------------------
Comment(by andy):
Thanks for looking at it Simon, I guess a big difference is that Debian is
still on some variant of stable branch.
Defiant, have a try of the same thing with the kernel you can find in
http://people.openmoko.org/andy the one with andy-tracking in the name,
see if it changes the behaviour. These are from today and quite similar
to what Simon is testing with.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2145#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2097: [testing image] list in Setting can't scroll
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: john_lee
Type: defect | Status: in_testing
Priority: highest | Milestone:
Component: Settings | Version:
Severity: blocker | Keywords: Om2008.11
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
------------------------+---------------------------------------------------
Changes (by john_lee):
* status: accepted => in_testing
Comment:
committed exposure r74
and om.dev 6381ae17c772ffb9526522fd6f9ee72362fdc1e4
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2097#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1542: gps does not get fix
-----------------------------------------+----------------------------------
Reporter: emdete | Owner: hardware
Type: defect | Status: closed
Priority: high | Milestone:
Component: hardware | Version:
Severity: blocker | Resolution: fixed
Keywords: gps antenna fix internal | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-----------------------------------------+----------------------------------
Changes (by mwester):
* status: new => closed
* haspatch: => 0
* resolution: => fixed
Comment:
The software fix for this problem on the GTA01 has been committed some
time ago, and should be present in all current distro's GTA01 kernels.
The fix is a port of the GTA02 solution, with the same behavior(notably,
that the SD clock is slowed down significantly whenever the GPS is powered
up, and the SD clock is stopped entirely except during actual reading or
writing of SD card data). Significant improvements in time-to-first-fix
are evident, including the ability to obtain fixes in locations where this
was previously not possible.
Marking this ticket as "fixed" -- re-open this if the problem persists
(after verifying that the GTA01 patch is present in the kernel, of
course).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1542#comment:27>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
