usb设备检测的一般过程（The general process of USB device detection）.doc

下载文档 降价啦

33
0
约5.73千字
约 9页
2017-08-31 发布于河南
举报
版权申诉
保障服务

usb设备检测的一般过程（The general process of USB device detection）.doc

1、本文档共9页，可阅读全部内容。
2、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。
3、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。

usb设备检测的一般过程（The general process of USB device detection）

usb设备检测的一般过程（The general process of USB device detection） You have to transplant the operating system to operate the camera? The general process of USB device detection USB device testing is also done through the USB file system in the /proc directory. To make a USB device work properly, the USB bridge module must be inserted into the system now. At the beginning of the test, it is generally necessary to check for the existence of the /proc/bus/usb directory, and if not, try inserting the USB bridge module. The general USB bridge module now has two types, UHCI and OHCI. When you decide to insert that bridge module, you can look at the /proc/pci file to decide. Open this file, if you find that the USB section is I/O, at, 0xHHHH format (for example, I/O at 0xe000 [0xe01f]) and HHHH is the 16 hexadecimal number, the bridge type is UHCI. If it is 32 bit, memory, at, 0xHH000000 form (for example, 32 bit memory at 0xee000000) and HH is 16 hexadecimal, the bridge type is OHCI. But if your bridge type does not satisfy any of the above, the only solution is that you try to insert the two modules until you succeed. In general, a UHCI type bridge whose plug-in module is UHCI or usb-uhci (determined by the kernel version); and for the OHCI type bridge, its plug-in module is OHCI or usb-ohci. After you have correctly inserted the bridge module, the USB device directory appears at the time of the /proc file system, but this directory is empty and there is no file. At this point you have to hook up the usbdevfs file system and then check the connection device through the file system. After successfully hooking up the USB file system, the files /proc/bus/usb/devices, /proc/bus/usb/drivers, and directory /proc/bus/usb/busNo are generated. Hook up the usbdevfs file and you can implement it as follows: Mount, -t, usbdevfs, none, /proc/bus/usb Or add on /etc/fstab None /proc/bus/usb usbdevfs defaults 00 Then, through the contents of the /proc/bus/usb/devices file, you can get the conne