From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 21 09:09:31 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 EB51A106564A for ; Fri, 21 Jan 2011 09:09:30 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 798288FC1B for ; Fri, 21 Jan 2011 09:09:30 +0000 (UTC) Received: by wwf26 with SMTP id 26so1486697wwf.31 for ; Fri, 21 Jan 2011 01:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BXCBAp7RTTqtRg5UIr5lyYFbNt3WEEfAwMlmMCx8go0=; b=IbwQses3Wkqw/ChcyfRXWjgTuPuBXFzHfMGjWDBPh1o2M1Zqf1JuHA4s60FdR4BCoU 0sBNeaSvYyac2raJbDgpFzJH0ndediW9AzV9G4abKi7trqD7+td0DFIXppnZL0tdwuHf bqyFfzttKXgt8Y0JvBPubMNKl0LjKuppw7Qxo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=beOVz2OY2FMBETF91+bznNxS+eWuF/SG3xBDhCINjjpH/V8qQtEQz29vw6S41hy948 gm+AuS9e+kq5wWa/t96O10mPAeZWMljzWGto4/A+bmkojJjoBYZs/WjyUWxoLQMAP3nk qKtqo91WiBtV7TV89goUNFbkeatfN2XL1r29Q= Received: by 10.227.144.131 with SMTP id z3mr380471wbu.198.1295600969448; Fri, 21 Jan 2011 01:09:29 -0800 (PST) Received: from Melon.malikania.fr (65.21.102-84.rev.gaoland.net [84.102.21.65]) by mx.google.com with ESMTPS id y29sm1579499wbd.10.2011.01.21.01.09.27 (version=SSLv3 cipher=RC4-MD5); Fri, 21 Jan 2011 01:09:28 -0800 (PST) Message-ID: <4D393F19.9020005@gmail.com> Date: Fri, 21 Jan 2011 09:08:57 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110111 Thunderbird/3.1.7 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4D3889D2.80508@gmail.com> <201101202043.p0KKhDIB076736@lurza.secnetix.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 21 Jan 2011 09:09:31 -0000 On 20/01/2011 23:43, Maksim Yevmenkin wrote: > On Thu, Jan 20, 2011 at 12:43 PM, Oliver Fromme wrote: >> David Demelier wrote: >> > It has two logical button at the both sides. It does "backward" or >> > "forward" in firefox or the same in nautilus. My logitech mouse has the >> > same feature on the wheel. if I press the mouse wheel to the side it >> > does 2 more click so the wheel has not only one middle click but three. >> > The middle click and "back" "next" >> > >> > These back/next buttons are not detected by xev. That's my current >> > trouble :-) >> >> If xev doesn't see them, the next step would be to find out >> if moused sees them. Run 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? > Thanks for your interest :-). There is the output when I press a middle click : > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] And there is when I press back and next : > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] > ACL data: handle 0x000b flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 0] It seems to be detected! Now just need to make it works. >> 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 Cheers, -- David Demelier