From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 19 19:10:29 2011 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FB40106566B for ; Wed, 19 Jan 2011 19:10:29 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 181828FC17 for ; Wed, 19 Jan 2011 19:10:28 +0000 (UTC) Received: by iwn39 with SMTP id 39so1151242iwn.13 for ; Wed, 19 Jan 2011 11:10:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=93tf8hqvdGLkDXLPbcW55hgp8dxBdYznUMhz16OReFg=; b=Jg8j68gKqRhLDGCXpDFT5cxAVv8FWluSdPkRkWl/TSVwYB/Lju4Q9pxSTT0b1K4+JL 36XCcZ6nZM7pHsgLkjOAh0iLVMWStEFFi1Ud5n4ankpS8R0BcuLQFLBsuxpHT1c/1qRm nZ+Ebd9MHZl1bY2oF4obQAbbSADk8elxr6Lq0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Jai4/19TIVSoh62bCgHYfL86laoYGbIIBideDOxD05Q86mdNJI4jKb55Q7J/0Xbahr uFbzGNsAFLypJEX3c4nIh6a82eF5zjtei3+ttKvePt0edF1csDMctlMx9wyNILLqeL/O y/LFdm9tjngT9mOXDgh1a3ksunhFU0xZ+4p/8= MIME-Version: 1.0 Received: by 10.231.11.200 with SMTP id u8mr1291915ibu.151.1295464228197; Wed, 19 Jan 2011 11:10:28 -0800 (PST) Received: by 10.231.206.5 with HTTP; Wed, 19 Jan 2011 11:10:28 -0800 (PST) In-Reply-To: <4D372C27.3040606@gmail.com> References: <4D36ED39.7070807@gmail.com> <4D372C27.3040606@gmail.com> Date: Wed, 19 Jan 2011 11:10:28 -0800 Message-ID: From: Maksim Yevmenkin To: David Demelier Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth mouse does not connect after reboot 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, 19 Jan 2011 19:10:29 -0000 On Wed, Jan 19, 2011 at 10:23 AM, David Demelier wrote: > It works ! In fact I didn't need to press the connect the button, only > moving it or clicking. It was easier than I tought. Thanks. great. glad to hear this :) > I'm just guessing, there is two more logical buttons in the wheel > (backward/forward) that are not understood by bthidd. > > Is this a bthidd limitation? > > [..snip..] > Input id=2 size=1 count=1 page=Button usage=Button_7 Variable, logical > range 0..1 > Input id=2 size=1 count=1 page=Button usage=Button_8 Variable, logical > range 0..1 > Input id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative, > logical range -2047..2047 > Input id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative, > logical range -2047..2047 > Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable > Relative, logical range -127..127 > Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, > logical range -127..127 > End collection > > I think it should be the button 7 and 8 that are not usable. bthidd(8) has little to do with it. what bthidd(8) does is simply receives hid reports from the device, decodes hid reports according to the provided hid descriptor, and, feeds those events to kernel. freebsd syscons(4) relies heavily on moused(8) to handle things like double clicks etc. i did not want to replicate this in bthidd(8). bottom line is that bluetooth mouse in text console is kinda lacking, i.e. x, y, z direction and button clicks (single) -- basically MOUSE_ACTION ioctl. Xorg however, can be configured to support for all the buttons/wheels etc (using /dev/sysmouse as input device). thanks, max