Hi, On Sat, Sep 19, 2015 at 10:52:13AM +0200, Robert Millan wrote:
> Since you most likely want to provide multiplexing, authorisation, > etc, to any application who wants to access USB, I wouldn't recommend > to lump USB mass storage and *HCI in the same Rump instance. Quite frankly, I wouldn't either :-) It just sounded like Bruno wanted to go with such a simplistic approach for the start... > Instead, you could run a Rump instance with USB mass storage only > which uses libusb as backend rather than its own *HCI driver (but that > requires some coding work as it's currently not implemented ;-)) Yeah, I guess that's the price to pay if we want a properly layered driver stack based on an originally monolithic implementation :-) As long as we don't need to jump through hoops to achieve that (and it gets upstream support), I'd say it's worth the effort... -antrik-
