From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jul 12 03:00:00 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B283B16A469 for ; Thu, 12 Jul 2007 03:00:00 +0000 (UTC) (envelope-from rpaulo@fnop.net) Received: from core.fnop.net (mx.fnop.net [82.102.11.82]) by mx1.freebsd.org (Postfix) with ESMTP id 29D8813C4BC for ; Thu, 12 Jul 2007 03:00:00 +0000 (UTC) (envelope-from rpaulo@fnop.net) Received: from core.fnop.net (mx.fnop.net [82.102.11.82]) by core.fnop.net (Postfix) with ESMTP id DF988690D69 for ; Thu, 12 Jul 2007 03:32:19 +0100 (WEST) Received: by core.fnop.net (Postfix, from userid 1015) id AAE61690DAB; Thu, 12 Jul 2007 03:32:19 +0100 (WEST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on core.fnop.net X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO,RCVD_IN_NJABL_DUL autolearn=no version=3.1.7 Received: from epsilon.local (87-196-146-232.net.novis.pt [87.196.146.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by core.fnop.net (Postfix) with ESMTP id 0D8E4690D69 for ; Thu, 12 Jul 2007 03:32:18 +0100 (WEST) Message-ID: <469593F2.1040703@fnop.net> Date: Thu, 12 Jul 2007 03:37:38 +0100 From: Rui Paulo User-Agent: Thunderbird 2.0.0.4 (X11/20070704) MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: HCI - HID proxy X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2007 03:00:00 -0000 Hi, For my SoC project I developed a userland utility that switches an ubt(4) controller from HID to HCI and vice versa. I have some design issues still being worked out, namely: 1) What's the best way to integrate this into the existing bluetooth utilities ? Create a new utility called, for example, ubthid2hci ? Name suggestions are welcome. 2) According to the hid2hci Linux utility, there are several dongles out there that need this tweak in order to work. I was thinking we could create a text file with the vendors/products and their bootup mode (HCI or HID); use ubthid2hci to read that file and then switch the device to HCI mode (or HID mode if the user requested it). This is mostly what the Linux hid2hci utility does, except that the vendor/product table is inside the program. 3) Fix libusb and use hid2hci on FreeBSD. Comments? Regards. -- Rui Paulo