Date: Thu, 6 Apr 2006 08:49:50 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: mouse battery status? Message-ID: <1144309790.220711.1109.nullmailer@galant.ukfsn.org> In-Reply-To: <4434980E.8050202@centtech.com> 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> <4434980E.8050202@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Apr 2006, Eric Anderson wrote: > What about a simple tiny kernel module that can maintain these and other > tweaks related to bluetooth? Like a btmon.ko? This seems overly complex. Can you not just add an entry in your syslog.conf to filter messages from bthidd? I have not tried this, but syslog.conf(5) on appears to show that it is possible, eg: !bthidd *.* |/usr/bin/batmon though I'm not so sure what the 'batmon' program would do - it can extract the battery reports at least, but can't really do anything with them. Probably better to just feed bthidd output to a logfile and get a user program to parse it. You could add a commandline option to bthidd to make it do special logging of the battery information, eg add if (battery_log) syslog(LOG_LOCAL7, "%s %d", bt_ntoa(&s->bdaddr, NULL), val); to the battery report section which might make parsing easier, and use something like !bthidd user.local7 /var/log/bthidd.batlog so you dont have to worry about all the other stuff. Then, your user program will just have to open battery.log and sit in a read() loop to get what it needs. iain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1144309790.220711.1109.nullmailer>