From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 20 22:43:15 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 E868D106564A for ; Thu, 20 Jan 2011 22:43:13 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id AEEE08FC16 for ; Thu, 20 Jan 2011 22:43:13 +0000 (UTC) Received: by iyb26 with SMTP id 26so1084262iyb.13 for ; Thu, 20 Jan 2011 14:43:13 -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:content-type:content-transfer-encoding; bh=kTADWavmGrADZwl3efa/BHcmGNKRKfJ2XL0RgRtd9zQ=; b=fIOA68pZxCG5EnXcuPBCJPpieeP282d0GDLMuKfRSZ868YCeqzNN70HzKdAsolG1zI IHXB6voaOgI7jHXF9Ay/2anOH0kgBBdzis41CDo+mHx64Xaccop4KhO9uOSO0p2el89e MkPRX/0lBke3KUieOqTRTLnq98ncs5RxbSN9s= 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 :content-type:content-transfer-encoding; b=vqnpbJD8PDbMxKk6djbpVu7jW9KHMIRhdZ6Fqy0GDFbkzyYE+RwklVNaCfny9bLV86 5mxxch1No+aocP1zLGbRy4P1QfpXo12IlAIqye+MTkV/x1LUvw9sbFpyeF14JZvh+7OG 1FHU9s255hfZFNWbxtmi8saxekKADwwxN+UaY= MIME-Version: 1.0 Received: by 10.231.169.74 with SMTP id x10mr3304690iby.26.1295563391301; Thu, 20 Jan 2011 14:43:11 -0800 (PST) Received: by 10.231.206.5 with HTTP; Thu, 20 Jan 2011 14:43:11 -0800 (PST) In-Reply-To: <201101202043.p0KKhDIB076736@lurza.secnetix.de> References: <4D3889D2.80508@gmail.com> <201101202043.p0KKhDIB076736@lurza.secnetix.de> Date: Thu, 20 Jan 2011 14:43:11 -0800 Message-ID: From: Maksim Yevmenkin To: freebsd-bluetooth@freebsd.org, demelier.david@gmail.com, maksim.yevmenkin@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: 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 22:43:15 -0000 On Thu, Jan 20, 2011 at 12:43 PM, Oliver Fromme wr= ote: > David Demelier wrote: > =A0> It has two logical button at the both sides. It does "backward" or > =A0> "forward" in firefox or the same in nautilus. My logitech mouse has = the > =A0> same feature on the wheel. if I press the mouse wheel to the side it > =A0> does 2 more click so the wheel has not only one middle click but thr= ee. > =A0> The middle click and "back" "next" > =A0> > =A0> These back/next buttons are not detected by xev. That's my current > =A0> trouble :-) > > If xev doesn't see them, the next step would be to find out > if moused sees them. =A0Run moused with the -f -d options, so > it will print all events. sorry, i'm a bit confused here. moused has nothing to do with bluetooth mouse. bthidd decodes hid reports (received over bluetooth link), fills mouse_info structure, and, feeds mouse_info to kernel via mouse_action ioctl. so, i don't think that moused will be able to trap that. i'd like to know how those "non-working" events are reported at hid level. David, could you please use hcidump and obtain traces for those "non-working" events? > By the way, I don't think this is bluetooth related at all. > Maybe you should open a new thread on the x11 list. it may or may not be bthidd related :) if bthidd can decode and put those events into kernel then there is no reason for it to not do that :) thanks, max