From owner-freebsd-current Sun Jan 2 14:43:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id DE39614DE6 for ; Sun, 2 Jan 2000 14:43:51 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-2ivf7bt.dialup.mindspring.com [165.247.157.125]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA02762 for ; Sun, 2 Jan 2000 17:43:47 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.3/8.9.3) id RAA01469; Sun, 2 Jan 2000 17:40:36 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <200001022240.RAA01469@vger.foo.com> Subject: tip features (cdelay and ldelay)? To: freebsd-current@freebsd.org Date: Sun, 2 Jan 2000 17:40:36 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a couple of really dumb devices that I use 'tip' to talk to. One is a Motorola 6811 microcontroller and the other is an old EEPROM burner. I find that 'tip' overflows these devices when I'm sending Motorola s-record and Intel Hex formatted files. It looks like tip's 'cdelay' and 'ldelay' features do just the trick. However, they are disabled, surrounded by '#ifdef notdef' sequences. Just to make sure, I re-enabled them locally, and re-implemented the apparently lost 'nap()' function to make sure that these features work for my application, and they do. My question is: does anyone remember why these were disabled in the first place? Is there an equivalent replacement feature that I can use instead to pace the outgoing characters so that I don't overrun dumb devices with no flow control? Thanks, -Brian -- Brian Dean brdean@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message