public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mouse <mouse@Rodents-Montreal.ORG>
To: linux-msdos@vger.kernel.org
Subject: Re: Emulated PCI devices?
Date: Wed, 19 Oct 2016 22:36:47 -0400 (EDT)	[thread overview]
Message-ID: <201610200236.WAA24661@Stone.Rodents-Montreal.ORG> (raw)
In-Reply-To: <d58feaad-c305-f3b8-a555-51b4a8cb0257@list.ru>

>> [...] the way dosemu emulates DOS in much the same sense that wine
>> emulates Windows, instead of emulating hardware proper [...]
> dosemu does emulate the HW and uses freedos (or any other dos you ask
> it to boot).

To a point, sure.  But, for example, it takes file I/O traps and
provides its own implementation, backed by the host filesystem, rather
than letting the FreeDOS implementation talk to (presumably emulated)
disk hardware.

>> [...] it involves a legacy application, running under DOS, which
>> depends on a particular (relatively rare and expensive) piece of
>> hardware.
> If you want the DOS driver to communicate to that hardware, [...].
> If you want to emulate the "very expensive hw" without actually using
> the real hw, then I wonder what's the point.

The point is to get the application running without the fancy hardware
(which is now EOLed) without having to rewrite the portions of the
application that talk to it.  The company has done an EOL buy of that
hardware, but that gives them only enough to last about half the time
we expect it to take to do the complete port/rewrite.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

  reply	other threads:[~2016-10-20  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 21:45 Emulated PCI devices? Mouse
2016-10-18 22:50 ` Stas Sergeev
2016-10-19  0:03   ` Mouse
2016-10-19 22:45     ` Stas Sergeev
2016-10-20  2:36       ` Mouse [this message]
2016-10-20 22:36         ` Stas Sergeev
2016-10-22 13:34           ` Mouse
2016-10-22 20:23             ` Stas Sergeev

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=201610200236.WAA24661@Stone.Rodents-Montreal.ORG \
    --to=mouse@rodents-montreal.org \
    --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