From: Johan Hovold <johan@kernel.org>
To: Joe Abbott <jabbott@rollanet.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: pl2303.c 110 baud not working
Date: Mon, 1 Feb 2021 09:43:17 +0100 [thread overview]
Message-ID: <YBe/Ja7ZFZ5JTbi7@hovoldconsulting.com> (raw)
In-Reply-To: <CADuz4OOVmpZtzjYFK7S=s+csAYnegjGpWE9KMh8enzmzEwn6Nw@mail.gmail.com>
On Sat, Jan 30, 2021 at 05:30:15AM -0600, Joe Abbott wrote:
> Sorry it's been so long. Busy.
No worries.
> > So in any case, we'd need to key this off of the device type.
> >
> Yes, key off type as I can't find the relationship. Windows
> uses a8 a6 01 80 02 07 for any request near 110 and switches
> to direct encode for anything near 75 or 150.
Ok, thanks for checking.
> > I noticed that
> >
> > 12000000 / 0x1a6a8 ~= 110.9
> >
> > Possibly just a coincidence, especially as 0x1aa22 would be closer
> > match. But perhaps you can try a few more rates not in baud_sup and see
> > if you can figure it out.
>
> Coincidence. 0x01aa22 doesn't work. Not even close.
>
> I had to give up. Too many other things to do and hard coding
> is working for me.
I fully understand. Let me check with Prolific and see if they are
willing to shed some light on this.
Johan
prev parent reply other threads:[~2021-02-01 8:44 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
[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 [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=YBe/Ja7ZFZ5JTbi7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox