| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This message is used to bind a muxed data port to a controller device.
The Muxed data port has to be managed by qmi_wwan driver.
The Muxed data port is identified by:
- mux_id: the numeric ID given to qmi_wwan once created
- interface number: the interface number of the qmi controller device on
the modem
Once the binding is completed, all the commands sent (and I expect also
received, but I could not test it) using the same Client ID are for the
binded data port instead of the real one.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[21 Oct 2015, 15:15:41] [Debug] Asynchronously getting autoconnect settings...
[21 Oct 2015, 15:15:41] [Debug] [/dev/cdc-wdm1] Sent message...
<<<<<< RAW:
<<<<<< length = 13
<<<<<< data = 01:0C:00:00:01:4D:00:01:00:34:00:00:00
[21 Oct 2015, 15:15:41] [Debug] [/dev/cdc-wdm1] Sent message (translated)...
<<<<<< QMUX:
<<<<<< length = 12
<<<<<< flags = 0x00
<<<<<< service = "wds"
<<<<<< client = 77
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 1
<<<<<< tlv_length = 0
<<<<<< message = "Get Autoconnect Settings" (0x0034)
[21 Oct 2015, 15:15:41] [Debug] [/dev/cdc-wdm1] Received message...
>>>>>> RAW:
>>>>>> length = 24
>>>>>> data = 01:17:00:80:01:4D:02:01:00:34:00:0B:00:02:04:00:00:00:00:00:01:01:00:00
[21 Oct 2015, 15:15:41] [Debug] [/dev/cdc-wdm1] Received message (translated)...
>>>>>> QMUX:
>>>>>> length = 23
>>>>>> flags = 0x80
>>>>>> service = "wds"
>>>>>> client = 77
>>>>>> QMI:
>>>>>> flags = "response"
>>>>>> transaction = 1
>>>>>> tlv_length = 11
>>>>>> message = "Get Autoconnect Settings" (0x0034)
>>>>>> TLV:
>>>>>> type = "Result" (0x02)
>>>>>> length = 4
>>>>>> value = 00:00:00:00
>>>>>> translated = SUCCESS
>>>>>> TLV:
>>>>>> type = "Status" (0x01)
>>>>>> length = 1
>>>>>> value = 00
>>>>>> translated = disabled
error: operation failed: Couldn't get the mandatory Roaming TLV: TLV 0x10 not found
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These values may be given along with a QMI error (e.g. out-of-call), so don't
assume that a success operation is a prerequisite to read them.
[04 Feb 2015, 20:55:07] [Debug] [/dev/cdc-wdm1] Received message...
>>>>>> RAW:
>>>>>> length = 42
>>>>>> data = 01:29:00:80:01:08:02:0D:00:24:00:1D:00:02:04:00:01:00:0F:00:1C:08:00:2B:17:00:00:00:00:00:00:1B:08:00:87:28:00:00:00:00:00:00
[04 Feb 2015, 20:55:07] [Debug] [/dev/cdc-wdm1] Received message (translated)...
>>>>>> QMUX:
>>>>>> length = 41
>>>>>> flags = 0x80
>>>>>> service = "wds"
>>>>>> client = 8
>>>>>> QMI:
>>>>>> flags = "response"
>>>>>> transaction = 13
>>>>>> tlv_length = 29
>>>>>> message = "Get Packet Statistics" (0x0024)
>>>>>> TLV:
>>>>>> type = "Result" (0x02)
>>>>>> length = 4
>>>>>> value = 01:00:0F:00
>>>>>> translated = FAILURE: OutOfCall
>>>>>> TLV:
>>>>>> type = "Last Call Rx Bytes Ok" (0x1c)
>>>>>> length = 8
>>>>>> value = 2B:17:00:00:00:00:00:00
>>>>>> translated = 5931
>>>>>> TLV:
>>>>>> type = "Last Call Tx Bytes Ok" (0x1b)
>>>>>> length = 8
>>>>>> value = 87:28:00:00:00:00:00:00
>>>>>> translated = 10375
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
IPv6 addresses are always sent in network byte order. Oddly,
IPv4 addresses appear to be sent as LE uint32s rather than
BE/network byte order.
|
| |
|
|
|
|
|
|
|
|
|
| |
Messages can now be tagged with a special 'abort' keyword, so that whenever the
message times out we issue a new ABORT command to cancel the specific timed out
request.
This support is currently only available for the NAS and WDS services, which are
the ones supporting ABORT for their long-running operations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'length-prefix-size'
Use the new 'size-prefix-format' property to specify whether the length prefix
variable is a 'guint8' or a 'guint16'.
We therefore consolidate the way how this length prefix variable is specified in
both arrays and strings.
So, instead of:
"length-prefix-size" : "16"
We now just do:
"size-prefix-format" : "guint16"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 'array-size' property was used to define an implicit variable to be found at
the beginning of every array. This property expected a dictionary with one
single 'format' key.
Instead of this setup, create a new 'size-prefix-format' property which directly
expects the format string of the variable to be used as array-length indicator.
So, instead of:
"array-size" : { "format" : "guint16" }
We can now just use:
"size-prefix-format" : "guint16"
Also, remove the explicit size definitions when the format is "guint8", as that
is the default already when none specified and the array is not of fixed size.
|
|
|
|
| |
Use the more generic `QmiWdsAuthentication' flags instead, which match properly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Not a guint8; flattened Gobi API says:
enum eQMIWDSExtendedTechPrefs:UINT16
{
...
}
Plus the values are wrong, so fix that.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also, make the 'last' TLV optional.
|
|
|
|
|
| |
We define new enums and flags to easier handle the response to the
`Get Current Data Bearer Technology' request.
|
|
|
|
|
| |
This new type is the `public-format' of the guint8 status given in the Get
Packet Service Status response.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|