public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: Can I use DOSEMU for testing device driver code?
Date: Sat, 14 Feb 2004 23:04:34 -0600	[thread overview]
Message-ID: <20040215050434.GC20725@dbz.icequake.net> (raw)
In-Reply-To: <S266614AbUBLVxi/20040212215338Z+303@vger.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]


On Thu, Feb 12, 2004 at 04:53:38PM -0500, easlab@absamail.co.za wrote:
> 
> All my DOS application can't do is toggle 2 pins of the par-port.
> No interupts.      dosemu-1.1.99 as root, won't do it, even with
> editing dosemu.conf to:
>      $_ports { device /dev/lp1 fast range 0x378 0x37f } # lpt1
> and other combinations

You don't want to use the lp device.  In fact, it will work better if
you remove the lp and all parport drivers before using dosemu.  I can
use the parallel port with:

1) removed all linux parallel port support (lp,ppdev,parport_pc,parport)
2) $_ports = "range 0x3bc,0x3be range 0x7bc,0x7be" and $_irqpassing = "7"
3) sudo dosemu

This is for a port at 0x3bc.  The 0x7bc range is the ECP registers,
which are usually unnecessary but in my case they were (even though ECP
DMA mode cannot be used under dosemu).  ECP control register is used to
set the parallel port's mode from spp to tristate on some chips that
boot up in spp mode.

If you are not using the interrupt, then you do not need irqpassing.
I was unable to get anything to work until removing the linux pp
drivers, probably because (Stas said) dosemu checks /proc/ioports for
already used port ranges by linux drivers and refuses to use them again.

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-02-15  5:04 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
2004-02-17  7:52           ` Ryan Underwood
2004-02-17  9:36           ` Ged Haywood
2004-02-15  5:04 ` Ryan Underwood [this message]
     [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=20040215050434.GC20725@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-msdos@vger.kernel.org \
    /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