Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
| software:flink:flink_lib [2014-12-02 11:58] – graf | software:flink:flink_lib [Unbekanntes Datum] (aktuell) – gelöscht - Externe Bearbeitung (Unbekanntes Datum) 127.0.0.1 | ||
|---|---|---|---|
| Zeile 1: | Zeile 1: | ||
| - | ====== flink Userspace Library ====== | ||
| - | |||
| - | <box blue right 38% | **Downloads**> | ||
| - | * [[https:// | ||
| - | </ | ||
| - | |||
| - | This is the user documentation for the flink userspace library in C. It provides a device and bus independent interface to the underlying driver modules. For more information about the inner workings see [[https:// | ||
| - | |||
| - | ===== Overview ===== | ||
| - | When flink is used on a Linux based system the flink userspace library offers an simple interface to communicate with the underlying kernel modules. The userspace library is split in two parts. | ||
| - | * High-Level API: Interface to predefined subdevices, such as PWM or GPIO. | ||
| - | * Low-Level API: Can be used to access user-defined subdevices. | ||
| - | The library must be built for the target platform architecture. | ||
| - | |||
| - | ===== Requirements ===== | ||
| - | * Linux based operating system | ||
| - | * GCC 4.6 or newer | ||
| - | * CMake 2.8 or newer | ||
| - | * GNU make | ||
| - | |||
| - | ===== Building ===== | ||
| - | - Clone git repository: < | ||
| - | - Create a build directory: < | ||
| - | - Build for the host plattform with: < | ||
| - | |||
| - | * The makefile will switch to the kernel directory, read the current configuration and compile all necessary flink kernel modules for the choosen target plattform. | ||
| - | |||
| - | ===== Installation ===== | ||
| - | * Move new kernel modules into the default location to ''/ | ||
| - | * Load each module with '' | ||
| - | * If dependency files were created beforehand its better to use < | ||
| - | * Some kernel module must be loaded with the appropriate arguments according to the target board specifications (see below) | ||
| - | |||