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

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