From: Bob Gleitsmann <rjgleits@bellsouth.net>
To: dri-devel@lists.freedesktop.org
Cc: bskeggs@redhat.com
Subject: [Fwd: [Patch] drm/nouveau: nouveau/nouveau_abi16.c does not return offset of allocated notifier]
Date: Wed, 06 Nov 2013 20:09:59 -0500 [thread overview]
Message-ID: <1383786599.1296.8.camel@s2895bg> (raw)
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
I think this may have been overlooked, but it does make a difference.
BTW, the comments in the code state that the fence has to be at zero
offset in the page. In the course of investigating this problem I found
that this is not the case, at least for the 6800 Ultra. I have it
located at f80 and it works correctly. Or seems to.
Best Wishes,
Bob
[-- Attachment #2: Forwarded message - [Patch] drm/nouveau: nouveau/nouveau_abi16.c does not return offset of allocated notifier --]
[-- Type: message/rfc822, Size: 4765 bytes --]
From: Bob Gleitsmann <rjgleits@bellsouth.net>
To: dri-devel@lists.freedesktop.org
Subject: [Patch] drm/nouveau: nouveau/nouveau_abi16.c does not return offset of allocated notifier
Date: Sat, 14 Sep 2013 01:40:23 -0400
Message-ID: <1379137223.1306.5.camel@s2895bg>
Hi,
The following patch fixes problems retrieving query results. I have
tested it on nv40 - 6800 Ultra.
Best Wishes,
Bob
--- a/drivers/gpu/drm/nouveau/nouveau_abi16.c
+++ b/drivers/gpu/drm/nouveau/nouveau_abi16.c
@@ -445,6 +445,7 @@
nouveau_abi16_ioctl_notifierobj_alloc(ABI16_IOCTL_ARGS)
sizeof(args), &object);
if (ret)
goto done;
+ info->offset = ntfy->node->offset;
done:
if (ret)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[-- Attachment #3: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2013-11-07 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1383786599.1296.8.camel@s2895bg \
--to=rjgleits@bellsouth.net \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.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