search for: libcuda

...level capabilities, like microcode/shader specifications, and maybe even how to drive them without the NVidia binary driver blob. It seems the hardware has a lot more possibilities than the current libraries expose, for various reasons. To do this, I'd like to intercept communications between libcuda.so and the /dev/nvidia* devices, and /dev/nvidiactl. Is this what the Noveau developers have been doing already for GL? (I'm new to this) Also, as more people are working on it according to TiNDC #21, can I find the things that are already known somewhere? -- Wladimir Ogre3D Team (http://www...

...g(nvidia-x11-drv-304xx) = 304.135-1.el6.elrepo grubby grubby libGL.so.1()(64bit) libOpenCL.so.1()(64bit) libX11.so.6()(64bit) libXext.so.6()(64bit) libXv.so.1()(64bit) libXvMC.so.1()(64bit) libXvMCNVIDIA_dynamic.so.1()(64bit) libatk-1.0.so.0()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libcuda.so.1()(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libgcc_s.so.1(GCC_3.3)(64bit) libgdk-x11-2.0.so.0()(64bit) libgdk_pixbuf-2.0.so.0()(64bit) libglib-2.0.so.0()(64bit) libgmodule-2.0.so.0()(64bit) libgobject-2.0.so.0()(64bit) libgtk...

https://bugs.freedesktop.org/show_bug.cgi?id=111213 Bug ID: 111213 Summary: VA-API nouveau SIGSEGV and asserts Product: Mesa Version: 19.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

...rubby > libGL.so.1()(64bit) > libOpenCL.so.1()(64bit) > libX11.so.6()(64bit) > libXext.so.6()(64bit) > libXv.so.1()(64bit) > libXvMC.so.1()(64bit) > libXvMCNVIDIA_dynamic.so.1()(64bit) > libatk-1.0.so.0()(64bit) > libc.so.6()(64bit) > libc.so.6(GLIBC_2.2.5)(64bit) > libcuda.so.1()(64bit) > libdl.so.2()(64bit) > libdl.so.2(GLIBC_2.2.5)(64bit) > libgcc_s.so.1()(64bit) > libgcc_s.so.1(GCC_3.0)(64bit) > libgcc_s.so.1(GCC_3.3)(64bit) > libgdk-x11-2.0.so.0()(64bit) > libgdk_pixbuf-2.0.so.0()(64bit) > libglib-2.0.so.0()(64bit) > libgmodule-2.0.so.0...

On Thu, 8 Feb 2018, Felipe Westfields wrote: > I'm on a network that is disconnected from the internet; makes things kind > of awkward sometimes. We have some internal repositories that are supposed > to mirror centos, and EPEL - don't have one (that I'm aware of) that > mirrors elrepo. > But it looks like it's looking for just that one package; if that's all I

Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s

Just wondering what it will take to get the nvidia binary driver working on a pv_ops kernel. It makes it difficult to debug without the source to the nvidia driver, but I think it should be possible to get it to work without changing the binary driver. If the dom0 kernel had access to all the resources that a bare metal kernel did, then it should work right? I''m using Jeremy''s

Hi Tobias, I didn't really get it. Is the idea that the same bitcode is going to be codegen'd for different architectures, or is each sub-module going to contain different bitcode? In the later case you may as well just use multiple modules, perhaps in conjunction with a scheme to store more than one module in the same file on disk as a convenience. Ciao, Duncan. > a couple of weeks

Hi, a couple of weeks ago I discussed with Peter how to improve LLVM's support for heterogeneous computing. One weakness we (and others) have seen is the absence of multi-module support in LLVM. Peter came up with a nice idea how to improve here. I would like to put this idea up for discussion. ## The problem ## LLVM-IR modules can currently only contain code for a single target