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