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 915] New: No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
2. [Bug 915] No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
3. [Bug 916] New: Alsa plufin for pulseaudio
([EMAIL PROTECTED])
4. [Bug 916] Alsa plufin for pulseaudio
([EMAIL PROTECTED])
5. [Bug 917] New: libmokojournal2 build failure: cann't find
gtk-doc.make ([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 916] Alsa plufin for pulseaudio
([EMAIL PROTECTED])
8. [Bug 915] No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
9. [Bug 915] No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
10. [Bug 915] No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
11. [Bug 915] No RSTR responses from libgsmdtool -m atcmd
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=915
Summary: No RSTR responses from libgsmdtool -m atcmd
Product: Neo1973 Hardware
Version: GTA01Bv4
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: GSM Modem
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
No RSTR responses from libgsmdtool -m atcmd.
gsmd, most of the time, fails to start on boot-up. Have to do:
/etc/init.d/gsmd start
to start the GSM daemon. Trying
libgsmdtool -m atcmd
opens a session, but, trying AT, or AT+CGMI doesn't produce any response from
the GSM chipset. Output is like this:
=== OUTPUT ===
[EMAIL PROTECTED]:~$ libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY
AT
STR=`AT'
== END ===
It just stops at that. I am able to press Control+C to break out of the
application and return to the prompt. But, then gsmd gets killed (?), and I have
to start gsmd manually again:
/etc/init.d/gsmd start
to try to test the application (which again doesn't produce any RSTR responses).
Manually using GSM works:
http://wiki.openmoko.org/wiki/Manually_using_GSM
after following this step:
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256#c6
Using OM2007.2 (recently built on October 5, 2007) on Debian Etch (x86).
------- 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=915
------- Additional Comments From [EMAIL PROTECTED] 2007-10-07 14:37 -------
OpenMoko image:
OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2
Kernel image:
uImage-2.6.21.5-r3-fic-gta01.bin
uname -a:
[EMAIL PROTECTED]:~$ uname -a
Linux fic-gta01 2.6.21.5-moko10 #1 PREEMPT Sun Aug 19 01:25:41 UTC 2007 armv4tl
unknown
------- 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=916
Summary: Alsa plufin for pulseaudio
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
URL: http://www.pulseaudio.org/wiki/PerfectSetup
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
An alsa application such as aplay can fail returning:
aplay: main:545: audio open error: Device or resource busy
because pulseaudio (or another alsa app) is using /dev/snd/pcmC0D0p
A solution would be to install the alsa plugin for pulseaudio [1].
Could you please add these packages?
They already exist in openembedded:
libasound-module-ctl-pulse - 1.0.14-r0 - Alsa plugin for ctl-pulse
libasound-module-pcm-pulse - 1.0.14-r0 - Alsa plugin for pcm-pulse
Note:
once the packages are installed
aplay -Dpulse file.wav
works :-), since /etc/asound.conf already defines a pulse device.
For having this behaviour by default, these lines can be added to
/home/root/.asoundrc
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
For some reason, it does not work if these lines are added to /etc/asound.conf
------- 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=916
------- Additional Comments From [EMAIL PROTECTED] 2007-10-07 23:41 -------
I don't quite understand the purpose of this. With these plugins you'd
effectively build an ALSA->PulseAudio->ALSA chain. To play files from console
it would be more effective to just install pulseaudio-misc and use paplay, no?
-Soeren
------- 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=917
Summary: libmokojournal2 build failure: cann't find gtk-doc.make
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
$ cat
/home/openmoko/build/tmp/work/armv4t-angstrom-linux-gnueabi/libmokojournal2-0.1.0+svnr3083-r2/temp/log.do_configure.27502
automake (GNU automake) 1.9.3
Written by Tom Tromey <[EMAIL PROTECTED]>.
Copyright 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
AUTOV is 1.9
NOTE: Executing autoreconf --verbose --install --force --exclude=autopoint -I
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 -I
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9 -I
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal
--force
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:45:
warning: underquoted definition of AC_LBL_C_INIT
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:172:
warning: underquoted definition of AC_LBL_C_INLINE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:228:
warning: underquoted definition of AC_LBL_LIBPCAP
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:296:
warning: underquoted definition of AC_LBL_TYPE_SIGNAL
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:326:
warning: underquoted definition of AC_LBL_FIXINCLUDES
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:372:
warning: underquoted definition of AC_LBL_LEX_AND_YACC
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:425:
warning: underquoted definition of AC_LBL_UNION_WAIT
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:454:
warning: underquoted definition of AC_LBL_SOCKADDR_SA_LEN
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:479:
warning: underquoted definition of AC_LBL_SOCKADDR_STORAGE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:512:
warning: underquoted definition of AC_LBL_HP_PPA_INFO_T_DL_MODULE_ID_1
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:538:
warning: underquoted definition of AC_LBL_HAVE_RUN_PATH
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:564:
warning: underquoted definition of AC_LBL_CHECK_TYPE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:593:
warning: underquoted definition of AC_LBL_UNALIGNED_ACCESS
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:698:
warning: underquoted definition of AC_LBL_DEVEL
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:828:
warning: underquoted definition of AC_LBL_LIBRARY_NET
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:851:
warning: underquoted definition of AC_C___ATTRIBUTE__
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:889:
warning: underquoted definition of AC_LBL_TPACKET_STATS
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/audiofile.m4:12:
warning: underquoted definition of AM_PATH_AUDIOFILE
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:45:
warning: underquoted definition of AC_LBL_C_INIT
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:172:
warning: underquoted definition of AC_LBL_C_INLINE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:228:
warning: underquoted definition of AC_LBL_LIBPCAP
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:296:
warning: underquoted definition of AC_LBL_TYPE_SIGNAL
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:326:
warning: underquoted definition of AC_LBL_FIXINCLUDES
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:372:
warning: underquoted definition of AC_LBL_LEX_AND_YACC
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:425:
warning: underquoted definition of AC_LBL_UNION_WAIT
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:454:
warning: underquoted definition of AC_LBL_SOCKADDR_SA_LEN
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:479:
warning: underquoted definition of AC_LBL_SOCKADDR_STORAGE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:512:
warning: underquoted definition of AC_LBL_HP_PPA_INFO_T_DL_MODULE_ID_1
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:538:
warning: underquoted definition of AC_LBL_HAVE_RUN_PATH
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:564:
warning: underquoted definition of AC_LBL_CHECK_TYPE
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:593:
warning: underquoted definition of AC_LBL_UNALIGNED_ACCESS
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:698:
warning: underquoted definition of AC_LBL_DEVEL
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:828:
warning: underquoted definition of AC_LBL_LIBRARY_NET
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:851:
warning: underquoted definition of AC_C___ATTRIBUTE__
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/libpcap.m4:889:
warning: underquoted definition of AC_LBL_TPACKET_STATS
/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal/audiofile.m4:12:
warning: underquoted definition of AM_PATH_AUDIOFILE
autoreconf: running: /home/openmoko/build/tmp/staging/i686-linux/bin/autoconf
--include=/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9
--include=/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal
--force --warnings=cross
autoreconf: running: /home/openmoko/build/tmp/staging/i686-linux/bin/autoheader
--include=/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal-1.9
--include=/home/openmoko/build/tmp/staging/arm-angstrom-linux-gnueabi/share/aclocal
--force --warnings=cross
autoreconf: running: automake --foreign --add-missing --copy --force-missing
--warnings=cross
automake: unknown warning category `cross'
configure.ac: installing `./install-sh'
configure.ac: installing `./missing'
automake: cannot open < gtk-doc.make: No such file or directory
autoreconf: automake failed with exit status: 1
FATAL: autoreconf execution failed.
------- 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=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=916
------- Additional Comments From [EMAIL PROTECTED] 2007-10-08 10:09 -------
Sorry if this comment comes twice (the first one has been sent by mail 11 hours
ago).
aplay is an example, the purpose is to ease the integration of a native Alsa
application.
Gilles
------- 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=915
------- Additional Comments From [EMAIL PROTECTED] 2007-10-08 10:55 -------
could you try these commands below?
1. >killall gsmd
2. > /usr/sbin/gsmd gsmd -p /dev/ttySAC0 -s 115200 -F
3. open another terminal:
> libgsmd-tool -m atcmd
> at + cgmr
I'd like to see the gsmd debug log information and your gsm firmware version.
Thanks!
------- 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=915
------- Additional Comments From [EMAIL PROTECTED] 2007-10-08 11:41 -------
could you please try these commands below?
1. > killall gsmd
2. > /usr/sbin/gsmd gsmd -p /dev/ttySAC0 -s 115200 -F
[see what the debug log message here]
3. open another terminal:
> libgsmd-tool -m atcmd
> at + cgmr
[see the firmware version]
I'd like to see the gsmd debug log information and your gsm firmware version.
Or you may try to update some files
1. update /etc/init.d/gsmd shell script
http://buildhost.openmoko.org/OM2007.2/tmp/rootfs/etc/init.d/gsmd
Or
2. update to the newest rootfs and kernal image
http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/
OpenMoko-openmoko-devel-image-glibc-ipk-P1-September-Snapshot-20070917-fic-gta01.rootfs.jffs2
uImage-2.6.22.5-moko11+svnr2937-r0-fic-gta01.bin
------- 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=915
------- Additional Comments From [EMAIL PROTECTED] 2007-10-08 11:49 -------
Created an attachment (id=338)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=338&action=view)
Output of "/usr/sbin/gsmd -p /dev/ttySAC0 -s 115200 -F"
------- 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=915
------- Additional Comments From [EMAIL PROTECTED] 2007-10-08 11:59 -------
1. Attached please find the file, gsmd-output-oct-8-2007-1510.txt that gives the
output of: "/usr/sbin/gsmd -p /dev/ttySAC0 -s 115200 -F".
2. After running libgsmd-tool -m atcmd, output is:
=== OUTPUT ===
[EMAIL PROTECTED]:~$ libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY
at+cgmr
STR=`at+cgmr'
=== END ===
It hangs there. So, I used manual method, and with bug #256 hint [1] (using stty
-F /dev/ttySAC0 crtscts) on another terminal, I found the AT+CGMR output as
follows:
+CGMR: "HW: GTA01Bv4, GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko1"
3. I would like to use libgsmd for my test application (atmycommand in
projects.openmoko.org). So, if I use the latest images, how can I update my
build environment to your latest gsm testing build environment?
4. From here:
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=176#c1
it is mentioned that lgsm_passthrough() should not be used by any application,
other than testing/debugging. My application is a testing/debugging application.
So, is it ok to use the same?
[1] http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256#c6
------- 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
