libusb 0.6.0-x86-linux

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 8745d74ba38a4b244a0a767c9f8d8b11399cb788
+  data.tar.gz: dfbabc151f3b6098b888a3a4c616d14d4053f079
+SHA512:
+  metadata.gz: caa29ff2a44bd7d16ec6f8b66df34c3cf071b08783dc50f47476739eb18ca30cbd1c5c63c18c83f6914f5d9413c039125fcb4aed4f96420331c7ecd4c7af48f8
+  data.tar.gz: b62f5112cc342bc683e7b625e0db0bc5b50088217f504148b1ed2fffec20c2cf8d05bd6da42607df8cd8a2298441a9d1be781727c9b2aa95768c86da02ac75f9

data/.gitignore

@@ -0,0 +1,8 @@
+*.gem
+.bundle
+Gemfile.lock
+pkg/*
+lib/libusb-1.0*
+lib/pkgconfig
+include
+tmp

data/.travis.yml

@@ -0,0 +1,17 @@
+language: ruby
+sudo: false
+rvm:
+  - "1.9.3"
+  - "2.0.0"
+  - "2.1"
+  - "2.2"
+  - "2.3.1"
+  - "2.3.1-clang"
+  - jruby-1.7.26
+  - jruby-9.1.5.0
+  - rbx
+matrix:
+  allow_failures:
+    - rvm: rbx
+    - rvm: "2.3.1-clang"
+script: bundle exec rake travis

data/.yardopts

@@ -0,0 +1,6 @@
+--title "libusb-1.0 Ruby Interface"
+--no-private
+lib/**/*.rb
+-
+README.md
+History.md

data/COPYING

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/Gemfile

@@ -0,0 +1,11 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in libusb.gemspec
+gemspec
+
+group :test do
+  gem 'eventmachine'
+  gem 'minitest'
+end
+
+gem 'rake-compiler-dock', git: 'http://github.com/rake-compiler/rake-compiler-dock'

data/History.md

@@ -0,0 +1,124 @@
+0.6.0 / 2016-12-09
+------------------
+* Update bundled libusb version to 1.0.21.
+* Set minimum Ruby version requirement to 1.9.3.
+* Add binary gems for Linux in addition to Windows.
+* Switch to mini_portile2 for (cross-) builing the libusb library.
+* Add Context#interrupt_event_handler new in libusb-1.0.21
+* Add support for persistent/zerocopy device memory for transfers.
+  It is new in libusb-1.0.21 and enabled by default for DevHandle#*_transfer methods.
+* Raise a more meaningful exception in case of bulk stream transfers on too old libusb versions.
+* Prefer the bundled libusb-dll over installed system library.
+
+0.5.1 / 2015-09-29
+------------------
+* Add ability to force use of the system or builtin libusb-1.0 library.
+    Use: gem install libusb -- --enable-system-libusb / --disable-system-libusb
+* Update to libusb-1.0.20.
+* Build Windows binary gems per rake-compiler-dock.
+* Fix memory leak in Context#pollfds and use libusb_free_pollfds() if available.
+
+0.5.0 / 2015-01-08
+------------------
+* Add support for BOS describtors of libusb-1.0.16
+* Add support for superspeed endpoint companion descriptors of libusb-1.0.16
+* Add support for USB-3.0 bulk streams of libusb-1.0.19
+* Update bundled libusb version to 1.0.19.
+* Update windows cross build to gcc-4.8 and recent rubygems
+
+0.4.1 / 2014-05-17
+------------------
+* Update bundled libusb version to 1.0.18.
+* Change libusbx references back to libusb, since they have merged again.
+
+0.4.0 / 2013-11-20
+------------------
+* Add support for device hotplug notifications.
+* Update to libusbx-1.0.17.
+* Add DevHandle#auto_detach_kernel_driver= of libusb-1.0.16.
+* Add new capabilities introduced with libusb-1.0.16.
+* Offer #has_capability? for libusb versions older than 1.0.9.
+* Add new method port_numbers with alias to port_path.
+* Use libusb_get_port_numbers preferred to now deprecated libusb_get_port_path.
+
+0.3.4 / 2013-04-05
+------------------
+* Avoid closing of pollfds by the Ruby GC when used as IO object.
+
+0.3.3 / 2013-04-05
+------------------
+* Build and package binary x64 version of libusb for Windows in addition to x86.
+* Fix build on Windows from source gem (although may take almost an hour).
+
+0.3.2 / 2013-02-16
+------------------
+* Don't enforces DevKit installation on Windows.
+* Fix error check on libusb_get_device_list(). Thanks to Paul Kunysch for the bug report.
+* Add support for Cygwin. Requires ffi-1.4.0.
+
+0.3.1 / 2013-01-22
+------------------
+* Fix loading of compiled libusb library on OSX
+
+0.3.0 / 2013-01-21
+------------------
+* Build bundled libusbx sources in case libusb-1.0.so can not be loaded from the system
+* Replace Hoe with Bundler
+* Add timeout and completion_flag to Context#handle_events
+* Add asynchronous DevHandle#{control|interrupt|bulk}_transfer method variants
+* Add the ability to retrieve the data already transfered when it comes to an exception
+* Add notification API for libusb's file describtors for event driven USB transfers
+* Add experimental integration to EventMachine
+* Add several convenience methods to descriptors
+* Add missing return code checks to libusb_init() and libusb_get_device_list()
+
+0.2.2 / 2012-10-19
+------------------
+* Add method Interface#bInterfaceNumber
+* Fix methods (#claim_interface, #detach_kernel_driver) with Interface-type parameter
+* update to libusbx-1.0.14 for windows build
+
+0.2.1 / 2012-09-25
+------------------
+* Rename Configuration#maxPower to #bMaxPower as done in libusbx-1.0.13 and in ruby-usb.gem
+* update to libusbx-1.0.13 for windows build (with support for libusbK and libusb0)
+
+0.2.0 / 2012-06-15
+------------------
+* Divide up the libusb library across multiple files, required with autoload
+* add methods: LIBUSB.has_capability?, Device#device_speed (libusb-1.0.9+)
+* add possibility to read out libusb version: LIBUSB.version (libusbx-1.0.10+)
+* add methods: Device#parent, Device#port_number, Device#port_path (libusbx-1.0.12+)
+* switch to libusbx-1.0.12 for windows build
+
+0.1.3 / 2012-03-15
+-------------------
+* Add documentation of descriptor accessors
+* Fix #extra accessor of Configuration, Setting and Endpoint
+
+0.1.2 / 2012-03-14
+------------------
+* Mark all blocking functions as blocking in FFI, so that parallel threads are not blocked
+* Add method Device#open_interface
+* Add block variant to #claim_interface
+* update API documentation
+
+0.1.1 / 2011-12-09
+------------------
+* avoid ffi calls with :blocking=>true, als long as it isn't stable on win32
+
+0.1.0 / 2011-10-01
+------------------
+* add test suite based on mass storage devices
+* usable async transfers
+* migration to rake-compiler and hoe
+* cross compiled Windows gems
+* distinct exception classes
+* new compatibility layer for ruby-usb.gem
+* many helper methods for different USB descriptors
+* add LIBUSB constants
+* downcase methods names
+
+0.0.1 / 2009-06-23
+------------------
+* first public release

data/README.md

@@ -0,0 +1,159 @@
+<!-- -*- coding: utf-8 -*- -->
+
+[![Build Status](https://travis-ci.org/larskanis/libusb.svg)](https://travis-ci.org/larskanis/libusb)
+[![Build Status](https://ci.appveyor.com/api/projects/status/mdfnfdwu4mil42o3?svg=true)](https://ci.appveyor.com/project/larskanis/libusb)
+
+Access USB devices from Ruby
+============================
+
+LIBUSB is a Ruby binding that gives Ruby programmers access to arbitrary USB devices.
+
+* [libusb](http://libusb.info) is a library that gives full access to devices connected via the USB bus. No special kernel driver is thus necessary for accessing USB devices.
+* This Ruby binding supports the API version 1.0 of [libusb](http://libusb.info). Note that the old "legacy" version 0.1.x of libusb uses a completely different API that is covered by the ruby extension [ruby-usb](http://www.a-k-r.org/ruby-usb/) .
+
+
+LIBUSB for Ruby is covered by the GNU Lesser General Public License version 3.
+
+Features
+--------
+
+* Access to descriptors of devices, configurations, interfaces, settings and endpoints
+* Synchronous and asynchronous communication for bulk, control, interrupt and isochronous transfers
+* Support for USB-3.0 descriptors and bulk streams
+* Compatibility layer for [ruby-usb](http://www.a-k-r.org/ruby-usb/) (API based on libusb-0.1). See {::USB} for description.
+
+Synopsis
+--------
+```ruby
+require "libusb"
+
+usb = LIBUSB::Context.new
+device = usb.devices(idVendor: 0x04b4, idProduct: 0x8613).first
+device.open_interface(0) do |handle|
+  handle.control_transfer(bmRequestType: 0x40, bRequest: 0xa0, wValue: 0xe600, wIndex: 0x0000, dataOut: 1.chr)
+end
+```
+{LIBUSB::Context#devices} is used to get all or only particular devices.
+After {LIBUSB::Device#open_interface opening and claiming} the {LIBUSB::Device} the resulting {LIBUSB::DevHandle} can be
+used to communicate with the connected USB device
+by {LIBUSB::DevHandle#control_transfer}, {LIBUSB::DevHandle#bulk_transfer},
+{LIBUSB::DevHandle#interrupt_transfer} or by using the {LIBUSB::Transfer} classes.
+
+A {LIBUSB::Device} can also be used to retrieve information about it,
+by using the device descriptor attributes.
+A {LIBUSB::Device} could have several configurations. You can then decide of which
+configuration to enable. You can only enable one configuration at a time.
+
+Each {LIBUSB::Configuration} has one or more interfaces. These can be seen as functional group
+performing a single feature of the device.
+
+Each {LIBUSB::Interface} has at least one {LIBUSB::Setting}. The first setting is always default.
+An alternate setting can be used independent on each interface.
+
+Each {LIBUSB::Setting} specifies it's own set of communication endpoints.
+Each {LIBUSB::Endpoint} specifies the type of transfer, direction, polling interval and
+maximum packet size.
+
+See [the documentation](http://rubydoc.info/gems/libusb/frames) for a full API description.
+
+Prerequisites
+-------------
+
+* Linux, MacOS or Windows system with Ruby MRI 1.9/2.x, JRuby or recent version of Rubinius
+* Optionally: [libusb](http://libusb.info) C-library version 1.0.8 or any newer version.
+  The system libusb library can be installed like so:
+  * Debian or Ubuntu:
+
+      ```
+      $ sudo apt-get install libusb-1.0-0-dev
+      ```
+  * MacOS: install with homebrew:
+
+      ```
+      $ brew install libusb
+      ```
+    or macports:
+
+      ```
+      $ port install libusb
+      ```
+  * Windows: libusb.gem already comes with a precompiled `libusb.dll`, but you need to install a device driver (see [below](#usage-on-windows))
+
+Install
+-------
+
+    $ gem install libusb
+
+While ```gem install``` the system is checked for a usable libusb library installation.
+If none could be found, a bundled libusb version is built and used, instead.
+
+Latest code can be used in this way:
+
+    $ git clone git://github.com/larskanis/libusb.git
+    $ bundle
+    $ rake install_gem
+
+Troubleshooting
+------------------------
+In order to implement a driver for a USB device, it's essential to have a look at the packets that are send to and received back from the USB device. [Wireshark](https://www.wireshark.org) has builtin capabilities to sniff USB traffic. On Linux you possibly need to load the usbmon kernel module before start:
+```
+    sudo modprobe usbmon
+```
+On Windows it's possible to sniff USB, if the USB kernel driver was installed by the Wireshark setup.
+
+![Wireshark](wireshark-usb-sniffer.png?raw=true "Wireshark sniffing USB packets")
+
+Device hotplug support
+----------------------
+
+Support for device hotplugging can be used, if ```LIBUSB.has_capability?(:CAP_HAS_HOTPLUG)``` returns ```true```.
+This requires libusb-1.0.16 or newer on Linux or MacOS. Windows support is [still on the way](https://github.com/libusbx/libusbx/issues/9).
+
+A hotplug event handler can be registered with {LIBUSB::Context#on_hotplug_event}.
+You then need to call {LIBUSB::Context#handle_events} in order to receive any events.
+This can be done as blocking calls (possibly in it's own thread) or by using {LIBUSB::Context#pollfds} to
+detect any events to handle.
+
+
+Usage on Windows
+----------------
+
+In contrast to Linux, any access to an USB device by LIBUSB on Windows requires a proper driver
+installed in the system. Fortunately creating such a driver is quite easy with
+[Zadig](http://zadig.akeo.ie/). Select the interesting USB device,
+choose WinUSB driver and press "Install Driver". That's it. You may take the generated output directory
+with it's INI-file and use it for driver installations on other 32 or 64 bit Windows
+systems.
+
+
+Cross compiling for Windows
+---------------------------
+
+Libusb-gem can be cross built for Windows and Linux operating systems, using the [rake-compiler-dock](https://github.com/larskanis/rake-compiler-dock) .
+Just run:
+
+    $ rake gem:native
+
+If everything works, there are several platform specific gem files (like `libusb-VERSION-x64-mingw32.gem`) in the pkg
+directory.
+
+EventMachine integration
+------------------------
+
+Libusb for Ruby comes with an experimental integration to [EventMachine](http://rubyeventmachine.com/).
+That API is currently proof of concept - see {LIBUSB::Context#eventmachine_register}.
+If you're experienced with EventMachine, please leave a comment.
+
+
+Resources
+---------
+
+* Project's home page: http://github.com/larskanis/libusb
+* API documentation: http://rubydoc.info/gems/libusb/frames
+* Mailinglist: http://rubyforge.org/mailman/listinfo/libusb-hackers
+* Overall introduction to USB: http://www.usbmadesimple.co.uk
+
+Todo
+----
+
+* stabilize EventMachine interface