Displaying 3 results from an estimated 3 matches for "xenidc".
2005 Nov 11
5
xen-unstable: TX/RX ring buffer exhaustion and NR_GRANT_FRAMES
Hi,
it seems as if it is not possible to have more than 3 nics per domU
right now. If I specify more, I get the usual
[...]
xen_net: Initialising virtual ethernet driver.
#### netfront can''t alloc rx grant refs
vif: probe of vif-3 failed with error -12
[...]
message - see bug #183. It was pointed out to me that it might be
possible to adjust this manually in
2005 Dec 06
4
latest USB code
...s
and it won''t be too hard to change the protocol so that the BE sends a
message to the FE to kick the FE into re-probing the BE. This will make
the BE device state machine a bit more complicated.
o - Design documentation for the USB driver is required.
o - We might not want to keep the xenidc code. API documentation for
the xenidc API is required if we are going to keep the xenidc code.
o - Isochronous URBs are untested.
o - My test machine is USB 1.2 and I''ve not yet tested with USB 2.0.
o - Suspend and resume is untested. Domain migration is untested.
o - I''ve...
2005 Nov 15
3
First post-xenbus-change USB patch
Here''s the first snapshot of the USB code after updating to the new
xenbus.
The xenidc code provides a much higher level of abstraction than the new
xenbus code so the changes didn''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 bec...