All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Michael Lotz <mmlr@mlotz.ch>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Native Port of QEMU to Haiku
Date: Tue, 19 May 2009 07:56:52 -0500	[thread overview]
Message-ID: <4A12AC94.9060101@codemonkey.ws> (raw)
In-Reply-To: <7861078417-BeMail@haiku>

Michael Lotz wrote:
> Hi there
>
> I'm one of the developers that work on the Haiku OS and have also been 
> maintaining the BeOS/Haiku port of QEMU for the last couple of years. 
> Due to BeOS being locked into GCC 2.95.3 and our commitment to provide 
> binary compatibility with BeOS R5 in the first Haiku release, getting 
> this port to work and maintaining it has been a lot of work and largely 
> just a hack.
>
> Haiku however also has a native GCC 4.3.3 toolchain since some time and 
> I brought the QEMU port up to date using it. Since QEMU is pure C, it 
> was possible to mix the Haiku display part and audio backend compiled 
> with GCC 2.95.3 with a GCC 4.3.3 compiled QEMU core (this doesn't 
> require any code changes and will simply continue to work once we 
> migrate fully to GCC 4). This made it possible to do a much cleaner 
> port that I think could now also be commited into the QEMU repository.
>
> Since BeOS is not going anywhere and since it is stuck with the old 
> GCC, I've removed all the leftovers from the original BeOS port so the 
> final patch simply adds native Haiku support to QEMU.
>
> The patch linked below is against the 0.10.4 release sources including 
> kqemu in a kqemu subdirectory. Please advice if you would be willing to 
> include this work into your repository. If necessary I can split this 
> up into multiple patches providing more detailed info on the different 
> parts or diff it against more current sources. Please just let me know.
>
> http://haiku.mlotz.ch/qemu-0.10.4-haiku.diff
>   

To even consider this, you have to send this to the mailing list as a 
series of patches either inlined or attached as plain text.  A URL to a 
file with a non-text mime encoding is not easily reviewable.

Regards,

Anthony Liguori

> Regards
> Michael
>
>
>   

  parent reply	other threads:[~2009-05-19 12:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 13:46 [Qemu-devel] Native Port of QEMU to Haiku Michael Lotz
2009-05-19  8:32 ` Stefan Weil
2009-05-19  8:48 ` Avi Kivity
2009-05-19 12:56 ` Anthony Liguori [this message]
2009-05-19 13:54 ` François Revol
2009-05-19 16:56   ` Andreas Färber
2009-05-21  1:04     ` Ingo Weinhold
2010-09-19 22:50 ` [Qemu-devel] [PATCH 0/8] Add Haiku host support Andreas Färber
2010-09-19 22:50   ` [Qemu-devel] [PATCH 1/8] configure: Add basic support for Haiku Andreas Färber
2010-09-19 22:50     ` [Qemu-devel] [PATCH 2/8] configure: Don't rely on special pthreads library Andreas Färber
2010-09-19 22:50       ` [Qemu-devel] [PATCH 3/8] Haiku doesn't have libm Andreas Färber
2010-09-19 22:50         ` [Qemu-devel] [PATCH 4/8] nbd: Haiku has _IO() in its BSD compatibility layer Andreas Färber
2010-09-19 22:50           ` [Qemu-devel] [PATCH 5/8] tap: Add stub for Haiku Andreas Färber
2010-09-19 22:50             ` [Qemu-devel] [PATCH 6/8] slirp: Silence warning on Haiku Andreas Färber
2010-09-19 22:50               ` [Qemu-devel] [FYI 7/8] qemu_malloc: Use areas on Haiku for sizes > 1 MiB Andreas Färber
2010-09-19 22:50                 ` [Qemu-devel] [FYI 8/8] ui: Haiku frontend Andreas Färber
2010-09-20 12:26                 ` [Qemu-devel] Re: [HaikuPorts-devs] [FYI 7/8] qemu_malloc: Use areas on Haiku for sizes > 1 MiB Oliver Tappe
2010-09-21 22:29                   ` Andreas Färber
2010-09-20 19:04   ` [Qemu-devel] Re: [HaikuPorts-devs] [PATCH 0/8] Add Haiku host support Ingo Weinhold
2010-09-21 20:54     ` Andreas Färber
2010-10-03  7:47   ` [Qemu-devel] " Blue Swirl

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=4A12AC94.9060101@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mmlr@mlotz.ch \
    --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.