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 #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
2. Re: Openmoko Bug #2257: gsm0710muxd: "Modem does not respond
to AT commands" (Openmoko Public Trac)
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by arhuaco):
Thanks, It did indeed work for me with the known-to-work kernel.
With the lastest andy-tracking I got further with the patch
ignore_s3c2410_serial_overruns.patch
(https://docs.openmoko.org/trac/ticket/2180#comment:11).
At least the modem sends a reply but it enters a loop (OK, OK, OK..). I
will test with SHR unstable later (I don't have gsm0710muxd in the distro
I'm using now).
Here is an interesting thread.
http://www.mail-archive.com/openmoko-
[email protected]/msg08118.html
I'll be reading more about this issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2257: gsm0710muxd: "Modem does not respond to AT commands"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: stable-kernel-2009.1
Component: System Software | Version: unspecified
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
-----------------------------+----------------------------------------------
Comment(by mwes...@…):
The output from nspy may be helpful in tracking down what's really going
on in the driver. Latest nspy patch (applies to the head of the andy-
tracking branch) can be found at
http://moko.mwester.net/download/nspy_andy_tracking_r901d73fe51...patch
Enable (at boot time would be good) by:
echo "1" >/sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-gsm.0/nspy_enable
I use the following script to monitor what's going on:
#!/bin/sh
while /bin/true; do
cat /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-gsm.0/nspy_buffer
sleep 1
done
Prebuilt kernel (with SHR defconfig) available, for a short only, at:
http://moko.mwester.net/download/uImage-2.6.28-oe1+gitr119783+901d73fe51f33032b34b2ae5612eb863ec90532a-r3
.4mwester-om-gta02.bin
(make sure to check the md5sum, my ISP has been known to twiddle bits:
5e2422398855284e33a2dc3b1ac30167 )
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2257#comment:20>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
