similar to: [PATCH] nouveau: Allow 3D accelerators with output ports

This patch let's cards with PCI class 0x30200 (3D controller) be operated by the nouveau driver as well. The nv Quadro NVS 450 is one such card, where the first GPU has PCI class 0x30000 and the other GPU has PCI class 0x30200. By ignoring the 1 << 9 bit in the PCI class mask, displays attached to the other GPU can also be used now. Signed-off-by: Marek Vasut <marex at denx.de>

Here are a few patches adding some missing functions in NvPlatformProbe, which iirc is being used as of xserver 1.13 First patch adds a nouveau_kernel_mode_enabled helper, similar to xf86-video-radeon Second and third use the function in Nv{Pci,Platform}Probe And last one ensures we can still use ZaphodHead and relative head positioning via xorg.conf The coding style may be a bit off, despite my

Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com> --- This is mostly just for testing, although it should be safe to apply to nouveau trunk. src/nouveau_dri2.c | 34 +++++++++++ src/nv_driver.c | 163 +++++++++++++++++++++++++++++++++++++++++++++++----- src/nv_type.h | 7 +++ 3 files changed, 191 insertions(+), 13 deletions(-) diff

Hi, this email is basically the result of a small discussion which made me think what the real end-goal of my work on Emerald-2 would be. Since Emerald has already a extensible system (Engines) I thought about giving the engines wider access, so that they are more like plugins. However the first thing needed is a nice plugin API. The base for that is the new settings backend of Emerald-2.

From: Christopher James Halse Rogers <raof at ubuntu.com> Barring some (admittedly significant) missing optimisations? this is reasonably complete, but can't be applied until the Xserver patch has landed, and that needs more work. This demonstrates the approach, however. There's probably some code to be shared with XWayland support, around the output handling (or lack thereof) and

Anybody using hardware SSL accelerators on CentOS? The architecture that I'm looking at is CentOS 4 32 bit and Tomcat, and the motherboards can accept PCI Express cards. But I'm interested in any observations at all, even on different software and hardware versions - what works for you, what to stay away from, etc. -- Florin Andrei http://florin.myip.org/

I was going to say, this reminds me of Kai's presentation at Fosdem yesterday. https://fosdem.org/2018/schedule/event/heterogenousd/ It's always good to see the cross-architecture power of LLVM being used in creative ways! :) cheers, --renato On 5 February 2018 at 13:35, Nicholas Wilson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Interesting. > > I do something

v2: Fix build against Xservers without Wayland support Don't try to acquire/drop drm master under Wayland Refresh for xserver 1.13 kill-all-direct-access-to-xf86Screens Remove #ifdef soup in favour of xwayland compat header Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers at canonical.com> --- configure.ac | 7 ++ src/Makefile.am |

It's dead code, the core handles all this directly now. The only special case is nouveau and tda988x which used one function for both legacy modeset code and -nv50 atomic world instead of 2 vtables. But amounts to exactly the same. v2: Rebase over the panel/brideg refactorings in stm/ltdc. Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Archit Taneja <architt at

It's dead code, the core handles all this directly now. The only special case is nouveau and tda988x which used one function for both legacy modeset code and -nv50 atomic world instead of 2 vtables. But amounts to exactly the same. v2: Rebase over the panel/brideg refactorings in stm/ltdc. Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Archit Taneja <architt at

It's dead code, the core handles all this directly now. The only special case is nouveau and tda988x which used one function for both legacy modeset code and -nv50 atomic world instead of 2 vtables. But amounts to exactly the same. v2: Rebase over the panel/brideg refactorings in stm/ltdc. Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Archit Taneja <architt at

Interesting. I do something similar for D targeting CUDA (via NVPTX) and OpenCL (via my forward proved fork of Khronos’ SPIRV-LLVM)[1], except all the code generation is done at compile time. The runtime is aided by compile time reflection so that calling kernels is done by symbol. What kind of performance difference do you see running code that was not developed with GPU in mind (e.g.

Hi, I compiled drm & xf86-video-nouveau to test nouveau yesterday -- the X server couldn't start. Today, Telek pointed me to drm/linux-core/drm_pciids.h, where I added my card. This made nouveau detect my card, and the xerver started successfully. I didn't test further -- for example I didn't compile the mesa nouveau code to enable 3D. So what should I test ? Snark PS1:

HI LLVM comunity, after 3 years of development, various talks on LLVM-HPC and EuroLLVM and other scientific conferences I want to present my PhD research topic to the lists. The main goal for my research was to develop a single-source programming model equal to CUDA or SYCL for accelerators supported by LLVM (e.g., Nvidia GPUs). PACXX uses Clang as front-end for code generation and comes with

Where are we going? It's time to start thinking ahead and really figure out how to make Compiz survive, specially in lieu of Dennis' suggestion. The reality is that there has been the equivalent of no progress since the merge. We've basically only been in maintenance mode. The reason for this, from my point of view, is a complete lack of direction and leadership. We've

I've downloaded wine 0.9.1 recently, after having used the last pre-.9 CVS drop for about a month or so, but the 0.9 version won't compile on my system. It conks out with an error in the loader subdir (actual data below). The following is the output I get when I run make: ------------------------------------------------------------------------------------- bas@pairadocs