linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brad Boyer <flar@cegt201.bradley.edu>
To: andreas@andreas.org (Andreas Bogk)
Cc: jpgarcia@execpc.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: EM86 port for LinuxPPC?
Date: Fri, 11 Jun 1999 18:08:00 -0500 (CDT)	[thread overview]
Message-ID: <199906112308.SAA24796@cegt201.bradley.edu> (raw)
In-Reply-To: <m3emjivpao.fsf@soma.andreas.org> from "Andreas Bogk" at Jun 11, 99 03:29:19 pm


> And then there is bochs, which is a complete PC emulator, and which
> certainly could be modularized:
> 
> http://www.bochs.org
> 
> It reaches the speed of a 2 MHz 486 on my 300 MHz G3, so it's not
> exactly a viable option for running x86 binaries on PPC.

In addition to being slow, it's also not free.  In any sense of the
word.  Bochs is shareware last I checked, so you're supposed to pay
for it if you use it.  The source code is available, but the license
didn't even resemble open source from what I could tell.  We might be
able to get a few hints from it, but we'd be in trouble if we used
anything directly...

		Brad Boyer
		flar@cegt201.bradley.edu

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-06-11 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-10 18:13 EM86 port for LinuxPPC? Joseph Palani Garcia
1999-06-10 21:03 ` Brad Boyer
1999-06-10 21:28   ` [patch] mol quit-at-shutdown Brad Midgley
1999-06-11 12:03     ` Benjamin Herrenschmidt
1999-06-11 13:29   ` EM86 port for LinuxPPC? Andreas Bogk
1999-06-11 23:08     ` Brad Boyer [this message]
1999-06-18 10:14     ` Gabriel Paubert
1999-06-10 22:56 ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199906112308.SAA24796@cegt201.bradley.edu \
    --to=flar@cegt201.bradley.edu \
    --cc=andreas@andreas.org \
    --cc=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).