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 #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
2. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
3. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
4. Re: Openmoko Bug #2207: trac sometimes throws " from pyPgSQL
import PgSQL trac sometimes throws "ImportError: No module named
pyPgSQL" (Openmoko Public Trac)
5. Re: Openmoko Bug #2207: trac sometimes throws " from pyPgSQL
import PgSQL trac sometimes throws "ImportError: No module named
pyPgSQL" (Openmoko Public Trac)
--- Begin Message ---
#2181: [andy-tracking] Not charging according to kernel when charging from a
stupid charger
-----------------------------+----------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Thanks ! There seems to be a problem with the cut-off current:
48 MBCC6 = 0x00 -- MBC charger control 6
cutoffcur -- cutoff current level (full in CV), 1/32*Ichg
0.0000 (0x00)
4d MBCS3 = 0x50 -- MBC charger status 3
[...]
ilim -- battery charge current > cutoffcur level
1 (0x1)
I'll attach the full decoded register dump.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2181: [andy-tracking] Not charging according to kernel when charging from a
stupid charger
-----------------------------+----------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
Oops no. The cutoff current is fine but usbok isn't.
Could it be that the "dumb" charger delivers considerably less than 5V ?
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2181: [andy-tracking] Not charging according to kernel when charging from a
stupid charger
-----------------------------+----------------------------------------------
Reporter: TimoJyrinki | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
I can see the USB insertion at +12370s in the dmesg log, there is no USB
removal subsequently. And in the register dump, I can see the MBC
recognizes that USB power is present, but is says that USB power is not
"OK". OK would have meant that USB power is >50mV above the current
battery level.
So it does seem something is wrong with your charger, it sends out
something less than ~4.3V when it should be a great source of 5.0VDC.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2207: trac sometimes throws " from pyPgSQL import PgSQL trac sometimes
throws
"ImportError: No module named pyPgSQL"
---------------------+------------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
---------------------+------------------------------------------------------
Comment(by lindi):
It's now https://admin-trac.openmoko.org/trac/ticket/1711
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2207#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2207: trac sometimes throws " from pyPgSQL import PgSQL trac sometimes
throws
"ImportError: No module named pyPgSQL"
------------------------+---------------------------------------------------
Reporter: lindi | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: invalid
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
------------------------+---------------------------------------------------
Changes (by wendy_hung):
* status: new => closed
* resolution: => invalid
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2207#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
