summaryrefslogtreecommitdiff
path: root/sys/dev/bluetooth/btdev.h
AgeCommit message (Collapse)Author
2015-09-06More on PR 41200: headers that declare ioctls should include sys/ioccom.h.dholland
This covers (I think) all the MI headers outside of external/ (and dist/).
2010-04-28allow for vendor-id and product-id properties, passing themplunky
through to child devices
2008-03-28Use deviter API to search for child devices.plunky
As all identifying information is stored in the device properties, this removes the need for child devices to have a reserved area (struct btdev) in the softc, and bthub(4) does no longer need to have a softc at all.
2007-11-03switch devices to using CFATTACH_DECL_NEW()plunky
softc no longer contains 'struct device' by default use 'device_t' instead of 'struct device *' use device_xxx() accessor functions remove casting of 'xxx_softc *' & 'struct device *' use aprint_xxx_dev() routines
2007-04-21Add 'service level' security for L2CAP and RFCOMM connections, followingplunky
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)
2006-10-04Internally, use the service name as the identifier for matchingplunky
2006-09-11also include service name in dictionary being sent to kernel.plunky
(this is not used just yet, but it might be in the future and it will be easier if we dont have to provide code to handle its absence)
2006-09-10update to bluetooth device attachment:plunky
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
2006-07-26Bluetooth fixes by Iain Hibbert:tron
Change the way in which bluetooth devices attach to system. The new way is for devices to attach directly to a btdevN device via its own control file /dev/btdevN. - bthub(4) is replaced by btdev(4). - /dev/bthubctl is replaced by /dev/btdevN. - configuration now uses proplib(3) property lists. - btcontrol(8) updated to use new API, and now uses private - XML config file /var/db/btdev.xml.
2006-06-19Initial import of bluetooth stack on behalf of Iain Hibbert. (plunky@,gdamore
NetBSD Foundation Membership still pending.) This stack was written by Iain under sponsorship from Itronix Inc. The stack includes support for rfcomm networking (networking via your bluetooth enabled cell phone), hid devices (keyboards/mice), and headsets. Drivers for both PCMCIA and USB bluetooth controllers are included.