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 #2208: consider sending touchscreen release
event on resume? (Openmoko Public Trac)
2. Re: Openmoko Bug #2207: trac sometimes throws " from pyPgSQL
import PgSQL trac sometimes throws "ImportError: No module named
pyPgSQL" (was: trac sometimes throws " from pyPgSQL import PgSQL
trac sometimes throws "ImportError: No module named pyPgSQL")
(Openmoko Public Trac)
3. Re: Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
4. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
5. Re: Openmoko Bug #2208: consider sending touchscreen release
event on resume? (Openmoko Public Trac)
6. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
7. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
8. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
--- Begin Message ---
#2208: consider sending touchscreen release event on resume?
-----------------------------+----------------------------------------------
Reporter: lindi | 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 arhuaco):
This fix makes sense :-) ... Kind of specific tough. Anyone has reason for
not doing this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2208#comment:1>
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 marek):
I think this report should go to http://admin-trac.openmoko.org/ ?!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2207#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2171: stable-tracking 80f4b57/resume: eth0: ERROR while getting interface
flags:
No such device
-----------------------------+----------------------------------------------
Reporter: lindi | 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 werner):
Okay, if you use power_on, that's expected. What power_on does is a reset
of the module, but completely behind the back of everything else.
Unbind/bind has pretty much the same effect (one layer above power_on),
so that's where you get the correct on/off action.
But what's the whole story ? Do you want to enter a power-saving state ?
There are currenly three choices for this that aren't specific to the
WLAN module: unbind/bind, suspend/resume (*), and module unload/load.
They all should produce the same effect, namely that the driver gets
removed and the module powers down.
(*) That is, unless you've set the "persist" option of the S3C MMC
driver.
Furthermore, you can use wmiconfig to disable the module without driver
removal. --power rec sets a sensible power consumption and --wlan disable
turns off transmission and rejects other ioctls until --wlan enable.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:4>
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 TimoJyrinki):
Hmm, does not look too good here. I do now get "Charging" as soon as I
plug the dumb charger in. Yes, even at 100mA. But even if I change to
500mA with the force_usb_dangerous option, it seems the capacity is only
dropping. I left it charging for an hour but it does seem to really be
pulling current even though the kernel indicates so.
Using andy-tracking 0f58c86e19a. Changing to non-dumb charger (ie. a
laptop) works and charges.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2208: consider sending touchscreen release event on resume?
-----------------------------+----------------------------------------------
Reporter: lindi | 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):
It will still be out of sync only in the event we woke and his finger is
still down, it seems less likely than the behaviour Lindi mentions. We
could perhaps issue the input event for up in suspend function if we were
down.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2208#comment:2>
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):
Could you please do a
# cat /sys/class/i2c-adapter/i2c-0/0-0073/dump_regs
when the system is supposedly charging from a "dumb" charger at
500mA, yet the capacity is dropping ? That would help to determine
what exactly the PMU thinks it's doing at that time.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:8>
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):
Timo also the dmesg might be useful, it'll show PMU interrupt events.
There was a patch some weeks ago aimed at solving exactly this. What kind
of battery is in there, the shipping GTA02 one?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:9>
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 TimoJyrinki):
There you go, taken a short while after attaching the dump charger + echo
500 > force_usb_dangerous and seeing that the capacity still drops. The
shipping GTA02 battery (from July, ie. first shipments).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
