From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Christoph Bumiller
<e0425955-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: ddx/nv50: use drawable.bitsPerPixel to decide format
Date: Wed, 30 Dec 2009 20:35:32 +0100 [thread overview]
Message-ID: <20091230193532.GA10600@joi.lan> (raw)
In-Reply-To: <4B3B9368.3020602-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
On Wed, Dec 30, 2009 at 06:52:40PM +0100, Christoph Bumiller wrote:
> On 12/30/2009 06:37 PM, Christoph Bumiller wrote:
> > On 12/29/2009 06:06 PM, Marcin Slusarz wrote:
> >> On Mon, Dec 28, 2009 at 06:55:23PM +0100, Maarten Maathuis wrote:
> >>> On Mon, Dec 28, 2009 at 6:37 PM, Marcin Slusarz
> >>> <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >>>>
> >>>> ---
> >>>> src/nv50_exa.c | 155 ++++++++++++++++++++++++++++++++++++--------------------
> >>>> 1 files changed, 100 insertions(+), 55 deletions(-)
> >>>>
> >>>> diff --git a/src/nv50_exa.c b/src/nv50_exa.c
> >>>> index 1f5a4ac..54968e8 100644
> >>>> --- a/src/nv50_exa.c
> >>>> +++ b/src/nv50_exa.c
> >>>> @@ -79,15 +79,16 @@ NV50EXA2DSurfaceFormat(PixmapPtr ppix, uint32_t *fmt)
> >>>>
> >>>> switch (ppix->drawable.depth) {
> >>>> case 8 : *fmt = NV50_2D_SRC_FORMAT_R8_UNORM; break;
> >>>> - case 15: *fmt = NV50_2D_SRC_FORMAT_X1R5G5B5_UNORM; break;
> >>>> - case 16: *fmt = NV50_2D_SRC_FORMAT_R5G6B5_UNORM; break;
> >>>> + case 15:
> >>>> + case 16:
> >>>> + *fmt = NV50_2D_SRC_FORMAT_R5G6B5_UNORM;
> >>>> + break;
> >>>
> >>> depth 15 is R5G5B5, why this change?
> >>
> >> it's the only value which passes rendercheck tests
> >> (rendercheck -t blend -o Src -f x1r5g5b5,r5g5b5)
> >>
> > This is as far as I can tell because x1r5g5b5 (XRender direct format as
> > queries by rendercheck) has depth set to 16, and therefore uses case 16
> > here.
> *queried
> > If you use the same for depth 15, the rendercheck test check succeeds,
> > but doing this is wrong.
> > If you check bitsPerPixel instead, this will be 15 for both x1r5g5b5
> > and r5g5b5, and all looks fine then.
I agree.
> If we e.g. copy from 15bpp to 16bpp though, can the 16th bit be alpha
> instead of green ? That would be problematic.
xserver advertises a1r5g5b5 as supported too so it's possible,
but rendercheck currently omits it, because it can't handle
(it uses colors which can't be represented in low-bits color formats,
rounds them and the "error" looks huge)
i don't know how to test it...
> > See the attached patch. I'm not sure if I should have changed the xv
> > stuff also.
rendercheck is happy with your patch :)
ps: i'll remove the piece you fixed differently and resend my patch soon
next prev parent reply other threads:[~2009-12-30 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 17:37 [rebased PATCH 1/2] nv50/exa: add support for more color formats Marcin Slusarz
[not found] ` <20091228173717.GA10639-OI9uyE9O0yo@public.gmane.org>
2009-12-28 17:55 ` Maarten Maathuis
[not found] ` <6d4bc9fc0912280955h348381der3ebae761e412ba5c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-29 17:06 ` Marcin Slusarz
[not found] ` <20091229170634.GA2879-OI9uyE9O0yo@public.gmane.org>
2009-12-30 17:37 ` ddx/nv50: use drawable.bitsPerPixel to decide format Christoph Bumiller
[not found] ` <4B3B8FD9.4070605-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
2009-12-30 17:52 ` Christoph Bumiller
[not found] ` <4B3B9368.3020602-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org>
2009-12-30 19:35 ` Marcin Slusarz [this message]
[not found] ` <20091230193532.GA10600-OI9uyE9O0yo@public.gmane.org>
2009-12-30 20:05 ` [PATCHv2 1/2] nv50/exa: add support for more color formats Marcin Slusarz
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=20091230193532.GA10600@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=e0425955-oe7qfRrRQffzPE21tAIdciO7C/xPubJB@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 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.