From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60370)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1bUSCm-0006IF-Ec
	for qemu-devel@nongnu.org; Tue, 02 Aug 2016 01:25:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1bUSCj-0005j0-7N
	for qemu-devel@nongnu.org; Tue, 02 Aug 2016 01:25:28 -0400
Message-ID: <1470115519.30562.80.camel@redhat.com>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Tue, 02 Aug 2016 07:25:19 +0200
In-Reply-To: <1470086678.5978.373.camel@kernel.crashing.org>
References: <1469608053.5978.132.camel@kernel.crashing.org>
	<20160728055102.GE2588@voom.fritz.box>
	<1470080328.30562.70.camel@redhat.com>
	<1470086678.5978.373.camel@kernel.crashing.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] ppc: Add MacOS VGA driver ROM
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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,
> >=20
> > > 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.
> >=20
> > Correct.  Also rules in roms/Makefile to build the thing, to document
> > the build process and to simplify the maintainer's job on updates.
>=20
> 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