On 2019-10-02 14:58, Kyle Evans wrote:
Sorry, I missed that the (ctx)->debug checks just moved a little
further in... debugging a little better, because LIBUSB_DEBUG=0
doesn't seem to do the trick for this person.
I believe the prints are off by default, unless you call
libusb_set_debug() in
On 2019-10-02 14:55, Kyle Evans wrote:
On Fri, Sep 14, 2018 at 8:41 AM Hans Petter Selasky
wrote:
Author: hselasky
Date: Fri Sep 14 13:41:37 2018
New Revision: 338679
URL: https://svnweb.freebsd.org/changeset/base/338679
Log:
Improve LibUSB debugging by simultaneously allowing both
On Wed, Oct 2, 2019 at 7:55 AM Kyle Evans wrote:
>
> On Fri, Sep 14, 2018 at 8:41 AM Hans Petter Selasky
> wrote:
> >
> > Author: hselasky
> > Date: Fri Sep 14 13:41:37 2018
> > New Revision: 338679
> > URL: https://svnweb.freebsd.org/changeset/base/338679
> >
> > Log:
> > Improve LibUSB
On Fri, Sep 14, 2018 at 8:41 AM Hans Petter Selasky
wrote:
>
> Author: hselasky
> Date: Fri Sep 14 13:41:37 2018
> New Revision: 338679
> URL: https://svnweb.freebsd.org/changeset/base/338679
>
> Log:
> Improve LibUSB debugging by simultaneously allowing both function
> and transfer prints.
Author: hselasky
Date: Fri Sep 14 13:41:37 2018
New Revision: 338679
URL: https://svnweb.freebsd.org/changeset/base/338679
Log:
Improve LibUSB debugging by simultaneously allowing both function
and transfer prints. Make sure the debug level comes from the
correct USB context.
Found by: