WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-users] RE: USB floppy issue in Xen 3.4

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "'xen-users@xxxxxxxxxxxxxxxxxxx'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: USB floppy issue in Xen 3.4
From: "Patro, Sumant" <Sumant.Patro@xxxxxxx>
Date: Wed, 27 May 2009 16:12:34 -0600
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Wed, 27 May 2009 15:13:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8194F90CDF4194468A47F48BF8632B38AB1E5643@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnVbXxqYK9D8I7ZSO2NVdJgoCEhSAAHFz7gAmMSFTA=
Thread-topic: USB floppy issue in Xen 3.4
Hello,

        I tried with the below patch to access the USB floppy in GOS. With this 
patch, the yellow bang in Device Manager does not appear, however, the device 
(a:) is not shown by the Windows Guest.

        Any pointers on what could be wrong or workaround to access the USB 
floppy ?

Regards,

Sumant

diff --git a/hw/usb-uhci.c b/hw/usb-uhci.c
index d42d394..70ed338 100644
--- a/hw/usb-uhci.c
+++ b/hw/usb-uhci.c
@@ -794,7 +794,7 @@ static int uhci_handle_td(UHCIState *s, uint32_t addr, 
UHCI_TD *td, uint32_t *in
     if (!async)
         return 1;
 
-    async->valid = 10;
+    async->valid = 32;
     async->td    = addr;
     async->token = td->token;
 
diff --git a/hw/usb.c b/hw/usb.c
diff --git a/usb-linux.c b/usb-linux.c
index 5dfed8c..f8046ba 100644
--- a/usb-linux.c
+++ b/usb-linux.c
@@ -144,6 +144,10 @@ static int is_isoc(USBHostDevice *s, int ep)
 {
     return s->endp_table[ep - 1].type == USBDEVFS_URB_TYPE_ISO;
 }
+static int is_intr(USBHostDevice *s, int ep)
+{
+    return s->endp_table[ep - 1].type == USBDEVFS_URB_TYPE_INTERRUPT;
+}
 
 static int is_halted(USBHostDevice *s, int ep)
 {
@@ -274,7 +278,6 @@ static void async_complete(void *opaque)
                 if (aurb->urb.type == USBDEVFS_URB_TYPE_CONTROL)
                     async_complete_ctrl(s, p);
                 break;
-
             case -EPIPE:
                 set_halt(s, p->devep);
                 /* fall through */
@@ -472,6 +475,9 @@ static int usb_host_handle_data(USBHostDevice *s, USBPacket 
*p)
         urb->flags    = USBDEVFS_URB_ISO_ASAP;
         urb->number_of_packets = 1;
         urb->iso_frame_desc[0].length = p->len;
+    } else if (is_intr(s, p->devep)) {
+        /* Setup interrupt transfer */
+        urb->type     = USBDEVFS_URB_TYPE_INTERRUPT;
     } else {
         /* Setup bulk transfer */
         urb->type     = USBDEVFS_URB_TYPE_BULK;





-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Patro, Sumant
Sent: Friday, May 15, 2009 11:50 AM
To: xen-devel@xxxxxxxxxxxxxxxxxxx; 'xen-users@xxxxxxxxxxxxxxxxxxx'
Subject: [Xen-devel] USB floppy issue in Xen 3.4

Hello,

        I want to access USB floppy from HVM guest (Windows, Linux) using Xen 
3.4. I checked with the version 3.4.0-rc4-pre. I have tried with USB floppy 
drives from three different vendors. The device is not accessible in both 
Windows and Linux.
 
        I have usb and usbdevice entry in the HVM config file. The device is 
listed in Windows Device Manager with a yellow bang. In RHEL 5.3 guest lsusb 
displays it, but is not associated with a device name. The same device works 
fine in Xen 3.3.
     
      Is there any workaround/fix for this in Xen 3.4?

Regards,

Sumant

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

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

<Prev in Thread] Current Thread [Next in Thread>