From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on dsp anyone?
Date: Wed, 11 May 2005 22:23:25 -0700 [thread overview]
Message-ID: <1115875405.17723.111.camel@aragorn> (raw)
In-Reply-To: <4282B989.3090108@sympatico.ca>
On Wed, 2005-05-11 at 22:03 -0400, Olivier Bourgois wrote:
> Has anybody tinkered with porting qemu to something like a TI TMS320C6X
> DSP host. The idea would be to be able to easily port LINUX and other
> open source software to such a DSP.
I would think porting uCLinux would be a better idea. Why give up so
much performance to emulation overhead?
-- John.
next prev parent reply other threads:[~2005-05-12 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 2:03 [Qemu-devel] qemu on dsp anyone? Olivier Bourgois
2005-05-12 5:23 ` John R. Hogerhuis [this message]
2005-12-11 10:15 ` [Qemu-devel] qemulating dsp (was Re: qemu on dsp anyone?) Antti P Miettinen
2005-12-11 13:38 ` Dave Feustel
2005-12-11 16:29 ` [Qemu-devel] Re: qemulating dsp Antti P Miettinen
2005-12-11 19:22 ` Dave Feustel
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=1115875405.17723.111.camel@aragorn \
--to=jhoger@pobox.com \
--cc=qemu-devel@nongnu.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).