Menu
▾
▴
openbt-commit
|
From: Gordon M. <gm...@us...> - 2001-04-25 23:32:01
|
The following file was modified in linux/drivers/char/bluetooth: Name Old version New version Comment ---- ----------- ----------- ------- README 1.26 1.27=20=20=20=20=20=20=20=20=20=20=20=20 The accompanying log: --Added a FAQ The diff of the modified file(s): --- README 2001/03/04 17:54:54 1.26 +++ README 2001/04/25 23:32:00 1.27 @@ -395,7 +395,16 @@ 8) It does not work, what am I doing wrong?=20 -------------------------------------------- =20 -FIXME -- add FAQ=20 +FAQ=20 + +Q: What is the difference between kernel mode and user mode? +A: bt.o is the kernel mode driver. When you insmod bt.o you are inserting = it + into the kernel, where it can cause bad things to happen if it screws u= p. + The user mode driver runs like an application. + + btduser is the user mode driver. It runs as an application in user spac= e, + where usually the worse thing that can happen is a segfault. You don't = have + to insmod anything for user mode. You just run the application. =20 o If you are having troubles with trashed data on the UART please look=20 at http://developer.axis.com/download/bluetooth/uart_problems |
|
From: Gordon M. <gm...@us...> - 2001-04-25 23:35:51
|
The following file was modified in linux/drivers/char/bluetooth:
Name Old version New version Comment
---- ----------- ----------- -------
README 1.27 1.28=20=20=20=20=20=20=20=20=20=20=20=20
The accompanying log:
--Fixed a cut & paste error.
The diff of the modified file(s):
--- README 2001/04/25 23:32:00 1.27
+++ README 2001/04/25 23:35:50 1.28
@@ -400,7 +400,6 @@
Q: What is the difference between kernel mode and user mode?
A: bt.o is the kernel mode driver. When you insmod bt.o you are inserting =
it
into the kernel, where it can cause bad things to happen if it screws u=
p.
- The user mode driver runs like an application.
=20
btduser is the user mode driver. It runs as an application in user spac=
e,
where usually the worse thing that can happen is a segfault. You don't =
have
|
|
From: Gordon M. <gm...@us...> - 2001-04-26 16:34:25
|
The following file was modified in linux/drivers/char/bluetooth:
Name Old version New version Comment
---- ----------- ----------- -------
README 1.28 1.29=20=20=20=20=20=20=20=20=20=20=20=20
The accompanying log:
--Added to FAQ about building usermode.
The diff of the modified file(s):
--- README 2001/04/25 23:35:50 1.28
+++ README 2001/04/26 16:34:24 1.29
@@ -403,7 +403,9 @@
=20
btduser is the user mode driver. It runs as an application in user spac=
e,
where usually the worse thing that can happen is a segfault. You don't =
have
- to insmod anything for user mode. You just run the application.
+ to insmod anything for user mode. You just run the application. To build
+ the 'stack' for usermode just go to the top level and type 'make', foll=
owed
+ by 'make install' (as root). Then btduser should be in your path.
=20
o If you are having troubles with trashed data on the UART please look=20
at http://developer.axis.com/download/bluetooth/uart_problems
|
|
From: Gordon M. <gm...@us...> - 2001-04-27 14:52:17
|
The following file was modified in linux/drivers/char/bluetooth:
Name Old version New version Comment
---- ----------- ----------- -------
README 1.29 1.30=20=20=20=20=20=20=20=20=20=20=20=20
The accompanying log:
--Ammended FAQ.
The diff of the modified file(s):
--- README 2001/04/26 16:34:24 1.29
+++ README 2001/04/27 14:52:17 1.30
@@ -404,8 +404,27 @@
btduser is the user mode driver. It runs as an application in user spac=
e,
where usually the worse thing that can happen is a segfault. You don't =
have
to insmod anything for user mode. You just run the application. To build
- the 'stack' for usermode just go to the top level and type 'make', foll=
owed
- by 'make install' (as root). Then btduser should be in your path.
+ the 'stack' for usermode just go to the top level and type 'make'. If y=
ou
+ see errors while building btduser then cd to the btduser directory and =
type
+ 'make links'. Then try again. Finally, at the top level type 'make inst=
all'
+ (as root). Then btduser should be in your path.
+
+Q: After I make a connection from the client and try to send data I see the
+ following error message on the server side:
+
+ BT SYS: ERROR :Line 0 not active and linebuf full, silent discard \
+ (considerincreasing line buffer [256])
+
+A: It's not an error (even though the debug says it...), it only tells=20
+ you that the line buffer is full. The reason for this is that you don'=
t=20
+ seem to have an application on top of the tty which takes care of the=
=20
+ data. The line buffer was meant to store a small amount of data until =
an=20
+ application was started after detecting that a connection was setup. E=
.g=20
+ pppd is started over /dev/ttyBT0 when a new rfcomm is discovered. If t=
his=20
+ takes too long the data won't be lost. (Answer provided by Mattias Agr=
en)
+
+
+
=20
o If you are having troubles with trashed data on the UART please look=20
at http://developer.axis.com/download/bluetooth/uart_problems
|
|
From: Peter K. <pk...@us...> - 2001-10-19 13:39:42
|
The following file was modified in linux/drivers/char/bluetooth: Name Old version New version Comment ---- ----------- ----------- ------- README 1.30 1.31=20=20=20=20=20=20=20=20=20=20=20=20 The accompanying log: Updated (finally) to match the current status of the stack somewhat better. The diff of the modified file(s): --- README 2001/04/27 14:52:17 1.30 +++ README 2001/10/19 13:39:40 1.31 @@ -1,126 +1,129 @@ =20 -Bluetooth Driver for Linux Kernel v2.0 and v2.2 ------------------------------------------------ - -These files are work in progress. For more information on Bluetooth=20 -on Linux see http://developer.axis.com where you can find the newest=20 -versions of the software. - -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - -What has happened lately ------------------------- +Bluetooth Driver for Linux Kernel v2.0, v2.2 and v2.4 +----------------------------------------------------- =20 -8 Jan 2001 +These files are a work in progress. For more information on Bluetooth=20 +on Linux see http://sourceforge.net/projects/openbt/ where you can find +the newest versions of the software. =20 -* Made connect command available again (rf_conn/rf_disc/rf_send)=20 - (only use rfcomm when connect as client, since sdp client is=20 - still not implemented due to redesign in sdp). +See the ChangeLog file for list of all changes. =20 -* Fixed bugs in sdp browsing. +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -* Fixed race problems in hci and btmem. +1) How to build and install the AXIS Bluetooth Stack +---------------------------------------------------- =20 -* Added blocking on all tty:s when doing connect/disconnect and added=20 - an ioctl which blocks until an rfcomm is up on a specific line. +# Unpack the archive: =20 -* Now uses a 'raw' interface in usermode to send any vendor specific HCI= =20 - commands down to the module. +tar xvfz <name of archive> =20 -* Now possible to open ttyBTC multiple times +# Create the Bluetooth stack module and all applications (both for use + with the kernel version of the stack and the user mode version): =20 -* Now it works to setup an rfcomm connection on any of ttyBT0-6 (line)=20 - and use it as a virtual serial port. +cd openbt +source init_env =20 -* Fixed bug in bluetooth.c which could cause the stack to stop receiving= =20 - data from the user mode application. +(See section 6 on how to compile for different Bluetooth HW) =20 -* Separated all vendor specific code into separate files. +make =20 -* Added security functionalities in HCI and IOCTLs for enabling=20 - authentication, handling linkkeys, pincodes etc in bluetooth.c +# Install the applications in /usr/local/bin and the SDP configuration + file in /etc (must be done as root): =20 -* Added functions in lower driver to cope with overruns on serial port. +make install =20 -* Fixed ip_forwarding when using pppd on usermode stack (ppp option=20 - ktune). Only works on pppd ver > 2.3.7. +# If the BT device nodes have not been created previously then do=20 + (as root): =20 -* Added pid file to stop multiple instances of btd running. +make devs =20 -* Improved error handling in both btd and kernel parts. +# Insert the module into the kernel (must be done as root): =20 -* Lots of bug fixes and smaller improvements to many to mention here. +insmod src/bt.o =20 +# To get debug messages in kernel start another window and issue: =20 -** Note 1 ** -This stack does not support using pcmcia drivers for any pcmcia based=20 -BT card and only supports the HCI interface towards that HW in terms of=20 -setting baudrate and other HW specific functions. However, if someone=20 -gets their hands on any pcmcia driver code for some bluetooth HW please -let us know or do it yourself :) +tail -f /var/log/messages=20 =20 -** Note 2 ** -Init option to btd (-i) is now removed and replaced by a define in=20 -btd.h and btconfig.h (kernel) which determines what type of init that=20 -should be done for each HW vendor (see section 6) +(or whatever file is set in /etc/syslog.conf) =20 +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -Please let us know if there are any unclear issues or errors in this=20 -README. Comments are appreciated and if there are someone that feels=20 -an urge of making it more complete please contact us or send us a text=20 -fragment and we will happily include it ! +2) Multi-Point Bluetooth Daemon application (btdm) +-------------------------------------------------- =20 -Best regards=20 -Bluetooth Team, -Axis Communications +2.1) How to start the btdm application? =20 -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + Both short and long options may be used whatever suits best. =20 + syntax: ./btdm [options] =20 -1) How to build and install the AXIS Bluetooth Stack ----------------------------------------------------- + options:=20 =20 -# Unpack the archive: + -u, --physdev <uart device> + sets which uart device that will be used by the stack + default: ttyS2 =20 -tar xvfz <name of archive> + -m, --modem + Use modem emulation (used when emulate modem in windows=20 + dialup.=20 + Can also be done from command line mode.=20 + default: on =20 -# Create the bluetooth stack module and all applications (both for use - with the kernel version of the stack and the user mode version): + -n, --local-name + prefix used for the local Bluetooth device name + default: nothing =20 -cd bluetooth -source init_env + -R, --reset + reset Bluetooth hardware before use + default: no reset =20 -(See section 6 on how to compile for different bluetooth HW) + -i, --initial-speed <speed | baudbase/divisor> + sets initial uart speed + default: 115200 baud =20 -make + -s, --speed <speed> + sets uart speed + 9600, 19200, 38400, 57600, 115200, 230400, 460800 + default: 115200 baud =20 -# Install the applications in /usr/local/bin and the SDP configuration - file in /etc (must be done as root): + -f, --noflow + force uart communication to not use CTS and RTS + default: flow control activated if defined hardware support = it =20 -make install + e.g if using module at 460800 baud and acting as server + ./btdm --speed 460800 =20 -# If the BT device nodes have not been created previously then do=20 - (as root): + if using non default devices + ./btdm --physdev /dev/ttyS2 [options...] =20 -make devs +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -# Insert the module into the kernel (must be done as root): +2.2) How to setup a session between two units? =20 -insmod src/bt.o +Server side: =20 -# To get debug messages in kernel start another window and issue: +1. btdm --reset --speed 115200 =20 -tail -f /var/log/messages=20 +Client side: =20 -(or whatever file is set in /etc/syslog.conf) +1. bti --reset --speed 115200 +2. Connect to the other unit by executing + btcon -a <bd address> =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 +3) Bluetooth Daemon application (btd) +------------------------------------- =20 -2) Bluetooth Daemon application (btd)=20 + BTD IS OBSOLETE, AND SHOULD ONLY BE USED IN CASE BTDM DOES NOT + WORK AS EXPECTED. DO NOT EXPECT TO RECEIVE ANY SUPPORT FOR BTD. + ------------------------------------ =20 +3.1) How to start the btd application? + Both short and long options may be used whatever suits best. =20 syntax: ./btd [options] @@ -131,8 +134,8 @@ sets which uart device that will be used by the stack default: ttyS2 =20=09=20=20=20=20=20=20 - -b, --btdev <bluetooth device> - sets which bluetooth device that will be used from=20 + -b, --btdev <Bluetooth device> + sets which Bluetooth device that will be used from=20 application default: ttyBT0 =20 @@ -153,7 +156,7 @@ default: skip command line mode =20=20 -n, --local-name - prefix used for the local bluetooth device name + prefix used for the local Bluetooth device name default: nothing =20 "-r server", --server @@ -163,7 +166,7 @@ default: server =20 -R, --reset - reset bluetooth hardware before use + reset Bluetooth hardware before use default: no reset =20 -s, --speed <speed> @@ -181,7 +184,6 @@ Server listens on <:port>, client tries to connect to=20 <ipaddr:port>. (usermode stack only) =20 -=09=20=20=20=20=20=20 e.g if using module at 460800 baud and acting server ./btd --speed 460800 =20 @@ -201,12 +203,10 @@ same network Server : ./btd --cmdmode --tcpsock <:port>=20 Client : ./btd --cmdmode --tcpsocket <ipaddr:port> --client - -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -3) What do the command menu options do ? ----------------------------------------- +3.2) What do the command menu options do in btd? =20 inq (inquiry scan) Performs an inquiry to see what other devices that are present @@ -252,12 +252,10 @@ quit =20 Just quit. - -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 +- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -4) How to setup a session between two units --------------------------------------------- +3.3) How to setup a session between two units =20 Server side: =20 @@ -271,63 +269,52 @@ =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 - -5) How to use the stack in user mode instead of in the kernel +4) How to use the stack in user mode instead of in the kernel ------------------------------------------------------------- =20 -/* - * THE USERMODE STACK SHOULD ONLY BE USED FOR DEVELOPMENT AND - * TESTING OF BASIC STACK FUNCTIONALITIES AND DOES NOT PROVIDE - * THE FULL STACK FUNCTIONALITIES (blocking calls, multiple lines=20 - * etc etc). - */=20 + THE USERMODE STACK SHOULD ONLY BE USED FOR DEVELOPMENT AND + TESTING OF BASIC STACK FUNCTIONALITIES AND DOES NOT PROVIDE + THE FULL STACK FUNCTIONALITIES (blocking calls, multiple lines=20 + etc etc). =20 1) Build the applications according to the instructions above. =20 -2) Run btduser (as root) with the same options as with the standard +2) Run btduser (as root) with the same options as with the btd application (see above). =20 -If something isn't working look in /var/log/messages or whatever file is -syslogger is set to use (see /etc/syslog.conf)=20 +If something does not work, then look in /var/log/messages or whatever +file syslog is set to use (see /etc/syslog.conf)=20 =20 *** NOTE -- pppd must support running on pty:s (version >=3D 2.3.7) *** =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - - -6) How do I setup the stack for different bluetooth hardware ------------------------------------------------------------- - -There are two files that needs to be changed =20 -Kernel : btconfig.h, set CONFIG_BLUETOOTH_<hardware> to whatever you are u= sing - -Usermode app : btd.c, set HW_CURRENT to whatever you are using=20 +5) How do I setup the stack for different Bluetooth hardware? +------------------------------------------------------------- =20 -** Note **=20 -If running usermode stack it is only necessary to change in btconfig.h +You need to modify btconfig.h, and define whichever of +CONFIG_BLUETOOTH_<hardware> that matches the hardware you are using. =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - =20 -7) How to setup a session without any bluetooth hardware +6) How to setup a session without any Bluetooth hardware -------------------------------------------------------- =20 -To make the stack work without any hardware HCI_EMULATION must be=20 +To make the stack work without any hardware, HCI_EMULATION must be=20 switched on in the file btconfig.h and the stack must be recompiled. -You will see a note in the debug messages when starting the stack if hci +You will see a note in the debug messages when starting the stack if HCI emulation really is used or not. =20 ******** * Note * ******** =20 -The HCI emulation as of today simply converts some hci commands to the=20 -corresponding events and simply forwards all acl/sco data. +The HCI emulation as of today simply converts some HCI commands to the=20 +corresponding events and simply forwards all ACL/SCO data. If you get messages from the stack that something fails when initiating=20 -the stack it is because those hci commands are not supported in the=20 -hci emulator. -Anyone that wants are welcome to improve it and send us a patch. For=20 +the stack it is because those HCI commands are not supported in the=20 +HCI emulator. +Anyone who wants to is welcome to improve it and send us a patch. For=20 example, there could be network delays/ packet losses included and=20 different kinds of hardware can be simulated. =20 @@ -340,7 +327,7 @@ =20 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -7.1) Using a serial cable (null modem) +6.1) Using a serial cable (null modem) =20 Connect 2 Linux PC with a null modem cable, and start the btd=20 application as server as one side and btd as client on the other side. @@ -360,7 +347,7 @@ =20 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -7.2) Using a local unix socket on one computer +6.2) Using a local unix socket on one computer =20 Server side: 1. btd --cmdmode --unixsock @@ -374,7 +361,7 @@ =20 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =20 -7.3) Using a network tcp socket between two computers +6.3) Using a network tcp socket between two computers =20 if using the stack in user mode over a TCP socket. Do the following on separate computers connected to a network @@ -390,10 +377,9 @@ (BD address is ignored) =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - =20 -8) It does not work, what am I doing wrong?=20 --------------------------------------------- +7) It does not work, what am I doing wrong?=20 +------------------------------------------- =20 FAQ=20 =20 @@ -423,106 +409,31 @@ pppd is started over /dev/ttyBT0 when a new rfcomm is discovered. If t= his=20 takes too long the data won't be lost. (Answer provided by Mattias Agr= en) =20 - - - o If you are having troubles with trashed data on the UART please look=20 at http://developer.axis.com/download/bluetooth/uart_problems =20 -o ... - -For debug when running in kernel look in /var/log/messages,=20 +For debug when running in kernel, look in /var/log/messages,=20 /var/log/debug or whatever file is specified in /etc/syslog.conf =20 If you think you have found a bug please switch on all debug in=20 btdebug.h and send the logs to blu...@ax... together with a=20 description of the problem. =20 -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - -9) OLD RELEASES - =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 - -Nov 15 2000 - -*** Bug fixes after the Unplugfest 4 *** - -- Corrected C/R-bit in RFCOMM. -- Corrected browsing in SDP. -- Added all unplugtests in rfcomm and l2cap. -- Misc fixes in all layers. - -*** Other *** - -- Started restructuring of btd to make the application hardware=20 - independent and more readable. -- Restructuring will also be done in hci to make it hardware=20 - independent too. -- Added connect indication and disconnect indication in bluetooth.c. -- Added connection ID consisting of |PSM 16 bits|layer specific 16 bits|= =20 - The layerspecific field in RFCOMM is | line 8 bits | dlci 8 bits |. - In the other layers are the connection ID not used at all (yet). - -------------------------------------------------------------------------- - -Oct 30 2000 - -Finally, a new release! - -There has been quite a few changes and it is hard to include everything -in this text. However, we will try to make a quick introduction of the=20 -new functionality. - - -*** Kernel Stack *** - -- We now support the use of several tty:s (currently 7, ttyBT0-ttyBT6)=20 - and the control of the stack has been moved to a dedicated tty=20 - called ttyBTC (minor 7) -- Improved interface between user mode tty and kernel. -- More ioctls for HCI commands -- Improved SDP which now uses a user mode database for queries. -- Added functionality for choosing different HW (init stuff) -- Added scheduling of cmd queueing for USB -- Lots of bug fixes - -*** Comment *** - - As of today we have no client functionality in SDP due to changes - in the design. However, as server Serial/LAN/DialUP profile is=20 - supported. This will be fixed soon. - -*** User Mode Applications *** - -- New SDP server database application using XML files.=20 - See /apps/sdp_server/README for details. -- Command line history -- Now pppd works together with the user mode stack (using pty:s) -- Using syslog for most debug (see /var/log/messages) -- Added functionality to run usermode stack on both a local UNIX socket - and on a network socket (used with hardware emulation, HCI_EMULATION) - Please let us know if there are any unclear issues or errors in this=20 README. Comments are appreciated and if there are someone that feels=20 an urge of making it more complete please contact us or send us a text=20 fragment and we will happily include it ! =20 -There are still patches left to include but due to heavy workload we=20 -have not had time to add them all. However, in the future if a patch=20 -is sent to us reasonably fast (within 2 weeks) after a new release we=20 -should be able to merge it in the stack. - Finally, we would also like to thank all contributors on the stack for=20 -comments and patches etc. Once we get our open CVS up and running this=20 -stack should be very useful for any bluetooth developer !! +comments and patches etc. =20 Keep up the good work ! =20 Best regards=20 -Bluetooth Team, -Axis Communications +The Bluetooth Team, +Axis Communications AB =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |
|
From: Peter K. <pk...@us...> - 2001-11-05 13:28:28
|
The following file was modified in linux/drivers/char/bluetooth: Name Old version New version Comment ---- ----------- ----------- ------- README 1.31 1.32=20=20=20=20=20=20=20=20=20=20=20=20 The accompanying log: Corrected the instruction for how to insmod the bt.o module. The diff of the modified file(s): --- README 2001/10/19 13:39:40 1.31 +++ README 2001/11/05 13:28:27 1.32 @@ -40,9 +40,9 @@ =20 # Insert the module into the kernel (must be done as root): =20 -insmod src/bt.o +insmod linux/drivers/char/bluetooth/bt.o =20 -# To get debug messages in kernel start another window and issue: +# To see debug messages from the kernel start another window and issue: =20 tail -f /var/log/messages=20 =20 |
Thanks for helping keep SourceForge clean.
X