From: Johan Hovold <johan@kernel.org>
To: Joe Abbott <jabbott@rollanet.org>
Cc: Johan Hovold <johan@kernel.org>, linux-usb@vger.kernel.org
Subject: Re: pl2303.c 110 baud not working
Date: Fri, 8 Jan 2021 15:32:48 +0100 [thread overview]
Message-ID: <X/htEGiNbjGb2dy8@hovoldconsulting.com> (raw)
In-Reply-To: <CADuz4ONNPq+mADWYPKp8+M2rZtuoMwjO=+HDXfgrO2dQ0S1vQA@mail.gmail.com>
Please keep the USB list on CC.
On Fri, Jan 08, 2021 at 08:02:36AM -0600, Joe Abbott wrote:
> Thanks for the reply.
>
> kernel version is 5.0.0-32-generic. I've restored pl2303.ko to original.
5.0 should work as well.
> Chip version is PL2303TA.
And I believe that one is supposed to be compatible with HXD.
> When I loopback rs232 to pc at 150 baud it looks normal. After
> setting to 110 baud it returns at a much higher rate and scope trace looks
> the same as when set to 9600 baud.
>
> Setting up debug might be beyond my abilities unless I could find a good
> how-to that I could follow.
You can either use debugfs:
echo module pl2303 +p > /sys/kernel/debug/dynamic_debug/control
or provide an argument to modprobe:
modprobe pl2303 dyndbg==p
Then just check demsg after calling stty (110 evenp).
> I'll look into capturing some windows packets at 110 and 9600.
Sounds good.
Johan
next prev parent reply other threads:[~2021-01-08 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:06 pl2303.c 110 baud not working Joe Abbott
2021-01-08 9:57 ` David Laight
2021-01-08 10:13 ` Johan Hovold
[not found] ` <CADuz4ONNPq+mADWYPKp8+M2rZtuoMwjO=+HDXfgrO2dQ0S1vQA@mail.gmail.com>
2021-01-08 14:32 ` Johan Hovold [this message]
[not found] ` <CADuz4OPCnq_4Xx-sWc-ZijoQRAZR-4+MRvpOx4np2rXifoCL5A@mail.gmail.com>
2021-01-10 12:04 ` Johan Hovold
2021-01-10 22:15 ` Joe Abbott
2021-01-11 9:28 ` Johan Hovold
[not found] ` <CADuz4OO9DnauGr5MwMupuZrKOxU7Jrr54-a2_vGGXRQTCxPc1Q@mail.gmail.com>
2021-01-30 11:30 ` Joe Abbott
2021-02-01 8:43 ` 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=X/htEGiNbjGb2dy8@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=jabbott@rollanet.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 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.