All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Bauer <mail@sebastianbauer.info>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	thuth@redhat.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] ppc: Include vga cirrus card into the compiling process
Date: Tue, 19 Jun 2018 12:46:01 +0200	[thread overview]
Message-ID: <a4d4ed6dd28280922d3444364da28de0@sebastianbauer.info> (raw)
In-Reply-To: <alpine.BSF.2.21.1806191218120.6476@zero.eik.bme.hu>

Am 2018-06-19 12:23, schrieb BALATON Zoltan:
> On Tue, 19 Jun 2018, David Gibson wrote:
>> Ok.  However, your patch doesn't apply against the ppc-for-3.0 tree.
>> It looks like you've made it against a tree including some of BALATON
>> Zoltan's proposed but not yet merged patches.
> I've sent those patches as well. But if this also works with pseries
> maybe it does not have to be in the For sam460ex part of the config
> but could be on it's own with a comment saying that multiple machines
> can use it.

In my opinion, it should be added to pci.mak (and removed from all 
present configs that include pci.mak). There is also CONFIG_VGA_PCI 
there, a bunch of network cards and other stuff. The Cirrus VGA is just 
another PCI card that one could plug into any systems that has a PCI(e) 
bus, also on physical hardware (whether it is supported by which guests 
is a different question).

However, I wanted to be conservative with my change so I added it only 
to the 32 bit PPC branch, because this is the platform that I can easily 
test. Does anybody know why CONFIG_VGA_CIRRUS is selectively enabled for 
PCI-based systems? What would speak against adding it to pci.mak?

Bye
Sebastian

  reply	other threads:[~2018-06-19 10:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 21:56 [Qemu-devel] [PATCH] ppc: Include vga cirrus card into the compiling process Sebastian Bauer
2018-06-18 23:55 ` David Gibson
2018-06-19  4:32   ` Sebastian Bauer
2018-06-19  4:36     ` David Gibson
2018-06-19 10:23       ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2018-06-19 10:46         ` Sebastian Bauer [this message]
2018-06-19 10:56           ` Thomas Huth
2018-06-19 10:57         ` Thomas Huth
2018-06-19 19:38       ` [Qemu-devel] " Sebastian Bauer
2018-06-29 18:06       ` Sebastian Bauer
2018-06-30  6:14         ` David Gibson
2018-06-30 11:29           ` BALATON Zoltan
2018-07-02  4:02             ` David Gibson
2018-07-02  5:22               ` David Gibson
2018-07-02  7:42                 ` Sebastian Bauer
2018-07-03  4:41                   ` David Gibson
2018-07-03 15:20                     ` Eric Blake
2018-07-04  1:30                       ` David Gibson
2018-06-19  5:24   ` Thomas Huth

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=a4d4ed6dd28280922d3444364da28de0@sebastianbauer.info \
    --to=mail@sebastianbauer.info \
    --cc=balaton@eik.bme.hu \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@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.