Displaying 3 results from an estimated 3 matches for "xenidc_endpoint".
2005 Nov 21
1
[PATCH][7/17] USB virt 2.6 split driver---gnttab channel
This patch implements the xenidc_channel interface using grant tables
but leaves the channel bring-up and tear-down sequencing to a derived
class (xenidc_gnttab_channel implements that). This code is part of the
implementation of the xenidc_endpoint used for interdomain communication
by the USB driver.
Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2005 Nov 30
0
[PATCH][14/17] REV 2 USB virt 2.6 split driver---USB interdomain protocol
...the last four patches are
reformatted and I''m able to test the code again. These fixes will go
into the correct patches if I do another revision.
Aside from the fixes, this patch defines the USB interdomain protocol
which consists of a number of transactions and a message sent using the
xenidc_endpoint code.
This protocol is a direct translation of the 2.4 protocol and uses
polling for device detection.
There is an issue with queued commands during error recovery. The
queued commands need to be stalled during the unlink process but
currently they are not.
Both the polling and the queued comma...
2005 Nov 15
3
First post-xenbus-change USB patch
...9;'t affect the usb driver much.
I had to put in empty frontend_changed and backend_changed functions
because the new xenbus code segfaults without them. The USB code
doesn''t need them because the entire state machine and all associated
ring/shared page setup is factored out into the xenidc_endpoint object
and the driver code gets connect and disconnect callbacks from the
endpoint instead.
I''d like the otherend_changed entrypoint to be optional please. This
will also let me remove the MixedCaps XenbusState typename from my
code :-)
I took the opportunity to implement suspend and re...