From: Willy Tarreau <email@example.com> To: Johan Hovold <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, "Paul Größel" <email@example.com> Subject: Re: [PATCH] Revert "USB: serial: ch341: fix character loss at high transfer rates" Date: Tue, 24 Aug 2021 17:06:52 +0200 [thread overview] Message-ID: <20210824150652.GA25488@1wt.eu> (raw) In-Reply-To: <YSTzPIkwNDOON5j8@hovoldconsulting.com> [ removed Cc stable for the rest of the discussion ] On Tue, Aug 24, 2021 at 03:25:16PM +0200, Johan Hovold wrote: > Zero-length packets are used to indicate completion of bulk transfers > that are multiples of the endpoint max-packet size (as per the USB > spec). Without those the host controller driver doesn't now that the > transfer is complete and that it should call the driver completion > callback (and instead waits for the other completion conditions). Thanks for the explanation. I guess that in my case, given that the serial port would emit lots of continuous data (e.g. "find /" or "dmesg"), there's always something pending and the risk that it ends exactly on a 64-byte boundary remained low and never happened in practice. > It may be possible to configure the device to send ZLPs somehow but > since there's no public documentation for the protocol that may require > some reverse engineering. I totally understand. I'll drop my CH34x adapters and try to figure more suitable ones (i.e. some which work *by default* under Linux). Their small footprint was nice but without doc they're only usable for low speeds :-/ Thanks! Willy
prev parent reply other threads:[~2021-08-24 15:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-24 12:19 Johan Hovold 2021-08-24 12:32 ` Willy Tarreau 2021-08-24 13:25 ` Johan Hovold 2021-08-24 15:06 ` Willy Tarreau [this message]
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=20210824150652.GA25488@1wt.eu \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] Revert "USB: serial: ch341: fix character loss at high transfer rates"' \ /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
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.