bthub(4) [netbsd man page]

BTHUB(4)						   BSD Kernel Interfaces Manual 						  BTHUB(4)

NAME

     bthub -- Bluetooth Remote Device Hub

SYNOPSIS

     bthub* at bcsp?
     bthub* at bt3c?
     bthub* at btbc?
     bthub* at btuart?
     bthub* at sbt?
     bthub* at ubt?

     bthidev* at bthub?
     btmagic* at bthub?
     btsco* at bthub?

DESCRIPTION

     The bthub device is used to attach remote Bluetooth devices to the system, and will attach to Bluetooth controllers as they are enabled.

CONFIGURATION

     Normally, Bluetooth Remote Devices will be configured on the bthub using the btdevctl(8) program, which passes a proplib(3) dictionary to the
     control file /dev/bthub with the BTDEV_ATTACH and BTDEV_DETACH ioctl(2) commands.

     The following properties are used by bthub:

     local-bdaddr  Local BD_ADDR.  This required property should be a six byte data blob.

     remote-bdaddr
		   Remote BD_ADDR.  This required property should be a six byte data blob.

     service-name  Service name.  This required property should be a string indicating the service to configure, and may be one of the following:

		   HF		 Handsfree, see btsco(4).
		   HID		 Human Interface Device, see bthidev(4).
		   HSET 	 Headset, see btsco(4).

     Properties used by the configured device are listed in the appropriate device manual page.

FILES

     /dev/bthub

SEE ALSO

     bluetooth(4), bthidev(4), btmagic(4), btsco(4), btdevctl(8)

HISTORY

     The bthub driver was written by Iain Hibbert under the sponsorship of Itronix, Inc. and first appeared in NetBSD 4.0.

BSD
								 October 17, 2010							       BSD

BTDEVCTL(8)						    BSD System Manager's Manual 					       BTDEVCTL(8)

NAME

     btdevctl -- Bluetooth remote device control utility

SYNOPSIS

     btdevctl [-A | -D] [-qv] [-m mode] -a address -d device -s service

DESCRIPTION

     The btdevctl utility is used to configure bluetooth devices in the system.  Normally, btdevctl will perform  an SDP query to the remote
     device as needed, and cache the results in the /var/db/btdevctl.plist file for later use.	If neither Attach nor Detach is specified,
     btdevctl will display the configuration.

     The options are:

     -A 	 Attach device

     -a address  Remote device address.  The address may be given as BDADDR or a name.	If a name was specified, btdevctl attempts to resolve the
		 name via bt_gethostbyname(3).

     -D 	 Detach device

     -d device	 Local device address.	May be given as BDADDR or device name.

     -m mode	 Connection link mode.	The following modes are supported:

		 none	  clear previously set mode.
		 auth	  require devices be paired, see btpin(1).
		 encrypt  auth, plus enable encryption.
		 secure   encryption, plus change of link key.

		 When configuring the HID service, btdevctl will set 'auth' by default, or 'encrypt' for keyboard devices.  If the device cannot
		 handle authentication, then the mode will need to be cleared manually.

     -q 	 Ignore any cached data and perform a SDP query for the given service.

     -s service  Service to configure.	Known services are:

		 HID	 Human Interface Device.
		 HF	 Handsfree.
		 HSET	 Headset.

     -v 	 Be verbose.

     For device configurations to persist across boots, add entries to the /etc/bluetooth/btdevctl.conf file and set the rc.conf(5) variable
     btdevctl to YES.

FILES

     /etc/bluetooth/btdevctl.conf
     /dev/bthub
     /var/db/btdevctl.plist

EXIT STATUS

     The btdevctl utility exits 0 on success, and >0 if an error occurs.

SEE ALSO

     btpin(1), bthidev(4), bthub(4), btsco(4), rc.conf(5)

     See the Bluetooth chapter of "The NetBSD Guide" for detailed examples of configuring keyboards, mice, and audio headsets.

HISTORY

     Parts of the btdevctl program originated in the FreeBSD bthidcontrol program.

AUTHORS

     Iain Hibbert for Itronix, Inc.
     Maksim Yevmenkin <m_evmenkin@yahoo.com>

BSD
								 December 26, 2012							       BSD