From owner-freebsd-questions@FreeBSD.ORG Tue Jun 15 02:39:38 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A128616A4CE for ; Tue, 15 Jun 2004 02:39:38 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B8B343D31 for ; Tue, 15 Jun 2004 02:39:38 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i5F2dbDX012676; Mon, 14 Jun 2004 21:39:37 -0500 (CDT) (envelope-from dan) Date: Mon, 14 Jun 2004 21:39:37 -0500 From: Dan Nelson To: Richard Kiss Message-ID: <20040615023937.GK62945@dan.emsphone.com> References: <20040614190735.A30698@kalamalka.gizzywump.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040614190735.A30698@kalamalka.gizzywump.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: ucom* at uftdi? does not work with getty X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 02:39:38 -0000 In the last episode (Jun 14), Richard Kiss said: > We run a dial-up call center and are trying to find a replacement for > our old Cyclades multi-port serial cards which never worked all that > well. We purchased a USB to 8 serial port converter that uses an FTDI > chipset from byterunner.com. The serial ports are hot-pluggable (a > nice plus) and present as ucom0 through ucom7. > > The ports work fine with minicom and modems, but NOT with getty. The > behaviour of ucomX appears to be similar to cuaaX, not ttydX -- > dialing a modem attached to ucomX yields auto-answer and a connect > just fine, but getty does not seem to notice that the line has been > picked up and does not seem to launch the subprocess. Sounds like a bug in ucom. It's also missing the init and lock devices. You might be able to get away with simply removing the UCOM_CALLOUT_MASK from the make_dev() call on line 186 of ucom.c. That looks like it will convert ucomX to a callin device. A correct fix would probably be to copy all the code in dev/sio/sio.c related to the "devs" array to ucom.c, and name the devices "ttyuX" and "cuauX" instead of "ucomX". -- Dan Nelson dnelson@allantgroup.com