GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
BTHIDD(8) FreeBSD System Manager's Manual BTHIDD(8)

bthidd
Bluetooth HID daemon

bthidd -h

bthidd [
-a BD_ADDR
] [
-c file
] [
-H file
] [
-p file
] [
-t val
] [
-u
]

The bthidd daemon handles remote Bluetooth HID devices.
The options are as follows:
BD_ADDR
Specify the local address to listen on. By default, the server will listen on ANY address. The address can be specified as BD_ADDR or name. If a name was specified, the bthidd daemon will attempt to resolve the name via bt_gethostbyname(3).
file
Specify path to the configuration file. The default path is /etc/bluetooth/bthidd.conf.
Do not detach from the controlling terminal, i.e., run in foreground.
file
Specify path to the known HIDs file. The default path is /var/db/bthidd.hids.
Display usage message and exit.
file
Specify path to the PID file. The default path is /var/run/bthidd.pid.
val
Specify client rescan interval in seconds. The bthidd daemon will periodically scan for newly configured Bluetooth HID devices or disconnected “passive” Bluetooth HID devices and will attempt to establish an outgoing connection. The default rescan interval is 10 seconds.
Enable support for input event device protocol. Requires evdev and uinput drivers to be loaded with kldload(8) or compiled into the kernel.

The bthidd daemon currently does not handle key auto repeat and double click mouse events. Those events work under X(7) just fine, but not in text console.
This manual page needs more work. A manual page documenting the format of the /etc/bluetooth/bthidd.conf configuration file is needed as well.

/etc/bluetooth/bthidd.conf
 
/var/db/bthidd.hids
 
/var/run/bthidd.pid
 

kbdmux(4), vkbd(4), bthidcontrol(8)

Maksim Yevmenkin <m_evmenkin@yahoo.com>

Any Bluetooth HID device that has HUP_KEYBOARD or HUP_CONSUMER entries in its descriptor is considered as “keyboard”. For each “keyboard” Bluetooth HID device, the bthidd daemon will use a separate instance of the virtual keyboard interface vkbd(4). Therefore the kbdmux(4) driver must be used to properly multiplex input from multiple keyboards.
April 30, 2018 FreeBSD 12.0-RELEASE

Search for    or go to Top of page |  Section 8 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.