summaryrefslogtreecommitdiffstats
path: root/Documentation/usb
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/usb')
-rw-r--r--Documentation/usb/acm.txt14
-rw-r--r--Documentation/usb/usb-serial.txt5
2 files changed, 0 insertions, 19 deletions
diff --git a/Documentation/usb/acm.txt b/Documentation/usb/acm.txt
index 8ef45ea8f691..737d6104c3f3 100644
--- a/Documentation/usb/acm.txt
+++ b/Documentation/usb/acm.txt
@@ -49,20 +49,6 @@ Abstract Control Model (USB CDC ACM) specification.
Unfortunately many modems and most ISDN TAs use proprietary interfaces and
thus won't work with this drivers. Check for ACM compliance before buying.
- The driver (with devfs) creates these devices in /dev/usb/acm:
-
- crw-r--r-- 1 root root 166, 0 Apr 1 10:49 0
- crw-r--r-- 1 root root 166, 1 Apr 1 10:49 1
- crw-r--r-- 1 root root 166, 2 Apr 1 10:49 2
-
- And so on, up to 31, with the limit being possible to change in acm.c to up
-to 256, so you can use up to 256 USB modems with one computer (you'll need
-three USB cards for that, though).
-
- If you don't use devfs, then you can create device nodes with the same
-minor/major numbers anywhere you want, but either the above location or
-/dev/usb/ttyACM0 is preferred.
-
To use the modems you need these modules loaded:
usbcore.ko
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
Currently the driver can handle up to 256 different serial interfaces at
one time.
- If you are not using devfs:
The major number that the driver uses is 188 so to use the driver,
create the following nodes:
mknod /dev/ttyUSB0 c 188 0
@@ -26,10 +25,6 @@ CONFIGURATION
mknod /dev/ttyUSB254 c 188 254
mknod /dev/ttyUSB255 c 188 255
- If you are using devfs:
- The devices supported by this driver will show up as
- /dev/usb/tts/{0,1,...}
-
When the device is connected and recognized by the driver, the driver
will print to the system log, which node(s) the device has been bound
to.