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 #2235: Monochrome display on resume
(Openmoko Public Trac)
2. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
3. Re: Openmoko Bug #2180: stable-tracking: 'rxserr' UART
messages (Openmoko Public Trac)
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
The difference with Qi is that it while it brings up the Glamo, it doesn't
bring up the LCM ASIC since it only inits the Glamo to get SD Card access.
So it'd be Qi "not doing" something there rather than doing something if
that's related.
I would guess anything to do with mono display action is a feature of the
LCM not the Glamo state. Controlling LCM state is not entirely in control
as we learned with the WSOD issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Yes it's written but I haven't tested it yet, I wonder what the impact
will be on throughput. I'll test it thisafternoon.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:27>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: System Software | Version:
Severity: major | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I just posted it to kernel list
http://lists.openmoko.org/pipermail/openmoko-
kernel/2009-February/008782.html
it doesn't seem to impact throughput insanely bad just from eyeballing the
boot anyway. But I doubt it improved matters there... maybe it can do
something about the latencies though.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:28>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
