All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael G. Katzmann" <michaelk@IEEE.org>
To: linux-serial@vger.kernel.org
Subject: non-standard baud rates with Prolific 2303 USB-serial
Date: Sun, 21 Feb 2021 10:37:20 -0500	[thread overview]
Message-ID: <3aee5708-7961-f464-8c5f-6685d96920d6@IEEE.org> (raw)

I am trying to use a USB serial interface with a Prolific chip to connect to an old ASR 33 Teletype at 110 Bd.

The USB device will work at 110 Bd in Windows 10 but not under the Linux driver. The USB PID/VID is 0673 / 2303 which corresponds to

static const struct usb_device_id id_table[] = {
    { USB_DEVICE(PL2303_VENDOR_ID, PL2303_PRODUCT_ID),
        .driver_info = PL2303_QUIRK_ENDPOINT_HACK },

in the pl2303 driver. The Manufacturer of this device is 'Sabrabt' (CB-DB9P) and I believe it's a genuine chip device (and not a clone).

The Linux driver does not seem to produce sensible baud rated for other than the 'supported' rates.

stty to 110 bd results in ~95,000 bd (that's not a typo but 95 thousand). Other rates like 200 also produce odd speeds although not in a logical manner.

The data sheets don't describe the formula used for deriving the four bytes used to set the speed.

I tried adding 110 to the supported rates but this did not produce the correct baud rate so I presume the Windows driver is using a formula different than the one in the Linux driver for 'non standard' baud rates.

Does anyone have any suggestions to get this working at 110bd or what other experiments to try?

- Michael



             reply	other threads:[~2021-02-21 15:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 15:37 Michael G. Katzmann [this message]
2021-02-22  2:15 ` non-standard baud rates with Prolific 2303 USB-serial Michael G. Katzmann
2021-02-22  8:52   ` 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
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
2021-02-22  3:57 ` Grant Edwards

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=3aee5708-7961-f464-8c5f-6685d96920d6@IEEE.org \
    --to=michaelk@ieee.org \
    --cc=linux-serial@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 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.