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 22:53:31 -0600	[thread overview]
Message-ID: <20040215045330.GA20725@dbz.icequake.net> (raw)
In-Reply-To: <loom.20040214T195807-602@post.gmane.org>

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


On Sat, Feb 14, 2004 at 07:00:04PM +0000, EL Henry wrote:
> Ryan Underwood <nemesis-lists <at> icequake.net> writes:
> 
> > That said, what type of device are you programming?  
> 
>  I'm not yet, that's why I want to read the book. I want to know if there's any
> chance of the standard DOS C code in it running in DOSEMU.

Yes, there is a chance, but it depends highly on the semantics and will
probably require $_ports and $_irqpassing to be configured as well as
dosemu running as root.

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

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

  reply	other threads:[~2004-02-15  4:53 UTC|newest]

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

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=20040215045330.GA20725@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