diff --git a/share/man/man4/btdev.4 b/share/man/man4/btdev.4 index 8bbde46345d4..028c48886a35 100644 --- a/share/man/man4/btdev.4 +++ b/share/man/man4/btdev.4 @@ -1,4 +1,4 @@ -.\" $NetBSD: btdev.4,v 1.1 2006/07/26 10:38:51 tron Exp $ +.\" $NetBSD: btdev.4,v 1.2 2006/07/29 23:57:03 wiz Exp $ .\" .\" Copyright (c) 2006 Itronix Inc. .\" All rights reserved. @@ -29,7 +29,7 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.Dd July 18, 2006 +.Dd July 26, 2006 .Dt BTDEV 4 .Os .Sh NAME @@ -51,23 +51,27 @@ Normally, Bluetooth Remote Devices will be configured using the program, which passes a .Xr proplib 3 dictionary to the appropriate control file -.Pa /dev/btdevN +.Pa /dev/btdevN with the following .Xr ioctl 2 calls: .Pp .Bl -tag -width XX -compact .It Cm BTDEV_ATTACH -Attach Bluetooth Device. The following properties are used by +Attach Bluetooth Device. +The following properties are used by .Nm : .Pp .Bl -tag .It local-bdaddr -Local BD_ADDR. This required property should be a six byte data blob. +Local BD_ADDR. +This required property should be a six byte data blob. .It remote-bdaddr -Remote BD_ADDR. This required property should be a six byte data blob. -.It device-type -Device type. This required property should be a string indicating the +Remote BD_ADDR. +This required property should be a six byte data blob. +.It device-type +Device type. +This required property should be a string indicating the device type to attach, and may be one of the following: .Pp .Bl -tag -compact @@ -93,9 +97,9 @@ Detach Bluetooth Device. Currently no properties are used. .El .Sh SEE ALSO .Xr bluetooth 4 , -.Xr btcontrol 8 , .Xr bthidev 4 , -.Xr btsco 4 +.Xr btsco 4 , +.Xr btcontrol 8 .Sh HISTORY The .Nm diff --git a/share/man/man4/bthidev.4 b/share/man/man4/bthidev.4 index 8d6f8c6ccd7d..6e58f0f7cea8 100644 --- a/share/man/man4/bthidev.4 +++ b/share/man/man4/bthidev.4 @@ -1,4 +1,4 @@ -.\" $NetBSD: bthidev.4,v 1.2 2006/07/26 10:40:50 tron Exp $ +.\" $NetBSD: bthidev.4,v 1.3 2006/07/30 00:01:24 wiz Exp $ .\" .\" Copyright (c) 2006 Itronix Inc. .\" All rights reserved. @@ -29,7 +29,7 @@ .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.Dd March 17, 2006 +.Dd July 26, 2006 .Dt BTHIDEV 4 .Os .Sh NAME @@ -43,20 +43,23 @@ .Sh DESCRIPTION The .Nm -driver handles all Bluetooth Human Interface Devices. Each HID -device can have several components, e.g., a keyboard and a mouse. +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 +distinguish which component data is coming from. +The .Nm driver may have several children attached that handle particular components and dispatches data to them based on the report id. .Pp Normally, Bluetooth HIDs will be attached using the .Xr btcontrol 8 -program. The following properties are used by the +program. +The following properties are used by the .Nm driver during autoconfiguration: -.Bl -tag -width interrupt_psmXX +.Bl -tag -width interrupt_psmXX .It local-bdaddr Local device address. .It remote-bdaddr @@ -66,11 +69,13 @@ Should be .Sq bthidev , indicating a Human Interface Device. .It control-psm -This, if set, will indicate the PSM to use for the Control channel. If not set, +This, if set, will indicate the PSM to use for the Control channel. +If not set, .Dv L2CAP_PSM_HID_CNTL will be used. .It interrupt-psm -This, if set, will indicate the PSM to use for the Interrupt channel. If not set, +This, if set, will indicate the PSM to use for the Interrupt channel. +If not set, .Dv L2CAP_PSM_HID_INTR will be used. .It descriptor @@ -79,22 +84,22 @@ reports the device will produce, and obtained via SDP. .It reconnect If this boolean value is set, and is true, then the .Nm -driver will initiate reconnections to the remote device when no connection is -present. +driver will initiate reconnections to the remote device when no +connection is present. .El .Pp When the .Nm -driver has configured its children, it will initate a connection to the remote -device. If this fails and the reconnect flag is not set, it will then wait for +driver has configured its children, it will initate 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. -.Pp .Sh SEE ALSO .Xr bluetooth 4 , -.Xr btcontrol 8 , .Xr btdev 4 , .Xr btkbd 4 , -.Xr btms 4 +.Xr btms 4 , +.Xr btcontrol 8 .Sh HISTORY The .Nm