similar to: [EXA] Updated wfb'ish patches

Add NV96 in NV9X_GRCLASS8297_CHIPSETS bitmask and remove the test blocking NV9x (another test is already present above) --- src/gallium/drivers/nv50/nv50_screen.c | 8 +------- 1 files changed, 1 insertions(+), 7 deletions(-) diff --git a/src/gallium/drivers/nv50/nv50_screen.c b/src/gallium/drivers/nv50/nv50_screen.c index 9bf5e8c..4130ede 100644 --- a/src/gallium/drivers/nv50/nv50_screen.c

Not much has changed, except that i've test run these patches for a few weeks now. I'm actually surprised i've avoided Out-Of-Memory issues. Patch 2 remains a temporary hack, awaiting a structural fix by darktama. The whole thing works fine, but XSHM is an issue (http://stillunknown.livejournal.com/928.html). With it disabled most apps are fine, although a few issues remain. As

https://bugs.freedesktop.org/show_bug.cgi?id=33977 Summary: X core font rendering is "laggy" Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

- Only for sufficiently new xserver's and exa_driver_pixmaps. --- src/nouveau_exa.c | 217 +++++++++++++++++++++++++++++++++++++++++++++++++++-- src/nv_driver.c | 51 +++++++++++-- src/nv_proto.h | 4 + src/nv_type.h | 12 +++- 4 files changed, 267 insertions(+), 17 deletions(-) diff --git a/src/nouveau_exa.c b/src/nouveau_exa.c index 93fc3c5..074a226 100644 ---

Fixes warning with xserver 1.20 and gcc 8.2: nv_driver.c:1443:9: warning: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Wimplicit-function-declaration] ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX, ^~~~~~~~~~~~~ fbScreenInit (See xserver 706e6d9cd074da606016ed4ecff51e9c2a822087) Signed-off-by: Rhys Kidd <rhyskidd at

http://bugs.freedesktop.org/show_bug.cgi?id=22253 Summary: KMS Nouveau - wfb crash Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=61731 Priority: medium Bug ID: 61731 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau not working on second monitor QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: rvhbox-freedesktop at

Webrat 0.4.2 doesn''t seem to allow you to click links by title. Am I missing something stupid? With steps below running in sequence, first passes, second fails Then /^I should see a view (\w+) details link$/ do |object| response.should have_tag("a[title=#{object}_details]") end When /^I follow view (\w+) details link$/ do |object| click_link "#{object}_details}"

A short series of compiler visibility warning fixes that I prepared whilst trialing improvements to xf86-video-nouveau's use of the core xorg-server utility macros. Rhys Kidd (4): wfb: Remove declaration for undefined function nouveau_wfb_init() dri2: Mark local create/destroy buffer and copy region functions as static xv: Mark local NVSetupTexturedVideo function as static

- map should handle this. --- src/nouveau_exa.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/nouveau_exa.c b/src/nouveau_exa.c index b656ca7..20ad380 100644 --- a/src/nouveau_exa.c +++ b/src/nouveau_exa.c @@ -259,7 +259,7 @@ nouveau_exa_mark_sync(ScreenPtr pScreen) static void nouveau_exa_wait_marker(ScreenPtr pScreen, int marker) { -

http://bugs.freedesktop.org/show_bug.cgi?id=20144 Summary: 2D images broken on nv28 (EXA failure?) Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

http://bugs.freedesktop.org/show_bug.cgi?id=22828 Summary: Nouveau EXA bug Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: d.okias at

http://bugs.freedesktop.org/show_bug.cgi?id=22905 Summary: EXA - image corruption Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

This patch will only work with Option "EXAPixmaps" "1", and will prevent classic exa from working. Occasionally a pixmap fails to map, but that's not related to this patch. I haven't done any hardcore optimisations, but suggestions are ofcource appreciated. In my experience some benchmarks suck now (gtkperf for which had it's performance halved), and qt4 is

Signed-off-by: Xavier Chantry <chantry.xavier at gmail.com> --- src/nv10_exa.c | 35 +++++++++++++++++++---------------- 1 files changed, 19 insertions(+), 16 deletions(-) diff --git a/src/nv10_exa.c b/src/nv10_exa.c index 1acb583..23a68e3 100644 --- a/src/nv10_exa.c +++ b/src/nv10_exa.c @@ -34,30 +34,33 @@ static struct pict_format { int exa; int hw; } nv10_tex_format_pot[] = { - {

On 02/11/15 08:28, poma wrote: > An interesting results. > > DRI2: > > $ vblank_mode=0 glxgears > ATTENTION: default value of option vblank_mode overridden by environment. > 6321 frames in 5.0 seconds = 1264.103 FPS > 6380 frames in 5.0 seconds = 1275.943 FPS > 6369 frames in 5.0 seconds = 1273.629 FPS > 6377 frames in 5.0 seconds = 1275.322 FPS > 6387 frames in

http://bugs.freedesktop.org/show_bug.cgi?id=27288 Summary: EXA corruption on small pixmaps Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

I've been doing some testing and it seems that glyphs (typically smaller than a page size on nv50) render slow'ish sometimes, mostly due to the many trips to the kernel (drm_addmap_core is the symbol that shows up). Ofcource this was a benchmark, but it does leave me wondering, do we really need need to call the kernel for every little pixmap? Also from a memory point of view, because a

From: Marcin Slusarz <marcin.slusarz at gmail.com> after this change nouveau passes all fill and blend tests of rendercheck (before: fill - 108/120, blend - 3323868/3569150) tested on NV34 Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- src/nv04_exa.c | 19 +++++++++---------- src/nv_accel_common.c | 5 ++++- 2 files changed, 13 insertions(+), 11

On Mon, Jun 12, 2017 at 5:46 PM, Samuel Pitoiset <samuel.pitoiset at gmail.com> wrote: > > > On 06/10/2017 09:14 AM, Aaryaman Vasishta wrote: >> >> See the 'wt' on the first fmul in exacanv110.fp, exacmnv110.fp and >> exasanv110.fp. Any ideas on what could be causing the first fmul to require >> $r0 and/or $r1? > > > 'tex nodep $r4 $r2