All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Paul Durrant <Paul.Durrant@citrix.com>, ajax <ajax@redhat.com>,
	"anthony.perard" <anthony.perard@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.paumonne@citrix.com>
Subject: Re: Wondering about cirris and stdvga
Date: Fri, 25 Nov 2016 19:17:31 +0100	[thread overview]
Message-ID: <1480097851.2712.209.camel@citrix.com> (raw)
In-Reply-To: <1479719053.3832.103.camel@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 2015 bytes --]

On Mon, 2016-11-21 at 10:04 +0100, Dario Faggioli wrote:
> On Sat, 2016-11-19 at 12:56 +0200, Pasi Kärkkäinen wrote:
> > 2) It'd good to create an upstream Wayland bugreport and
> > investigate
> > more about why cirrus is broken with Wayland.
> > 
> Sure, I can do that.
> 
An update.

The discussion here has gone on a bit:
https://bugzilla.redhat.com/show_bug.cgi?id=1227770

The conclusion seems to be that:
"cirrus (virtual) hardware is simply to old to run wayland."

And so this is (and will very likely remain) a 'WONTFIX' for cirrus, at
least on Fedora.

I've also opened a thread on wayland-devel mailing list:
https://lists.freedesktop.org/archives/wayland-devel/2016-November/0318
56.html

There, I learned that Wayland is not the component to blame, as Wayland
is the protocol. So, in our case, the 'bug' is most likely in
gnome-shell / Mutter.

That's not a good thing, though. In fact, just to cite a few sentences
from the thread:

"Packed 24bpp is going to be pain, not least because I don't know of
any clients which render in packed-24"

"The 24bpp paths in pretty much everything are also badly untested, so
that's asking for trouble."

"you will need to test and fix every single Wayland compositor out
there."

"I really think you'd be far far better off trying to figure out how to
move off the legacy Cirrus emulation as soon as you can."

So, we can try seeing if I manage to get some logs out of Mutter to
figure out the actual bug more precisely _but_, considering all that
people have said both here and in the other forums, I think it would be
better to spend that time figuring out how to switch (and document this
for 4.8 and previous version, of course).

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-25 18:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 18:04 Wondering about cirris and stdvga Dario Faggioli
2016-11-19 10:56 ` Pasi Kärkkäinen
2016-11-21  8:34   ` Paul Durrant
2016-11-21 17:47     ` Stefano Stabellini
2016-11-21  9:04   ` Dario Faggioli
2016-11-25 18:17     ` Dario Faggioli [this message]
2016-11-29  4:55       ` Konrad Rzeszutek Wilk
2017-03-17 14:19       ` Konrad Rzeszutek Wilk
2017-03-17 15:51         ` Dario Faggioli
2017-03-17 16:08           ` Konrad Rzeszutek Wilk
2017-03-20 14:13         ` Roger Pau Monné
2017-03-20 14:21           ` Paul Durrant
2017-03-20 14:25             ` Roger Pau Monne
2017-04-04 20:18               ` Konrad Rzeszutek Wilk

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=1480097851.2712.209.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=ajax@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=pasik@iki.fi \
    --cc=roger.paumonne@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.