From: Stas Sergeev <stsp@list.ru>
To: Mouse <mouse@Rodents-Montreal.ORG>, linux-msdos@vger.kernel.org
Subject: Re: Emulated PCI devices?
Date: Wed, 19 Oct 2016 01:50:39 +0300 [thread overview]
Message-ID: <d42dd07d-faeb-26dc-b640-7ad28cdeb351@list.ru> (raw)
In-Reply-To: <201610182145.RAA07490@Stone.Rodents-Montreal.ORG>
19.10.2016 00:45, Mouse пишет:
> 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.)
Good luck.
> 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?
There was never any need to emulate the PCI device
for DOS. There are hardly too many DOS drivers for the
PCI devices. Maybe you can instead emulate the ISA version
of that device, which should be much simpler than adding
the PCI bus emulator. Or maybe you simply want to use qemu
because I can't think of the real use-cases where you want
to emulate some modern device under dosemu or dosbox.
next prev parent reply other threads:[~2016-10-18 22:50 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 [this message]
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=d42dd07d-faeb-26dc-b640-7ad28cdeb351@list.ru \
--to=stsp@list.ru \
--cc=linux-msdos@vger.kernel.org \
--cc=mouse@Rodents-Montreal.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