Changes between Version 17 and Version 18 of expansion/gw16126

Timestamp:

01/17/2019 10:57:07 PM (7 years ago)

Author:

Ryan Erbstoesser

Comment:

update software section and integrate into modem and ble areas

expansion/gw16126

@@ -45 +45 @@
 == u-blox SARA-R4 LTE Cat M-1 modem
 The [https://www.u-blox.com/sites/default/files/SARA-R4-N4_ProductSummary_%28UBX-16019228%29.pdf u-blox SARA-R410M-52B] LTE Cat M1 modem supports M1 bands 2,4,5,12,13. For more info on the CATM1 standard and use cases see the following [https://www.u-blox.com/en/lte-cat-m1 CATM1 Explained Link]. 
+
+[=#software]
+=== Software Support
+In General, the following software is necessary for the GW16126:
+ * LTE Cat-M1 modem:
+  - Linux 4.17+ kernel with option driver (CONFIG_USB_SERIAL_OPTION) and qmi driver (CONFIG_USB_NET_QMI_WWAN)
+   * Linux 4.5+ needed for QMI RAW IP support (unless backported)
+   * Linux 4.17+ needed for ublox R410M (unless backported)
+ 
+
+Ubuntu:
+ - LTE Cat-M1 modem: requires network-manager modemmanager libqmi
+ - BLE HCI: requires bluez
+ - fully supported (with the above)
+
+OpenWrt 18.6.1:
+ - requires kmod-usb-net-opton, kmod-usb-net-qmi-wwan, kmod-usb-serial, kmod-usb-serial-ftdi, kmod-usb-serial-qualcomm, kmod-bluetooth, kmod-crypto-user, kmod-crypto-hash, bluez-daemon, uqmi
+ - fully supported (with the above)
+
+OpenWrt 16.02:
+ - will not work without backporting qmi raw-ip support and modem ID's to option1/qmi-wwan driver
 
 The modem features a Qualcomm chipset that uses the 'option' and 'qmi_wwan' Linux drivers providing the following devices:
@@ -293 +314 @@
   - FTDI UART support (CONFIG_USB_SERIAL_FTDI_SIO)
   - HCI UART with H4 (CONFIG_BT_HCIUART and CONFIG_BT_HCIUART_H4) in order to provide a bluetooth HCI over UART
-  - crypto userspace API (CONFIG_CRYPTO_USER, CONFIG_CRYPTO_USER_API_AEAD, CONFIG_CRYPTO_USER_API_HASH, CONFIG_CRYPTO_USER_API_RNG, CONFIG_CRYPTO_USER_API_SKCIPHER) in order to generate a random Bluetooth MAC (BDADDR)
- * Bluetooth stack such as BlueZ (4.45+)
+  - crypto userspace API (CONFIG_CRYPTO_USER, CONFIG_CRYPTO_USER_API_AEAD, CONFIG_CRYPTO_USER_API_HASH, CONFIG_CRYPTO_USER_API_RNG, CONFIG_CRYPTO_USER_API_SKCIPHER, CONFIG_CRYPTO_USER_API*) in order to generate a random Bluetooth MAC (BDADDR)
+ * Bluetooth stack such as BlueZ (4.45+ with Experimental support (-E param on bluetoothd))
+
 
 The following shows how you would interact with the BLE controller via BlueZ on Ubuntu bionic:
@@ -525 +547 @@
 
 
-[=#software]
-== Software Support
-In General, the following software is necessary for the GW16126:
- * LTE Cat-M1 modem:
-  - Linux 4.17+ kernel with option driver (CONFIG_USB_SERIAL_OPTION) and qmi driver (CONFIG_USB_NET_QMI_WWAN)
-   * Linux 4.5+ needed for QMI RAW IP support (unless backported)
-   * Linux 4.17+ needed for ublox R410M (unless backported)
- * BLE HCI:
-  - Linux 4.5+ kernel
-  - hci_uart driver (CONFIG_BT_HCIUART, CONFIG_BT_HCIUART_H4 hci_uart)
-  - Userspace cryptographic algorithm support (CONFIG_CRYPTO_USER_API*) (for generation of random bdaddr in BlueZ)
-  - Bluetooth stack such as BlueZ (4.45+ with Experimental support (-E param on bluetoothd))
-
-Ubuntu:
- - LTE Cat-M1 modem: requires network-manager modemmanager libqmi
- - BLE HCI: requires bluez
- - fully supported (with the above)
-
-OpenWrt 18.6.1:
- - requires kmod-usb-net-opton, kmod-usb-net-qmi-wwan, kmod-usb-serial, kmod-usb-serial-ftdi, kmod-usb-serial-qualcomm, kmod-bluetooth, kmod-crypto-user, kmod-crypto-hash, bluez-daemon, uqmi
- - fully supported (with the above)
-
-OpenWrt 16.02:
- - will not work without backporting qmi raw-ip support and modem ID's to option1/qmi-wwan driver
+