The driver in tree is for u-blox M8 devices, not M10. The M10 series devices (from Protocol Version 23.01) use a different, non backwards compatible interface for configuring the modem behaviour. Of the two boards tested in the original PR, the "VMU RT1170" is explicitly listed as having a u-blox NEO-M8N modem, while I have been unable to find any information online about the "FMURT6" board. Leaving the naming as-is will cause problems when M10 drivers are contributed. Signed-off-by: Jordan Yates <jordan@embeint.com> |
||
|---|---|---|
| .. | ||
| adc | ||
| audio/dmic | ||
| auxdisplay | ||
| can | ||
| charger | ||
| clock_control_litex | ||
| clock_control_xec | ||
| counter | ||
| crypto | ||
| dac | ||
| display | ||
| eeprom | ||
| espi | ||
| ethernet/eth_ivshmem | ||
| flash_shell | ||
| fpga/fpga_controller | ||
| gnss | ||
| haptics/drv2605 | ||
| ht16k33 | ||
| i2c | ||
| i2s | ||
| ipm | ||
| jesd216 | ||
| kscan | ||
| lcd_cyclonev_socdk | ||
| lcd_hd44780 | ||
| led_apa102c_bitbang | ||
| led_is31fl3194 | ||
| led_is31fl3216a | ||
| led_is31fl3733 | ||
| led_lp50xx | ||
| led_lp3943 | ||
| led_lp5562 | ||
| led_lp5569 | ||
| led_pca9633 | ||
| led_pwm | ||
| led_strip | ||
| led_sx1509b_intensity | ||
| led_xec | ||
| lora | ||
| mbox | ||
| mbox_data | ||
| memc | ||
| misc | ||
| mspi | ||
| peci | ||
| ps2 | ||
| smbus | ||
| soc_flash_nand | ||
| soc_flash_nrf | ||
| spi_bitbang | ||
| spi_flash | ||
| spi_flash_at45 | ||
| spi_fujitsu_fram | ||
| uart | ||
| video | ||
| virtualization/ivshmem/doorbell | ||
| w1/scanner | ||
| watchdog | ||
| drivers.rst | ||