Comments (6)
This is Windows implementation of usbipd which is not canonical. In my project I'm considering Linux compatibility only. This project is abandoned defacto.
from usbip-win.
Linux 'usbip bind' uses --busid only, as well as 'usbip attach'. pid/vid is not unique.
from usbip-win.
See also https://github.com/torvalds/linux/blob/master/tools/usb/usbip/src/usbip_network.h#L62,
from usbip-win.
@vadimgrn Thanks for taking the time to provide such an interesting & on-point response
In response, I wonder why usbipd allows binding by VID if it's possible for a "non-unique" exception to be raised on the host side as well, in theory?
So I still find this inconsistency between the client and host to be strange, and I still maintain that it would be a convenient feature to allow binding by VID on the client side. If there are more than 1 device with the same VID, the client could just throw an error. But if there's one device that matches, I don't see why the method can't be used, as it would save more trouble than it causes (you have to ask yourself: how common is it to explicitly bind several devices with the same VID on the host side?). Only in special cases where the host is binding several devices with the same VID (relatively rare occurence), should the client need to take special care about which BUS ID has a specific device. For every other case (which I imagine is over 90% of use cases), people will need to forward a single device only (and even if more than one device, chances are they have different VIDs), in which case VID matching would make a lot more sense
But yes, ideally the patch would then be applied upstream at the linux codebase first... So I guess it's up to this project's maintainers to decide if an exception should be made for the windows version or not...
In the meanwhile, I guess I'll just need to create a script that does the matching externally, from usbip list
output.
Cheers for now & thanks again.
from usbip-win.
I do not understand where did you get info about support for bind or attach by VID?
Kernel 6.2.0-26-generic
~$ usbip bind -h
usage: usbip bind <args>
-b, --busid=<busid> Bind usbip-host.ko to device on <busid>
vadym@pc:~$ usbip attach -h
usage: usbip attach <args>
-r, --remote=<host> The machine with exported USB devices
-b, --busid=<busid> Busid of the device on <host>
-d, --device=<devid> Id of the virtual UDC on <host>
from usbip-win.
I do not understand where did you get info about support for bind or attach by VID? Kernel 6.2.0-26-generic
C:\WINDOWS\system32>usbipd bind --help
usbipd-win 2.4.1
Description:
Registers a single USB device for sharing, so it can be attached to other machines. Unless the --force option is
used, shared devices remain available to the host until they are attached to another machine.
Exactly one of the options '--busid' or '--hardware-id' is required.
Usage:
usbipd bind [options]
Options:
-b, --busid <BUSID> Share device having <BUSID>
-f, --force Force binding; the host cannot use the device
-i, --hardware-id <VID:PID> Share device having <VID>:<PID>
-?, -h, --help Show help and usage information
note the -i
parameter (which, by the way, works exactly as expected on the host side). But yeah this is for usbipd-win
(https://github.com/dorssel/usbipd-win) so I just assumed it was the same on linux side... It should be, anyway.
from usbip-win.
Related Issues (20)
- install usbip vhci driver cause a BSOD HOT 2
- how to use usb device that is redirected from server to client HOT 5
- usbip work normally in WLAN? HOT 1
- About debug in VS2019
- USB microphone does not work (does not transmit a signal). USB flash works
- is it possible to use usbip inside a remote desktop session together with a wacom tablet?
- failed to attach, code:-6 HOT 1
- usbip:error:attacher.exe not found
- Device shows up on client, but stops working after attached HOT 1
- Xbox Wireless Adapter for Windows Attaches but unable to associate controller HOT 11
- python hid.py usbip.py
- Driver signing / Microsoft
- Merge in upstream?
- Confused about the notes on release usbip-win 0.3.6-dev HOT 1
- Unable to Bind More Than 12 USB Devices Using USB IP Solution
- Device from Linux server on Windows client disconnects after 3 seconds
- USBIP error on attach with: usbip: error: failed to attach on client and usbipd: info: request 0x8003(5): failed on server
- Camera issues HOT 3
- Device is "Unstably bound"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from usbip-win.