From owner-freebsd-hackers  Wed Jun  7 07:42:25 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id HAA21185
          for hackers-outgoing; Wed, 7 Jun 1995 07:42:25 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA21173
          for <freebsd-hackers@FreeBSD.org>; Wed, 7 Jun 1995 07:42:19 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA21380; Thu, 8 Jun 1995 00:35:27 +1000
Date: Thu, 8 Jun 1995 00:35:27 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506071435.AAA21380@godzilla.zeta.org.au>
To: bde@zeta.org.au, imb@scgt.oz.au
Subject: Re: silo overflows
Cc: freebsd-hackers@FreeBSD.org
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>> No, FIFO_TRIGGER_14 is a constant, not an option.  Change the one
>> place in sio.c where it is used to initialize com->ftl_init.  Use
>> FIFO_TRIGGER_8 instead.

>Could this be "externalised", please. I have a mix of machines from 386DX/40

>#ifndef FIFO_TRIGGER
>#define FIFO_TRIGGER FIFO_TRIGGER_14
>#endif

>	:

>com->ftl_init = FIFO_TRIGGER;

> .. is all that's necessary. If at all possible, site-dependent "hacks"
>should be kept out of the kernel sources.

I prefer `comcontrol /dev/ttydX ftl N', but there is no time to implement
this for 2.0.5.

Do you want a barely documented option in 2.0.5 if the option will become
obsolete in 2.0.6?

Bruce