Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

New sentence, new line.

Browse Source
This commit is contained in:
wiz 2009-05-04 20:42:00 +00:00
parent d0405d7091
commit 6272d564d6
2 changed files with 46 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
share/man/man4/bluetooth.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: bluetooth.4,v 1.12 2009/04/10 15:14:06 joerg Exp $
.\" $NetBSD: bluetooth.4,v 1.13 2009/05/04 20:42:00 wiz Exp $
.\"
.\" Copyright (c) 2006 Itronix Inc.
.\" All rights reserved.
@ -70,9 +70,11 @@ Protocols included are:
This gives raw access to the Host Controller Interface of local devices
using the HCI protocol as described in the Bluetooth Core Specification.
Any user may open an HCI socket but there are limitations on what
unprivileged users can send and receive. The local address specified by
unprivileged users can send and receive.
The local address specified by
.Xr bind 2
may be used to select the device that the socket will receive packets from. If
may be used to select the device that the socket will receive packets from.
If
.Dv BDADDR_ANY
is specified then the socket will receive packets from all
devices on the system.
@ -93,13 +95,16 @@ and should be set to zero.
HCI socket options:
.Bl -tag -width XX
.It Dv SO_HCI_EVT_FILTER Op Ar struct hci_filter
This filter controls which events will be received at the socket. See
This filter controls which events will be received at the socket.
See
.In netbt/hci.h
for available events. By default, Command_Complete and Command_Status
for available events.
By default, Command_Complete and Command_Status
events only are enabled.
.It Dv SO_HCI_PKT_FILTER Op Ar struct hci_filter
This filter controls the type of packets that will be received at the
socket. By default, Event packets only are enabled.
socket.
By default, Event packets only are enabled.
.It Dv SO_HCI_DIRECTION Op Ar int
When set, this enables control messages on packets received at the socket
indicating the direction of travel of the packet.
@ -115,11 +120,12 @@ Default send buffer size for HCI sockets.
Default receive buffer size for HCI sockets
.It Dv net.bluetooth.hci.acl_expiry
If set, this is the time in seconds after which unused ACL data connections
will be expired. If zero, connections will not be closed.
will be expired.
If zero, connections will not be closed.
.It Dv net.bluetooth.hci.memo_expiry
Time, in seconds, that the system will keep records of Bluetooth devices
in the vicinity after an Inquiry Response packet has been received. This
information is used for routing purposes.
in the vicinity after an Inquiry Response packet has been received.
This information is used for routing purposes.
.It Dv net.bluetooth.hci.eventq_max
The maximum number of packets on the low level Event queue.
.It Dv net.bluetooth.hci.aclrxq_max
@ -278,11 +284,13 @@ Default receive buffer size for SCO sockets.
.Sh INFORMATION
The following
.Xr ioctl 2
calls may be used to manipulate Bluetooth devices. The
calls may be used to manipulate Bluetooth devices.
The
.Xr ioctl 2
must be made on
.Cm BTPROTO_HCI
sockets. All of the requests take a
sockets.
All of the requests take a
.Ar btreq
structure defined as follows as their parameter and unless otherwise
specified, use the
@ -347,25 +355,30 @@ struct bt_stats {
.Ed
.Bl -tag -width SIOCGBTPOLICY
.It Dv SIOCGBTINFO
Get Bluetooth device Info. Given the device name, fill in the
Get Bluetooth device Info.
Given the device name, fill in the
btreq structure including the address field for use with socket addressing
as above.
.It Dv SIOCGBTINFOA
Get Bluetooth device Info from Address. Given the device address, fill in the
Get Bluetooth device Info from Address.
Given the device address, fill in the
btreq structure including the name field.
.It Dv SIOCNBTINFO
Next Bluetooth device Info . If name field is empty, the first device
will be returned. Otherwise, the next device will be returned. Thus, you
can cycle through all devices in the system.
Next Bluetooth device Info.
If name field is empty, the first device will be returned.
Otherwise, the next device will be returned.
Thus, you can cycle through all devices in the system.
.It Dv SIOCSBTFLAGS
Set Bluetooth device Flags. Not all flags are settable.
Set Bluetooth device Flags.
Not all flags are settable.
.It Dv SIOCSBTPOLICY
Set Bluetooth device Link Policy. Link Policy bits are defined in
Set Bluetooth device Link Policy.
Link Policy bits are defined in
.In netbt/hci.h ,
though you can only set bits that the device supports.
.It Dv SIOCSBTPTYPE
Set Bluetooth device Packet Types. You can only set packet types
that the device supports.
Set Bluetooth device Packet Types.
You can only set packet types that the device supports.
.It Dv SIOCGBTSTATS
Read device statistics.
.It Dv SIOCZBTSTATS

21
share/man/man4/usb.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: usb.4,v 1.89 2009/04/10 15:02:03 joerg Exp $
.\" $NetBSD: usb.4,v 1.90 2009/05/04 20:42:34 wiz Exp $
.\"
.\" Copyright (c) 1999-2008 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -100,13 +100,14 @@ during cold boot.
Normally, only the USB host controller and the
.Va usb
device are detected during the autoconfiguration when the
machine is booted. The rest of the devices are detected once
machine is booted.
The rest of the devices are detected once
the system becomes functional and the kernel thread for the
.Va usb
device is started.
Sometimes it is desirable to have a device detected early in the
boot process, e.g., the console keyboard. To achieve this use
a
boot process, e.g., the console keyboard.
To achieve this use a
.Va flags
value of 1.
.Pp
@ -470,7 +471,8 @@ All
.Tn USB
events are reported via the
.Pa /dev/usb
device. This devices can be opened for reading and each
device.
This devices can be opened for reading and each
.Xr read 2
will yield an event record (if something has happened).
The
@ -506,7 +508,8 @@ The
.Va ue_type
field identifies the type of event that is described.
The possible events are attach/detach of a host controller,
a device, or a device driver. The union contains information
a device, or a device driver.
The union contains information
pertinent to the different types of events.
.Pp
The
@ -530,8 +533,10 @@ contains the name of the device (driver) as seen in, e.g.,
kernel messages.
.Pp
Note that there is a separation between device and device
driver events. A device event is generated when a physical
USB device is attached or detached. A single USB device may
driver events.
A device event is generated when a physical
USB device is attached or detached.
A single USB device may
have zero, one, or many device drivers associated with it.
.Sh KERNEL THREADS
For each USB bus, i.e., for each host controller, there is