diff options
| author | Aleksander Morgado <aleksander@lanedo.com> | 2012-08-31 12:31:00 +0200 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@lanedo.com> | 2012-08-31 12:31:00 +0200 |
| commit | e8ca43e315688f04a4f896646abaffab2b3a395e (patch) | |
| tree | ea115b0d326dec5aa2ff65ac78357f22ea640dd1 /src/mm-error-helpers.c | |
| parent | a3d32c552c526a7f5850007428a5a32216766a64 (diff) | |
broadband-modem: if the generic CNMI request fails, try a Qualcomm-compatible one
This is the port to git master of the following commit:
commit 1d9164ec90788d1be134482ff88c501e3c5d623c
Author: Dan Williams <dcbw@redhat.com>
Date: Mon Aug 27 18:20:33 2012 -0500
gsm: if the generic CNMI request fails, try a Qualcomm-compatible one
Many devices based on Qualcomm chipsets don't support a <ds> value
of '1', despite saying they do in the AT+CNMI=? response. But they
do accept '2'. Since we're not doing much with delivery status
reports yet, if we get a CME 303 (not supported) error when setting
the message indication parameters via CNMI, fall back to the
Qualcomm-compatible CNMI parameters.
If we don't do this, we don't get SMS indications on these devices,
because the original CNMI failed.
Tested on Huawei E1550, Huawei E160G, ZTE MF622, and Novatel XU870.
Diffstat (limited to 'src/mm-error-helpers.c')
0 files changed, 0 insertions, 0 deletions