Re: Configure.help entries for Bluetooth (updated)

Re: Configure.help entries for Bluetooth (updated)

[Rob Landley]

Okay, I'll bite.  What's HCI stand for?

I'm guessing it ends in "Connection Interface", but the H has me stumped.  
Happy?  Hostile?  Hysterical?  Hippopotamus?

If we're connecting a bluetooth compliant hippopotamus to Linux, I can only 
hope there's an RFC somewhere explaining how to do it.  That's not the kind 
of thing you want to make up your own interface for.  Especially since Alan 
Cox is entirely likely to get bored enough to try and implement it some day.  
The pigeons didn't stop him...

Rob

(I can just see Alan now, sneaking up on a hippopotamus with a blue magic 
marker to color its teeth with, and whatever tiny PDA he's managed to port 
Linux to by then.  A wristwatch, probably.  If Telsa is in the area, the 
question becomes "is it possible to crash a hippopotamus?)

I need to go home now.

Configure.help entries for Bluetooth (updated)

[Maksim Krasnyanskiy]

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 sure ? 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 sure ? 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 sure ? 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 sure ? 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 sure ? say M.

Thanks
Max

Maksim Krasnyanskiy		
Senior Kernel Engineer
Qualcomm Incorporated

maxk@qualcomm.com
(408) 557-1092

Re: Configure.help entries for Bluetooth (updated)

[Maksim Krasnyanskiy]

>Okay, I'll bite. 
Ouch that hurts ;)

>What's HCI stand for?
>I'm guessing it ends in "Connection Interface", but the H has me stumped.  
Wrong guess. HCI - Host Controller Interface.

People who use Bluetooth would know. HCI is the basic thing in Bluetooth world.
I don't think explaining that abbreviation would help in kernel configuration. 

Max

Maksim Krasnyanskiy		
Senior Kernel Engineer
Qualcomm Incorporated

maxk@qualcomm.com
(408) 557-1092