fence_signalled), or call
__nouveau_fence_wait so what would you map to? I will ponder your comments
further, but I have doubts.
Anyway thanks for your input.
BG
> Bob Gleitsmann writes:
> > Hello everyone,
> >
> > When trying the demo program copytex for the first time
diff --git a/src/gallium/drivers/nouveau/nouveau_screen.c
b/src/gallium/drivers/nouveau/nouveau_screen.c
index a9426df..0918537 100644
--- a/src/gallium/drivers/nouveau/nouveau_screen.c
+++ b/src/gallium/drivers/nouveau/nouveau_screen.c
@@ -166,7 +166,8 @@ nouveau_screen_fence_finish(struct pipe_
diff --git a/include/drm/nouveau_drm.h b/include/drm/nouveau_drm.h
index b18cad0..d2ce47e 100644
--- a/include/drm/nouveau_drm.h
+++ b/include/drm/nouveau_drm.h
@@ -49,6 +49,10 @@ struct drm_nouveau_channel_free {
int channel;
};
+struct drm_nouveau_channel_wait {
+ int channel;
+
diff --git a/drivers/gpu/drm/nouveau/nouveau_channel.c
b/drivers/gpu/drm/nouveau/nouveau_channel.c
index a3d33a5..ac2fe5a 100644
--- a/drivers/gpu/drm/nouveau/nouveau_channel.c
+++ b/drivers/gpu/drm/nouveau/nouveau_channel.c
@@ -466,6 +466,35 @@ nouveau_ioctl_fifo_free(struct drm_device *dev, vo
Hello everyone,
When trying the demo program copytex for the first time recently, I noticed
pathological behavior: after running for a long time it asserted out and
locked up X. Investigation showed this to be due to the glFinish function
acting like glFlush and not waiting as it is supposed to
--cflags-only-I or something along those lines?
>
> Sending from a mobile, pardon the brevity. ~ C.
>
> On Dec 6, 2010 9:42 AM, "Dan Nicholson" wrote:
> > On Mon, Dec 6, 2010 at 9:15 AM, Brian Paul wrote:
> >> On 12/05/2010 02:06 AM, Bob Gleitsmann wrote:
matter what, making
debugging very difficult. Removing it seems to have no catastrophic effects (or
even detectable ones).
But maybe I am missing something.
Best Wishes,
Bob Gleitsmann
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http
