fox2mike    05/07/26 11:44:34

  Modified:    xml/htdocs/doc/en/draft bluetooth-guide.xml
  Log:
  Mixed bag of changes...

Revision  Changes    Path
1.2       +58 -102   xml/htdocs/doc/en/draft/bluetooth-guide.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bluetooth-guide.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bluetooth-guide.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bluetooth-guide.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: bluetooth-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bluetooth-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bluetooth-guide.xml 25 Jul 2005 11:12:45 -0000      1.1
+++ bluetooth-guide.xml 26 Jul 2005 11:44:34 -0000      1.2
@@ -123,19 +123,19 @@
 <M>   L2CAP protocol support
 <M>   SCO links support
 <M>   RFCOMM protocol support
-   [*]        RFCOMM TTY support
+[*]     RFCOMM TTY support
 <M>   BNEP protocol support
-   [*]        Multicast filter support
-   [*]        Protocol filter support
+[*]     Multicast filter support
+[*]     Protocol filter support
 <M>   HIDP protocol support
 
 Bluetooth device drivers  --->
 <M> HCI USB driver
-   [*]      SCO (voice) support
+[*]   SCO (voice) support
 <M> HCI UART driver
-   [*]      UART (H4) protocol support
-   [*]      BCSP protocol support
-   [*]        Transmit CRC with every BCSP packet
+[*]   UART (H4) protocol support
+[*]   BCSP protocol support
+[*]   Transmit CRC with every BCSP packet
 <M> HCI BCM203x USB driver
 <M> HCI BPA10x USB driver
 <M> HCI BlueFRITZ! USB driver
@@ -156,8 +156,8 @@
 <*> Support for Host-side USB
 --- USB Host Controller Drivers
 <M> EHCI HCD (USB 2.0) support
-   [ ]      Full speed ISO transactions (EXPERIMENTAL)
-   [ ]      Root Hub Transaction Translators (EXPERIMENTAL)
+[ ]   Full speed ISO transactions (EXPERIMENTAL)
+[ ]   Root Hub Transaction Translators (EXPERIMENTAL)
 <*> OHCI HCD support
 <*> UHCI HCD (most Intel and VIA) support
 < > SL811HS HCD support
@@ -193,7 +193,7 @@
 </chapter>
 
 <chapter id="bluez">
-<title>BlueZ installation, configuration and PIN pairing</title>
+<title>BlueZ Installation</title>
 <section>
 <title>Installing BlueZ</title>
 <body>
@@ -202,18 +202,14 @@
 Now that the device is detected by the kernel, we need a layer that lets
 applications communicate with the Bluetooth device. BlueZ provides the official
 Linux Bluetooth stack. The ebuilds that provide what we need are
-<c>bluez-libs</c> and <c>bluez-utils</c>.
+<c>bluez-libs</c> and <c>bluez-utils</c>. Devices that need Broadcom firmware
+files or the like may need <c>bluez-firmware</c>.
 </p>
 
 <pre caption="Installing bluez-libs and bluez-utils">
 # <i>emerge net-wireless/bluez-libs net-wireless/bluez-utils</i>
 </pre>
 
-<impo>
-Some devices might also need <c>bluez-firmware</c> to get the Broadcom firmware
-files.
-</impo>
-
 <warn>
 Do not emerge <c>bluez-kernel</c> or <c>bluez-sdp</c> as they will break
 <c>bluez-utils</c>!
@@ -239,16 +235,16 @@
 
 <p>
 Now it's time to see if the Bluetooth device is being picked up correctly by 
the
-system.
+system. We start up the required Bluetooth services first.
 </p>
 
 <pre caption="Running hciconfig">
 <comment>(Start up Bluetooth)</comment>
 # <i>/etc/init.d/bluetooth start</i>
 * Starting Bluetooth ...
-*     Starting hcid ...                                                  [ ok ]
-*     Starting sdpd ...                                                  [ ok ]
-*     Starting rfcomm ...                                                [ ok ]
+*     Starting hcid ...                                                 [ ok ]
+*     Starting sdpd ...                                                 [ ok ]
+*     Starting rfcomm ...                                               [ ok ]
 
 # <i>hciconfig</i>
 hci0:   Type: USB
@@ -261,85 +257,45 @@
 <p>
 This shows that the Bluetooth device has been recognised. As you might have
 noticed the device is <e>DOWN</e>. Let's configure it so that we can bring it
-up. A sample file with an already configured device is below. For additional
-details: <c>man hcid.conf</c>.
+up. The configuration file is at <path>/etc/bluetooth/hcid.conf</path>. The
+required changes to the config file are shown below. For additional details
+please refer to <c>man hcid.conf</c>.
 </p>
 
-<pre caption="/etc/bluetooth/hcid.conf">
-<comment>#</comment>
-<comment># HCI daemon configuration file.</comment>
-<comment>#</comment>
-
-<comment># HCId options</comment>
-options {
-        <comment># Automatically initialize new devices</comment>
-        autoinit yes;
-
-        <comment># Security Manager mode</comment>
-        <comment>#   none - Security manager disabled</comment>
-        <comment>#   auto - Use local PIN for incoming connections</comment>
-        <comment>#   user - Always ask user for a PIN</comment>
-        <comment>#</comment>
+<pre caption="Editing /etc/bluetooth/hcid.conf">
+<comment>(Recommended changes to be made to the file are shown)</comment>
+
+<comment>(Change security to "auto")</comment>
+        # Security Manager mode
+        #   none - Security manager disabled
+        #   auto - Use local PIN for incoming connections
+        #   user - Always ask user for a PIN
+        #
         security auto;
-
-        <comment># Pairing mode</comment>
-        <comment>#   none  - Pairing disabled</comment>
-        <comment>#   multi - Allow pairing with already paired devices
-        </comment>
-        <comment>#   once  - Pair once and deny successive attempts</comment>
-        pairing multi;
-
-        <comment># PIN helper</comment>
-        <comment># pin_helper /usr/bin/bluepin;</comment>
+                               
+<comment>(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
+        # PIN helper
         pin_helper /etc/bluetooth/pin-helper;
 
-        <comment># D-Bus PIN helper</comment>
-        <comment>#dbus_pin_helper;</comment>
-}
-
-<comment># Default settings for HCI devices</comment>
-device {
-        <comment># Local device name</comment>
-        <comment> #   %d - device id</comment>
-        <comment> #   %h - host name</comment>
+<comment>(Set your device name here, you can call it anything you
+want)</comment>
+        # Local device name
+        #   %d - device id
+        #   %h - host name
         name "BlueZ at %h (%d)";
 
-        <comment> # Local device class</comment>
-        class 0x3e0100;
-
-        <comment> # Default packet type</comment>
-        <comment> #pkt_type DH1,DM1,HV1;</comment>
-
-        <comment> # Inquiry and Page scan</comment>
-        iscan enable; pscan enable;
-
-        <comment># Default link mode</comment>
-        <comment>#   none   - no specific policy</comment>
-        <comment>#   accept - always accept incoming connections</comment>
-        <comment>#   master - become master on incoming connections,</comment>
-        <comment>#            deny role switch on outgoing connections
-        </comment>
-        lm accept;
-
-        <comment># Default link policy</comment>
-        <comment>#   none    - no specific policy</comment>
-        <comment>#   rswitch - allow role switch</comment>
-        <comment>#   hold    - allow hold mode</comment>
-        <comment>#   sniff   - allow sniff mode</comment>
-        <comment>#   park    - allow park mode</comment>
-        lp rswitch,hold,sniff,park;
-
-        <comment># Authentication and Encryption (Security Mode 3)</comment>
-        <comment>#auth enable;</comment>
-        <comment>#encrypt enable;</comment>
+<comment>(Leave as is, if you don't know what exactly these do)</comment>
+        # Authentication and Encryption (Security Mode 3)
+        #auth enable;
+        #encrypt enable;
 }
 </pre>
 



-- 
[email protected] mailing list

Reply via email to