Commit c611d2cd2f74988baa9a4c6cfc8a48064fd075e6
Committed by
Linus Torvalds
1 parent
d4ece29d89
Exists in
master
and in
7 other branches
[PATCH] USB: Delete leftovers from bluetty driver
This patch deletes the bluetooth.txt help file of the bluetty driver and hands over its major device nodes for character devices to the RFCOMM TTY implementation of the Bluetooth subsystem. Signed-off-by: Marcel Holtmann <marcel@holtmann.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Showing 2 changed files with 6 additions and 50 deletions Side-by-side Diff
Documentation/devices.txt
... | ... | @@ -2903,14 +2903,14 @@ |
2903 | 2903 | 196 = /dev/dvb/adapter3/video0 first video decoder of fourth card |
2904 | 2904 | |
2905 | 2905 | |
2906 | -216 char USB BlueTooth devices | |
2907 | - 0 = /dev/ttyUB0 First USB BlueTooth device | |
2908 | - 1 = /dev/ttyUB1 Second USB BlueTooth device | |
2906 | +216 char Bluetooth RFCOMM TTY devices | |
2907 | + 0 = /dev/rfcomm0 First Bluetooth RFCOMM TTY device | |
2908 | + 1 = /dev/rfcomm1 Second Bluetooth RFCOMM TTY device | |
2909 | 2909 | ... |
2910 | 2910 | |
2911 | -217 char USB BlueTooth devices (alternate devices) | |
2912 | - 0 = /dev/cuub0 Callout device for ttyUB0 | |
2913 | - 1 = /dev/cuub1 Callout device for ttyUB1 | |
2911 | +217 char Bluetooth RFCOMM TTY devices (alternate devices) | |
2912 | + 0 = /dev/curf0 Callout device for rfcomm0 | |
2913 | + 1 = /dev/curf1 Callout device for rfcomm1 | |
2914 | 2914 | ... |
2915 | 2915 | |
2916 | 2916 | 218 char The Logical Company bus Unibus/Qbus adapters |
Documentation/usb/bluetooth.txt
1 | -INTRODUCTION | |
2 | - | |
3 | - The USB Bluetooth driver supports any USB Bluetooth device. | |
4 | - It currently works well with the Linux USB Bluetooth stack from Axis | |
5 | - (available at http://developer.axis.com/software/bluetooth/ ) and | |
6 | - has been rumored to work with other Linux USB Bluetooth stacks. | |
7 | - | |
8 | - | |
9 | -CONFIGURATION | |
10 | - | |
11 | - Currently the driver can handle up to 256 different USB Bluetooth | |
12 | - devices at once. | |
13 | - | |
14 | - If you are not using devfs: | |
15 | - The major number that the driver uses is 216 so to use the driver, | |
16 | - create the following nodes: | |
17 | - mknod /dev/ttyUB0 c 216 0 | |
18 | - mknod /dev/ttyUB1 c 216 1 | |
19 | - mknod /dev/ttyUB2 c 216 2 | |
20 | - mknod /dev/ttyUB3 c 216 3 | |
21 | - . | |
22 | - . | |
23 | - . | |
24 | - mknod /dev/ttyUB254 c 216 254 | |
25 | - mknod /dev/ttyUB255 c 216 255 | |
26 | - | |
27 | - If you are using devfs: | |
28 | - The devices supported by this driver will show up as | |
29 | - /dev/usb/ttub/{0,1,...} | |
30 | - | |
31 | - When the device is connected and recognized by the driver, the driver | |
32 | - will print to the system log, which node the device has been bound to. | |
33 | - | |
34 | - | |
35 | -CONTACT: | |
36 | - | |
37 | - If anyone has any problems using this driver, please contact me, or | |
38 | - join the Linux-USB mailing list (information on joining the mailing | |
39 | - list, as well as a link to its searchable archive is at | |
40 | - http://www.linux-usb.org/ ) | |
41 | - | |
42 | - | |
43 | -Greg Kroah-Hartman | |
44 | -greg@kroah.com |