mirrors
/
Bochs
mirror of https://github.com/bochs-emu/Bochs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Bochs/bochs
History
Stanislav Shwartsman bee5940167 fixed compilation err with trace cache off 2011-04-03 03:43:38 +00:00
..
bios set propertities for more files 2011-02-25 15:32:08 +00:00
build Unify manifest file for Win32 and Win64 - also fixes MSDEV command line compilation issue 2011-03-07 17:07:29 +00:00
bx_debug implemented AVX instructions support 2011-03-19 20:09:34 +00:00
cpu fixed compilation err with trace cache off 2011-04-03 03:43:38 +00:00
disasm first fixups after AVX 2011-03-20 18:27:31 +00:00
doc update docs for new xsaveopt .bochsrc option 2011-03-25 20:35:58 +00:00
docs-html - removed old stuff 2009-04-29 11:22:02 +00:00
dynamic - remove obsolete makefile 2002-10-26 13:19:06 +00:00
font Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
fpu rename model_specific.h to be cpuid.h 2011-03-19 17:35:18 +00:00
gui - fixed segfault if Xrandr extension is not installed. If not present, use 2011-04-01 15:52:13 +00:00
host/linux/pcidev another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
instrument updated instrumentation callbacks 2011-03-22 22:18:40 +00:00
iodev - small optimization in read / write sector loop: no need to calculate logical 2011-04-02 13:19:52 +00:00
memory rename model_specific.h to be cpuid.h 2011-03-19 17:35:18 +00:00
misc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
patches new Bochs icons from patches folder 2009-11-07 21:07:59 +00:00
plex86 Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
.bochsrc update docs for new xsaveopt .bochsrc option 2011-03-25 20:35:58 +00:00
.conf.amigaos - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.beos - enable VBE support by default in configure script 2006-11-20 18:55:16 +00:00
.conf.everything - added documentation for the ES1370 soundcard 2011-03-13 09:09:34 +00:00
.conf.linux allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.macos allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.macosx allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.nothing added smalles possible confiure script 2009-10-15 15:47:15 +00:00
.conf.sparc allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
.conf.win32-cygwin cleanups 2010-04-13 15:55:02 +00:00
.conf.win32-vcpp allow to configure CPU features at runtime - implemened on example of SSE/AES/MOVBE/POPCNT 2010-02-25 22:04:31 +00:00
CHANGES updated CHANGES 2011-03-26 22:05:47 +00:00
COPYING - removed wrong character from FSF address (converted invisible and useless 2009-02-08 09:05:52 +00:00
Makefile.in rename model_specific.h to be cpuid.h 2011-03-19 17:35:18 +00:00
PARAM_TREE.txt added XSAVEOPT instruction emulation (for now with no state tracking according to Intel docs, just alias it to XSAVE) 2011-03-25 20:32:07 +00:00
README - preparing release 2.4.6 2011-02-22 17:10:47 +00:00
README-plugins another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
README-wxWindows another whitespace cleanup by Sebastien 2008-02-05 22:57:43 +00:00
README.rfb - remove GPL'd rfbproto.h 2004-04-05 12:09:25 +00:00
TESTFORM.txt Make XAPIC runtime option as well 2010-02-28 14:52:17 +00:00
TODO CPU features set should be runtime options - could be done for most of the CPU stuff without emulation slowdown at all. 2010-02-09 21:55:08 +00:00
aclocal.m4 - removed wrong character from FSF address (converted invisible and useless 2009-02-08 09:05:52 +00:00
bochs.h - moved BX_MIN and BX_MAX macro definitions to bochs.h, removed duplicates and 2011-03-15 22:18:40 +00:00
bxversion.h.in - I have tried to make the --prefix argument to configure control 2001-11-10 03:48:22 +00:00
bxversion.rc.in Added Bochs version info for Win32 - patch from @SF tracker 2008-02-09 07:51:15 +00:00
config.cc added XSAVEOPT instruction emulation (for now with no state tracking according to Intel docs, just alias it to XSAVE) 2011-03-25 20:32:07 +00:00
config.guess Update config.guess/config.sub o latest revision (May 2010) 2010-06-10 17:56:46 +00:00
config.h.in implemented AVX instructions support 2011-03-19 20:09:34 +00:00
config.sub Update config.guess/config.sub o latest revision (May 2010) 2010-06-10 17:56:46 +00:00
configure - CVS to SVN changes 2011-04-01 16:20:15 +00:00
configure.in - CVS to SVN changes 2011-04-01 16:19:15 +00:00
crc.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
extplugin.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
gdbstub.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
install-sh - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
load32bitOShack.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
logio.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
ltdl.c Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
ltdl.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
ltdlconf.h.in Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
ltmain.sh - removed wrong character from FSF address (converted invisible and useless 2009-02-08 09:05:52 +00:00
main.cc - CVS to SVN changes 2011-04-01 16:19:15 +00:00
msrs.def added msrs def example 2008-12-28 20:54:48 +00:00
osdep.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
osdep.h fixed configure for M$ 2011-03-03 16:03:59 +00:00
param_names.h added XSAVEOPT instruction emulation (for now with no state tracking according to Intel docs, just alias it to XSAVE) 2011-03-25 20:32:07 +00:00
pc_system.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
pc_system.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
plex86-interface.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
plex86-interface.h Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
plugin.cc Adding Id and Rev property to all files 2011-02-24 22:05:47 +00:00
plugin.h - implemented gameport (joystick) presence control by external device and use 2011-03-31 16:54:06 +00:00
win32_enh_dbg.rc - Added graphical Bochs debugger under Win32 host ! 2008-10-21 13:45:03 +00:00
win32res.rc Unify manifest file for Win32 and Win64 - also fixes MSDEV command line compilation issue 2011-03-07 17:07:29 +00:00
wxbochs.rc - added version info for wxMSW port 2008-02-10 22:03:47 +00:00

README 

Bochs - The cross platform IA-32 (x86) emulator
Updated: Tue Feb 22 18:07:00 CET 2011
Version: 2.4.6

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.  Currently, Bochs can be compiled to emulate a 386, 486,
Pentium/PentiumII/PentiumIII/Pentium4 or x86-64 CPU, including optional
MMX, SSEx and 3DNow! instructions.  Bochs is capable of running
most Operating Systems inside the emulation, for example Linux, DOS,
Windows 95/98/NT/2000/XP or Windows Vista.
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 CVS to get the latest sources, or grab a CVS
snapshot which is updated nightly.  The releases contain the most
stable code, but if you want the very newest features try the
CVS 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 CVS
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 CVS.  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.