From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Instruction Set Simulator
Date: Sat, 18 Feb 2006 03:19:47 -0500 [thread overview]
Message-ID: <43F6D8A3.3030907@dlasys.net> (raw)
In-Reply-To: <001301c633a5$b4cde290$9e01120a@bilisim.local>
I looked at PearPC running on an X86 and was able to get Debian ppc
Linux installed on it.
I was looking to use it as a pseudo native platform to do crossplatform
development.
The performance was slow. But otherwise it was interesting.
Eventually I bought a powerbook off eBay cheap.
Most of the time I use cross tools, but now and then it is useful to
have a running
PPC based system to sanity check what you are trying to do on the
embedded system you are developing for.
Of cource the closer it is to the platform you are developing for the
better.
I thought about modifying PearPc to emulate my hardware, but it looked
too much like wark and no one was paying for it. The idea is still
somewhat intriguing. developing for an embedded system on a software
emulator for that system. Yes, I know that is not an new idea.
Mustafa Çayır wrote:
>Hi all,
>
>Can you provide some information about PowerPC simulators? Which one is best?
>
>Best Regards
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
next prev parent reply other threads:[~2006-02-18 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 9:37 Instruction Set Simulator Mustafa Çayır
2006-02-17 15:22 ` Grant Likely
2006-02-18 8:19 ` David H. Lynch Jr. [this message]
2006-02-18 13:48 ` jeanwelly
2006-02-18 20:56 ` Mark Chambers
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=43F6D8A3.3030907@dlasys.net \
--to=dhlii@dlasys.net \
--cc=linuxppc-embedded@ozlabs.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).