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: Sat, 22 Oct 2016 09:34:58 -0400 (EDT)	[thread overview]
Message-ID: <201610221334.JAA26901@Stone.Rodents-Montreal.ORG> (raw)
In-Reply-To: <a3b8a5cc-9bef-25e8-6d26-91baf6cbb59f@list.ru>

> Its just that usually when you have some expensive HW, emulating it
> in software is not enough because the HW is usually doing something
> useful, not just makes some program to work. :)  If you don't need
> any functionality of that HW other than to make some DOS prog happy,

Sort of.  It's a (relatively-)high-speed input device, and we plan to
replace it with either a pre-canned data file or a network connection
as a data source.  But, even once the host machine has the data, we
have to get it into the program somehow.  I could replace all the
relevant hardware accesses with traps to the emulator, but I could also
simulate the hardware it's expecting.  I thought the latter was at
least worth looking at; it would have the benefit that it would be
running an identical software image to a real machine with real
hardware, making some kinds of debugging and verification easier.

> then I am afraid dosemu is not prepared for that, and you'll need to
> implement the PCI emulator (in which case you can try qemu).

OK, I'll talk with the other people invovled and we'll decide what tack
to take: hack on the program, add PCI emulation to dosemu, switch
emulators, whatever.

Many thanks for all your help.  Even if we end up switching away from
it, dosemu has been extremely helpful in this endeavour!

/~\ 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-22 13:34 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
2016-10-20 22:36         ` Stas Sergeev
2016-10-22 13:34           ` Mouse [this message]
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=201610221334.JAA26901@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