public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Edenyard <mail@edenyard.co.uk>
To: Ryan Underwood <nemesis-lists@icequake.net>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Can I use DOSEMU for testing device driver code?
Date: Mon, 16 Feb 2004 11:27:30 +0000	[thread overview]
Message-ID: <4030A922.5040306@edenyard.co.uk> (raw)
In-Reply-To: <20040215045827.GB20725@dbz.icequake.net>

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.




  reply	other threads:[~2004-02-16 11:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 21:53 Can I use DOSEMU for testing device driver code? easlab
2004-02-13  8:17 ` Edenyard
2004-02-13 12:01   ` Bart Oldeman
2004-02-14 12:52     ` Edenyard
2004-02-15  4:58       ` Ryan Underwood
2004-02-16 11:27         ` Edenyard [this message]
2004-02-17  7:52           ` Ryan Underwood
2004-02-17  9:36           ` Ged Haywood
2004-02-15  5:04 ` Ryan Underwood
     [not found] <4034D439.5080308@edenyard.co.uk>
2004-02-19 18:36 ` Ged Haywood
  -- strict thread matches above, loose matches on Subject: below --
2004-02-15 11:15 Stas Sergeev
2004-02-13 20:12 Stas Sergeev
2004-02-12  6:11 synthespian
2004-02-12 10:15 ` Ryan Underwood
2004-02-14 19:00   ` EL Henry
2004-02-15  4:53     ` Ryan Underwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4030A922.5040306@edenyard.co.uk \
    --to=mail@edenyard.co.uk \
    --cc=linux-msdos@vger.kernel.org \
    --cc=nemesis-lists@icequake.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox