Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209411] When retrieving string descriptor from mobile device returns eproto error
Date: Mon, 12 Oct 2020 18:30:25 +0000
Message-ID: <bug-209411-208809-9r9AlHMi3b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209411-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209411

--- Comment #38 from Alan Stern (stern@rowland.harvard.edu) ---
\Is there any way to find out exactly what Windows sends to the device?  Maybe
it's different from what your program sends.

Keep in mind also that the kernel sends a Set-Config request to the device when
you plug it into the computer.  That request doesn't appear to cause problems
either.

The only logs which might give you more information about what's happening on
the device are the device's own logs.  Maybe you can learn something, for
example, by running dmesg in a terminal app on the device.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply index

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 17:51 [Bug 209411] New: " bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] " bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] New: " Greg KH
2020-09-29 14:35 ` [Bug 209411] " bugzilla-daemon
2020-09-29 14:38 ` bugzilla-daemon
2020-09-29 16:04 ` bugzilla-daemon
2020-09-29 16:23 ` bugzilla-daemon
2020-09-29 16:24 ` bugzilla-daemon
2020-09-29 16:40 ` bugzilla-daemon
2020-09-30 11:05 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 14:47 ` bugzilla-daemon
2020-09-30 14:52 ` bugzilla-daemon
2020-09-30 14:53 ` bugzilla-daemon
2020-09-30 15:04 ` bugzilla-daemon
2020-09-30 15:15 ` bugzilla-daemon
2020-09-30 15:37 ` bugzilla-daemon
2020-09-30 15:41 ` bugzilla-daemon
2020-09-30 15:43 ` bugzilla-daemon
2020-09-30 15:44 ` bugzilla-daemon
2020-09-30 19:25 ` bugzilla-daemon
2020-10-02 16:02 ` bugzilla-daemon
2020-10-02 16:04 ` bugzilla-daemon
2020-10-02 16:46 ` bugzilla-daemon
2020-10-05 13:53 ` bugzilla-daemon
2020-10-05 14:38 ` bugzilla-daemon
2020-10-05 14:48 ` bugzilla-daemon
2020-10-07  4:54 ` bugzilla-daemon
2020-10-10 18:02 ` bugzilla-daemon
2020-10-11  1:15 ` bugzilla-daemon
2020-10-11  4:27 ` bugzilla-daemon
2020-10-11  8:13 ` bugzilla-daemon
2020-10-11 14:13 ` bugzilla-daemon
2020-10-12 12:49 ` bugzilla-daemon
2020-10-12 12:50 ` bugzilla-daemon
2020-10-12 14:47 ` bugzilla-daemon
2020-10-12 16:25 ` bugzilla-daemon
2020-10-12 16:49 ` bugzilla-daemon
2020-10-12 18:30 ` bugzilla-daemon [this message]
2020-10-12 18:50 ` bugzilla-daemon
2020-10-13  0:24 ` bugzilla-daemon
2020-10-13  4:09 ` bugzilla-daemon
2020-10-13  5:10 ` bugzilla-daemon
2020-10-13  6:02 ` bugzilla-daemon
2020-10-13  6:21 ` bugzilla-daemon
2020-10-13  6:25 ` bugzilla-daemon
2020-10-13  6:37 ` bugzilla-daemon
2020-10-13 17:51 ` bugzilla-daemon
2020-10-13 17:55 ` bugzilla-daemon
2020-10-13 17:56 ` bugzilla-daemon
2020-10-13 17:58 ` bugzilla-daemon
2020-10-14  3:56 ` bugzilla-daemon
2020-10-14 13:24 ` bugzilla-daemon
2020-10-14 18:43 ` bugzilla-daemon
2020-10-14 18:49 ` bugzilla-daemon
2020-10-14 18:56 ` bugzilla-daemon

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=bug-209411-208809-9r9AlHMi3b@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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

Linux-USB Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-usb/0 linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ https://lore.kernel.org/linux-usb \
		linux-usb@vger.kernel.org
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-usb


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git