bthidev(4) [netbsd 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

BTMAGIC(4)						   BSD Kernel Interfaces Manual 						BTMAGIC(4)

NAME

     btmagic -- Apple Magic Mouse

SYNOPSIS

     btmagic*  at bthub?
     wsmouse*  at btmagic?

DESCRIPTION

     The btmagic driver provides support for the Bluetooth ``Magic Mouse'' from Apple, Inc.  As remote devices cannot be discovered by autoconfig,
     configuring a mouse is normally carried out with the btdevctl(8) program.

     The Magic Mouse uses the standard USB Human Interface Device protocol to communicate, but does not provide a proper HID Descriptor, and
     requires specific initializations to enable the proprietary touch reports.

     The Magic Mouse provides basic mouse functionality with two buttons, and the btmagic driver additionally interprets the touch reports to emu-
     late a middle mouse button when more than one firm touch is detected during a click event, plus horizontal and vertical scrolling for touch
     movements greater than a certain distance.  The mouse has a base resolution of 1300dpi, which the driver scales by default to a less sensi-
     tive 650dpi, but this is adjustable with sysctl(8) along with the pressure needed to discern a firm touch, the minimum distance necessary to
     trigger scrolling and the additional downscale factor applied to scroll movements.

     btmagic interfaces to the system as usual through the wsmouse(4) driver, and the following properties are used during autoconfiguration:

     vendor-id	    Must be 0x05ac.

     product-id     Must be 0x030d.

     local-bdaddr   Local device address.

     remote-bdaddr  Remote device address.

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

     When the btmagic driver has configured, it will attempt to open a connection to the mouse and, if this fails or the connection is lost, will
     wait for the mouse to initiate connections.  The Magic Mouse requires connections to be authenticated, and should accept a PIN of '0000' dur-
     ing the pairing process.

SEE ALSO

     bluetooth(4), bthub(4), wsmouse(4), btdevctl(8), sysctl(8)

HISTORY

     The btmagic driver was written by Iain Hibbert with reference to the Linux driver written by Michael Poole.

BSD
								 October 11, 2010							       BSD