Bochs/bochs
Volker Ruppert 55c9bad4ef Some work on the Voodoo Banshee emulation.
- Happy new year!
- Improved pixel format conversion in host-to-screen operations.
- Rewrite of the linear framebuffer read/write code fixes icons in 16 bpp mode.
- Don't flood log file when polling the 2D status register (similar to 3D one).
- FIXME list:
  - Minor issues in all Banshee modes (e.g. forward/back buttons in explorer).
  - Display errors in 16 bpp mode after leaving 3D mode.
  - Display errors in 16 bpp mode in case debug messages are turned on (timing).
  - Voodoo2 3D demo "donut" still fails.
  - Bochs crashes on Windows host (MSVC in some cases, MSYS2 64-bit build also
    reported, but not yet reproduced.
- TODO list:
  - Remaining 2D stuff: polygon fill, stretching functions.
  - Move Banshee stuff to separate files.
  - Add Voodoo3 support (it's an improved Banshee card).
2018-01-01 19:08:16 +00:00
..
bios Regenerated configure script and recompiled BIOS for HPET support. 2017-04-17 07:28:22 +00:00
build Updated default MSVC workspace for current SVN (TODO: plugins workspace). 2017-12-31 09:34:59 +00:00
bx_debug remove include which is not needed 2017-09-03 11:43:30 +00:00
cpu fixed buffer overflow when printing instruction disasm for opcode bytes which cannot be decoded 2017-12-31 21:22:04 +00:00
disasm old legacy disasm: omit printing rep prefix if no repeatable opcode 2017-12-28 20:52:46 +00:00
doc Some work on the Voodoo Banshee emulation. 2017-12-29 11:18:45 +00:00
docs-html
gui Fixed possible compilation error (thanks to Ben Lunt). 2017-12-03 08:09:47 +00:00
host/linux/pcidev
instrument
iodev Some work on the Voodoo Banshee emulation. 2018-01-01 19:08:16 +00:00
memory small change to extract ia_opcodes.h from instr.h to dedicated file. this would remove compilation dep of all files on ia_opcodes.h (now called ia_opcdes.def). regenerating dep ober all files in Makefiles.in 2017-10-19 21:27:25 +00:00
misc Minor fixes and cleanups in the bxhub code. 2017-07-04 18:53:33 +00:00
patches
.bochsrc Some work on the Voodoo Banshee emulation. 2017-12-29 11:18:45 +00:00
.conf.amigaos
.conf.everything
.conf.linux
.conf.macos
.conf.macosx
.conf.nothing
.conf.sparc
.conf.win32-cygwin
.conf.win32-vcpp
aclocal.m4
bochs.h Moved all Bochs multi-threading definitions from bochs.h and osdep.h to a new 2017-09-10 15:55:13 +00:00
bxdisasm_new.cc added compilation instructions for bxdisasm_new.cc 2017-12-13 20:27:02 +00:00
bxdisasm_old.cc distinguish between vzeroupper/vzeroall in old legacy disasm 2017-12-28 20:20:13 +00:00
bxthread.cc Added SDL / SDL2 specific multi-threading support. If one of these guis is 2017-09-16 22:01:49 +00:00
bxthread.h Added SDL / SDL2 specific multi-threading support. If one of these guis is 2017-09-16 22:01:49 +00:00
bxversion.h.in
bxversion.rc.in
CHANGES Some work on the Voodoo Banshee emulation. 2017-12-29 11:18:45 +00:00
config.cc Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +00:00
config.guess
config.h.in Fixes and updates for wxWidgets 3.0 2017-06-04 09:32:58 +00:00
config.sub
configure Fixed bxhub compilation in MSYS2. 2017-12-30 14:56:54 +00:00
configure.in Fixed bxhub compilation in MSYS2. 2017-12-30 14:56:54 +00:00
COPYING
cpudb.h skylake CPUID should compile also with no EVEX 2017-08-09 21:04:15 +00:00
crc.cc
extplugin.h Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +00:00
gdbstub.cc
install-sh
LICENSE
load32bitOShack.cc Added symbol BX_LOAD32BITOSHACK to disable this legacy feature. With the 2017-04-17 13:26:44 +00:00
logio.cc Moved all Bochs multi-threading definitions from bochs.h and osdep.h to a new 2017-09-10 15:55:13 +00:00
ltdl-bochs.h
ltdl.c
ltdlconf.h.in
ltmain.sh
main.cc Rewrite of the USB devices plugin code similar to the network driver code. 2017-05-28 08:13:06 +00:00
Makefile.in small change to extract ia_opcodes.h from instr.h to dedicated file. this would remove compilation dep of all files on ia_opcodes.h (now called ia_opcdes.def). regenerating dep ober all files in Makefiles.in 2017-10-19 21:27:25 +00:00
msrs.def
osdep.cc Moved all Bochs event / wait functions required for multi-threading to a new 2017-09-14 16:18:12 +00:00
osdep.h Moved all Bochs multi-threading definitions from bochs.h and osdep.h to a new 2017-09-10 15:55:13 +00:00
param_names.h Added symbol BX_LOAD32BITOSHACK to disable this legacy feature. With the 2017-04-17 13:26:44 +00:00
PARAM_TREE.txt Removed Voodoo realtime option. Since the gui screen update timing is now 2017-08-18 15:19:30 +00:00
pc_system.cc Prepared devices and timer code for HPET support 2017-04-15 20:31:07 +00:00
pc_system.h Prepared devices and timer code for HPET support 2017-04-15 20:31:07 +00:00
plugin.cc Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +00:00
plugin.h Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +00:00
qemu-queue.h
README Preparing release 2.6.9 2017-04-09 06:45:39 +00:00
README-plugins
README-wxWidgets
README.rfb
TESTFORM.txt
TODO
win32_enh_dbg.rc
win32res.rc
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Sun Apr  9 08:45:00 CEST 2017
Version: 2.6.9

WHAT IS BOCHS?

Bochs is a highly portable open source IA-32 (x86) PC emulator
written in C++, that runs on most popular platforms.  It includes
emulation of the Intel x86 CPU, common I/O devices, and a custom
BIOS. Bochs can be compiled to emulate many different x86 CPUs,
from early 386 to the most recent x86-64 Intel and AMD processors
which may even not reached the market yet. Bochs is capable of running
most Operating Systems inside the emulation, for example DOS,
Linux or Windows. Bochs was written by Kevin Lawton and is currently
maintained by the Bochs project at "http://bochs.sourceforge.net".

Bochs can be compiled and used in a variety of modes, some which are
still in development.  The 'typical' use of bochs is to provide
complete x86 PC emulation, including the x86 processor, hardware
devices, and memory.  This allows you to run OS's and software within
the emulator on your workstation, much like you have a machine
inside of a machine.  Bochs will allow you to run Windows
applications on a Solaris machine with X11, for example.

Bochs is distributed under the GNU LGPL. See LICENSE and COPYING for details.

GETTING CURRENT SOURCE CODE

Source code for Bochs is available from the Bochs home page at
http://bochs.sourceforge.net.  You can download the most recent
release, use SVN to get the latest sources, or grab a SVN
snapshot which is updated frequently. The releases contain the most
stable code, but if you want the very newest features try the
SVN version instead.

WHERE ARE THE DOCS?

The Bochs documentation is written in Docbook.  Docbook is a text
format that can be rendered to many popular browser formats such
as HTML, PDF, and Postscript.  Each binary release contains the
HTML rendering of the documentation.  Also, you can view the
latest documentation on the web at
  http://bochs.sf.net/doc/docbook/index.html

WHERE CAN I GET MORE INFORMATION?  HOW DO I REPORT PROBLEMS?

Both the documentation and the Bochs website have instructions on how
to join the bochs-developers mailing list, which is the primary
forum for discussion of Bochs.  The main page of the website also
has links to bug reports and feature requests.  You can browse and
add to the content in these areas even if you do not have a (free)
SourceForge account.  We need your feedback so that we know what
parts of Bochs to improve.

There is a patches section on the web site too, if you have made
some changes to Bochs that you want to share.

HOW CAN I HELP?

If you would like contribute to the Bochs project, a good first step
is to join the bochs-developers mailing list, and read the archive
of recent messages to see what's going on.

If you are a technical person (can follow hardware specs, can write
C/C++) take a look at the list of open bug reports and feature
requests to see if you are interested in working on any of the
problems that are mentioned in them.  If you check out the SVN
sources, make some changes, and create a patch, one of the
developers will be very happy to apply it for you.  Developers who
frequently submit patches, or who embark on major changes in the
source can get write access to SVN.  Be sure to communicate with the
bochs-developers list to avoid several people working on the same
thing without realizing it.

If you are a Bochs user, not a hardware/C++ guru, there are still
many ways you could help out.  For example:
  - write instructions on how to install a particular operating system
  - writing/cleaning up documentation
  - testing out Bochs on every imaginable operating system and
    reporting how it goes.