From: "Michael G. Katzmann" <michaelk@IEEE.org>
To: "Yeh.Charles [葉榮鑫]" <charles-yeh@prolific.com.tw>,
"Johan Hovold" <johan@kernel.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-usb@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: Tue, 23 Feb 2021 08:25:23 -0500 [thread overview]
Message-ID: <f91e9f1b-affc-8b13-19eb-a1ab19771032@IEEE.org> (raw)
In-Reply-To: <43da22ced8e14442bbc8babea77e4ed7@MailHC2.prolific.com.tw>
The markings on the device I have are
PL2303TA
G19101E
CDH81920
... and yes I had to destroy it to open it 8-(
Photo here..... https://photos.app.goo.gl/ontHBzGBbaDV6FWu6
Michael.
On 2/23/21 5:14 AM, Yeh.Charles [葉榮鑫] wrote:
> I set 110 bps / 8 data bits/ none parity / 1 stop bit.
> I used PL2303TA , I got the data is d5 0e 00 80 00 00 08 on 5.8.0-41 kernel.
> Please refer to attached file : PL2303TA.png.
>
> The divider algorithm is OK on Linux for my test.
>
> Can you use you PL2303TA board to print log?
> What are the differences between the log you printed and the log printed in the attachment?
next prev parent reply other threads:[~2021-02-23 13:26 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
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 [this message]
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=f91e9f1b-affc-8b13-19eb-a1ab19771032@IEEE.org \
--to=michaelk@ieee.org \
--cc=charles-yeh@prolific.com.tw \
--cc=charlesyeh522@gmail.com \
--cc=jabbott@rollanet.org \
--cc=johan@kernel.org \
--cc=linux-serial@vger.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).