From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 6 04:25:01 2006 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 941A016A401 for ; Thu, 6 Apr 2006 04:25:01 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 115F743D45 for ; Thu, 6 Apr 2006 04:25:00 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k364OxZN059051; Wed, 5 Apr 2006 23:24:59 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4434980E.8050202@centtech.com> Date: Wed, 05 Apr 2006 23:24:46 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: Maksim Yevmenkin References: <43F34314.7030606@centtech.com> <43F3688B.8060700@savvis.net> <43F4B7AA.5030000@centtech.com> <43F5229C.8050106@savvis.net> <43F5D186.7060302@centtech.com> <43F60A7B.2090206@savvis.net> <43F62314.1070101@centtech.com> <43F645BB.4070008@savvis.net> In-Reply-To: <43F645BB.4070008@savvis.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1376/Wed Apr 5 00:51:25 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-bluetooth@freebsd.org Subject: Re: mouse battery status? 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, 06 Apr 2006 04:25:01 -0000 Maksim Yevmenkin wrote: > Eric Anderson wrote: > > [...] > >>>>>> I wonder where the right place to report the battery information is? >>>>> >>>>> like i said, right now it goes to /var/log/messages. info, notice >>>>> and warning levels are used for different battery states (ok, low, >>>>> very low). if this is not the right place, please let me know where >>>>> do you want it to be? >>>> >>>> I suppose if one wanted to make a tool to monitor the mouse battery >>>> (say, for an X window manager), you could poll/parse the output of >>>> bthidcontrol, right? Is there a better way to grab the info (a >>>> bthid library or something)? Sorry if this is a trivial question - >>>> I'm not a bluetooth hacker :) >>> >>> not quite. "battery report" is an input report, i.e. mouse should >>> send it periodically. bhtidd(8) already parses it. the question is >>> what should it do with this information? right now it just logs it. >>> it could send another message to another application (i.e. mouse >>> battery monitoring tool) so it can do whatever is required. >> >> I think either a sysctl entry that shows the value (0 - 3) would be >> nice. I guess ng_hci would create it? Then bthidd would just change >> the sysctl value when it gets the report from the mouse.. ? > > sysctl sounds like a good idea, but i'm not sure who would create such > sysctl. it most definitely does not belong at bluetooth hci, l2cap, > rfcomm and even socket layer. this information is strictly for hid. so, > i think, syslog is the best place for it right now. it is possible to > divert these messages into another file and have monitoring tool > look/parse the file periodically. What about a simple tiny kernel module that can maintain these and other tweaks related to bluetooth? Like a btmon.ko? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------