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: Emulated PCI devices?
Date: Tue, 18 Oct 2016 17:45:30 -0400 (EDT)	[thread overview]
Message-ID: <201610182145.RAA07490@Stone.Rodents-Montreal.ORG> (raw)

I'm working with dosemu and would like to add an emulated PCI device to
the emulated DOS machine.  Obviously, I know enough about the hardware
I want to emulate to believe I can write an emulation of it.

But I'm not sure where to hook it in.  (I'm working based on commit
18f6f5cdf1beceae8c7532718bfaf423e4a44f6a.)  I found
src/base/async/pci_bios.c and src/base/dev/misc/pci.c, but they appear
to be all about giving the emulated machine access to real PCI hardware
on the real machine.  That's not what I want; I'm trying to supply the
emulated machine with hardware that is not actually present.

There is src/env/video/matrox.c, which appears to be monkeying with PCI
stuff, but even that checks the real machine's /proc/pci and doesn't
run unless there's real hardware backing it (see matroxProbe(), which
incidentally is incorrectly commented as being MGAProbe).

Is this something that's already got hooks supporting it, or am I
breaking new ground here?

/~\ 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-18 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 21:45 Mouse [this message]
2016-10-18 22:50 ` Emulated PCI devices? 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
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=201610182145.RAA07490@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