Quantcast

libusb_open_device_with_vid_pid

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

libusb_open_device_with_vid_pid

1010
need help

dev_handle = libusb_open_device_with_vid_pid(NULL, ivendor, iproduct);
libusb_release_interface(dev_handle, 0);

why  dev_handle ==NULL;

++libusb_get_device_list is OK
      libusb_get_device_descriptor is OK
      so I think liusb_open() failed, but why??

I only want to get information of usbdev through netlink, if dev is storage , make it disable(libusb_release_interface)。what can i do?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: libusb_open_device_with_vid_pid

Xiaofan Chen
On Tue, Nov 22, 2011 at 1:59 PM, 1010 <[hidden email]> wrote:

> need help
>
> dev_handle = libusb_open_device_with_vid_pid(NULL, ivendor, iproduct);
> libusb_release_interface(dev_handle, 0);
>
> why  dev_handle ==NULL;
>
> ++libusb_get_device_list is OK
>      libusb_get_device_descriptor is OK
>      so I think liusb_open() failed, but why??

What is the OS? What is the device? If it is Windows, did you install
WinUSB driver? If it is Linux, did you have proper permission?

> I only want to get information of usbdev through netlink, if dev is storage
> , make it disable(libusb_release_interface)。what can i do?

I have no idea what you are talking about. What is netlink?
What do you want to do?

If it is a USB Mass Storage Device and your aim is to disable
USB Mass Storage Device, then libusb is the wrong tool.


--
Xiaofan

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

回复: Re: libusb_open_device_with_vid_pid

1010
sorry
 
plat:x86 linux 2.6.18 root执行
 
我就是想控制一下u盘使用啊
 
因为需求是要适合所有linux版本 所以不能动内核。只能在用户态写了。
 
根据netlink接收usb的上报事件, 如果是存储设备的接口,借助libusb释放一下usb设备,从而达到禁用usb的功能。
 
2011-11-22


发件人: "Xiaofan Chen [via LibUSB]" <[hidden email]>
发送时间: 2011-11-22 15:34
主 题: Re: libusb_open_device_with_vid_pid
收件人: 1010 <[hidden email]>


On Tue, Nov 22, 2011 at 1:59 PM, 1010 <[hidden email]> wrote:

> need help
>
> dev_handle = libusb_open_device_with_vid_pid(NULL, ivendor, iproduct);
> libusb_release_interface(dev_handle, 0);
>
> why  dev_handle ==NULL;
>
> ++libusb_get_device_list is OK
>      libusb_get_device_descriptor is OK
>      so I think liusb_open() failed, but why??
What is the OS? What is the device? If it is Windows, did you install
WinUSB driver? If it is Linux, did you have proper permission?

> I only want to get information of usbdev through netlink, if dev is storage
> , make it disable(libusb_release_interface)。what can i do?

I have no idea what you are talking about. What is netlink?
What do you want to do?

If it is a USB Mass Storage Device and your aim is to disable
USB Mass Storage Device, then libusb is the wrong tool.


--
Xiaofan

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel



If you reply to this email, your message will be added to the discussion below:
http://libusb.6.n5.nabble.com/libusb-open-device-with-vid-pid-tp5012586p5012733.html
To unsubscribe from libusb_open_device_with_vid_pid, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: libusb_open_device_with_vid_pid

1010
In reply to this post by 1010
x86  linux2.6.18   root
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: libusb_open_device_with_vid_pid

Xiaofan Chen
In reply to this post by 1010
On Tue, Nov 22, 2011 at 3:51 PM, 1010 <[hidden email]> wrote:
> sorry
>
> plat:x86 linux 2.6.18 root执行

Please take note English is the working language for this list.

> 我就是想控制一下u盘使用啊

Translation: I just want to control USB Mass Storage Device.

> 因为需求是要适合所有linux版本 所以不能动内核。只能在用户态写了。

Translation: because this needs to work for all Linux version, I
can not touch the kernel and thus can only use user-space.

> 根据netlink接收usb的上报事件, 如果是存储设备的接口,
> 借助libusb释放一下usb设备,从而达到禁用usb的功能。

Transkation: use netlink to receive usb event, if it is USB Mass
Storage Interface, use libusb to release the interface, in order
to disable the USB nass storage device.

--------------

Answer: libusb is not the right tool for access control of USB
mass storage device. Others may give you some suggestions
for the right tool to use.


--
Xiaofan

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: libusb_open_device_with_vid_pid

Alan Stern
On Tue, 22 Nov 2011, Xiaofan Chen wrote:

> On Tue, Nov 22, 2011 at 3:51 PM, 1010 <[hidden email]> wrote:
> > sorry
> >
> > plat:x86 linux 2.6.18 rootִ��
>
> Please take note English is the working language for this list.
>
> > �Ҿ��������һ��u��ʹ�ð�
>
> Translation: I just want to control USB Mass Storage Device.
>
> > ��Ϊ������Ҫ�ʺ�����linux�汾 ���Բ��ܶ��ںˡ�ֻ�����û�̬д�ˡ�
>
> Translation: because this needs to work for all Linux version, I
> can not touch the kernel and thus can only use user-space.
>
> > ���netlink����usb���ϱ��¼��� ����Ǵ洢�豸�Ľӿڣ�
> > ����libusb�ͷ�һ��usb�豸���Ӷ�ﵽ����usb�Ĺ��ܡ�
>
> Transkation: use netlink to receive usb event, if it is USB Mass
> Storage Interface, use libusb to release the interface, in order
> to disable the USB nass storage device.
>
> --------------
>
> Answer: libusb is not the right tool for access control of USB
> mass storage device. Others may give you some suggestions
> for the right tool to use.
If you want to prevent people from using USB mass-storage devices, the
best approach is to blacklist the usb-storage driver, by adding its
name to a blacklist-*.conf file in /etc/modprobe.d.  The same thing has
to be done with the ub driver, if it is present.

Alan Stern



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

回复: Re: 回复: Re: libusb_open_device_with_vid_pid

1010
At first thank Alan Stern 
for your answer,
 
but "Once you add an entry to the blacklist.conf file, you must reboot your system for the changes to take effect".
how should ido without depend on reboot?
 
2011-11-23


发件人: "Alan Stern [via LibUSB]" <[hidden email]>
发送时间: 2011-11-23 00:25
主 题: Re: 回复: Re: libusb_open_device_with_vid_pid
收件人: 1010 <[hidden email]>


On Tue, 22 Nov 2011, Xiaofan Chen wrote:

> On Tue, Nov 22, 2011 at 3:51 PM, 1010 <[hidden email]> wrote:
> > sorry
> >
> > plat:x86 linux 2.6.18 rootִ��
>
> Please take note English is the working language for this list.
>
> > �Ҿ��������һ��u��ʹ�ð�
>
> Translation: I just want to control USB Mass Storage Device.
>
> > ��Ϊ������Ҫ�ʺ�����linux�汾 ���Բ��ܶ��ںˡ�ֻ�����û�̬д�ˡ�
>
> Translation: because this needs to work for all Linux version, I
> can not touch the kernel and thus can only use user-space.
>
> > ���netlink����usb���ϱ��¼��� ����Ǵ洢�豸�Ľӿڣ�
> > ����libusb�ͷ�һ��usb�豸���Ӷ�ﵽ����usb�Ĺ��ܡ�
>
> Transkation: use netlink to receive usb event, if it is USB Mass
> Storage Interface, use libusb to release the interface, in order
> to disable the USB nass storage device.
>
> --------------
>
> Answer: libusb is not the right tool for access control of USB
> mass storage device. Others may give you some suggestions
> for the right tool to use.
If you want to prevent people from using USB mass-storage devices, the
best approach is to blacklist the usb-storage driver, by adding its
name to a blacklist-*.conf file in /etc/modprobe.d.  The same thing has
to be done with the ub driver, if it is present.

Alan Stern



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel



If you reply to this email, your message will be added to the discussion below:
http://libusb.6.n5.nabble.com/libusb-open-device-with-vid-pid-tp5012586p5014027.html
To unsubscribe from libusb_open_device_with_vid_pid, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

回复: Re: 回复: Re: libusb_open_device_with_vid_pid

1010
In reply to this post by Alan Stern

Sometimes you can use the /proc and /sys filesystems to disable the hardware. For example, if you want to disable a cpu you would use the following command:

echo 0 >> /sys/devices/system/cpu/cpu1/online

I find a method, but i do not know whether it is useful for usb storage is disabled.

2011-11-23


发件人: "Alan Stern [via LibUSB]" <[hidden email]>
发送时间: 2011-11-23 00:25
主 题: Re: 回复: Re: libusb_open_device_with_vid_pid
收件人: 1010 <[hidden email]>


On Tue, 22 Nov 2011, Xiaofan Chen wrote:

> On Tue, Nov 22, 2011 at 3:51 PM, 1010 <[hidden email]> wrote:
> > sorry
> >
> > plat:x86 linux 2.6.18 rootִ��
>
> Please take note English is the working language for this list.
>
> > �Ҿ��������һ��u��ʹ�ð�
>
> Translation: I just want to control USB Mass Storage Device.
>
> > ��Ϊ������Ҫ�ʺ�����linux�汾 ���Բ��ܶ��ںˡ�ֻ�����û�̬д�ˡ�
>
> Translation: because this needs to work for all Linux version, I
> can not touch the kernel and thus can only use user-space.
>
> > ���netlink����usb���ϱ��¼��� ����Ǵ洢�豸�Ľӿڣ�
> > ����libusb�ͷ�һ��usb�豸���Ӷ�ﵽ����usb�Ĺ��ܡ�
>
> Transkation: use netlink to receive usb event, if it is USB Mass
> Storage Interface, use libusb to release the interface, in order
> to disable the USB nass storage device.
>
> --------------
>
> Answer: libusb is not the right tool for access control of USB
> mass storage device. Others may give you some suggestions
> for the right tool to use.
If you want to prevent people from using USB mass-storage devices, the
best approach is to blacklist the usb-storage driver, by adding its
name to a blacklist-*.conf file in /etc/modprobe.d.  The same thing has
to be done with the ub driver, if it is present.

Alan Stern



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel



If you reply to this email, your message will be added to the discussion below:
http://libusb.6.n5.nabble.com/libusb-open-device-with-vid-pid-tp5012586p5014027.html
To unsubscribe from libusb_open_device_with_vid_pid, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

回复: Re: 回复: Re: libusb_open_device_with_vid_pid

1010
In reply to this post by Alan Stern

Sometimes you can use the /proc and /sys filesystems to disable the hardware. For example, if you want to disable a cpu you would use the following command:

echo 0 >> /sys/devices/system/cpu/cpu1/online

I find a method, but i do not know whether it is useful for usb storage is disabled.

2011-11-23


发件人: "Alan Stern [via LibUSB]" <[hidden email]>
发送时间: 2011-11-23 00:25
主 题: Re: 回复: Re: libusb_open_device_with_vid_pid
收件人: 1010 <[hidden email]>


On Tue, 22 Nov 2011, Xiaofan Chen wrote:

> On Tue, Nov 22, 2011 at 3:51 PM, 1010 <[hidden email]> wrote:
> > sorry
> >
> > plat:x86 linux 2.6.18 rootִ��
>
> Please take note English is the working language for this list.
>
> > �Ҿ��������һ��u��ʹ�ð�
>
> Translation: I just want to control USB Mass Storage Device.
>
> > ��Ϊ������Ҫ�ʺ�����linux�汾 ���Բ��ܶ��ںˡ�ֻ�����û�̬д�ˡ�
>
> Translation: because this needs to work for all Linux version, I
> can not touch the kernel and thus can only use user-space.
>
> > ���netlink����usb���ϱ��¼��� ����Ǵ洢�豸�Ľӿڣ�
> > ����libusb�ͷ�һ��usb�豸���Ӷ�ﵽ����usb�Ĺ��ܡ�
>
> Transkation: use netlink to receive usb event, if it is USB Mass
> Storage Interface, use libusb to release the interface, in order
> to disable the USB nass storage device.
>
> --------------
>
> Answer: libusb is not the right tool for access control of USB
> mass storage device. Others may give you some suggestions
> for the right tool to use.
If you want to prevent people from using USB mass-storage devices, the
best approach is to blacklist the usb-storage driver, by adding its
name to a blacklist-*.conf file in /etc/modprobe.d.  The same thing has
to be done with the ub driver, if it is present.

Alan Stern



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel



If you reply to this email, your message will be added to the discussion below:
http://libusb.6.n5.nabble.com/libusb-open-device-with-vid-pid-tp5012586p5014027.html
To unsubscribe from libusb_open_device_with_vid_pid, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: libusb_open_device_with_vid_pid

Peter Stuge
In reply to this post by 1010
1010 wrote:
> if dev is storage, make it disable

1010 wrote:
> Sometimes you can use the /proc and /sys filesystems to disable the
> hardware.
..
> I find a method, but i do not know whether it is useful for usb
> storage is disabled.

This mailing list is about libusb so it is not the best place to ask
for help with what you want to do. I suggest the linux-usb mailing
list, in order to reach all experts on Linux kernel drivers for USB.

There is more than one way to disable a USB device on Linux, and
possibly some more ways to disable storage devices. Which way you
should use is impossible to say without knowing all your
requirements, so please remember to include more information if and
when you post to the linux-usb list.

Note that if you require a race free solution, so that the device is
disabled before the device appears as a storage device in the system,
then there only very few choices remain, possibly only Alan's
suggestion of blacklisting the driver will work reliably.

Linux does not have userspace hooks for filtering USB device attach.
(Neither does any other operating system as far as I know.)

Of course you can send a patch for adding this to Linux. That should
also be sent to the linux-usb mailing list and possibly some others,
depending on which parts of the kernel you have to change.

Linux offers userspace hooks to react to USB device attach, in the
udev package. If disabling the device after it has already been added
to the system is OK, then you can write a udev rule to do it
automatically. Installing such a rule requires root permission at
time of installation only.


//Peter

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: libusb_open_device_with_vid_pid

1010
In reply to this post by Alan Stern
thank Peter's suggestion
I'm not good at English
Maybe what i said is not clear enough

requirement:
the usb storage is allowed to use or not accord to Manufacturer,Model。
if  vendor_id product_id  can be select in Database ,system normal use usb——storage,Otherwise, the disabled。
so if only add driver_name to backlist, it can make all usb_storages disabled.

I had get vendor_id product_id from kernel when usb_storage plugs . what i need to do now is release the dev before
udev load attached driver in user_space code. I don't know libusb can help me or not.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: libusb_open_device_with_vid_pid

1010
In reply to this post by Alan Stern
thank Peter's suggestion
I'm not good at English
Maybe what i said is not clear enough

requirement:
the usb storage is allowed to use or not accord to Manufacturer,Model。
if  vendor_id product_id  can be select in Database ,system normal use usb——storage,Otherwise, the disabled。
so if only add driver_name to backlist, it can make all usb_storages disabled.

I had get vendor_id product_id from kernel when usb_storage plugs . what i need to do now is release the dev before
udev load attached driver in user_space code. I don't know libusb can help me or not.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: libusb_open_device_with_vid_pid

Peter Stuge
In reply to this post by 1010
1010 wrote:
> requirement:
> the usb storage is allowed to use or not accord to Manufacturer,Model。
> if  vendor_id product_id  can be select in Database ,system normal use
> usb——storage,Otherwise, the disabled。
> so if only add driver_name to backlist, it can make all usb_storages
> disabled.

Yes, I understand that you need to filter based on some criteria.
(E.g. a particular vendor ID.)


> I had get vendor_id product_id from kernel when usb_storage plugs .
> what i need to do now is release the dev before udev load attached
> driver in user_space code.

This is a misunderstanding; udev is purely reactive, meaning that
once udev rules are evaluated and executed, the driver has already
been loaded and attached to the device. A udev rule can not block a
driver for a device. The best udev can do is to detach the driver
or disable the device after the driver has already been attached.
If this is done, the storage device will exist in the system for a
short amount of time, and your requirements do not mention if this
is a critical problem.


> I don't know libusb can help me or not.

It can not help. libusb is useful for data transfer to and from USB
devices in user space programs. libusb is not useful for kernel
driver management.

As far as I know you must implement your filter in the kernel. It is
possible that there already exists a mechanism for filtering vendor
IDs in the USB storage driver, so that you only have to add your
vendor ID into a list, in order to block the driver on those devices.
Then the storage device will never appear in the system.

Doing this of course means that only systems with very new kernels
will work as you like. A workaround may be to distribute your own
kernels until your fix has reached all distributions you care about.


//Peter

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: 回复: Re: libusb_open_device_with_vid_pid

Alan Stern
In reply to this post by 1010
On Tue, 22 Nov 2011, 1010 wrote:

> At first thank Alan Stern
> for your answer,
>
> but "Once you add an entry to the blacklist.conf file, you must reboot your system for the changes to take effect".
> how should ido without depend on reboot?

After adding the blacklist entry, rmmod usb-storage.  Then you don't
have to reboot.

Alan Stern


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: 回复: Re: 回复: Re: libusb_open_device_with_vid_pid

Tim Roberts
In reply to this post by 1010
1010 wrote:
> At first thank Alan Stern for your answer,
>  
> but "Once you add an entry to the blacklist.conf file, you must reboot
> your system for the changes to take effect".
> how should ido without depend on reboot?

Why would that be an issue?  You are not thinking  about how this kind
of thing is really used.  This is a computer policy setting.  Those
kinds of things are configured once when the machine is set up.  You
wouldn't be modifying this blacklist on the fly, except as part of an
upgrade, at which point a reboot is not that painful.

--
Tim Roberts, [hidden email]
Providenza & Boekelheide, Inc.


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: libusb_open_device_with_vid_pid

1010
In reply to this post by 1010
I decide to remove the original  usb_storage and Force  customers to use libusb driver which can control storage  by vendor_id product_id. but I don't know the Skeleton of libusb driver, Some example code only exec once {
printf();
printf();
open();
read();
write();
close();
return;
},
is it need "whie" to become a deamon ??  
how the file system call driver's read/write?
who can give me a libusb storage driver project code??
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: libusb_open_device_with_vid_pid

Xiaofan Chen
On Thu, Nov 24, 2011 at 1:36 PM, 1010 <[hidden email]> wrote:

> I decide to remove the original  usb_storage and Force  customers to use
> libusb driver which can control storage  by vendor_id product_id. but I
> don't know the Skeleton of libusb driver, Some example code only exec once {
> printf();
> printf();
> open();
> read();
> write();
> close();
> return;
> },
> is it need "whie" to become a deamon ??
> how the file system call driver's read/write?
> who can give me a libusb storage driver project code??

You will not get the code since libusb is not the right tool
to be used for USB Mass Storage Device.
Ref: http://www.libusb.org/wiki/FAQ#CanIuselibusbtoopenafileonaUSBstoragedevice

What is your real goal here? If you want to enable customers to
use the USB mass storage device, then you have to enable the
usb_storage driver.


--
Xiaofan

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Libusb-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/libusb-devel
Loading...