ath3kfw(8) [freebsd man page]

ATH3KFW(8)						    BSD System Manager's Manual 						ATH3KFW(8)

NAME

     ath3kfw -- firmware download utility for Atheros AR3011 chip based Bluetooth USB devices

SYNOPSIS

     ath3kfw -d device_name -f firmware_file_name
     ath3kfw -h

DESCRIPTION

     The ath3kfw utility downloads the specified firmware file to the specified ugen(4) device.

     This utility will only work with Atheros AR3011 chip based Bluetooth USB devices.	The identification is currently based on USB vendor
     ID/product ID pair.  The vendor ID should be 0x0cf3 (USB_VENDOR_ATHEROS2) and the product ID should be 0x3000.

     Firmware files ath3k-1.fw and ath3k-2.fw can be obtained from the linux-firmware RPM.

     The options are as follows:

     -d device_name
	     Specify ugen(4) device name.

     -f firmware_file_name
	     Specify firmware file name for download.

     -h      Display usage message and exit.

EXIT STATUS

     The ath3kfw utility exits 0 on success, and >0 if an error occurs.

SEE ALSO

     libusb(3), ugen(4), devd(8)

AUTHORS

     Maksim Yevmenkin <m_evmenkin@yahoo.com>

BUGS

     Most likely.  Please report if found.

BSD
								 November 9, 2010							       BSD

UBTBCMFW(4)						   BSD Kernel Interfaces Manual 					       UBTBCMFW(4)

NAME

     ubtbcmfw -- Firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices

SYNOPSIS

     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device ubtbcmfw

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   ubtbcmfw_load="YES"

DESCRIPTION

     The ubtbcmfw is a firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices.  It provides minimal access to the parts of the
     device required to download firmware.

     The ubtbcmfw driver creates three fixed endpoint device nodes.

     The control transfers can only happen on the control endpoint which is always endpoint 0.	Control requests are issued by ioctl(2) calls.

     Only incoming transfers are supported on an interrupt endpoint.  To perform I/O on an interrupt endpoint, read(2) should be used.	All I/O
     operations on an interrupt endpoint are unbuffered.  Interrupt endpoint is always endpoint 1.

     Only outgoing bulk transfers are supported on a bulk endpoint.  To perform I/O on a bulk endpoint, write(2) should be used.  All I/O opera-
     tions on a bulk endpoint are unbuffered.  Outgoing bulk endpoint is always endpoint 2.

     The control endpoint (endpoint 0) handles the following ioctl(2) calls:

     USB_GET_DEVICE_DESC (usb_device_descriptor_t)
	     Return the device descriptor.

FILES

     /dev/ubtbcmfwN.EE	Endpoint EE of device N.

SEE ALSO

     ng_ubt(4), ugen(4), usb(4), bcmfw(8)

HISTORY

     The ubtbcmfw driver was implemented in FreeBSD 5.0.

AUTHORS

     Maksim Yevmenkin <m_evmenkin@yahoo.com>

BUGS

     Most likely.  Please report if found.

BSD
								 November 22, 2006							       BSD