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. [Bug 762] GTA01v4 Only Charges at 40ma
([EMAIL PROTECTED])
2. [Bug 762] GTA01v4 Only Charges at 40ma
([EMAIL PROTECTED])
3. [Bug 762] GTA01v4 Only Charges at 40ma
([EMAIL PROTECTED])
4. [Bug 885] New: do_compile failure for
gst-plugins-bad_0.10.5.bb ([EMAIL PROTECTED])
5. [Bug 770] Battery discharging while phone is off (GSM part)
([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
8. [Bug 886] New: [PATCH] Segmentation fault triggered from
DEBUG_BLOCK_PRINT in block-raw.c because logfile is NULL
([EMAIL PROTECTED])
9. [Bug 886] [PATCH] Segmentation fault triggered from
DEBUG_BLOCK_PRINT in block-raw.c because logfile is NULL
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=762
------- Additional Comments From [EMAIL PROTECTED] 2007-09-19 15:27 -------
Harald!
For GTA01BV4 green PCB, my experiment and observation were:
a. When battery voltage is about 3.29(couldn't power on) , then plug in usb
cable(white), the charge current is 43mA(about 50mA)
b. 30 mins later, battery voltage became 3.52V, booting kernel and plug in usb
cable(white) again, charge current is 490mA(about 500mA)
c. 2.5 hours later, battery voltage become 4.2V and the charge current became
0mA finally.
So looks like the charge current work as pcf50606 datasheet described.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=762
------- Additional Comments From [EMAIL PROTECTED] 2007-09-19 17:41 -------
Well 43ma is about 40ma not 50ma. In any case the charge current when
not-enumerated should by your design be 100ma not 50ma. Looking at the pcf50606
data sheet, it may be simply CURRAT in MBCC3 remains at its default of 0.1 *
Ifast where it should probably be set to 0.2 to produce a 100ma precharge
instead of 50ma.
The reset value is probably appropriate for Ifast of 1C but the nominal charge
on the GTA01v4 appears to be closer to 0.5C.
Assuming that the standby battery battery is connected to the pcf50606,
reprogramming CURRAT to 0.2*Ifast should allow precharge at 100ma. This will
at least halve the time from dead to u-bootable and halve the time to charge
without enumerating.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=762
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=885
Summary: do_compile failure for gst-plugins-bad_0.10.5.bb
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: OE bitbake recipes / build system
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I am building with MokoMakefile. I did an 'update-makefile' then a 'make setup
update openmoko-devel-image' earlier today, and the build failed here:
| ccache arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t
-DHAVE_CONFIG_H -I. -I. -I../.. -isystem/myth/OpenMoko4/build/tmp
/staging/arm-angstrom-linux-gnueabi/include -I../../gst-libs -I../../gst-libs
-pthread -I/myth/OpenMoko4/build/tmp/staging/arm-angstrom
-linux-gnueabi/include/gstreamer-0.10
-I/myth/OpenMoko4/build/tmp/staging/arm-angstrom-linux-gnueabi/include/glib-2.0
-I/myth/OpenMoko4
/build/tmp/staging/arm-angstrom-linux-gnueabi/lib/glib-2.0/include
-I/myth/OpenMoko4/build/tmp/staging/arm-angstrom-linux-gnueabi/inclu
de/libxml2 -Wall -g -DGST_DISABLE_DEPRECATED
-isystem/myth/OpenMoko4/build/tmp/staging/arm-angstrom-linux-gnueabi/include
-fexpensive-o
ptimizations -fomit-frame-pointer -frename-registers -Os -MT
libgstcdaudio_la-gstcdaudio.lo -MD -MP -MF .deps/libgstcdaudio_la-gstcdaud
io.Tpo -c gstcdaudio.c -fPIC -DPIC -o .libs/libgstcdaudio_la-gstcdaudio.o
| gstcdaudio.c:25:21: error: cdaudio.h: No such file or directory
| gstcdaudio.c:54: error: field 'info' has incomplete type
| gstcdaudio.c:55: error: field 'volume' has incomplete type
| gstcdaudio.c: In function 'gst_cdaudio_change_state':
| gstcdaudio.c:293: warning: implicit declaration of function 'cd_init_device'
| gstcdaudio.c:299: warning: implicit declaration of function 'cd_close'
| gstcdaudio.c:302: warning: implicit declaration of function 'cd_stat'
| gstcdaudio.c:308: warning: implicit declaration of function 'cddb_discid'
| gstcdaudio.c:316: warning: implicit declaration of function 'cd_resume'
| gstcdaudio.c:318: warning: implicit declaration of function 'cd_play'
| gstcdaudio.c:335: warning: implicit declaration of function 'cd_pause'
| gstcdaudio.c:340: warning: implicit declaration of function 'cd_stop'
| gstcdaudio.c:342: warning: implicit declaration of function 'cd_finish'
| gstcdaudio.c: In function 'gst_cdaudio_send_event':
| gstcdaudio.c:425: warning: implicit declaration of function 'cd_play_pos'
| make[4]: *** [libgstcdaudio_la-gstcdaudio.lo] Error 1
| make[4]: Leaving directory
`/myth/OpenMoko4/build/tmp/work/armv4t-angstrom-linux-gnueabi/gst-plugins-bad-0.10.5-r1/gst-plugins-bad-0.
10.5/ext/cdaudio'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory
`/myth/OpenMoko4/build/tmp/work/armv4t-angstrom-linux-gnueabi/gst-plugins-bad-0.10.5-r1/gst-plugins-bad-0.
10.5/ext'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory
`/myth/OpenMoko4/build/tmp/work/armv4t-angstrom-linux-gnueabi/gst-plugins-bad-0.10.5-r1/gst-plugins-bad-0.
10.5'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory
`/myth/OpenMoko4/build/tmp/work/armv4t-angstrom-linux-gnueabi/gst-plugins-bad-0.10.5-r1/gst-plugins-bad-0.
10.5'
| FATAL: oe_runmake failed
NOTE: Task failed:
/myth/OpenMoko4/build/tmp/work/armv4t-angstrom-linux-gnueabi/gst-plugins-bad-0.10.5-r1/temp/log.do_compile.5805
NOTE: package gst-plugins-bad-0.10.5-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package gst-plugins-bad-0.10.5: failed
ERROR: Build of
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-bad_0.10.5.bb
do_compile failed
.bb, do_install)
NOTE: Running task 3250 of 3476 (ID: 3239,
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-good_0.10.6.bb,
do_qa_configure)
NOTE: Running task 3251 of 3476 (ID: 3240,
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-good_0.10.6.bb,
do_compile)
NOTE: Running task 3252 of 3476 (ID: 3244,
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-good_0.10.6.bb,
do_install)
NOTE: Running task 3253 of 3476 (ID: 3229,
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-bad_0.10.5.bb,
do_qa_configure)
NOTE: Running task 3254 of 3476 (ID: 3230,
/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-bad_0.10.5.bb,
do_compile)
ERROR: Task 3230
(/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-bad_0.10.5.bb,
do_compile) failed
NOTE: Tasks Summary: Attempted 3253 tasks of which 3025 didn't need to be rerun
and 1 failed.
ERROR:
'/myth/OpenMoko4/openembedded/packages/gstreamer/gst-plugins-bad_0.10.5.bb'
failed
make: *** [openmoko-devel-image] Error 1
The problem is repeatable after doing a 'make clean-package-gst-plugins-bad'.
I was able to work around the problem by removing the cdaudio packages from my
host system, then cleaning the package and re-running 'make
openmoko-devel-image'.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=770
------- Additional Comments From [EMAIL PROTECTED] 2007-09-20 04:37 -------
Harald!
For the GTA01BV4 green pcb, before phone is off, power off audio amplifier and
send [EMAIL PROTECTED] to GSM modem, the current become 0mA finally. So,
[EMAIL PROTECTED] is
workable. BTW, when modem receive this command, you could not get any response
from modem.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=129
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-09-20 05:19 -------
Out of curiousity: how will a GSM modem firmware update be delivered? The wiki
page http://wiki.openmoko.org/wiki/GTA01_gsm_modem says:
"Upgrading the modem's firmware is technically possible but no proper software
is currently legally available to users outside OpenMoko staff."
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=886
Summary: [PATCH] Segmentation fault triggered from
DEBUG_BLOCK_PRINT in block-raw.c because logfile is NULL
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: qemu-neo1973
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
This problem appeared when upstream changes were pulled in revision 2981. This
triggers the following segmentation fault when running flash.sh:
openmoko/flash.sh: line 88: 1421 Segmentation fault (core dumped) $qemu
-mtdblock "$script_dir/$flash_base" -kernel "$script_dir/$1" -serial stdio
-nographic -usb -monitor null 0<&0
I used gdb to generate a backtrace and found that the segmentation fault was due
to the DEBUG_BLOCK_PRINT macro in block-raw.c being called while logfile was
NULL.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=886
------- Additional Comments From [EMAIL PROTECTED] 2007-09-20 05:32 -------
Created an attachment (id=316)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=316&action=view)
make DEBUG_BLOCK_PRINT check if logfile is NULL
I'm not sure if this is the most appropriate fix but it seems to solve the
problem for me.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
