From owner-freebsd-alpha  Sat Jan 20 16:58:55 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9C04637B400
	for <freebsd-alpha@FreeBSD.ORG>; Sat, 20 Jan 2001 16:58:38 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA09956;
	Sat, 20 Jan 2001 19:58:38 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0L0wca08028;
	Sat, 20 Jan 2001 19:58:38 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 20 Jan 2001 19:58:37 -0500 (EST)
To: leclercn@videotron.ca
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: FIFO files: device not configured
In-Reply-To: <3A6A156B.1010809@videotron.ca>
References: <3A6A156B.1010809@videotron.ca>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14954.13113.352982.366550@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


tcn writes:
 >    Are fifo files supported in FreeBSD Axp?

Yes.

The only thing I can think of which makes any sense is that, by
default, sio1 is reserved for the kernel debugger.  (This should
probably be changed!).  Try using cuaa0 or rebuild a kernel without
the 0x40 bit set on the sio1 flags.  Eg:

	device          sio1    at isa? port IO_COM2 irq 3

(note the lack of "flags 0x50")

Drew


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