linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214131] ch341 communication problem
Date: Tue, 24 Aug 2021 11:44:23 +0000	[thread overview]
Message-ID: <bug-214131-208809-JPVCKnWu6G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214131-208809@https.bugzilla.kernel.org/>

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

--- Comment #7 from Johan Hovold (johan@kernel.org) ---
On Mon, Aug 23, 2021 at 09:14:49AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=214131
> 
> --- Comment #5 from Paul Größel (pb.g@gmx.de) ---
> I agree, I couldn't find any enumerate related symptoms here:

I was able to reproduce the problem here. The device doesn't send a
zero-length package in case the received data is a multiple of the
endpoint size so that the bulk transfer doesn't complete (e.g. your
flashing application may not receive replies).

We need to revert the offending commit until we can figure out how to
configure the device to send ZLPs.

Thanks again for reporting this, and sorry about the breakage.

Johan

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2021-08-24 11:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  7:11 [Bug 214131] New: ch341 communication problem bugzilla-daemon
2021-08-22 23:32 ` [Bug 214131] " bugzilla-daemon
2021-08-23  7:09 ` bugzilla-daemon
2021-08-23  9:07 ` bugzilla-daemon
2021-08-23  9:14 ` bugzilla-daemon
2021-08-23  9:14 ` bugzilla-daemon
2021-08-24 11:44   ` Johan Hovold
2021-08-24 11:44 ` bugzilla-daemon [this message]
2021-08-25  7:21 ` bugzilla-daemon
2021-10-04  9:21 ` bugzilla-daemon
2021-10-11  8:55   ` Johan Hovold
2021-10-11  8:55 ` bugzilla-daemon
2021-10-22 13:58 ` 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-214131-208809-JPVCKnWu6G@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
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 NNTP newsgroup(s).