From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 20 17:55:40 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 97FF21065674 for ; Thu, 20 Jan 2011 17:55:40 +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 5CADB8FC18 for ; Thu, 20 Jan 2011 17:55:40 +0000 (UTC) Received: by iwn39 with SMTP id 39so818172iwn.13 for ; Thu, 20 Jan 2011 09:55:39 -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 :content-transfer-encoding; bh=W7LInGUZYv3AUdWvtqXsfdbUUQbbbaFm1qNz2IQCmKc=; b=uYy2uJFbB/zzALt3QskG6FH6S0rfJcEHfoAEKIaGRh5DuwOEhsiYbqgEQkVR7SL0XR fAgF36hXGx6dyVYukv28cKjDP6uydJkpyWNJlsT+dwzUKR2VgEJD/vseMOK1u1Z1t1am /snJjjoS+lSnzMoXsIWNBG4QDt16i/2qoR79k= 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:content-transfer-encoding; b=JuauWN2+gKJ4heeXHjUkL+rOTt6cdCmx9sx/SBGE1vatqvsnSzeHIiQHxFawt9cHWN q3kMtZgT8CDkPS9c4vIOJrts7j1evY3J/ropzWMMGajR2iScR8mjMdBbFLsEmfZaaecz wUThyxDkrDbYfDQ2fb3Zx10/P8GQTueb6a2AU= MIME-Version: 1.0 Received: by 10.231.32.141 with SMTP id c13mr2884289ibd.101.1295546139388; Thu, 20 Jan 2011 09:55:39 -0800 (PST) Received: by 10.231.206.5 with HTTP; Thu, 20 Jan 2011 09:55:39 -0800 (PST) In-Reply-To: <4D37F7DB.4020709@gmail.com> References: <4D36ED39.7070807@gmail.com> <4D372C27.3040606@gmail.com> <4D37F7DB.4020709@gmail.com> Date: Thu, 20 Jan 2011 09:55:39 -0800 Message-ID: From: Maksim Yevmenkin To: David Demelier Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Thu, 20 Jan 2011 17:55:40 -0000 On Thu, Jan 20, 2011 at 12:52 AM, David Demelier wrote: > On 19/01/2011 20:10, Maksim Yevmenkin wrote: >> >> On Wed, Jan 19, 2011 at 10:23 AM, David Demelier >> =A0wrote: >>> >>> 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 =A0 id=3D2 size=3D1 count=3D1 page=3DButton usage=3DButton_7 Vari= able, logical >>> range 0..1 >>> Input =A0 id=3D2 size=3D1 count=3D1 page=3DButton usage=3DButton_8 Vari= able, logical >>> range 0..1 >>> Input =A0 id=3D2 size=3D12 count=3D1 page=3DGeneric_Desktop usage=3DX V= ariable >>> Relative, >>> logical range -2047..2047 >>> Input =A0 id=3D2 size=3D12 count=3D1 page=3DGeneric_Desktop usage=3DY V= ariable >>> Relative, >>> logical range -2047..2047 >>> Input =A0 id=3D2 size=3D8 count=3D1 page=3DGeneric_Desktop usage=3DWhee= l Variable >>> Relative, logical range -127..127 >>> Input =A0 id=3D2 size=3D8 count=3D1 page=3DConsumer usage=3DAC_Pan Vari= able 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 > > Then I should edit my mouse section in my xorg.conf ? I tried this : > > Section "InputDevice" > =A0 =A0 =A0 =A0Identifier =A0 =A0 =A0"Mouse0" > =A0 =A0 =A0 =A0Driver =A0 =A0 =A0 =A0 =A0"mouse" > =A0 =A0 =A0 =A0Option =A0 =A0 =A0 =A0 =A0"Protocol" "auto" > =A0 =A0 =A0 =A0Option =A0 =A0 =A0 =A0 =A0"Device" "/dev/sysmouse" > =A0 =A0 =A0 =A0Option =A0 =A0 =A0 =A0 =A0"ZAxisMapping" "4 5 6 7" > =A0 =A0 =A0 =A0Option =A0 =A0 =A0 =A0 =A0"Buttons" "7" > EndSection > > But it does not change anything could you please be more specific what exactly works and what does not? your configuration seems to be correct. so, i would expect that x, y and vertical scroll/wheel should work. horizontal scroll (AC_Pan) is not currently decoded by bthidd(8). while it is very easy to add it, mouse_info structure has no place to put the value in :( so, basically, bthidd(8) is limited by what sysmouse(4) can understand. thanks, max