Commit 21470e32 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab Committed by Greg Kroah-Hartman

usb: fix some references for /proc/bus/usb

Since when we got rid of usbfs, the /proc/bus/usb is now
elsewhere. Fix references for it.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
Acked-by: default avatarSerge Hallyn <serge@hallyn.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent ac9d9476
...@@ -140,7 +140,7 @@ dev_hint ...@@ -140,7 +140,7 @@ dev_hint
A camera is specified by its type (the number from the camera model, A camera is specified by its type (the number from the camera model,
like PCA645, PCVC750VC, etc) and optionally the serial number (visible like PCA645, PCVC750VC, etc) and optionally the serial number (visible
in /proc/bus/usb/devices). A hint consists of a string with the following in /sys/kernel/debug/usb/devices). A hint consists of a string with the following
format: format:
[type[.serialnumber]:]node [type[.serialnumber]:]node
......
...@@ -12,7 +12,7 @@ config USB_ACM ...@@ -12,7 +12,7 @@ config USB_ACM
Please read <file:Documentation/usb/acm.txt> for details. Please read <file:Documentation/usb/acm.txt> for details.
If your modem only reports "Cls=ff(vend.)" in the descriptors in If your modem only reports "Cls=ff(vend.)" in the descriptors in
/proc/bus/usb/devices, then your modem will not work with this /sys/kernel/debug/usb/devices, then your modem will not work with this
driver. driver.
To compile this driver as a module, choose M here: the To compile this driver as a module, choose M here: the
......
...@@ -294,7 +294,7 @@ static int usblp_ctrl_msg(struct usblp *usblp, int request, int type, int dir, i ...@@ -294,7 +294,7 @@ static int usblp_ctrl_msg(struct usblp *usblp, int request, int type, int dir, i
/* /*
* See the description for usblp_select_alts() below for the usage * See the description for usblp_select_alts() below for the usage
* explanation. Look into your /proc/bus/usb/devices and dmesg in * explanation. Look into your /sys/kernel/debug/usb/devices and dmesg in
* case of any trouble. * case of any trouble.
*/ */
static int proto_bias = -1; static int proto_bias = -1;
......
...@@ -24,7 +24,7 @@ ...@@ -24,7 +24,7 @@
* <mountpoint>/devices contains USB topology, device, config, class, * <mountpoint>/devices contains USB topology, device, config, class,
* interface, & endpoint data. * interface, & endpoint data.
* *
* I considered using /proc/bus/usb/devices/device# for each device * I considered using /dev/bus/usb/device# for each device
* as it is attached or detached, but I didn't like this for some * as it is attached or detached, but I didn't like this for some
* reason -- maybe it's just too deep of a directory structure. * reason -- maybe it's just too deep of a directory structure.
* I also don't like looking in multiple places to gather and view * I also don't like looking in multiple places to gather and view
...@@ -40,7 +40,7 @@ ...@@ -40,7 +40,7 @@
* Converted the whole proc stuff to real * Converted the whole proc stuff to real
* read methods. Now not the whole device list needs to fit * read methods. Now not the whole device list needs to fit
* into one page, only the device list for one bus. * into one page, only the device list for one bus.
* Added a poll method to /proc/bus/usb/devices, to wake * Added a poll method to /sys/kernel/debug/usb/devices, to wake
* up an eventual usbd * up an eventual usbd
* 2000-01-04: Thomas Sailer <sailer@ife.ee.ethz.ch> * 2000-01-04: Thomas Sailer <sailer@ife.ee.ethz.ch>
* Turned into its own filesystem * Turned into its own filesystem
......
...@@ -42,7 +42,7 @@ ...@@ -42,7 +42,7 @@
* - a patch that adds the entry for your device, including your * - a patch that adds the entry for your device, including your
* email address right above the entry (plus maybe a brief * email address right above the entry (plus maybe a brief
* explanation of the reason for the entry), * explanation of the reason for the entry),
* - a copy of /proc/bus/usb/devices with your device plugged in * - a copy of /sys/kernel/debug/usb/devices with your device plugged in
* running with this patch. * running with this patch.
* Send your submission to either Phil Dibowitz <phil@ipom.com> or * Send your submission to either Phil Dibowitz <phil@ipom.com> or
* Alan Stern <stern@rowland.harvard.edu>, and don't forget to CC: the * Alan Stern <stern@rowland.harvard.edu>, and don't forget to CC: the
......
...@@ -318,7 +318,7 @@ void usb_put_intf(struct usb_interface *intf); ...@@ -318,7 +318,7 @@ void usb_put_intf(struct usb_interface *intf);
* struct usb_interface (which persists only as long as its configuration * struct usb_interface (which persists only as long as its configuration
* is installed). The altsetting arrays can be accessed through these * is installed). The altsetting arrays can be accessed through these
* structures at any time, permitting comparison of configurations and * structures at any time, permitting comparison of configurations and
* providing support for the /proc/bus/usb/devices pseudo-file. * providing support for the /sys/kernel/debug/usb/devices pseudo-file.
*/ */
struct usb_interface_cache { struct usb_interface_cache {
unsigned num_altsetting; /* number of alternate settings */ unsigned num_altsetting; /* number of alternate settings */
......
...@@ -205,7 +205,7 @@ struct vfs_cap_data { ...@@ -205,7 +205,7 @@ struct vfs_cap_data {
#define CAP_SYS_MODULE 16 #define CAP_SYS_MODULE 16
/* Allow ioperm/iopl access */ /* Allow ioperm/iopl access */
/* Allow sending USB messages to any device via /proc/bus/usb */ /* Allow sending USB messages to any device via /dev/bus/usb */
#define CAP_SYS_RAWIO 17 #define CAP_SYS_RAWIO 17
......
...@@ -224,7 +224,8 @@ struct usb_ctrlrequest { ...@@ -224,7 +224,8 @@ struct usb_ctrlrequest {
* through the Linux-USB APIs, they are not converted to cpu byte * through the Linux-USB APIs, they are not converted to cpu byte
* order; it is the responsibility of the client code to do this. * order; it is the responsibility of the client code to do this.
* The single exception is when device and configuration descriptors (but * The single exception is when device and configuration descriptors (but
* not other descriptors) are read from usbfs (i.e. /proc/bus/usb/BBB/DDD); * not other descriptors) are read from character devices
* (i.e. /dev/bus/usb/BBB/DDD);
* in this case the fields are converted to host endianness by the kernel. * in this case the fields are converted to host endianness by the kernel.
*/ */
......
...@@ -244,7 +244,7 @@ Detach the imported device: ...@@ -244,7 +244,7 @@ Detach the imported device:
- See 'Debug Tips' on the project wiki. - See 'Debug Tips' on the project wiki.
- http://usbip.wiki.sourceforge.net/how-to-debug-usbip - http://usbip.wiki.sourceforge.net/how-to-debug-usbip
- usbip-host.ko must be bound to the target device. - usbip-host.ko must be bound to the target device.
- See /proc/bus/usb/devices and find "Driver=..." lines of the device. - See /sys/kernel/debug/usb/devices and find "Driver=..." lines of the device.
- Target USB gadget must be bound to vudc - Target USB gadget must be bound to vudc
(using USB gadget susbsys, not usbip bind command) (using USB gadget susbsys, not usbip bind command)
- Shutdown firewall. - Shutdown firewall.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment