From: Josh Parsons <jbparsons@ucdavis.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu on armeb host
Date: Sat, 23 Jul 2005 09:29:51 -0700 [thread overview]
Message-ID: <1122136192.12335.14.camel@localhost.localdomain> (raw)
I'm new to this list, but I thought I'd join it, as I've been attempting
to build qemu for an armeb host, specifically the linksys nslu2 running
the "unslung" firmware. It took a bit of patching, but I now have a
working qemu-i386 (other targets still need looking at). As well as
patches related to armeb host support, I found a couple of cross-
compilation related bugs (the nslu2 is not a fast system, so I am cross-
compiling for it on an i386).
Has anyone else here tried qemu hosted on armeb? What is the best way to
submit my patches? Should I post them here, or add them to the bug list
on savannah?
Thanks,
--
Josh Parsons
Philosophy Department
1238 Social Sciences and Humanities Bldg.
University of California
Davis, CA 95616-8673
USA
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
next reply other threads:[~2005-07-23 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 16:29 Josh Parsons [this message]
2005-07-23 17:14 ` [Qemu-devel] qemu on armeb host Karel Gardas
2005-07-25 7:15 ` Josh Parsons
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=1122136192.12335.14.camel@localhost.localdomain \
--to=jbparsons@ucdavis.edu \
--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).