Bug#814032: ITP: libiio -- Linux Industrial I/O (IIO) support library
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: wnpp
Severity: wishlist
Owner: "A. Maitland Bottoms" <bottoms@debian.org>
* Package name : libiio
Version : 0.6
Upstream Author : Paul Cercueil <paul.cercueil@analog.com>
* URL : https://github.com/analogdevicesinc/libiio
* License : LGPL v2.1+
Programming Lang: C++, Python, C#/Mono
Description : Linux Industrial I/O (IIO) support library
Linux Industrial I/O Subsystem:
https://wiki.analog.com/software/linux/docs/iio/iio
libiio - IIO system library:
https://wiki.analog.com/resources/tools-software/linux-software/libiio
Libiio is a library that has been developed by Analog Devices to ease
the development of software interfacing Linux Industrial I/O (IIO)
devices.
The library abstracts the low-level details of the hardware, and
provides a simple yet complete programming interface that can be used
for advanced projects.
The library is composed by one high-level API, and several backends:
the "local" backend, which interfaces the Linux kernel through the sysfs virtual filesystem,
the "network" backend, which interfaces the iiod server through a network link.
The IIO Daemon (IIOD) server is a good example of an application that
uses libiio. It creates a libiio context that uses the "local"
backend, and then share it on the network to any client application
using the "network" backend of libiio and connected to the server.
Source of several binary packages...
iiod - Daemon to share IIO devices on the network
libiio-cil-dev - CLI bindings for libiio (development)
libiio-dev - libiio development files
libiio-utils - Miscellaneous libiio utilities
libiio0 - Library for interfacing with IIO devices
libiio0-cil - CLI bindings for libiio
libiio0-doc - libiio documentation
python-libiio - Python bindings for libiio
- -Maitland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWt4tmAAoJEFBB8YkfROCQHz4QAKGBrPHpWS0mltp5BoKvameY
o4eUViyEI2uLW9OShl3HbxOVgUnUNWOA/DJYKq+X/iR+CvguvdtmnZTuiMr2vU29
8sQsS5goYrSVdgG9bvfqXtjKEmg8BxWI0HPfjFHfOzTtoCgC4pLoFdcveG3nfxFc
qRGZzXSqPw3hflgTP65bPXucoEfQa2rYYvLKb2U8xSBaoS2HvIpBXDbTx6iorBfu
ojVGJGHN5bUeoON+vSbT6XM47PU8MeoqTOC7OHvRnV10ZYFZC4oGQDmirSztXCJl
XEHBs8Iprg0mKNFUHgu+1sbqaH0qJGNDmG7Cu17GqvzbPr9KYjXsYwi469cd7cN4
ceSixAVjea3kI2igEeSCRxfCEohtgOOFh83TM/4eaYmJLF45ujy0OHPIAjA0BuE5
cRKdffXnpMZV0QJGzgKVC9mOogB8ALLT22ppbjOWjITeq56fSfDOWw2F5SzkyD/y
0uoDSICfWWQrpnHeHlUhq8hKMP5EUyEahdr8IDJzV1+XQwzDEhsxkArKDDrCRBIL
tSrWeJcDQppDKv4EdhwT2BbSvxG5czFSZK6eG2imy24xQNMXg2xQZVuMC6ZA1+D8
GdlRFaSP8bONu8ao51uEjHrJ3SujEnsz0eDjzFA/1z35xihrZ6KkhYzDMniRcs1y
g22dPmhl4EP4ucz25gBA
=LOCX
-----END PGP SIGNATURE-----
Reply to: