All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ppc: Add MacOS VGA driver ROM
Date: Thu, 28 Jul 2016 09:04:25 +0200	[thread overview]
Message-ID: <5799AE79.8060500@suse.de> (raw)
In-Reply-To: <20160728055102.GE2588@voom.fritz.box>

On 07/28/2016 07:51 AM, David Gibson wrote:
> On Wed, Jul 27, 2016 at 06:27:33PM +1000, Benjamin Herrenschmidt wrote:
>> The project is at https://github.com/ozbenh/QemuMacDrivers
>>
>> This adds a native MacOS driver in ROM (which can be picked up
>> by MacOS once OpenBIOS has been updated if Mark accepts
>> the patches I sent him) which allows MacOS classic
>> (tested 9.2.1) and MacOS X (tested 10.1.4 and 10.4)
>> to properly use QEMU std VGA (10.1.x doesn't work at all
>> without it, the others get the ability to change resolution
>> and color depth).
>>
>> Building the ROM is tricky and requires CodeWarrior for MacOS
>> so I include a pre-built binary.
> 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.
>
> Not sure who the right person to talk to about that would be.

I think Stefan handles the logistics there now. CC'ed him.


The reason for the submodule is so that on tar releases, the source gets 
included automatically. That way we can ensure that we always include 
all GPL sources that we deliver binaries for.


Alex

  reply	other threads:[~2016-07-28  7:04 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 [this message]
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
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=5799AE79.8060500@suse.de \
    --to=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 \
    --cc=stefanha@redhat.com \
    /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.