diff options
author | Adrian Bunk <bunk@stusta.de> | 2006-10-03 16:17:48 -0400 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 16:17:48 -0400 |
commit | bf6ee0ae494596aaf311e8430684db85d1d2f25c (patch) | |
tree | 80af10d1539d20ed00ffe19bb5af51cd6a976a19 /Documentation/usb/usb-serial.txt | |
parent | 0a8fe0d756fba2953462cec6db09c81dd732d0b5 (diff) |
remove mentionings of devfs in documentation
Now that devfs is removed, there's no longer any need to document how to
do this or that with devfs.
This patch includes some improvements by Joe Perches.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/usb/usb-serial.txt')
-rw-r--r-- | Documentation/usb/usb-serial.txt | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/Documentation/usb/usb-serial.txt b/Documentation/usb/usb-serial.txt index a2dee6e6190d..eca85f373419 100644 --- a/Documentation/usb/usb-serial.txt +++ b/Documentation/usb/usb-serial.txt | |||
@@ -13,7 +13,6 @@ CONFIGURATION | |||
13 | Currently the driver can handle up to 256 different serial interfaces at | 13 | Currently the driver can handle up to 256 different serial interfaces at |
14 | one time. | 14 | one time. |
15 | 15 | ||
16 | If you are not using devfs: | ||
17 | The major number that the driver uses is 188 so to use the driver, | 16 | The major number that the driver uses is 188 so to use the driver, |
18 | create the following nodes: | 17 | create the following nodes: |
19 | mknod /dev/ttyUSB0 c 188 0 | 18 | mknod /dev/ttyUSB0 c 188 0 |
@@ -26,10 +25,6 @@ CONFIGURATION | |||
26 | mknod /dev/ttyUSB254 c 188 254 | 25 | mknod /dev/ttyUSB254 c 188 254 |
27 | mknod /dev/ttyUSB255 c 188 255 | 26 | mknod /dev/ttyUSB255 c 188 255 |
28 | 27 | ||
29 | If you are using devfs: | ||
30 | The devices supported by this driver will show up as | ||
31 | /dev/usb/tts/{0,1,...} | ||
32 | |||
33 | When the device is connected and recognized by the driver, the driver | 28 | When the device is connected and recognized by the driver, the driver |
34 | will print to the system log, which node(s) the device has been bound | 29 | will print to the system log, which node(s) the device has been bound |
35 | to. | 30 | to. |