From mboxrd@z Thu Jan  1 00:00:00 1970
From: Edenyard <mail@edenyard.co.uk>
Subject: Re: Can I use DOSEMU for testing device driver code?
Date: Mon, 16 Feb 2004 11:27:30 +0000
Sender: linux-msdos-owner@vger.kernel.org
Message-ID: <4030A922.5040306@edenyard.co.uk>
References: <Pine.LNX.4.44.0402131157050.16608-100000@pg5.enm.bris.ac.uk> <402E19FA.1050704@edenyard.co.uk> <20040215045827.GB20725@dbz.icequake.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-msdos-owner@vger.kernel.org>
In-Reply-To: <20040215045827.GB20725@dbz.icequake.net>
List-Id: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Ryan Underwood <nemesis-lists@icequake.net>
Cc: linux-msdos@vger.kernel.org

Ryan Underwood wrote:

> First use setserial to disable Linux's
> use of the port though.

	Reading the man page for setserial, it seems that the way to disable
the port (/dev/ttyS0) is: 'setserial /dev/ttyS0 uart none'. Is that 
correct?  When I try that (as root), although it doesn't issue any error
message, it doesn't disable /dev/ttyS0 either. When I subsequently do
'setserial /dev/ttyS0' to check, it merely says that the UART is
unknown, but that ttyS0 is STILL using IRQ4 and port address 0x3f8.

	How do I get to disable ttyS0 completely so that DOSEMU can have
direct access to it?

	TIA,

		Gerald.