I'm working on re-implementing an application to use mesa-solo with dri. I'm using a Radeon 9200 SE (rv280), latest CVS drm code and mesa drivers.
In my mesa-solo tests I'm finding that there are two calls to drmCreateContext. The first is made by the server, and the second is made by the client application via glXCreateContext. The second call fails (access permission) at the ioctl call DRM_IOCTL_ADD_CTX. ------ cut -------- [17185712.396000] [drm:drm_ioctl] pid=5525, cmd=0xc0086420, nr=0x20, dev 0xe200, auth=1 [17185712.396000] [drm:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 1 [17185712.396000] [drm:drm_addctx] 1 [17185712.396000] [drm:drm_ioctl] pid=5525, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 [17185712.396000] [drm:drm_lock] 1 (pid 5525) requests lock (0x00000000), flags = 0x00000000 [17185712.396000] [drm:drm_lock] 1 has lock [17185712.396000] [drm:drm_ioctl] pid=5525, cmd=0x40546440, nr=0x40, dev 0xe200, auth=1 ------ cut -------- [17185716.412000] [drm:drm_ioctl] pid=5527, cmd=0xc0086420, nr=0x20, dev 0xe200, auth=1 [17185716.412000] [drm:drm_ioctl] ret = fffffff3 ------- cut ---------- Both processes are run as root, but there are two separate processes requesting the context - the miniglx "server" app is the first (successful), and the client prog is second (fails). I notice that the server app requests a lock which it doesn't surrender. Can this be the problem? (i.e. can the client add a context when the server holds the lock?). I don't understand the ioctl perms, but I'd have thought that root should get to do this. Is it that there are two processes here, and only one can have the context? Any ideas would be appreciated. Dan Sperka Center for Neuroscience UC Davis djsperka_at_ucdavis_dot_edu ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
