From: Lauren Weinstein <lauren4321@gmail.com>
To: cygwin@cygwin.com
Subject: cygwin libusb missing one device
Date: Fri, 04 Mar 2016 05:01:00 -0000 [thread overview]
Message-ID: <loom.20160304T055120-618@post.gmane.org> (raw)
Greetings. I installed the current cygwin on a Win32 system specifically to
use libusb functions. This mostly works, except it appears that the library
doesn't see one particular USB device, even though its driver loads and the
associated Windows app works OK. Unfortunately, I need to use libusb to load
in new firmware, and while the same hardware works fine with libusb when set
to use different drivers (via different VID/PIDs), in this one important case
the libusb functions simply don't seem to see the device at all (e.g., lsusb
doesn't list it, the library open/read/write functions fail, etc.) Any ideas?
Thanks very much.
--Lauren--
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2016-03-04 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160304T055120-618@post.gmane.org \
--to=lauren4321@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).