[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] anyone using pvusb?



> 
>  >> Bus 001 Device 006: ID 0204:6025 Chipsbank Microelectronics Co.,
Ltd
>  > CBM2080
>  >> Flash drive controller
>  >> Device Descriptor:
>  >>   bLength                18
>  >>   bDescriptorType         1
>  >>   bcdUSB               1.10
>  >
>  > For some reason the device has booted up as USB 1.10 instead of USB
>  > 2.00. It didn't work any better when it booted as USB 2.00 though.
> 
> I want to confirm. Does this device surely work properly
> on Dom0 kernel (w/o pvusb)?
> 

Yes, it works perfectly, even without a reboot since trying to use it
with pvusb

On the Intel machine that I'm testing with now, I do this to use it with
pvusb:

# Set some variables
device_id="1-4:1.0"
bus_id=`echo $device_id | sed 's/:.*//'`
domid=`xm domid $1`

# unlink all devices from any currently bound vports
cat /sys/bus/usb/drivers/usbback/vports | while read port
do
  echo "$port" >/sys/bus/usb/drivers/usbback/remove_vport
done

# set vport
echo "$bus_id:$domid:0:1" >/sys/bus/usb/drivers/usbback/new_vport

# call provided init script
~/usb_init_xs.sh $domid 0

# wait for a bit
echo waiting
sleep 5

# unbind device from whatever it is currently bound to (usb-storage in
this case) then wait a bit more
echo unbind
echo -n "$device_id" >/sys/bus/usb/devices/$device_id/driver/unbind
sleep 5

# bind the device to usbback
echo bind
echo -n "$device_id" >/sys/bus/usb/drivers/usbback/bind



after that, I unbound the device from usbback and re-bound it to
usb-storage and mounted the filesystem.

Have you been able to test with 3.4.1 or 3.4-testing yet?

Thanks

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.