In USB, the interface and endpoint descriptors, and possibly other vendor-specific descriptors, are nested inside the configuration descriptors. This makes it possible to retrieve the complete information about a configuration in one single call. Our drivers do this, and so does libusb (the Device Kit doesn't, it only cares about individual descriptors and does not provide access to the vendor-specific ones). The driver did not expose the full descriptor, only the part that belongs strictly to the configuration. libusb worked around this by getting the descriptor from the device directly, using a control transfer. This should be ok, but apparently some devices get confused when you do this too often or at unexpected times. These changes introduce a variation of the GET_CONFIGURATION_DESCRIPTOR ioctl that allows the caller to specify a size. This way, one can get the complete descriptor (after getting the configuration-only part to figure out the size needed, most likely). The data is copied from structures stored by the driver, so no further communication with the device is necessary, making this safe to the problems mentioned above, and faster. Change-Id: Id97e40ea0d45b8c051ae8548486c4751fc6aad2a Reviewed-on: https://review.haiku-os.org/453 Reviewed-by: Jérôme Duval <jerome.duval@gmail.com>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.