El 24/09/15 a les 00:05, Olaf Buddenhagen ha escrit:
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...
If someone implements a libusb backend for Rump, I think upstream will be
more than happy to accept it.
On my experience, Rump upstream is demanding in terms of code quality, but
very friendly and always open to discuss things.
--
Robert Millan
