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 #1158: Charging stops even while connected
(Openmoko Public Trac)
2. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
3. Re: Openmoko Bug #2165: gtk layout differences between 2007.2
and 2008.testing (Openmoko Public Trac)
4. Openmoko Bug #2179: GTA02 ASoC capture kernel oops
(Openmoko Public Trac)
5. Re: Openmoko Bug #2179: GTA02 ASoC capture kernel oops
(Openmoko Public Trac)
6. Openmoko Bug #2180: stable-tracking: 'rxserr' UART messages
(Openmoko Public Trac)
7. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
8. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: p...@… | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: blocker | Resolution:
Keywords: power management | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
---------------------------------+------------------------------------------
Comment(by lindi):
It went now down to 81% so it does not start recharging anytime soon. I
unfortunately need to use my phone now so I can't leave it to the charger
for any longer.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:58>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: p...@… | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: blocker | Resolution:
Keywords: power management | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
---------------------------------+------------------------------------------
Comment(by andy):
Thanks for the test Lindi it's obvious 81% isn't good enough.
I'll ask for info from battery vendor about constant voltage trickle
charge advisability.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:59>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2165: gtk layout differences between 2007.2 and 2008.testing
-------------------------+--------------------------------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords: gtk, cacao,
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
Comment(by iknowjoseph):
Thanks Zecke,
This small java application would display the file open dialogue on
2007.2, but not on 2008.x:
http://blogs.thehumanjourney.net/finds/resource/java-test_0.1_armv4t.ipk
Juan Lucas, can we provide an example of the splash screen?
Thanks, Joseph
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2165#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2179: GTA02 ASoC capture kernel oops
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version: current svn head
Severity: normal | Keywords: asoc capture
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
When trying to use the GTA02 to capture PCM data, the stable-tracking
kernel oopses.
The following steps can be used to reproduce this:
$ wget http://wildsau.enemy.org/~moko/voice-recording.state
$ alsactl -f voice-recording.state restore
$ arecord -v -f cd -c 2 foo.wav
Segmentation fault
I will attach the kernel oops
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2179>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2179: GTA02 ASoC capture kernel oops
-----------------------------+----------------------------------------------
Reporter: laforge | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: FSO
Component: System Software | Version: current svn head
Severity: normal | Keywords: asoc capture
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by laforge):
there seem to be actually two independent problems
1) the fact that there are no matching rates " WM8753 HiFi <-> s3c24xx-i2s
No matching rates"
2) the fact that this causes a kernel oops in the
neo1973_gta02_hifi_hw_free() function. This is caused by
dai_ops.set_pll() == NULL, which in turn seems to be caused by the fact
that snd_pcm_open_substream() is not finished (due to the 'no matching
rate' bug above) and calls snd_pcm_release_substream() for a not fully
opened substream.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2179#comment:1>
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: normal | Keywords: gps s3x24xx_serial rxerr
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
the stable-tracking kernel shows a number of receive error messages on the
UART for GPS:
[ 4559.800000] rxerr: port ch=0x39, rxs=0x00000001
[ 4562.285000] rxerr: port ch=0x00, rxs=0x0000000c
Those perceived receive errors lead to missing characters in the u-blox
binary protocol and corrupt the checksum and lead to all kinds of havoc on
higher layers.
This bug did not occur with older kernel versions, though it is unclear
what was the last working version.
The same problem also exists with non-gta02 hardware (e.g. the E-TEN
glofiish devices), so it is believed to be a bug in the s3c24xx serial
driver.
It can be reproduced _always_ during power-up of the GPS device. However,
it also occurs sporadically later during data transmission.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: p...@… | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: blocker | Resolution:
Keywords: power management | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
---------------------------------+------------------------------------------
Comment(by joerg):
I suggest setting battery charger to constant voltage 4.15V, and a maximum
charge current of up to 1200mA (I know we can't charge at his rate with
50633)
Anyway that's what GTA01-cell spec says:
''3.3 Charge Conditions''
'' (1) Charge Voltage : 4.20±0.05 V''
'' (2) Maximum Charge Current : 1200 mA (1C)''
'' (3) Charge Method : CC-CV (Constant Current - Constant
Voltage)''
There's no switching off of charging voltage mentioned, and I never heard
a battery would need this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:60>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: p...@… | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: blocker | Resolution:
Keywords: power management | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: sometimes |
---------------------------------+------------------------------------------
Comment(by andy):
I already asked Dkay several hours ago to confirm with vendor about
constant voltage mode, and Dkay told ''| In my memorize of discuss with
vendor before, if we don't stop charging | when battery full. It will make
battery to swell and decrease battery | lifetime '' but he will check it.
So we won't make any change until we find out about it from vendor.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:61>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
