From: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Maarten Maathuis <madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/2] exa: turn WaitMarker into a NOP.
Date: Fri, 27 Feb 2009 14:43:16 +1000 [thread overview]
Message-ID: <1235709796.3423.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1235681723-11180-1-git-send-email-madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, 2009-02-26 at 21:55 +0100, Maarten Maathuis wrote:
> - map should handle this.
It does, but we don't use prepare/finish_access() hooks to do map() on
the buffer in the non-driver-pixmaps case. I guess we could use
prepare/finish_access() there too, it probably wouldn't hurt any.
Ben.
> ---
> src/nouveau_exa.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/nouveau_exa.c b/src/nouveau_exa.c
> index b656ca7..20ad380 100644
> --- a/src/nouveau_exa.c
> +++ b/src/nouveau_exa.c
> @@ -259,7 +259,7 @@ nouveau_exa_mark_sync(ScreenPtr pScreen)
> static void
> nouveau_exa_wait_marker(ScreenPtr pScreen, int marker)
> {
> - NVSync(xf86Screens[pScreen->myNum]);
> + return;
> }
>
> static Bool
prev parent reply other threads:[~2009-02-27 4:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 20:55 [PATCH 1/2] exa: turn WaitMarker into a NOP Maarten Maathuis
[not found] ` <1235681723-11180-1-git-send-email-madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-02-26 20:55 ` [PATCH 2/2] exa: do PrepareAccess for classic too, since we do need to map the frontbuffer Maarten Maathuis
[not found] ` <1235681723-11180-2-git-send-email-madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-02-27 4:42 ` Ben Skeggs
[not found] ` <1235709737.3423.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-02-27 10:07 ` Hervé Cauwelier
[not found] ` <49A7BB4F.7040103-GANU6spQydw@public.gmane.org>
2009-02-27 11:31 ` Maarten Maathuis
2009-02-27 4:43 ` Ben Skeggs [this message]
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=1235709796.3423.3.camel@localhost.localdomain \
--to=skeggsb-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=madman2003-Re5JQEeQqe8AvxtiuMwx3w@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.