Bochs/bochs
2017-05-21 15:08:20 +00:00
..
bios Regenerated configure script and recompiled BIOS for HPET support. 2017-04-17 07:28:22 +00:00
build Preparing release 2.6.9 2017-04-09 06:45:39 +00:00
bx_debug fixes for debugger and disasm 2017-05-10 18:31:59 +00:00
cpu fixes for debugger and disasm 2017-05-10 18:31:59 +00:00
disasm extracted fetchdecode into separated folder under cpu and also out of BX_CPU_C class into stand-alone module. Next step: wrap it up nicely and define clear interace to CPU model to minimize dependencies. Ideally I need fetchdecode to not include CPU at all 2016-06-12 21:23:48 +00:00
doc Some documentation updates. 2017-05-21 07:27:26 +00:00
docs-html implemented SMAP (Supervisor Mode Access Protection) from [Intel Architecture Instruction Set Extensions Programming Reference] rev14 2012-09-10 15:22:26 +00:00
gui Bochs thread handling improvements: 2017-05-18 18:34:00 +00:00
host/linux/pcidev
instrument fixed compliation err 2015-10-26 17:49:45 +00:00
iodev The resampler and mixer threads are now stopped with BX_THREAD_KILL(). 2017-05-21 15:08:20 +00:00
memory Simplified code for the "optromimage" and "optramimage" options stuff (saving 2017-02-14 20:11:58 +00:00
misc Compilation fixes for Cygwin. 2017-04-18 20:45:28 +00:00
patches Updated user plugin example. 2017-01-28 20:31:18 +00:00
.bochsrc Some documentation updates. 2017-05-21 07:27:26 +00:00
.conf.amigaos
.conf.everything The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.linux Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.macos Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.macosx Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.nothing Enable PCI support by default / better text formatting for 'configure --help' 2012-10-25 16:02:03 +00:00
.conf.sparc
.conf.win32-cygwin Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.win32-vcpp Continued release preparations: 2017-03-24 18:23:07 +00:00
aclocal.m4
bochs.h Bochs thread handling improvements: 2017-05-18 18:34:00 +00:00
bxversion.h.in
bxversion.rc.in Fixed template for the win32 version information. 2014-05-15 21:19:54 +00:00
CHANGES Preparing release 2.6.9 2017-04-09 06:45:39 +00:00
config.cc If setenv() is present on Windows and variable BXSHARE is not set, use the 2017-04-22 10:17:54 +00:00
config.guess
config.h.in Added symbol BX_LOAD32BITOSHACK to disable this legacy feature. With the 2017-04-17 13:26:44 +00:00
config.sub Added Android host platform support to Bochs based on SF patch #534. 2016-08-12 17:06:14 +00:00
configure Removed gui support auto-detection using --with-all-libs option for the MacOS 9 2017-04-17 14:41:02 +00:00
configure.in Removed gui support auto-detection using --with-all-libs option for the MacOS 9 2017-04-17 14:41:02 +00:00
COPYING
cpudb.h implemented CLZERO instruction from AMD Ryzen CPU 2017-03-25 20:12:31 +00:00
crc.cc
extplugin.h Rewrite of the network driver plugin code. 2017-03-12 07:48:08 +00:00
gdbstub.cc For each WSAStartup() we have to call WSACleanup() on exit. 2017-03-06 21:30:05 +00:00
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 Added macro BX_FATAL() that works like BX_PANIC(), but with hardcoded action 2016-12-30 10:04:06 +00:00
ltdl-bochs.h Renamed "ltdl.h" to "ltdl-bochs.h" to avoid conflicts with the include file 2013-12-17 19:58:43 +00:00
ltdl.c fixed problems found by cppcheck tool (patch by Maxim Derbasov) 2015-01-03 13:53:52 +00:00
ltdlconf.h.in
ltmain.sh
main.cc If setenv() is present on Windows and variable BXSHARE is not set, use the 2017-04-22 10:17:54 +00:00
Makefile.in Reverted 'clean' target optimization. MinGW/MSYS uses targets without ".exe", 2017-03-18 09:27:48 +00:00
msrs.def
osdep.cc c++ better to use new/delete and not malloc 2016-12-05 19:05:31 +00:00
osdep.h Fixed some MSVC warnings in the debugger code. 2014-12-23 11:53:35 +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 Implemented 'realtime' option for the Voodoo update timer similar to the VGA 2017-04-30 09:07:25 +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 Cleanups in the Bochs system timer code 2017-03-30 18:08:15 +00:00
plugin.h Moved method release_keys() to the common devices code to make sure this 2017-04-22 15:32:07 +00:00
qemu-queue.h Added QEMU queue macros (required for EHCI) as a separate file. Removed already 2016-01-08 18:58:27 +00:00
README Preparing release 2.6.9 2017-04-09 06:45:39 +00:00
README-plugins
README-wxWidgets Domumentation updates and cleanups 2013-12-24 08:55:07 +00:00
README.rfb Domumentation updates and cleanups 2013-12-24 08:55:07 +00:00
TESTFORM.txt
TODO Some release preparations: 2017-03-21 20:12:07 +00:00
win32_enh_dbg.rc Added capability to use the gui debugger output window as a log viewer 2014-01-13 21:31:14 +00:00
win32res.rc Added symbol VSIDE in the MSVC workspace files and and the manifest section 2017-03-19 12:22:27 +00:00
wxbochs.rc Modified win32 resource files based on patch.mingw-resources. We already use 2013-12-28 15:11:13 +00:00

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.