TS-RF2 Driver: Difference between revisions
(Created page with "The driver is available [ftp://ftp.embeddedarm.com/pc104-peripherals/ts-rf2 here]. You can install the module to /lib/modules/<driver version>/") |
m (Links auto-updated for 2022 re-branding ( https://files.embeddedarm.com/pc104-peripherals/ts-rf2 → https://files.embeddedTS.com/pc104-peripherals/ts-rf2)) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The driver is available [ | The driver is available [https://files.embeddedTS.com/pc104-peripherals/ts-rf2 here]. You can install the module to your kernel module directory (usually /lib/modules/<kernel version>) and use modprobe, or run 'insmod ts-rf2.ko' with the absolute path of the module. If you receive a message that the symbols are invalid, you will have to compile that module with your kernel sources. The sources are available in the same directory as the binaries. | ||
Once loaded, a new TS-UART device file will appear in /dev. The exact name of this file will depend on the the number of TS-UARTs already loaded on your system, but the name of the driver will be of the form ttyTSx for the TS-72XX series, or from tttsx where x is an integer denoting the order in which the driver was loaded. You can run dmesg after loading the driver to see where it is created. | |||
Latest revision as of 17:43, 17 January 2022
The driver is available here. You can install the module to your kernel module directory (usually /lib/modules/<kernel version>) and use modprobe, or run 'insmod ts-rf2.ko' with the absolute path of the module. If you receive a message that the symbols are invalid, you will have to compile that module with your kernel sources. The sources are available in the same directory as the binaries.
Once loaded, a new TS-UART device file will appear in /dev. The exact name of this file will depend on the the number of TS-UARTs already loaded on your system, but the name of the driver will be of the form ttyTSx for the TS-72XX series, or from tttsx where x is an integer denoting the order in which the driver was loaded. You can run dmesg after loading the driver to see where it is created.