Bochs/bochs
Volker Ruppert 43c1ac48f4 - implemented TFTP support in eth_slirp.cc
* moved TFTP request processing core from eth_vnet.cc to netmod.cc
  * added TFTP handling in eth_slirp.cc similar to DHCP
2012-08-16 11:59:44 +00:00
..
bios fixed comments 2012-08-06 17:59:54 +00:00
build - updated MSVC plugins workspace 2012-08-06 20:16:53 +00:00
bx_debug - generate parser / lexer files only if both flex and yacc are present and also 2012-08-11 07:16:23 +00:00
cpu SSE cvt instructions: transition from FPU to MMX state has higher priority than SSE exception (#XF/#UD) 2012-08-11 07:41:13 +00:00
disasm set of small cpu fixes 2012-08-09 13:11:25 +00:00
doc - implemented TFTP support in eth_slirp.cc 2012-08-16 11:59:44 +00:00
docs-html implemented ADCX/ADOX instructions from rev013 of arch extensions published by Intel 2012-07-12 14:51:54 +00:00
fpu Standartization of Bochs instruction handlers. 2012-08-05 13:52:40 +00:00
gui - minor cleanups in the wx code 2012-08-15 12:47:08 +00:00
host/linux/pcidev
instrument cleanup instrumentation stub 2012-08-05 13:40:32 +00:00
iodev - implemented TFTP support in eth_slirp.cc 2012-08-16 11:59:44 +00:00
memory - fixes based on Debian patches by Guillem Jover 2012-07-14 07:01:43 +00:00
misc - moved the lowlevel cdrom and disk image stuff to the new subdirectory iodev/hdimage 2012-08-05 18:13:38 +00:00
patches - removed outdated patch 2012-07-15 09:31:02 +00:00
.bochsrc - added VirtualPC image support, new disk image mode is called 'vpc' 2012-08-05 09:33:33 +00:00
.conf.amigaos
.conf.everything implemented SVM emulation support for Bochs (incomplete yet) 2011-12-25 19:35:29 +00:00
.conf.linux - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.macos - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.macosx - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.nothing Fixed SF bug [3548109] VMX State Not Restored After Entering SMM on 32-bit Systems 2012-07-27 08:13:39 +00:00
.conf.sparc
.conf.win32-cygwin - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
.conf.win32-vcpp - added devices ES1370 and E1000 to shortcut scripts (known to work with Linux 2012-05-01 18:03:43 +00:00
aclocal.m4 - fixed autoconf 2.68 warnings 2012-02-19 19:50:56 +00:00
bochs.h add new instrumentation callbacks for physical memory access from CPU 2012-06-18 11:41:26 +00:00
bxversion.h.in
bxversion.rc.in
CHANGES - implemented TFTP support in eth_slirp.cc 2012-08-16 11:59:44 +00:00
config.cc Allow larger quantum value for SMP simulations (up to 32) 2012-08-02 20:48:27 +00:00
config.guess
config.h.in Allow larger quantum value for SMP simulations (up to 32) 2012-08-02 20:48:27 +00:00
config.sub
configure - generate parser / lexer files only if both flex and yacc are present and also 2012-08-11 07:16:50 +00:00
configure.in - generate parser / lexer files only if both flex and yacc are present and also 2012-08-11 07:16:23 +00:00
COPYING
cpudb.h update CHANGES 2012-05-26 19:40:18 +00:00
crc.cc
extplugin.h - added new plugin type PLUGTYPE_STANDARD for optional plugins which are used in 2012-01-10 17:45:18 +00:00
gdbstub.cc - compilation fixes for MSVC (SF bug #2905969) 2012-03-11 18:12:50 +00:00
install-sh
load32bitOShack.cc
logio.cc added const to several class members 2012-03-27 21:30:34 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc - fixed location of optional plugin load / unload calls 2012-07-14 15:48:48 +00:00
Makefile.in - don't clean pcidev subdirectory if support is disabled 2012-08-09 18:26:14 +00:00
msrs.def
osdep.cc
osdep.h undo bxswap change - it breaks build with bx_debugger enabled. error - multiple definition of bx_swap16 in parser.o and lexer.o 2011-12-28 22:43:18 +00:00
param_names.h - several fixes for "2nd run" support in wx (still incomplete) 2012-08-14 19:33:24 +00:00
PARAM_TREE.txt implemented ADCX/ADOX instructions from rev013 of arch extensions published by Intel 2012-07-12 14:51:54 +00:00
pc_system.cc - wx: use new log function name for the table of log modules 2012-02-23 17:16:35 +00:00
pc_system.h
plugin.cc - devices 'parallel' and 'serial': 2012-04-16 19:17:10 +00:00
plugin.h - prepared support for sending absolute x/y values from the gui to the mouse emulation 2012-06-21 17:33:37 +00:00
README update README file with newest Bochs CPU emulation caps 2012-02-10 16:02:22 +00:00
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt update TESTFORM for 2.5 release 2011-11-07 19:04:52 +00:00
TODO update TODO and CHANGES 2012-08-05 19:55:00 +00:00
win32_enh_dbg.rc
win32res.rc - second try to fix duplicate resource id 2012-08-06 21:00:42 +00:00
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Sun Nov 27 16:55:00 CET 2011
Version: 2.5.1

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 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 nightly.  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

Some information has not yet been transferred from the older
HTML docs.  These can be found at http://bochs.sf.net/docs-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.