From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 21 08:00:54 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 ED3BC106564A for ; Fri, 21 Jan 2011 08:00:54 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 665688FC16 for ; Fri, 21 Jan 2011 08:00:54 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p0L80bQt004049; Fri, 21 Jan 2011 09:00:52 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p0L80bim004048; Fri, 21 Jan 2011 09:00:37 +0100 (CET) (envelope-from olli) Date: Fri, 21 Jan 2011 09:00:37 +0100 (CET) Message-Id: <201101210800.p0L80bim004048@lurza.secnetix.de> From: Oliver Fromme To: freebsd-bluetooth@FreeBSD.ORG, demelier.david@gmail.com, maksim.yevmenkin@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-bluetooth User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Fri, 21 Jan 2011 09:00:53 +0100 (CET) Cc: Subject: Re: Bluetooth mouse does not connect after reboot X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-bluetooth@FreeBSD.ORG, demelier.david@gmail.com, maksim.yevmenkin@gmail.com 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 08:00:55 -0000 Maksim Yevmenkin wrote: > Oliver Fromme wrote: > > David Demelier wrote: > >  > 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. Oops ... I'm sorry. I thought that bluetooth would feed the sysmouse protocol data via moused(8), just like USB. I've never used a bluetooth mouse before, which explains my mistake. :-) But on the other hand, I think it would be very useful if bluetooth mice used moused(8), too, so you could use all of its features, like dynamic acceleration, physical-to- logical button mapping, wheel mapping, and so on. That might even enable David to solve his problem. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd It's trivial to make fun of Microsoft products, but it takes a real man to make them work, and a God to make them do anything useful.