Bochs/bochs
Volker Ruppert e08024f6a1 Some work on the networking modules and documentation.
- The 'vnet' module now uses the 'script' parameter for an alternative log
  file name.
- Renamed log file names in some networking modules (replaced 'ne2k' by a name
  related to the module name).
- Documentation updates (networking stuff and cmosimage).
2017-03-04 10:26:22 +00:00
..
bios Recompiled after MP table fix. 2017-03-02 18:39:35 +00:00
build remove SMP and AVX from Android build script. reduce the binary size and make faster binary (SMP makes binary a lot slower) 2016-08-30 18:42:39 +00:00
bx_debug Fixed compilation errors that occur with debugger enabled. 2016-12-06 18:07:05 +00:00
cpu add vex.w into bxInstruction to be used in disasm 2017-01-28 19:25:30 +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 work on the networking modules and documentation. 2017-03-04 10:26:22 +00:00
docs-html
gui Set up VGA palette entries for gui console to make sure the text is visible. 2017-03-03 12:43:20 +00:00
host/linux/pcidev
instrument fixed compliation err 2015-10-26 17:49:45 +00:00
iodev Some work on the networking modules and documentation. 2017-03-04 10:26:22 +00:00
memory Simplified code for the "optromimage" and "optramimage" options stuff (saving 2017-02-14 20:11:58 +00:00
misc Some changes in bxhub and related code. 2017-03-03 09:56:18 +00:00
patches Updated user plugin example. 2017-01-28 20:31:18 +00:00
.bochsrc Some work on the networking modules and documentation. 2017-03-04 10:26:22 +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 The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.macos The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.macosx The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.nothing
.conf.sparc
.conf.win32-cygwin The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.win32-vcpp The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
aclocal.m4
bochs.h Added macro BX_FATAL() that works like BX_PANIC(), but with hardcoded action 2016-12-30 10:04:06 +00:00
bxversion.h.in
bxversion.rc.in
CHANGES Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +00:00
config.cc Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +00:00
config.guess
config.h.in Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +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 Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +00:00
configure.in Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +00:00
COPYING
cpudb.h added Broadwell ULT CPUID definition to CPUDB 2015-02-12 21:28:24 +00:00
crc.cc
extplugin.h Rewrite of the sound driver plugin code. 2017-02-20 18:21:19 +00:00
gdbstub.cc Fixed SF bug #1376 (this change was missing in rev. 12473). 2015-05-25 12:33:39 +00:00
install-sh
LICENSE
load32bitOShack.cc fixed problems found by cppcheck tool (patch by Maxim Derbasov) 2015-01-03 13:53:52 +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
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 Modified plugin system to support the new PLUGTYPE_GUI. 2017-02-18 16:28:04 +00:00
Makefile.in Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +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
param_names.h Simplified code for the "optromimage" and "optramimage" options stuff (saving 2017-02-14 20:11:58 +00:00
PARAM_TREE.txt Preparing Bochs release 2.6.8 2015-05-03 06:36:30 +00:00
pc_system.cc fixed %d->%u format found by cppcheck (patch by Maxim Derbasov) 2015-01-25 21:24:13 +00:00
pc_system.h
plugin.cc Rewrite of the "no-plugins" code for loading/unloading gui, optional and sound 2017-02-24 19:45:23 +00:00
plugin.h Fixed compilation with plugins enabled and removed obsolete declaration. 2017-02-24 20:02:18 +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 Bochs release 2.6.8 2015-05-03 06:36:30 +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 May  3 08:36:00 CEST 2015
Version: 2.6.8

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.