summaryrefslogtreecommitdiff
path: root/data
AgeCommit message (Collapse)AuthorFilesLines
2017-11-11nas: new 'Extended LTE Band Preference' TLV in "Set/Get SSP"Aleksander Morgado1-2/+30
The "LTE Band Preference" TLV is defined as a 64bit mask, and therefore it can only report up to 64 bands (1-64). The new 'Extended LTE Band Preference' TLV is defined as a sequence of four 64-bit masks, allowing up to 256 bands reported. <<<<<< TLV: <<<<<< type = "Extended LTE Band Preference" (0x23) <<<<<< length = 32 <<<<<< value = DF:18:09:3B:A0:01:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 <<<<<< translated = { [0] = '1787696847071 ' [1] = '0 ' [2] = '0 ' [3] = '0 '} Based on a patch from Wolfgang Tolkien <wtolkien@cypress.bc.ca>
2017-11-11dms: new 'Extended LTE Band Capability' TLV in "Get Band Capabilities"Aleksander Morgado1-1/+10
The 'LTE Band Capability' TLV (0x10) is a 64-bit mask, and therefore isn't capable of reporting more than 64 bands (1 to 64). In order to support LTE bands greater than 64, this new 'extended' TLV is defined, as an array of uint16 values, one per band. E.g. this "Get Band Capabilities" response where the modem reports band 66: [/dev/cdc-wdm0] received message... <<<<<< RAW: <<<<<< length = 98 <<<<<< data = 01:61:00:80:02:01:02:01:00:45:00:55:00:02:04:00:00:00:00:00:01:08:00:00:00:C0:07:00:00:02:00:10:08:00:DF:18:09:3B:A0:01:00:00:11:08:00:00:00:00:00:00:00:00:00:12:2A:00:14:00:01:00:02:00:03:00:04:00:05:00:07:00:08:00:0C:00:0D:00:11:00:14:00:19:00:1A:00:1C:00:1D:00:1E:00:26:00:28:00:29:00:42:00 [/dev/cdc-wdm0] received generic response (translated)... <<<<<< QMUX: <<<<<< length = 97 <<<<<< flags = 0x80 <<<<<< service = "dms" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "response" <<<<<< transaction = 1 <<<<<< tlv_length = 85 <<<<<< message = "Get Band Capabilities" (0x0045) <<<<<< TLV: <<<<<< type = "Result" (0x02) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = SUCCESS <<<<<< TLV: <<<<<< type = "Band Capability" (0x01) <<<<<< length = 8 <<<<<< value = 00:00:C0:07:00:00:02:00 <<<<<< translated = wcdma-2100, wcdma-pcs-1900, wcdma-dcs-1800, wcdma-1700-us, wcdma-850-us, wcdma-900 <<<<<< TLV: <<<<<< type = "LTE Band Capability" (0x10) <<<<<< length = 8 <<<<<< value = DF:18:09:3B:A0:01:00:00 <<<<<< translated = 1, 2, 3, 4, 5, 7, 8, 12, 13, 17, 20, 25, 38, 40, 41 <<<<<< TLV: <<<<<< type = 0x11 <<<<<< length = 8 <<<<<< value = 00:00:00:00:00:00:00:00 <<<<<< TLV: <<<<<< type = "Extended LTE Band Capability" (0x12) <<<<<< length = 42 <<<<<< value = 14:00:01:00:02:00:03:00:04:00:05:00:07:00:08:00:0C:00:0D:00:11:00:14:00:19:00:1A:00:1C:00:1D:00:1E:00:26:00:28:00:29:00:42:00 <<<<<< translated = { [0] = '1 ' [1] = '2 ' [2] = '3 ' [3] = '4 ' [4] = '5 ' [5] = '7 ' [6] = '8 ' [7] = '12 ' [8] = '13 ' [9] = '17 ' [10] = '20 ' [11] = '25 ' [12] = '26 ' [13] = '28 ' [14] = '29 ' [15] = '30 ' [16] = '38 ' [17] = '40 ' [18] = '41 ' [19] = '66 '} Based on a patch from Wolfgang Tolkien <wtolkien@cypress.bc.ca> Updated according to suggestions from Carlo Lobrano <c.lobrano@gmail.com>
2017-10-30dms: new 'Swi Get/Set USB Composition' messagesAleksander Morgado1-0/+43
And corresponding '--dms-swi-get-usb-composition' and '--dms-swi-set-usb-composition=[x]' qmicli actions. Based on Bjørn Mork's swi_setusbcomp.pl tool: https://git.mork.no/?p=wwan.git;a=blob_plain;f=scripts/swi_setusbcomp.pl $ sudo qmicli -d /dev/cdc-wdm2 --dms-swi-get-usb-composition [/dev/cdc-wdm2] Successfully retrieved USB compositions: USB composition 6: DM, NMEA, AT, QMI [*] USB composition 8: DM, NMEA, AT, MBIM USB composition 9: MBIM $ sudo qmicli -d /dev/cdc-wdm2 --dms-swi-set-usb-composition=9 [/dev/cdc-wdm2] Successfully set USB composition You may want to power-cycle the modem now, or just set it offline and reset it: $> sudo qmicli ... --dms-set-operating-mode=offline $> sudo qmicli ... --dms-set-operating-mode=reset $ sudo qmicli -d /dev/cdc-wdm2 --dms-set-operating-mode=offline [/dev/cdc-wdm2] Operating mode set successfully $ sudo qmicli -d /dev/cdc-wdm2 --dms-set-operating-mode=reset [/dev/cdc-wdm2] Operating mode set successfully (module reboots) $ sudo qmicli -d /dev/cdc-wdm2 --dms-swi-get-usb-composition [/dev/cdc-wdm2] Successfully retrieved USB compositions: USB composition 6: DM, NMEA, AT, QMI USB composition 8: DM, NMEA, AT, MBIM [*] USB composition 9: MBIM
2017-06-23wds: add Get Channel RatesDan Williams1-0/+23
Reports bogus current TX/RX rates on my Huawei E397 though.
2017-05-09loc: fix Since: versionsDan Williams1-4/+5
2017-05-09nas: add Attach/Detach messageDan Williams1-0/+16
2017-04-17loc: add boilerplate and start/stop message skeletonsDan Williams2-1/+73
2017-02-28wds: added WDS Bind Mux Data Port messageCarlo Lobrano1-1/+33
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.
2017-02-28wda: extended wda set format message to enable QMUXCarlo Lobrano1-1/+12
Added the following configurable values: - upload datagram protocol - download datagram protocol - download datagram max size - download max datagrams - endpoint type - endpoint interface number According to last GobiNet from CodeAura project, it is necessary to set the following values to enable multiple data connection through one controller device: - upload datagram protocol = QMAP - download datagram protocol = QMAP - download datagram max size = 32 (it seems working even without setting it) - download max datagrams = 32768 (it seems working even without setting it) - endpoint type = HSUSB (it seems working even without setting it) - endpoint interface number = this depends on the modem, but it seems working even without setting it
2017-02-14nas: add Get Operator Name and Operator Name indicationDan Williams2-1/+137
2017-02-13uim: added SIM power on/off functionalityKasper Holtze1-1/+38
2017-02-10data: specify 'since' tags for all messages and TLVsAleksander Morgado12-202/+1276
2017-01-29dms: new 'SWI Get Current Firmware'Aleksander Morgado1-0/+63
This is a vendor-specific message with id 0x5556. E.g. for a Dell DW5570: [/dev/cdc-wdm1] Successfully retrieved current firmware: Model: MC8805 Boot version: SWI9X15C_01.08.16.02 r15159 carmd-fwbuild1 2013/05/16 17:41:33 AMSS version: SWI9X15C_01.08.16.02 r15159 carmd-fwbuild1 2013/05/16 17:41:33 SKU ID: 1101798 Package ID: 1101798_9902617_SWI9X15C_01.08.16.02_00_Dell_001.005_000 Carrier ID: 12 Config version: unknown And for a MC7455: [/dev/cdc-wdm1] Successfully retrieved current firmware: Model: MC7455 Boot version: SWI9X30C_02.14.03.00 AMSS version: SWI9X30C_02.14.03.00 SKU ID: 1102476 Package ID: unknown Carrier ID: 202 Config version: 000.008_000
2017-01-29dms: make "HP Change Device Mode" vendor-specificAleksander Morgado1-0/+1
We are going to include a different version of DMS 0x5556 for Sierra devices.
2017-01-29dms: renamed DMS 0x5556 to 'HP Change Device Mode'Aleksander Morgado1-6/+7
Also, define a new QmiDmsHpDeviceMode enumeration with the modes found out of the HPlt4120. Note this command is flagged as 'HP' because it only applies to HP devices, at least only to the HPlt4120.
2017-01-16dms: add support for 'Set firmware id'Aleksander Morgado1-0/+8
This command is the one used by Sierra modems to get into Boot & Hold mode, and very likely has a set of TLVs that we don't know about. For now, just an empty message.
2017-01-16dms: implement 'Get/Set Boot Image Download Mode'Aleksander Morgado1-0/+29
2016-10-26pdc: no need to CamelCase parameter namesAleksander Morgado1-1/+1
2016-10-26pdc: new PDC service implementationAliaksandr Barouski2-0/+365
Added calls for configure hp4120 LTE modem
2016-10-24dms: new 'Change Device Download Mode' commandAleksander Morgado1-0/+13
Based on a patch from Aliaksandr Barouski <alex.borovsky@gmail.com> https://bugs.freedesktop.org/show_bug.cgi?id=96465
2016-10-06wds: make WDS Extended Error Code TLV a common-refDan Williams2-72/+20
2016-10-06wds: add more TLVs and ModifyProfile/DeleteProfile requestsDan Williams2-30/+264
2016-10-06wds: add more Profile-related TLVsDan Williams2-8/+108
2016-10-06wds: move common Profile-related TLVs to common-refsDan Williams2-404/+221
2016-10-06wds: add Go Dormant, Go Active, and Get Dormancy StatusDan Williams1-0/+31
2016-10-06wds: add Set Event Report and Event Report IndicationDan Williams1-0/+293
2016-09-23wds: add CreateProfileDan Williams1-0/+203
2016-09-07dms: Get Band Capabilities supported on DMS 1.1Dan Williams1-1/+1
But only seems supported on GSM/UMTS firmware. Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: Read ERI File supported on DMS 1.1Dan Williams1-1/+1
Need CDMA/EVDO firmware for it though. Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: User Lock State messages supported on DMS 1.1Dan Williams1-3/+3
Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: Activation-related messages supported on DMS 1.1Dan Williams1-3/+3
But you usually need a CDMA/EVDO capable device and firmware to use it. Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: Get PRL Version supported on DMS 1.1Dan Williams1-1/+1
But of course you need a CDMA/EVDO capable device and firmware version to read it. Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: Get Time supported on DMS 1.1Dan Williams1-1/+1
Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-09-07dms: Get Hardware Revision supported on DMS 1.1Dan Williams1-1/+1
Tested on Novatel USB1000: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services: [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0) [07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
2016-08-19nas: fix RX/TX mixupBjørn Mork1-2/+2
Don't know what I was thinking here, but the referenced channels are of course *RX* channels. None of my modems can do TX CA. Yet :) Signed-off-by: Bjørn Mork <bjorn@mork.no>
2016-06-10nas: support 'Force Network Search'Aleksander Morgado1-0/+8
2016-04-03nas: no exact version for 'Get LTE Cphy CA Info'Aleksander Morgado1-1/+0
We're not sure about it, so just don't specify it.
2016-04-03nas: untabifyAleksander Morgado1-27/+26
2016-04-03nas: implement 'Get LTE Cphy CA Info'Bjørn Mork1-0/+56
Carrier aggregation is much more fun when you can watch it being activated :) $ qmicli -p -d /dev/cdc-wdm0 --nas-get-lte-cphy-ca-info [/dev/cdc-wdm0] Successfully got carrier aggregation info DL Bandwidth: '20' Secondary Cell Info Physical Cell ID: '101' TX Channel: '3050' DL Bandwidth: '20' LTE Band: 'eutran-7' State: 'activated' Primary Cell Info Physical Cell ID: '299' TX Channel: '1450' DL Bandwidth: '20' LTE Band: 'eutran-3' Secondary Cell index: '1' I have absolutely no clue about the required NAS version, so I just put the current version I have there... Signed-off-by: Bjørn Mork <bjorn@mork.no>
2016-01-30uim: implement 'UIM Change PIN'Aleksander Morgado1-0/+60
2016-01-30uim: implement 'UIM Unblock PIN'Aleksander Morgado1-0/+60
2016-01-30uim: implement 'UIM Verify PIN'Aleksander Morgado1-0/+58
2016-01-30uim: implement 'UIM Set PIN protection'Aleksander Morgado1-0/+52
2016-01-11wds: add GetPDNThrottleInfo messageDan Williams1-1/+35
2015-12-29nas: set TLV as mandatory in Get RF Band Information responseAleksander Morgado1-1/+1
2015-12-04nas: correct ID for Get RF Band Information result TLVAlbert Diserholt1-1/+1
2015-10-25nas: new optional TLV in 'Get Home Network' to know whether MNC is 2 or 3 digitsAleksander Morgado1-1/+12
Also, version bump to 1.13.5 to flag the exact version in which the change was introduced.
2015-10-21wds: 'roaming' TLV is always optional in Get/Set Autoconnect settingsAleksander Morgado1-2/+2
[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
2015-10-06wds: new 'WDS Set Autoconnect Setting' command supportAleksander Morgado1-1/+21
2015-10-06wds: new 'WDS Get Autoconnect Setting' command supportAleksander Morgado1-0/+22
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-31 03:26:16 +0000