From owner-freebsd-usb@FreeBSD.ORG Fri Aug 28 07:30:41 2009 Return-Path: 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 A8BC01066CD2 for ; Fri, 28 Aug 2009 07:30:41 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id A883090554 for ; Fri, 28 Aug 2009 07:11:46 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=s3R5Xy8iAAAA:8 a=gmsw_GjgWQwsxR4nwQoA:9 a=sEQU4H-cGpMf8JiO81c-XK5iNZoA:4 a=nXJSi8zRXSkA:10 a=HMEDajeASh8A:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe08.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1295460115; Fri, 28 Aug 2009 09:11:28 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 28 Aug 2009 09:11:44 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908280911.45358.hselasky@c2i.net> Cc: Subject: Re: VMWare USB fail X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2009 07:30:48 -0000 On Friday 28 August 2009 00:24:44 Trevor Blackwell wrote: > 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? > The new kernel presents an ugen device for all devices present in the system. There should be a uhub device associated with your ugen device! You could turn on uhub debugging if in doubt: sysctl hw.usb.uhub.debug=15 --HPS > ugen0.3: 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 > iProduct = 0x0001 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0019 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x0001 > bmAttributes = 0x00e0 > bMaxPower = 0x0000 > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0001 > bInterfaceClass = 0x0009 > bInterfaceSubClass = 0x0000 > bInterfaceProtocol = 0x0000 > iInterface = 0x0001 > > 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 >