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 #2162: Changing screen modes (QVGA)
corrupted in stable-tracking (Openmoko Public Trac)
2. Re: Openmoko Bug #788: Starting or stopping gsmd completely
locks up the Neo (Openmoko Public Trac)
3. Re: Openmoko Bug #2156: rtctest.c does not exit with
stable-tracking kernel (Openmoko Public Trac)
4. Re: Openmoko Bug #81: Decide how PMU RTC alarm interrupt is
signalled to userspace (Openmoko Public Trac)
5. Re: Openmoko Bug #96: make sure PMU alarm (set via rtc
interface) is persistent (Openmoko Public Trac)
6. Re: Openmoko Bug #1392: ar6000: switching wifi modes does not
work (Openmoko Public Trac)
7. Re: Openmoko Bug #2045: [Om2008.9] Wifi associating is very
unreliable (Openmoko Public Trac)
8. Re: Openmoko Bug #1929: Wlan stops working after some time...
(Openmoko Public Trac)
--- Begin Message ---
#2162: Changing screen modes (QVGA) corrupted in stable-tracking
-----------------------------+----------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Balaji knows how to fix half of this already anyway, he says XGlamo is
using the wrong /sys path. On current kernels it needs to be
/sys/bus/spi/devices/spi2.0/state
If you do the xrandr, and on a terminal do
export DISPLAY=:0 ; echo qvga-normal > /sys/bus/spi/devices/spi2.0/state
it will correct the bad display into good QVGA.
The remaining problem is after framebuffer blanking, you'll get a WSOD.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2162#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#788: Starting or stopping gsmd completely locks up the Neo
--------------------------------+-------------------------------------------
Reporter: mwes...@… | Owner: openmoko-kernel
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: System Software | Version: 2007.2
Severity: critical | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Comment(by andy):
"flowcontrolled" /sys option was added to neo1973-pm-gsm for this, it was
enough of a solution that we can close this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/788#comment:57>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2156: rtctest.c does not exit with stable-tracking kernel
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: balajirrao
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by andy):
* status: accepted => closed
* resolution: => fixed
Comment:
Seems it's fixed.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2156#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#81: Decide how PMU RTC alarm interrupt is signalled to userspace
-------------------------------------+--------------------------------------
Reporter: lafo...@… | Owner: werner
Type: defect | Status: closed
Priority: high | Milestone:
Component: System Software | Version: current svn head
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-------------------------------------+--------------------------------------
Changes (by andy):
* status: new => closed
* haspatch: => 0
* resolution: => fixed
Comment:
On wake you can figure out the wake source generally from here:
# cat /sys/bus/platform/devices/neo1973-resume.0/resume_reason
EINT00_ACCEL1
EINT01_GSM
EINT02_BLUETOOTH
EINT03_DEBUGBRD
EINT04_JACK
EINT05_WLAN
EINT06_AUXKEY
EINT07_HOLDKEY
EINT08_ACCEL2
* EINT09_PMU
EINT10_NULL
EINT11_NULL
EINT12_GLAMO
EINT13_NULL
EINT14_NULL
EINT15_NULL
and in the event of it being the PMU interrupt, which is the case for RTC
alarm, you can get more info from here:
# cat /sys/class/i2c-adapter/i2c-0/0-0073/resume_reason
4000000000
That bit shown above should be set on RTC alarm wake.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/81#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#96: make sure PMU alarm (set via rtc interface) is persistent
-------------------------------------+--------------------------------------
Reporter: lafo...@… | Owner: michael
Type: defect | Status: closed
Priority: high | Milestone:
Component: System Software | Version: current svn head
Severity: major | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
-------------------------------------+--------------------------------------
Changes (by andy):
* status: reopened => closed
* haspatch: => 0
* resolution: => fixed
Comment:
People are able to use the RTC alarm stuff to wake from suspend now with a
commandline utility that definitely exits before the suspend. So it's
definitely persistent now.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/96#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1392: ar6000: switching wifi modes does not work
------------------------------------+---------------------------------------
Reporter: thebohem...@… | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
------------------------------------+---------------------------------------
Comment(by andy):
Has anyone tried this with a recent 2.6.29 kernel to verify it's solved?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1392#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2045: [Om2008.9] Wifi associating is very unreliable
-----------------------------+----------------------------------------------
Reporter: Matthias | Owner: openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Changes (by andy):
* haspatch: => 0
Comment:
Have you tried this same test with a recent 2.6.29 kernel, from andy-
tracking or stable now? There have been several changes in WLAN stack
there.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2045#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1929: Wlan stops working after some time...
-----------------------------+----------------------------------------------
Reporter: Treviño | Owner: marek
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: System Software | Version: Om2008.8
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Can you retry this with a recent 2.6.29 kernel, from andy-tracking or
stable branch now? There have been several changes to the WLAN stack that
might impact this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1929#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
