From: Gerd Hoffmann <kraxel@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Gibson <david@gibson.dropbear.id.au>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] ppc: Add MacOS VGA driver ROM
Date: Tue, 02 Aug 2016 07:25:19 +0200 [thread overview]
Message-ID: <1470115519.30562.80.camel@redhat.com> (raw)
In-Reply-To: <1470086678.5978.373.camel@kernel.crashing.org>
On Di, 2016-08-02 at 07:24 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2016-08-01 at 21:38 +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > So, I believe qemu convention is to include the ROM source via a
> > > submodule - even though it won't typically be built from there and
> > the
> > > prebuilt blob will be used instead.
> >
> > Correct. Also rules in roms/Makefile to build the thing, to document
> > the build process and to simplify the maintainer's job on updates.
>
> That's the part we cannot provide unfortunately. There is sadly no
> toolchain that can produce a MacOS PEF binary other than hosted in
> MacOS itself. In fact I don't think Apple XCode can either, which
> leaves us with CodeWarrior (commercial) or MPW (which I think at some
> point became free but I didn't find it and it doesn't work on OS X
> afaik).
Firmware builds often have specific requirements, such as only working
on $arch due to firmware not being cross-buildable (thats why there are
the prebuilt binaries in the first place). So if those makefile rules
work only on macos with CodeWarrior installed that is perfectly fine.
cheers,
Gerd
next prev parent reply other threads:[~2016-08-02 5:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 8:27 [Qemu-devel] [PATCH] ppc: Add MacOS VGA driver ROM Benjamin Herrenschmidt
2016-07-28 5:51 ` David Gibson
2016-07-28 7:04 ` Alexander Graf
2016-07-28 8:28 ` Stefan Hajnoczi
2016-07-28 12:44 ` Benjamin Herrenschmidt
2016-08-01 4:49 ` Jeff Cody
2016-08-01 6:31 ` Benjamin Herrenschmidt
2016-07-28 12:41 ` Benjamin Herrenschmidt
2016-08-01 19:38 ` Gerd Hoffmann
2016-08-01 21:24 ` Benjamin Herrenschmidt
2016-08-02 5:25 ` Gerd Hoffmann [this message]
2016-08-02 5:35 ` Benjamin Herrenschmidt
2016-08-02 8:55 ` Gerd Hoffmann
2016-08-02 9:17 ` Benjamin Herrenschmidt
2016-08-02 10:53 ` Gerd Hoffmann
2016-08-02 13:17 ` Benjamin Herrenschmidt
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=1470115519.30562.80.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.