do not create a virtual host controller, just write your own hub driver.
that way you do not have to deal with reverse engineering an interface
between the port and miniport, you just have to implement the public URB
interface and all of the various IOCTLs and QIs. no small task either
though.
d
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"anshul makkar" <> wrote in message
news:a9ae2b39-c5b8-4883-9aaf-...
> Hi,
>
> As per the documentation available (a single PDF file) to implement
> USBOIP we have to implement a virtual host controller driver .
>
> - Virtual Host control driver will be equivalent to USB Host
> Controller driver and will be responsible for handling of URBs.
> - USBs will be converted to USB/IP packets and sent to remote machine
> - At remote machine another application will extract URBs from USB/IP
> packets and submit them to local USB drivers.
>
> Now according to earlier postings and other documentation , Microsoft
> does not provide any support / documentation for writing host
> controller driver. I may have to do lot of reverse enginnering to
> decipher the functionality of USB Host Controller driver.
>
> So just wondering whethe the above design approach will be correct,
> considering lack of support/documentation from Microsoft.
>
> Is there any other design approach that can be suitable ?
>
> Please share your views and experiences.
>
> --
> Thanks
> Anshul Makkar
> justkernel.com
>