History log of /netbsd-src/usr.sbin/btdevctl/btdevctl.8 (Results 1 – 12 of 12)
Revision Date Author Comments
# 68a3deed 12-Jun-2015 plunky <plunky@NetBSD.org>

the Bluetooth rc.d setup was simplified some time ago, so
'btdevctl' variable is no longer used. change wording to
reflect this


# 6cb10275 18-Mar-2014 riastradh <riastradh@NetBSD.org>

Merge riastradh-drm2 to HEAD.


# a5684d07 20-Jul-2013 wiz <wiz@NetBSD.org>

Use Mt for email addresses.


# c5b7b2f3 26-Dec-2012 plunky <plunky@NetBSD.org>

whitespace ' ' -> ' '


# b504b003 26-Dec-2012 plunky <plunky@NetBSD.org>

add a comment pointing out that the link-mode may need to be
changed manually, for devices which cannot authenticate

for PR/47286


# 8a0067fe 12-Oct-2010 wiz <wiz@NetBSD.org>

Sort sections, use serial comma.


# 2cf0f09d 11-Oct-2010 plunky <plunky@NetBSD.org>

add a reference in the SEE ALSO section to "The NetBSD Guide" for
detailed examples of device configuration


# 4721bd89 02-Dec-2007 wiz <wiz@NetBSD.org>

Drop trailing whitespace, remove superfluous Pp.


# f5db72e7 21-Apr-2007 plunky <plunky@NetBSD.org>

Add 'service level' security for L2CAP and RFCOMM connections, following
the Linux (BlueZ) API.

- L2CAP or RFCOMM connections can require the baseband radio link
mode be any of:
authenticat

Add 'service level' security for L2CAP and RFCOMM connections, following
the Linux (BlueZ) API.

- L2CAP or RFCOMM connections can require the baseband radio link
mode be any of:
authenticated (devices are paired)
encrypted (implies authentication)
secured (encryption, plus generate new link key)

- for sockets, the mode is set using setsockopt(2) and the socket
connection will be aborted if the mode change fails.

- mode settings will be applied during connection establishment, and
for safety, we enter a wait state and will only proceed when the mode
settings are successfuly set.

- It is possible to change the mode on already open connections, but
not possible to guarantee that data already queued (from either end)
will not be delivered. (this is a feature, not a bug)

- bthidev(4) and rfcomm_sppd(1) support "auth", "encrypt" and
"secure" options

- btdevctl(8) by default enables "auth" for HIDs, and "encrypt" for
keyboards (which are required to support it)

show more ...


# 4f1cbddc 10-Sep-2006 plunky <plunky@NetBSD.org>

update to bluetooth device attachment:

remove pseudo-device btdev(4) and inherent limitations

add bthub(4) which autoconfigures at bluetooth controllers as they
are enabled. bluetooth devices now a

update to bluetooth device attachment:

remove pseudo-device btdev(4) and inherent limitations

add bthub(4) which autoconfigures at bluetooth controllers as they
are enabled. bluetooth devices now attach here.

btdevctl(8) and its cache is updated to handle new semantics

etc/rc.d/btdevctl is updated to configure devices from a list
in /etc/bluetooth/btdevctl.conf

show more ...


# c980b109 27-Aug-2006 plunky <plunky@NetBSD.org>

BluetootH SCO Audio update.

Provide an ioctl to set the SCO mtu value in the controller and
place limits in the SCO code such that only packets of this size
may be sent.

Move the mtu option from bt

BluetootH SCO Audio update.

Provide an ioctl to set the SCO mtu value in the controller and
place limits in the SCO code such that only packets of this size
may be sent.

Move the mtu option from btsco(4) and btdevctl(8), to the
btconfig(8) program.

Remove temporary BLUETOOTH_SCO kernel option, and enable SCO
socket access.

Fix incoming connection handling for btsco(4) and SCO sockets.

Fix documentation to reflect the new world order.

show more ...


# 885b13c5 13-Aug-2006 plunky <plunky@NetBSD.org>

rename btcontrol(8) as btdevctl(8) to make it fit with the NetBSD naming
scheme for control programs. This fixes pr 34051.