From owner-freebsd-hackers Sun Jan 11 17:06:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28692 for hackers-outgoing; Sun, 11 Jan 1998 17:06:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA28660 for ; Sun, 11 Jan 1998 17:06:37 -0800 (PST) (envelope-from jak@cetlink.net) Received: from hot1.auctionfever.com (ts1-cltnc-22.cetlink.net [209.54.58.22]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id UAA26856; Sun, 11 Jan 1998 20:06:18 -0500 (EST) From: jak@cetlink.net (John Kelly) To: "John S. Dyson" Cc: hackers@FreeBSD.ORG Subject: Re: 16650 Support(?) Date: Mon, 12 Jan 1998 02:07:04 GMT Message-ID: <34c0795e.7050337@mail.cetlink.net> References: <199801120007.TAA00316@dyson.iquest.net> In-Reply-To: <199801120007.TAA00316@dyson.iquest.net> X-Mailer: Forte Agent 1.01/16.397 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA28666 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Sun, 11 Jan 1998 19:07:35 -0500 (EST), "John S. Dyson" wrote: >> The 650 support seems to be broken, so don't flag it as a 650. Run it >> as a 550 and it should work fine. You still get the benefit of the >> deeper FIFO, even when it's defined as a 550. You don't get the auto >> CTS/RTS flow control, but that has questionable value anyway. >> >I have a 16650 based card, and it appears to work well. It would be interesting >to figure out why mine works, and others don't. > Do you have it flagged as a 650 in your kernel, or as a 550? I emailed you about the SIO 650 support a couple of months ago but I guess you were busy with other stuff. There seem to be some changes in SIO for 650 support, attributed to you. If that is true, can you describe the changes? When I tried to use the 650 support in -current a couple of months ago I would always get interrupt-level buffer overflows. But as long as it was defined as a 550 it worked (and still works) fine. John