usb-safe: Type-safe communication with USB devices.
|Versions||0.1, 0.2, 0.3, 0.4, 0.4.1, 0.5, 0.5.1, 0.5.1.1, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.11.0.1, 0.11.0.2, 0.12, 0.13, 0.14|
|Dependencies||base (>=4 && <4.4), base‑unicode‑symbols (>=0.1.1 && <0.3), bytestring (==0.9.*), iteratee (>=0.3.5 && <0.6), monad‑peel (==0.1.*), regions (==0.8.*), transformers (==0.2.*), usb (>=0.5 && <0.7), usb‑enumerator (==0.2.*) [details]|
|Copyright||2009–2010 Bas van Dijk|
|Author||Bas van Dijk <email@example.com>|
|Maintainer||Bas van Dijk <firstname.lastname@example.org>|
|Category||System, Monadic Regions|
|Source repo||head: darcs get http://code.haskell.org/~basvandijk/code/usb-safe|
|Uploaded||by BasVanDijk at Sat Nov 6 15:57:49 UTC 2010|
|Downloads||5870 total (45 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
usb package provides a standard Haskell abstraction layer over
bindings-libusb providing: abstract types instead of
marshalling and unmarshalling, automatic garbage collection,
exceptions instead of integer return codes, etc..
While all that is very nice there are still some things that you can do wrong. For example doing I/O with a closed device or reading from or writing to an endpoint which doesn't belong to the claimed interface. Or reading from an Out endpoint or writing to an In endpoint.
usb-safe provides the following guarantees:
You can't reference handles to devices that are closed. In other words: no I/O with closed handles is possible.
The programmer specifies the region in which devices should remain open. On exit from the region the opened devices will be closed automatically.
You can't reference handles to configurations that have not been set.
You can't reference handles to interfaces that have not been claimed.
Just like with devices, the programmer can specify the region in which interfaces should remain claimed. On exit from the region the claimed interfaces will be released automatically.
You can't reference handles to alternates that have not been set.
You can't reference endpoints that don't belong to a setted alternate.
You can't read from an endpoint with an Out transfer direction.
You can't write to an endpoint with an In transfer direction.
You can't read from or write to endpoints with the unsupported transfer types Control and Isochronous. Only I/O with endpoints with the Bulk and Interrupt transfer types is allowed.
The primary technique used in usb-safe is called "Lightweight monadic regions" which was invented by Oleg Kiselyov and Chung-chieh Shan. See:
This technique is implemented in the
regions package which is
usb-safe-examples package for examples how to use this library:
For package maintainers and hackage trustees