From owner-freebsd-usb@FreeBSD.ORG  Fri Aug 28 07:02:01 2009
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 697D6106568B
	for <freebsd-usb@freebsd.org>; Fri, 28 Aug 2009 07:02:01 +0000 (UTC)
	(envelope-from tlb@tlb.org)
Received: from anybots.com (mail.anybots.com [64.142.12.96])
	by mx1.freebsd.org (Postfix) with SMTP id B0B9C9052F
	for <freebsd-usb@freebsd.org>; Thu, 27 Aug 2009 22:51:44 +0000 (UTC)
Received: (qmail 45976 invoked from network); 27 Aug 2009 22:24:45 -0000
Received: from unknown (HELO ?10.10.10.66?) (10.10.10.66)
	by 10.10.10.20 with SMTP; 27 Aug 2009 22:24:45 -0000
Message-Id: <F0E9BBA5-534D-4547-B870-DB36D8444EFC@tlb.org>
From: Trevor Blackwell <tlb@tlb.org>
To: freebsd-usb@freebsd.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 27 Aug 2009 15:24:44 -0700
X-Mailer: Apple Mail (2.935.3)
Subject: VMWare USB fail
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2009 07:02:01 -0000


I'm working on a new driver for empia 28XX USB cameras, and since it  
needs isochronous support I'm upgrading to HPS's new stack. However,  
it doesn't seem to work at all under VMWare.
I'm running yesterday's checkout of RELENG_8, under VMWare Fusion  
1.1.2 on a Mac 10.5.8 host. That setup has worked well for me in the  
past developing USB drivers with the -7 kernel.

Does the fact that this shows up as ugen instead of uhub mean that it  
doesn't recognize the hub at all?

ugen0.3: <product 0x0002 vendor 0x0e0f> at usbus0, cfg=0 md=HOST  
spd=FULL (12Mbps) pwr=SAVE

   bLength = 0x0012
   bDescriptorType = 0x0001
   bcdUSB = 0x0110
   bDeviceClass = 0x0009
   bDeviceSubClass = 0x0000
   bDeviceProtocol = 0x0000
   bMaxPacketSize0 = 0x0008
   idVendor = 0x0e0f
   idProduct = 0x0002
   bcdDevice = 0x0100
   iManufacturer = 0x0000  <no string>
   iProduct = 0x0001  <VMware Virtual USB Hub>
   iSerialNumber = 0x0000  <no string>
   bNumConfigurations = 0x0001


  Configuration index 0

     bLength = 0x0009
     bDescriptorType = 0x0002
     wTotalLength = 0x0019
     bNumInterfaces = 0x0001
     bConfigurationValue = 0x0001
     iConfiguration = 0x0001  <VMware Virtual USB Hub>
     bmAttributes = 0x00e0
     bMaxPower = 0x0000

     Interface 0
       bLength = 0x0009
       bDescriptorType = 0x0004
       bInterfaceNumber = 0x0000
       bAlternateSetting = 0x0000
       bNumEndpoints = 0x0001
       bInterfaceClass = 0x0009
       bInterfaceSubClass = 0x0000
       bInterfaceProtocol = 0x0000
       iInterface = 0x0001  <VMware Virtual USB Hub>

      Endpoint 0
         bLength = 0x0007
         bDescriptorType = 0x0005
         bEndpointAddress = 0x0081
         bmAttributes = 0x0003
         wMaxPacketSize = 0x0001
         bInterval = 0x00ff
         bRefresh = 0x0000
         bSynchAddress = 0x0000

--
Trevor Blackwell		650 776 7870	tlb@tlb.org