All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com
Cc: nitinroger123@gmail.com
Subject: Re: [Qemu-devel] ARM->ARM
Date: Sun, 18 Jan 2009 10:36:17 -0700 (MST)	[thread overview]
Message-ID: <20090118.103617.-1572315281.imp@bsdimp.com> (raw)
In-Reply-To: <200901181632.26646.paul@codesourcery.com>

In message: <200901181632.26646.paul@codesourcery.com>
            Paul Brook <paul@codesourcery.com> writes:
: On Sunday 18 January 2009, Nitin Natarajan wrote:
: > Hi all,
: >         I have been thinking about doing a project that will try to run
: > windows mobile executable on a linux based mobile phone. I just wanted to
: > know if this would be feasible and if I could use parts of qemu to achieve
: > the same. I also thought of extracting the assemble from the windows
: > executable and trying to run that after doing a 1->1 ARM mapping. Your
: > comments will be very helpful. Looking forward to hearing from you.
: 
: Sounds like you just need to port Wine.
: 
: You don't need to do any instruction translation or hardware emulation, so 
: qemu is unlikely to be of any real use to you.

The other option would be to do something ala the Citrus Project from
a few years ago on NetBSD and execute PECOFF binaries directly in the
kernel.

Wine has a LOT of x86 specific code in it and would be very hard to
port.

Warner

      reply	other threads:[~2009-01-18 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18  9:12 [Qemu-devel] ARM->ARM Nitin Natarajan
2009-01-18 16:32 ` Paul Brook
2009-01-18 17:36   ` M. Warner Losh [this message]

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=20090118.103617.-1572315281.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=nitinroger123@gmail.com \
    --cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.