| 
      
      
      From: trobinson <tr...@pi...> - 2007-09-27 19:22:23
      
     | 
| First, a thanks to Stephen Myers and the rest of the LibUsb-Win32 crew for an excellent universal USB driver. My next (All CSharp) version of LibUsbDotNet uses 3 (three) new IOCTL codes I'm hoping to get included in the LibUsb-Win32 project. LIBUSB_IOCTL_GET_REG_PROPERTY requests a device property by index using IoGetDeviceProperty. LIBUSB_IOCTL_GET_CUSTOM_REG_PROPERTY LIBUSB_IOCTL_SET_CUSTOM_REG_PROPERTY Get/Sets a custom property in the device objects registry key. I have allready modifed the libusb-win32 kernel driver source code to include these IOCTL codes. Attached is an HTML diff report. http://www.nabble.com/file/p12927507/LibUsbWin32Diff.html LibUsbWin32Diff.html I made no changes to the dll because LibUsbDotNet talks directly to the kernel driver. Why I Need this: 1) These IOCTL codes allow me to query basic device information of the attached USB devices without actually requesting descriptors. Some cheap USB devices don't deal well with control request if they are busy on other endpoints. 2) GET_CUSTOM_REG_PROPERTY gets the custom registry properties by name, mainly the "SymbolicName" of the device. The SymbolicName matches the name returned by WM_DEVICECHANGE notifications. This makes it easy to associate a LibUsb device with the WM_DEVICECHANGE notifications. 3) SET_CUSTOM_REG_PROPERTY is obviously a bit dangerous, LibUsbDotNet does not make any "Set" request to the device registry key. However, used with caution this could be very useful. It would enable someone to associate custom information with a USB device that is persistent acrossed boots. Regards, Travis Robinson tr...@pi... -- View this message in context: http://www.nabble.com/LibUsb-Win32-source-changes--tf4530174.html#a12927507 Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |