History log of /netbsd-src/usr.sbin/btattach/Makefile (Results 1 – 4 of 4)
Revision Date Author Comments
# 8622efc4 10-Aug-2017 jmcneill <jmcneill@NetBSD.org>

Derive the firmware name from the device's local name instead of
hard-coding BCM4340A1. Search hw.firmware.path for the firmware image
instead of loading it from the current directory.


# e5d9803b 10-Aug-2017 nat <nat@NetBSD.org>

Add support for bcm 43xx devices using the btuart h5 protocol.

Currently It will only load 1 firmware image for rpi3.

To use change to the directory containing the firmware BCM4340A1.hcd.
Then issu

Add support for bcm 43xx devices using the btuart h5 protocol.

Currently It will only load 1 firmware image for rpi3.

To use change to the directory containing the firmware BCM4340A1.hcd.
Then issue: btattach -FPi 115200 bcm43xx /dev/ttydevice 921600.

Then you can use the bluetooth device btfive0.

This enables the embedded bluetooth controller on rpi3.

show more ...


# 4e74fe32 06-Dec-2009 kiyohara <kiyohara@NetBSD.org>

Support Infineon UniStone (PBA31308).
from Gumstix's bluez-utils-hciattach-pba31308.patch.
tested on Gumstix verdex-pro.


# 486e4624 15-Apr-2008 plunky <plunky@NetBSD.org>

some changes to serial bluetooth host controller interfaces

btuartd(8) should be named btattach(8) for consistency
with other parts of NetBSD

make btattach(8) a single-use tool for less complexity

some changes to serial bluetooth host controller interfaces

btuartd(8) should be named btattach(8) for consistency
with other parts of NetBSD

make btattach(8) a single-use tool for less complexity

device specicific initialisation (from btuart(4)) is carried
out prior to activating the line discipline (in btattach(8)),
which simplifies the API somewhat and means that the user
tool and the kernel do not need to be kept in sync.

btuart(4) driver is much reduced; naming is made consistent
and all tsleep() and delay() are removed to userland

show more ...