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 #2134: touchscreen sometimes forgets to
report a release? (Openmoko Public Trac)
2. Re: Openmoko Bug #2133: kmmcd: page allocation failure.
order:4, mode:0xd0 (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 #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
5. Re: Openmoko Bug #2181: [andy-tracking] Not charging
according to kernel when charging from a stupid charger
(Openmoko Public Trac)
6. Openmoko Bug #2208: consider sending touchscreen release
event on resume? (Openmoko Public Trac)
7. Re: Openmoko Bug #2171: stable-tracking 80f4b57/resume: eth0:
ERROR while getting interface flags: No such device
(Openmoko Public Trac)
8. Re: Openmoko Bug #2156: rtctest.c does not exit with
stable-tracking kernel (Openmoko Public Trac)
--- Begin Message ---
#2134: touchscreen sometimes forgets to report a release?
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
--------------------------------+-------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => fixed
Comment:
Great, thanks for the confirmation.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2134#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2133: kmmcd: page allocation failure. order:4, mode:0xd0
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version:
Severity: minor | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => fixed
Comment:
Great, thanks again for the confirmation.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2133#comment:9>
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 lindi):
At least with andy-tracking b8b36e5ec3db71 I can reliably start wifi with
{{{
echo 1 | sudo tee $sys_pm_wlan/power_on
echo s3c2440-sdi | sudo tee $sys_wlan_driver/unbind 2> /dev/null >
/dev/null
echo s3c2440-sdi | sudo tee $sys_wlan_driver/bind
sudo ifconfig eth0 up
}}}
so this issue must have been fixed somewhere during the last 5 weeks?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:1>
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):
Do you actually need to explicitly power on and unbind/bind before you
can use eth0 after resume ? In general, it should come up without such
things. (If using andy-tracking.)
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#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 lindi):
Just for the record I can no longer reproduce this with andy-tracking
b8b36e5e. Here's what I did:
{{{
0) capacity is 98%
1) status is "Discharging"
2) connect dumb usb battery
3) status is "Not charging"
4) force 500mA
5) status is "Charging"
6) pretty soon capacity rises to 99%
}}}
Timo, can you retry with these exact steps? Maybe when 500mA is not forced
the 100mA is consumed by the processor and nothing is left for charging
the battery?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2181#comment:6>
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:
-----------------------------+----------------------------------------------
This bug is quite cosmetic but something that might be useful to fix.
Maybe generating one spurious call to stylus_updown() could work?
{{{
Steps to reproduce:
1) type "apm -s" in xterm or similar
2) press enter down on a virtual keyboard
3) wait for the phone to suspend and release enter after that
4) resume the phone
Expected results:
4) applications receive touchscreen release event so that they notice that
user is no longer pressing touchscreen.
Actual results:
4) applications do not receive touchscreen release event on resume and
think that the user is still holding the enter key on the virtual
keyboard.
More info:
1) This was observed on andy-tracking b8b36e5ec3db71d5.
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2208>
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 lindi):
Yes I do, power_on alone is not enough:
{{{
li...@ginger:~$ apm -s
li...@ginger:~$ echo 1 | sudo tee /sys/bus/platform/drivers/gta02-pm-
wlan/gta02-pm-wlan.0/power_on
1
li...@ginger:~$ cat /sys/bus/platform/drivers/gta02-pm-wlan/gta02-pm-
wlan.0/power_on
1
li...@ginger:~$ sudo ifconfig eth0 up
eth0: ERROR while getting interface flags: No such device
li...@ginger:~$ echo s3c2440-sdi | sudo tee
/sys/bus/platform/drivers/s3c2440-sdi/bind
s3c2440-sdi
li...@ginger:~$ sudo ifconfig eth0 up
li...@ginger:~$
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2171#comment:3>
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: accepted
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by werner):
If you could give it a try with the version using RTC_ALM_SET, that
would be nice. If it's okay, then we can close it. Seems that Balaji
hasn't found any trouble.
- Werner
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2156#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
