btsco(4) [netbsd man page]

BTSCO(4)						   BSD Kernel Interfaces Manual 						  BTSCO(4)

NAME

     btsco -- Bluetooth SCO Audio

SYNOPSIS

     btsco*    at bthub?
     audio*    at audiobus?

DESCRIPTION

     The btsco driver provides support for Bluetooth SCO Audio devices through the audio(4) driver.

     The btsco driver must be configured at run time with the btdevctl(8) program.  The following properties are used by the btsco driver during
     autoconfiguration:

     local-bdaddr
	       Local device address.

     remote-bdaddr
	       Remote device address.

     service-name
	       The btsco driver matches the 'HF' and 'HSET' services.  For the 'HF' service, the btsco device will, on open(2), listen for incom-
	       ing connections from the remote device.	Otherwise, btsco will attempt to initiate a connection to the remote device.

     rfcomm-channel
	       This integer value is not used directly, but will be stored and passed via the BTSCO_INFO ioctl as below:

     SCO connections require a baseband connection between the two devices before they can be created.	The btsco driver does not create this, but
     can provide information to facilitate an application setting up a control channel prior to use, via the BTSCO_INFO ioctl(2) call on the mixer
     device, which returns a btsco_info structure as follows:

     #include <dev/bluetooth/btsco.h>

     struct btsco_info {
	     bdaddr_t	     laddr;	     /* controller bdaddr */
	     bdaddr_t	     raddr;	     /* headset bdaddr */
	     uint8_t	     channel;	     /* RFCOMM channel */
	     int	     vgs;	     /* mixer index speaker */
	     int	     vgm;	     /* mixer index mic */
     };

     #define BTSCO_INFO      _IOR('b', 16, struct btsco_info)

     The btsco driver can be configured to act in Connect or Listen mode.  In Connect mode, the btsco driver will initiate a connection to the
     remote device on an open(2) call, whereas in Listen mode, open(2) will block until the remote device initiates the connection.

SEE ALSO

     bthset(1), ioctl(2), audio(4), bluetooth(4), bthub(4), btdevctl(8)

HISTORY

     The btsco driver was written for NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc.

BUGS

     btsco takes no notice of the HCI Voice Setting in the Bluetooth controller, and this must be 0x0060 (the default) as alternate values are
     currently unsupported.

BSD
								  October 4, 2006							       BSD

Check Out this Related Man Page

BTHIDEV(4)						   BSD Kernel Interfaces Manual 						BTHIDEV(4)

NAME

     bthidev -- Bluetooth Human Interface Device support

SYNOPSIS

     bthidev* at bthub?

     btkbd*   at bthidev? reportid ?
     btms*    at bthidev? reportid ?

DESCRIPTION

     The bthidev driver handles all Bluetooth Human Interface Devices.	Each HID device can have several components, e.g., a keyboard and a mouse.
     These components use different report identifiers to distinguish which component data is coming from.  The bthidev driver may have several
     children attached that handle particular components and dispatches data to them based on the report id.

     Normally, Bluetooth HIDs will be attached using the btdevctl(8) program.  The following properties are used by the bthidev driver during
     autoconfiguration:

     local-bdaddr     Local device address.

     remote-bdaddr    Remote device address.

     service-name     The bthidev driver matches the 'HID' service.

     control-psm      This, if set, will indicate the PSM to use for the Control channel.  If not set, L2CAP_PSM_HID_CNTL will be used.

     interrupt-psm    This, if set, will indicate the PSM to use for the Interrupt channel.  If not set, L2CAP_PSM_HID_INTR will be used.

     descriptor       This required binary blob is the HID descriptor containing information about reports the device will produce, and obtained
		      via SDP.

     reconnect	      If this boolean value is set, and is true, then the bthidev driver will initiate reconnections to the remote device when no
		      connection is present.

     link-mode	      This optional string represents the link mode of the baseband link, and may be one of 'auth', 'encrypt', or 'secure'.

     When the bthidev driver has configured its children, it will initiate a connection to the remote device.  If this fails and the reconnect
     flag is not set, it will then wait for the device to initiate the connection.

SEE ALSO

     bluetooth(4), bthub(4), btkbd(4), btms(4), btdevctl(8)

HISTORY

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

BSD
								  April 10, 2007							       BSD

Linux and UNIX Man Pages

btsco(4) [netbsd man page]

Check Out this Related Man Page