similar to: [PATCH] More explicit error message when the kernel module has been configured 'noaccel' but the xorg configuration doesn't disable accelleration

Based on the original patch by Christoph Bumiller, but since it depends on kernel support patched I cannot push it yet. The changes are that I enable vblank by default, and offset takes OFFSET_HIGH/LOW instead of something relative to notifier_bo. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/man/nouveau.man b/man/nouveau.man index 7c72907..8765569

Straight port of Matthias Hopf's KMS backlight code for xf86-video-intel, with reformatting and a couple of minor cleanups. Works fine on my MacBookAir2,1. Signed-off-by: Daniel Stone <daniel at fooishbar.org> --- src/drmmode_display.c | 269 ++++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed, 268 insertions(+), 1 deletions(-) diff --git a/src/drmmode_display.c

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 |

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

From: Dave Airlie <airlied at redhat.com> This is preperation for the backlight support code. Signed-off-by: Dave Airlie <airlied at redhat.com> --- src/drmmode_display.c | 54 ++++++++++++++++++++++++++++++++------------------- 1 file changed, 34 insertions(+), 20 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 6033a6d..ad7bc1f 100644 ---

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

--- src/drmmode_display.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/drmmode_display.c b/src/drmmode_display.c index 803785d..4d2d09d 100644 --- a/src/drmmode_display.c +++ b/src/drmmode_display.c @@ -357,7 +357,7 @@ drmmode_set_mode_major(xf86CrtcPtr crtc, DisplayModePtr mode, if (ret) { xf86DrvMsg(crtc->scrn->scrnIndex, X_ERROR, - "failed

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Untested. I don't have the hardware. src/nv_driver.c | 2 ++ src/nvc0_accel.c | 10 +++++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index fff83f8..61940a8 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -390,6 +390,7 @@ NVHasKMS(struct pci_device *pci_dev,

This requires at least a quick test. :-) Acked-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> On 10/16/2016 09:14 PM, Ilia Mirkin wrote: > Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> > --- > > Untested. I don't have the hardware. > > src/nv_driver.c | 2 ++ > src/nvc0_accel.c | 10 +++++++++- > 2 files changed, 11 insertions(+), 1

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/nv_driver.c | 2 ++ src/nvc0_accel.c | 10 +++++++++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index fff83f8..61940a8 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -390,6 +390,7 @@ NVHasKMS(struct pci_device *pci_dev, struct xf86_platform_device *platform_dev)

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- v1 -> v2: add 0x130 as a valid chip type early on in detection src/nouveau_copy.c | 2 ++ src/nouveau_exa.c | 1 + src/nv_accel_common.c | 1 + src/nv_driver.c | 4 ++++ src/nv_type.h | 1 + src/nvc0_accel.c | 6 ++++++ 6 files changed, 15 insertions(+) diff --git a/src/nouveau_copy.c

Exit with proper message instead of crashing when user forgot to uninstall the proprietary driver. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- src/nv_driver.c | 35 +++++++++++++++++++++++++++++++++++ 1 files changed, 35 insertions(+), 0 deletions(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index f60b6d9..2c953da 100644 --- a/src/nv_driver.c +++

This has two purposes : - cleaner code - reduce the diff between nv30 and nv40 exa for a possible nvfx_exa merge ? The main differences seem to be that nv30 uses rect texture format (and does not support repeat on that). Then there are some minor changes in TX_FORMAT RT_FORMAT and TEX_FILTER usage. And NVAccelInitNVx0TCL look complete different. Tested with: ./rendercheck -t

Hi, is there anyone here who succeed to run any 3D software at good speed with such 3D hardware ? On my side, 3D accelleration is ok with Xorg and pure linux game (xmoto for example run really fine). Is there anything to do with Wine to allow programs runs under it to work as "native" Linux software ? Have I miss something somewhere ? (I think of wine compilation and especially

Hi! I've written a small amount of code that gets the randr 1.2 branch much closer to working for me on a laptop. Most of the changes are fairly obvious, but a couple of comments: 1) The changes to nv_crtc.c are clearly bogus, but I'm not sure what on earth these registers do. I need to set them to get a moderately sane-looking picture 2) The fp registers poked in nv_output.c

This largely copies the code from modesetting with minor adjustments. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I've tried privately to get people to test this out, but to no avail. I don't have the hardware to verify this one way or the other. Ideally with this patch you should be (a) able to use a tiled monitor at 60hz with DP-MST and (b) be able to see connectors

That would be great, as long as it does only that and does not go into the "drivername" territory. As the said driver ;-) "A driver name to use can be provided instead of simple boolean value, which will be passed to the GL implementation for it to load the appropriate backend." -Emil On 4 July 2015 at 18:17, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > IMO

X-Server versions older than 1.16.3 have bugs in their DRI3/Present implementation which impair nouveau, so it is better to stick to good old DRI2 by default on such servers. E.g., page flipping doesn't work at all under DRI3/Present with older servers, and use of extensions like OML_sync_control, SGI_video_sync or INTEL_swap_events also causes failure of Present. nouveau's glamor accel

This largely copies the code from modesetting with minor adjustments. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I've tested this back and forth with a GTX 960 + 2x U2415 monitors, chained to each other. I turned them on/off. I messed with their DP 1.1/1.2 settings. I pulled plugs a few times. This seems to pass the test. No crashes, the connectors seem to come and go

The DRI option with the intel ddx can be used to indicate the following - whether dri is disabled - the dri "version" - dri1, dri2, dri3 - the dri module name - doo_dri.so bar_dri.so I'm not sure how exactly it's supposed to work/works, and I believe most of that is due to legacy reasons. I'm just saying let's not do the whole thing - just the dri "version"