From: "Xiang, Haihao" <haihao.xiang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Daniel Vetter <daniel-/w4YWyX8dFk@public.gmane.org>
Cc: intel-gfx
<intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"libva-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<libva-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Ville Syrjälä"
<ville.syrjala-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Make sample_c messages go faster on Haswell.
Date: Tue, 04 Nov 2014 16:48:00 +0800 [thread overview]
Message-ID: <1415090880.24035.4.camel@xhh-u64> (raw)
In-Reply-To: <CAKMK7uH7-ar7OB2sdZ0phoZJ6j8-660Nr_c5CyiZRqTfgtMGHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 2014-11-03 at 13:48 +0100, Daniel Vetter wrote:
> On Fri, Oct 31, 2014 at 11:27:33AM +0200, Ville Syrjälä wrote:
> > On Thu, Oct 30, 2014 at 12:57:04PM -0700, Kenneth Graunke wrote:
> > > Before we get too much further...we should check if libva is actually broken.
> > > I don't know if this means the sampler palette completely doesn't work, or if
> > > it just means sample_c doesn't work with the palette. If it's the latter,
> > > we're probably fine, because I doubt libva uses sample_c.
> >
> > Yeah if we wouldn't break any existing userspace I guess we could just
> > flip the switch in the kernel. If anyone later wants to start doing
> > something that no longer works they'd have to deal with disabling the
> > bit using an LRI.
>
> It very much looks like libva uses palettes, since it supports C8 and C4
> image formats (well some crazy fourcc nonsense, but meh). And it does so
> on all generations support by the libva driver, i.e. including hsw afaict
>
> Cc'ing people and lists with more clue who should be able to tell whether
> its not just there but actually works ...
Yes, libva driver uses sample (00000) and palette on HSW
Thanks
Haihao
> -Daniel
_______________________________________________
Libva mailing list
Libva@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libva
next prev parent reply other threads:[~2014-11-04 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 22:12 [PATCH] drm/i915: Make sample_c messages go faster on Haswell Kenneth Graunke
2014-10-30 8:50 ` Ville Syrjälä
2014-10-30 9:00 ` Ville Syrjälä
2014-10-30 9:32 ` Kenneth Graunke
2014-10-30 11:01 ` Ville Syrjälä
2014-10-30 17:32 ` Kenneth Graunke
2014-10-30 19:26 ` Ville Syrjälä
2014-10-30 19:57 ` Kenneth Graunke
2014-10-31 9:27 ` Ville Syrjälä
2014-10-31 9:43 ` Jani Nikula
2014-11-03 12:48 ` Daniel Vetter
[not found] ` <CAKMK7uH7-ar7OB2sdZ0phoZJ6j8-660Nr_c5CyiZRqTfgtMGHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-04 8:48 ` Xiang, Haihao [this message]
2014-11-03 16:15 ` Dave Gordon
2014-11-07 18:46 ` Matt Turner
2014-11-11 10:16 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2015-01-01 0:23 Kenneth Graunke
2015-01-05 21:39 ` Kenneth Graunke
2015-01-06 5:11 ` Xiang, Haihao
2015-01-06 5:54 ` Kenneth Graunke
2015-01-06 6:39 ` Xiang, Haihao
2015-01-06 7:00 ` [Intel-gfx] " Xiang, Haihao
2015-01-06 7:03 ` Kenneth Graunke
2015-01-06 7:15 ` [Intel-gfx] " Xiang, Haihao
2015-01-06 8:08 ` Daniel Vetter
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=1415090880.24035.4.camel@xhh-u64 \
--to=haihao.xiang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=daniel-/w4YWyX8dFk@public.gmane.org \
--cc=intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=libva-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ville.syrjala-VuQAYsv1563Yd54FQh9/CA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox