From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 77A35C433DB for ; Mon, 22 Feb 2021 15:51:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2E34A64EC3 for ; Mon, 22 Feb 2021 15:51:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230202AbhBVPvU (ORCPT ); Mon, 22 Feb 2021 10:51:20 -0500 Received: from mail.kernel.org ([198.145.29.99]:32876 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230425AbhBVPvT (ORCPT ); Mon, 22 Feb 2021 10:51:19 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0545464DAF; Mon, 22 Feb 2021 15:50:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1614009036; bh=V6jqKt0LOcFxkEOD3N1TIJAk0oUlGSIXrXDWTYmEP58=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mCx4nFWy5l+mBS6PsXfKNqvYMppOZbZJaN/Dh8Ngu6daajHG1BPD/KTjoDMK76Wv9 NVYJN8b0aojELAptxfYB8357V3piaz1EQHnBlEYjpJv3yTS7DYoO6Q6JXiQx13on7/ g7N+CxD2vok2V83qqUS+n3mfWCbRKsMmbVKt3MKC6PS7hzCb1AGsPkEEf+j0OH3Rbx TOFDpo6XyT92AqoR3Hv6ZqRCAfyZPDGNw6LDUwjipqpey5KH+StapOgHynKA5mejq0 5cevxIgos0rAyhU71tUanSPhGyT2fgyzoGtn7d0cv5rOx5L2DEmbK9jLYav1wYuQcB k14GZiKtx28Ug== Received: from johan by xi.lan with local (Exim 4.93.0.4) (envelope-from ) id 1lEDU4-00064X-QC; Mon, 22 Feb 2021 16:50:52 +0100 Date: Mon, 22 Feb 2021 16:50:52 +0100 From: Johan Hovold To: "Michael G. Katzmann" Cc: charles-yeh@prolific.com.tw, linux-serial@vger.kernel.org, linux-usb@vger.kernel.org, Charles Yeh , Joe Abbott Subject: Re: non-standard baud rates with Prolific 2303 USB-serial Message-ID: References: <3aee5708-7961-f464-8c5f-6685d96920d6@IEEE.org> <0f9caf26-af58-13a9-9947-47bb646f505e@IEEE.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0f9caf26-af58-13a9-9947-47bb646f505e@IEEE.org> Precedence: bulk List-ID: X-Mailing-List: linux-serial@vger.kernel.org [ Please try to avoid top posting to the lists. ] On Mon, Feb 22, 2021 at 10:42:25AM -0500, Michael G. Katzmann wrote: > Sorry, my mistake .. when I put it in the right order it does indeed > also give 110Bd ! Heh, thanks for verifying that. So two ways of encoding the divisors then. :) > On 2/22/21 10:34 AM, Johan Hovold wrote: > > On Mon, Feb 22, 2021 at 09:53:39AM -0500, Michael G. Katzmann wrote: > >> On 2/22/21 8:18 AM, Johan Hovold wrote: > >> > >> I tried hardcoding buf[6-0] in pl2303_set_termios as > >> > >> a8 a6 01 80 00 02 07 and got a bitrate of ~200kb > >> > >> so, no these settings do not work in my case (or I missunderstood your > >> instructions 8-)) > > Thanks for testing (and that was with 0xa8 in byte 0, right?) > > > > So it seems we have three devices with bcdDevice 0x0300 encoding the > > divisors in slightly different ways and that are all still supported by > > the vendor's Windows driver. > > > > Unless Prolific are willing to shed some light on this, I guess someone > > needs to try to figure out how the Windows driver determines which > > encoding to use. > > > > Is your device supposedly also a PL2303 TA? Could you post the output of > > lsusb -v for completeness? Was your device also a TA? Johan