log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> ___
> linux-usb-devel@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourcef
On Thu, 2005-12-08 at 16:44 -0800, Greg KH wrote:
> On Thu, Dec 08, 2005 at 11:20:35AM -0500, Alan Stern wrote:
> > Part of the problem is that the stub drivers on the back-end are forced to
> > bind to USB interfaces instead of USB devices. It would make life simpler
> > for you guys if the stub
On Thu, 2005-12-08 at 13:53 -0500, Alan Stern wrote:
> On Thu, 8 Dec 2005, Harry Butterworth wrote:
>
> > > I'm not sure what you mean by that. Do you _want_ to virtualize power
> > > management operations?
> >
> > I want to do the minimum amount of wo
On Thu, 2005-12-08 at 10:20 -0500, Alan Stern wrote:
> On Wed, 7 Dec 2005, Harry Butterworth wrote:
>
> > > Suspend/resume is liable to cause trouble. For instance, what happens to
> > > the various front-ends if the back-end decides to suspend a USB device?
> >
the HUB to each of four guest domains.
Any device plugged into the port mapped to a given guest domain will
appear attached to a port on the virtual USB controller in the guest
domain.
USB devices in domain zero are just driven by the normal USB driver
code. My split driver is not involved. Sorr
he back-end decides to suspend a USB device?
I don't know. Could you explain this scenario in more detail (imagine
that none of the 800 page USB spec sunk in when I read it :-). What
should happen in this case?
--
Harry Butterworth <[EMAIL PROTECTED]>
