Undocumented configuration symbols in 2.4.6pre2

The 2.4.6-pre2 kernel introduces some new configuration symbols:

CONFIG_AMD7409_OVERRIDE
CONFIG_BLK_DEV_AMD7409
CONFIG_BLK_DEV_OSB4
CONFIG_BLUEZ
CONFIG_BLUEZ_HCIEMU
CONFIG_BLUEZ_HCIUART
CONFIG_BLUEZ_HCIUSB
CONFIG_BLUEZ_L2CAP

Would the people responsible for these symbols please write Configure.help entries and send them to me? Before this update Configure.help had complete coverage; let's try to keep it that way.

		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

"Today, we need a nation of Minutemen, citizens who are not only prepared to
take arms, but citizens who regard the preservation of freedom as the basic
purpose of their daily life and who are willing to consciously work and
sacrifice for that freedom."	-- John F. Kennedy

Hi Eric,

Yep, those are mine. They belong to Linux Bluetooth subsystem.

btw Linux is the first OS that has official Bluetooth support.

Here we go:

CONFIG_BLUEZ
Bluetooth is low-cost, low-power, short-range wireless technology. It was designed as a replacement for cables and other short-range technologies like IrDA. Bluetooth operates in personal area range that typically extends up to 10 meters.
More information about Bluetooth can be found at http://www.bluetooth.com

Linux Bluetooth subsystem consist of several layers:
HCI Core (device and connection manager, scheduler) HCI Device drivers (interface to the hardware) L2CAP Module (L2CAP protocol)

Say Y here to enable Linux Bluetooth support and to build HCI Core layer.

To use Linux Bluetooth subsystem, you will need several user-space utilities like hciconfig and hcid. These utilities and updates to Bluetooth kernel modules are provided in the BlueZ package.
For more information, see http://bluez.sf.net.

If you want to compile HCI Core as module (hci.o) say M here.

Not unsure ? say N.

CONFIG_BLUEZ_L2CAP
L2CAP (Logical Link Control and Adaptation Protocol) provides connection oriented and connection-less data transport. L2CAP support is required for most Bluetooth applications.

Say Y here to compile L2CAP support into the kernel or say M to compile it as module (l2cap.o).

Not unsure ? say M.

CONFIG_BLUEZ_HCIUART
Bluetooth HCI UART driver.
This driver is required if you want to use Bluetooth devices with serial port interface.

Say Y here to compile support for Bluetooth UART devices into the kernel or say M to compile it as module (hci_uart.o).

Not unsure ? say M.

CONFIG_BLUEZ_HCIUSB
Bluetooth HCI USB driver.
This driver is required if you want to use Bluetooth devices with USB interface.

Say Y here to compile support for Bluetooth USB devices into the kernel or say M to compile it as module (hci_usb.o).

Not unsure ? say M.

CONFIG_BLUEZ_HCIEMU
Bluetooth Virtual HCI device driver.
This driver is required if you want to use HCI Emulation software.

Say Y here to compile support for Virtual HCI devices into the kernel or say M to compile it as module (hci_usb.o).

Not unsure ? say M.

Thanks
Max

Maksim Krasnyanskiy
Senior Kernel Engineer
Qualcomm Incorporated

[email protected]
(408) 557-1092