From owner-freebsd-current  Thu May 28 16:14:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA20398
          for freebsd-current-outgoing; Thu, 28 May 1998 16:14:17 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20329
          for <freebsd-current@FreeBSD.ORG>; Thu, 28 May 1998 16:13:54 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA10039;
	Fri, 29 May 1998 09:13:37 +1000
Date: Fri, 29 May 1998 09:13:37 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199805282313.JAA10039@godzilla.zeta.org.au>
To: dmaddox@scsn.net, freebsd-current@FreeBSD.ORG, joelh@gnu.org
Subject: Re: sio0 flag 0x20000
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> The probe reports the chip as a 16550A... is that reliable?
>
>The 0x20000 flag is for use with 16>6<50s, not 16550s...
>                                    ^
>During the brief time when it was enabled by default, it caused problems
>with my 16550A-clone serial ports,

Yes, it should completely break 16550s.

>but it works fine for the 16650-based
>LavaPort I have...

On Startech16650s, it should improve CTS flow control and unimprove RTS
flow control (hardware RTS flow control is broken as designed on at
least ST16550s).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message