From: Karl Magdsick <kmagnum@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Port to IRIX host
Date: Sun, 3 Oct 2004 12:48:46 -0400 [thread overview]
Message-ID: <cd8ecdef04100309483d850369@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410031528430.14868@wgmdd8.biozentrum.uni-wuerzburg.de>
> > Just one remark
> > before merging your patch: could you distinguish the IRIX specific parts
> > from the mips specific ones ? I saw you used '#ifdef __mips__' at places
> > where it may be in fact IRIX specific code.
>
> Yes, you are correct. I just used what was easiest for me, but I will add
> a check in configure, and according to that, a define.
In my closet, I have an SGI Indy (MIPS64) with Debian Linux installed.
Now I'm really tempted to dust it off and try running some of those
packages that fail to compile for MIPS.
At the time I stopped using the Indy machine, Debian used the 32-bit
MIPS kernels. I'm not sure if this has changed recently. Is the MIPS
port for 64-bit or 32-bit MIPS?
In any case, the MIPS port of QEMU looks really cool. Thanks for all
the hard work! About how many hours did it take to port QEMU to MIPS?
-Karl
next prev parent reply other threads:[~2004-10-03 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 7:13 [Qemu-devel] Port to IRIX host Johannes Schindelin
2004-10-03 11:57 ` Fabrice Bellard
2004-10-03 14:00 ` Johannes Schindelin
2004-10-03 14:12 ` Jim C. Brown
2004-10-03 14:44 ` Fabrice Bellard
2004-10-04 6:41 ` Johannes Schindelin
2004-10-03 15:23 ` Karl Magdsick
2004-10-03 16:48 ` Karl Magdsick [this message]
2004-10-04 6:42 ` Johannes Schindelin
2004-10-11 13:55 ` Ian Rogers
2004-10-11 15:02 ` Johannes Schindelin
2004-10-11 15:56 ` [Qemu-devel] transitive was: " Anand Kumria
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=cd8ecdef04100309483d850369@mail.gmail.com \
--to=kmagnum@gmail.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).