From owner-freebsd-arm@FreeBSD.ORG Sun Apr 12 00:07:03 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27E44890 for ; Sun, 12 Apr 2015 00:07:03 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id 122C8A75 for ; Sun, 12 Apr 2015 00:07:02 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id 487CA1A929AD for ; Sat, 11 Apr 2015 17:07:02 -0700 (PDT) Date: Sat, 11 Apr 2015 17:06:32 -0700 (MST) From: SvenB To: freebsd-arm@freebsd.org Message-ID: <1428797192241-6004458.post@n5.nabble.com> In-Reply-To: <04cf01d070f0$6f993d40$4ecbb7c0$@polycoresoftware.com> References: <04cf01d070f0$6f993d40$4ecbb7c0$@polycoresoftware.com> Subject: Re: Bluetooth on the Wandboard Quad MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2015 00:07:03 -0000 Hello, Some additional information on this topic. The IOGEAR Bluetooth 4.0 USB Micro Adapter GBU521W6, works fine when plugged into USB2 on amd64 both server and VM client, both 10.1. It doesn't work when plugged into USB3 on the server (10.1) or the Wandboard (11.0 current) USB host connector (not sure if USB3, the plastic inside is blue). Below is some information on the various setups. Any advice on how to get it working on the Wandboard, or information on alternative bluetooth adapter that works with the Wandboard would be appreciated. It's a Wandboard-Quad. Regards, Sven ================================================ Server FreeBSD 10.1-RELEASE-p11, amd64 USB2 connector (the bluetooth adapter works in this setup): # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (100mA) ugen3.4: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen3.5: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) # usbconfig -d ugen3.5 dump_device_desc ugen3.5: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0a5c idProduct = 0x21e8 bcdDevice = 0x0112 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <000272D69EE6> bNumConfigurations = 0x0001 USB3 connector (the bluetooth adapter DOESN'T work in this setup): # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.3: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (100mA) ugen3.4: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) The device is not recognized when plugged into USB3 connector ================================================ VM running on amd64 USB2 Hub (the bluetooth adapter works in this setup): # usbconfig -d ugen0.4 dump_device_desc ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0a5c idProduct = 0x21e8 bcdDevice = 0x0112 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <000272D69EE6> bNumConfigurations = 0x0001 ================================================ Wandboard USB3? connector (not sure if it is 3, but the platic in the connector is blue) (the bluetooth adapter DOESN'T work in this setup): # usbconfig -d ugen1.2 dump_device_desc ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x0001 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0a5c idProduct = 0x21e8 bcdDevice = 0x0112 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Console output whe the bt adapter is plugged in: ugen1.2: at usbus1 ubt0: on usbus1 WARNING: attempt to domain_add(netgraph) after domainfinalize() ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=10 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=12 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=11 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ng_hci_process_event: ubt0hci - got HCI event=0xe, length=4 ubt0: ubt_ctrl_write_callback:780: control transfer failed: USB_ERR_IOERROR ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x13. Timeout -- View this message in context: http://freebsd.1045724.n5.nabble.com/Bluetooth-on-the-Wandboard-Quad-tp6003976p6004458.html Sent from the freebsd-arm mailing list archive at Nabble.com.