On Sun, Aug 4, 2013 at 9:08 AM, Pete Batard wrote:
> On 2013.08.04 00:51, Alan Stern wrote:
>> Out of curiosity, what data do you need to request from the parent hub?
>
> Now that I've looked a bit through old e-mails, it seems that these are
> config descriptors, coming from a Windows
> IOCTL_USB
On Mon, Aug 5, 2013 at 7:39 AM, Pete Batard wrote:
> On 2013.08.04 07:46, Hans de Goede wrote:
>>> So I may be misremembering things, as the data we seem to derive from
>>> the first IOCTL isn't used for the topology, but to cache the actual
>>> config descriptor (which libusb mandates us to cache
On Mon, 5 Aug 2013, Pete Batard wrote:
> > True. But do you look forward to telling users: "Libusb doesn't work
> > with your device because it crashes when we send it this request for
> > information which we don't really need"?
>
> Well, considering that we're not applying any quirks when a us
I
would like to have a private contact with someone who could give me
some pointers about BASIC libusb build and usage in Windows MFC.
I
do not need help in style -"read the manual".
I
have been told by "expert" to use libusb0.1 but the
software I am using clearly loads libusb0.dll
Basically
w
On 2013.08.05 15:53, Alan Stern wrote:
> The line is clear as can be. Problematic requests created by the
> user's program are the user's fault and can be fixed by the user (or
> the program author -- at any rate, they aren't libusb's fault).
> Problematic requests created autonomously by libusb _
