From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 7 23:07:55 2008 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A43551065673 for ; Wed, 7 May 2008 23:07:55 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 33E218FC16 for ; Wed, 7 May 2008 23:07:55 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A550B9.dip.t-dialin.net [84.165.80.185]) by redbull.bpaserver.net (Postfix) with ESMTP id 7AF482E163; Thu, 8 May 2008 01:07:49 +0200 (CEST) Received: from deskjail (unknown [192.168.1.109]) by outgoing.leidinger.net (Postfix) with ESMTP id A8AAE1022FA; Thu, 8 May 2008 01:07:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1210201666; bh=UldtfPmY3+USbRk656kvyXkg2QyuKM0Tp c/JZAW0k1g=; h=Date:From:To:Subject:Message-ID:In-Reply-To: References:Mime-Version:Content-Type:Content-Transfer-Encoding; b=3Ud9n9jp1U9G9wwk8M/auq/Ngp/lu8Q5bEQudE+4uybU3XTW9tMHrptTX5+JAL8Rk ANkhNfiFpX6v2iF9k9nP5jOUB5T+nlE+Q7nZdxlW1HvtTzl7T1Ev7ZPRtul2kMwNXMn hEd1k6uj10Lgg7zG9HFGYFqHTG0W6G2rfryYN8m4XOzJi+QW+ESOvtRIzxuPXCdxvG6 qtqJiRWglH7Z0uN5rP/uYvoe95wdBEOwJbfhMtPkt0RCEVwTFAJwjQ5yaHatBy3+Nqp xx9gG/8qfutNyFZtA6Me2WxffBd4jkfADO3E/TcQ8/Q6qrfjipqeR7ZoexnmzGNl7JB HyyuHN59Q== Date: Thu, 8 May 2008 01:07:46 +0200 From: Alexander Leidinger To: "Maksim Yevmenkin" , bluetooth@freebsd.org Message-ID: <20080508010746.0388b146@deskjail> In-Reply-To: References: <20080507192434.32afce8b@deskjail> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i686-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.323, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, NO_RDNS 0.50, RDNS_DYNAMIC 0.10, TW_KB 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: Subject: Re: Fun with Logitech bluetooth keyboard (diNovo Edge)... 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: Wed, 07 May 2008 23:07:55 -0000 Quoting "Maksim Yevmenkin" (Wed, 7 May 2008 13:05:02 -0700): > On Wed, May 7, 2008 at 10:24 AM, Alexander Leidinger > wrote: > > Hi, > > > > I bought a keyboard with an integrated touchpad from logitech. Just > > plugging in the BT-dongle gives an usb hub with ums and ukbd. > > Unfortunately the ums doesn't work for me yet (problem in a separate > > mail to usb@). > > > > I googled a litte bit around and found a posting here > > (http://lists.freebsd.org/mailman/htdig/freebsd-bluetooth/2006-December/000824.html) > > which contains a program which puts the device into hci mode (by > > accessing /dev/uhidX), so that I can use the HID devices with the > > FreeBSD bluetooth stack directly. I haven't tried this yet (I would > > have to remove ukbd and ums from the kernel...). > > > > Is there the possibility to get this hid2hci feature in our userland > > (or into the kernel controllable via a sysctl)? I would would be good > > to have this functionality at boot (in the kernel it would would allow > > to have ukbd available while still being able to put the device into > > hci mode). > > well, someone already ported hid2hci. > > http://lists.freebsd.org/pipermail/freebsd-bluetooth/2007-July/000989.html > > is a good starting point. i do not think that using sysctl is good It doesn't make sense to have something like this in the base system? > solution for this. last time i looked this stuff was implemented on > csr chips using so-called "boot mode" feature. basically, the device > has a split personality - in one mode it pretends to be an usb hub > with keyboard and mouse attached (hid) to it and in another - > bluetooth dongle (hci). to switch between the modes one must set a > so-called ps key and perform warm reset. > > the problems are > > 1) this is highly device specific > > 2) there is no good way to know if device can be switched between hid > and hci. it is basically left to user to know that. There's no way to know this based upon some vendor/product IDs? > 3) usually hid mode is made default, so device has to be switched into > hci mode every time it is attached. > > the hid mode is really for user's advantage. its makes it possible to > use wireless keyboards in bios screens etc. os does not need to know Yes, I understand that, the problem is: the ums part does not work for me (8-current from March). > anything about bluetooth. all that is required from the os is usb > support. while i do not object to hid2hci utility, personally, i would > get a separate bluetooth dongle for another $20 or less. I have a separate dongle, but having a second one (the logitech one) would not be bad. We just need a way to say "I want this to be a hci device when I plug it in automatically". Bye, Alexander. -- Fry: I'm not a robot like you. I don't like having disks crammed into me... unless they're Oreos, and then only in the mouth. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137