From: Johan Hovold <johan@kernel.org>
To: "Michael G. Katzmann" <michaelk@IEEE.org>
Cc: charles-yeh@prolific.com.tw, linux-serial@vger.kernel.org,
linux-usb@vger.kernel.org, Charles Yeh <charlesyeh522@gmail.com>,
Joe Abbott <jabbott@rollanet.org>
Subject: Re: non-standard baud rates with Prolific 2303 USB-serial
Date: Mon, 22 Feb 2021 16:50:52 +0100 [thread overview]
Message-ID: <YDPS3AP63/PwmwJU@hovoldconsulting.com> (raw)
In-Reply-To: <0f9caf26-af58-13a9-9947-47bb646f505e@IEEE.org>
[ Please try to avoid top posting to the lists. ]
On Mon, Feb 22, 2021 at 10:42:25AM -0500, Michael G. Katzmann wrote:
> Sorry, my mistake .. when I put it in the right order it does indeed
> also give 110Bd !
Heh, thanks for verifying that. So two ways of encoding the divisors
then. :)
> On 2/22/21 10:34 AM, Johan Hovold wrote:
> > On Mon, Feb 22, 2021 at 09:53:39AM -0500, Michael G. Katzmann wrote:
> >> On 2/22/21 8:18 AM, Johan Hovold wrote:
> >>
> >> I tried hardcoding buf[6-0] in pl2303_set_termios as
> >>
> >> a8 a6 01 80 00 02 07 and got a bitrate of ~200kb
> >>
> >> so, no these settings do not work in my case (or I missunderstood your
> >> instructions 8-))
> > Thanks for testing (and that was with 0xa8 in byte 0, right?)
> >
> > So it seems we have three devices with bcdDevice 0x0300 encoding the
> > divisors in slightly different ways and that are all still supported by
> > the vendor's Windows driver.
> >
> > Unless Prolific are willing to shed some light on this, I guess someone
> > needs to try to figure out how the Windows driver determines which
> > encoding to use.
> >
> > Is your device supposedly also a PL2303 TA? Could you post the output of
> > lsusb -v for completeness?
Was your device also a TA?
Johan
next prev parent reply other threads:[~2021-02-22 15:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3aee5708-7961-f464-8c5f-6685d96920d6@IEEE.org>
[not found] ` <dc3458f1-830b-284b-3464-20124dc3900a@IEEE.org>
2021-02-22 8:52 ` non-standard baud rates with Prolific 2303 USB-serial Johan Hovold
2021-02-22 12:39 ` Michael G. Katzmann
2021-02-22 13:18 ` Johan Hovold
[not found] ` <fb1489c2-b972-619b-b7ce-4ae8e1d2cc0f@IEEE.org>
2021-02-22 15:34 ` Johan Hovold
2021-02-22 15:42 ` Michael G. Katzmann
2021-02-22 15:50 ` Johan Hovold [this message]
2021-02-22 16:37 ` Michael G. Katzmann
2021-02-22 16:48 ` Johan Hovold
2021-02-24 23:08 ` Joe Abbott
2021-02-25 8:44 ` Johan Hovold
[not found] ` <43da22ced8e14442bbc8babea77e4ed7@MailHC2.prolific.com.tw>
2021-02-23 10:18 ` Johan Hovold
2021-02-23 13:25 ` Michael G. Katzmann
2021-02-23 14:58 ` Michael G. Katzmann
2021-02-23 15:43 ` Johan Hovold
2021-02-23 15:57 ` Michael G. Katzmann
2021-02-23 16:14 ` Johan Hovold
2021-02-23 16:30 ` Michael G. Katzmann
2021-02-23 16:52 ` Johan Hovold
2021-02-23 19:15 ` Michael G. Katzmann
2021-02-24 17:04 ` Johan Hovold
2021-02-24 18:13 ` Michael G. Katzmann
2021-02-25 8:42 ` Johan Hovold
2021-04-08 15:35 ` Johan Hovold
2021-02-24 7:34 ` Charles Yeh
2021-02-24 17:00 ` Johan Hovold
2021-02-24 17:12 ` Michael G. Katzmann
2021-03-05 9:32 ` Charles Yeh
2021-03-05 9:36 ` Johan Hovold
2021-03-06 20:18 ` Michael G. Katzmann
2021-03-07 4:15 ` Michael G. Katzmann
2021-03-11 16:08 ` Johan Hovold
2021-03-12 13:17 ` Michael G. Katzmann
2021-03-12 13:44 ` Johan Hovold
2021-03-12 20:29 ` Michael G. Katzmann
2021-03-13 1:28 ` Michael G. Katzmann
2021-03-15 9:07 ` Johan Hovold
2021-03-15 10:07 ` Charles Yeh
2021-03-15 10:24 ` Johan Hovold
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=YDPS3AP63/PwmwJU@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=charles-yeh@prolific.com.tw \
--cc=charlesyeh522@gmail.com \
--cc=jabbott@rollanet.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michaelk@IEEE.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).