search for: ddx

Ben, Looks like the reality is that glamor is just not hooked up properly in the nouveau DDX. Mainly it's missing DRI2, which in turn means no core GL contexts, and probably lots of other issues. While this could probably be fixed somehow, I doubt there's any advantage to using the nouveau DDX over something like modesetting nowadays. How would you feel about dropping glamor suppo...

On Tue, Jul 7, 2015 at 5:05 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 8 July 2015 at 06:06, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> Ben, >> >> Looks like the reality is that glamor is just not hooked up properly >> in the nouveau DDX. Mainly it's missing DRI2, which in turn means no >> core GL contexts, and probably lots of other issues. While this could >> probably be fixed somehow, I doubt there's any advantage to using the >> nouveau DDX over something like modesetting nowadays. >> >> Ho...

Video and input drivers Subgroups and projects on gitlab does not list modesetting DDX, presumably because it's not packaged separately from the server. Where's the right place to report a modesetting DDX bug that manifests only on an NVidia GPU? Directly against the server https://gitlab.freedesktop.org/xorg/xserver? Here are some particulars: How can I tell whether this sh...

...; low-mem cards. > Ah that is interesting, so this can workaround the problem on my nv25 that cannot render too big pictures in firefox. (my test case is a single picture : 3782x2592 resized to 550x368) So about that, I must mention the different behavior I got, in chronological order : 1) old ddx (10/01) : X instant crash 2) newer ddx, after all the "handle reloc failures" patches : picture is not displayed, just a black area instead. *much* better :) 3) after upgrading kernel/drm from 12/08 - 2.6.32-rc6 to 12/11 - 2.6.32 : X locks up. I don't even see the usual message in dme...

On Fri, Feb 28, 2020 at 11:06 AM Felix Miata <mrmazda at earthlink.net> wrote: > Video and input drivers Subgroups and projects on gitlab does not list modesetting > DDX, presumably because it's not packaged separately from the server. Where's the > right place to report a modesetting DDX bug that manifests only on an NVidia GPU? > Directly against the server https://gitlab.freedesktop.org/xorg/xserver? I don't know if anyone (from nouveau) looks...

Hi, all I'm trying to implement kms for pre-nv50 in last cuples of days. My current work[1] is based on the code of nv50 kms & ddx. Basicly, I just blindly port the code to kernel land :). I think I'm getting very close to working state, but it still doesn't work. Current state: 1) vbios parser is synced with ddx 2) i2c works 3) Something shows on internel LVDS panel and external DVI flat panel, but the image is dis...

Hi, uevent support was added to the nouveau DDX in a recent commit. A test is made in configure.ac for libudev being present but there is no minimum version. I have had problems with this as I am using Fedora 11 which has udev-141 in it. This version does not support all of the functions required by the DDX and will crash Xorg. At least this...

https://bugs.freedesktop.org/show_bug.cgi?id=106294 Bug ID: 106294 Summary: GM204/modesetting DDX: Odd corruption (red backgrounds) introduced by Mesa Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/...

http://bugs.freedesktop.org/show_bug.cgi?id=15861 Summary: Account Request For Nouveau DDX Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: jb17bs...

Two "updated" patches, according to Michel Daenzers review. See separate e-mail for details. 01/10: Replaces original 01/09 -- Same code, updated commit message. 10/10: Just for demonstration, not for application to ddx.

...used for certain chipsets. >> I will take some time this week to see how this is coded and if its >> possible but i just wanted a head sup opinion on you guys before i start >> wasting my time. >> > I'm not entirely sure if you're talking about the kernel module, ddx > (xf86-video-nouveau) or mesa. > > In either case, all three should be relatively easy to do, as normally > the generation specific code is divided. Not too sure if it's worth the > effort though > > * kernel module - 1.7 MiB, ~400KiB gzip > * ddx - ~200KiB > * mesa...

https://bugs.freedesktop.org/show_bug.cgi?id=101191 Bug ID: 101191 Summary: [NVC3] Vsync stops working after mode changes in nouveau DDX Product: xorg Version: 7.7 (2012.06) Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org...

...> I will take some time this week to see how this is coded and if its >>>> possible but i just wanted a head sup opinion on you guys before i start >>>> wasting my time. >>>> >>> I'm not entirely sure if you're talking about the kernel module, ddx >>> (xf86-video-nouveau) or mesa. >>> >>> In either case, all three should be relatively easy to do, as normally >>> the generation specific code is divided. Not too sure if it's worth the >>> effort though >>> >>> * kernel module -...

With this patch the DDX almost works with GK20A, the missing piece is adding COHERENT mappings to the right places. ;-) If you specify NOUVEAU_BO_APER the kernel will truncate valid_domains to the domains specified at creation time. This means that as long as we only specify the correct domain in nouveau_allocate_surface...

...t;, >>>> but that seems to also automatically disable all DRI, leading to >>>> software rendering. >>>> >>>> I discussed this with Ben this morning and he suggested that this >>>> is likely a Mesa issue since with DRI3 mesa rather then the ddx >>>> allocs the surfaces. I've tried disabling swizzling in the >>>> mesa code by forcing nv30_miptree_create() to always take >>>> the code path for linear textures, but that leads to the exact >>>> same result as before that change. >>>...

...hat i only lightly "test" it via regular desktop use, so >> maybe that's were problems remain? > > Adam is the one who actually understands it... I was just asking > questions and the answer was "that's broken". A user was using DRI3 > with EXA (nouveau DDX), and was seeing render fail in the form of > stale things on the screen. The nouveau DDX does a lot of "implicit" > sync stuff... it just emits commands into a pushbuf without kicking > it. However the libdrm code has cleverness to kick out any pushbufs if > you do a nouveau_...

Hi, thank you very much for your reply. I will explain my use case in more detail. First thing is to note that it worked with nvidia (apart from this annoying system freeze which happened roughly every three months). > First off, you're not using the nouveau ddx, you're using the > modesetting ddx. This isn't a problem in itself, but if you're going > to report bugs, you should file them against the proper component. oh, wow. I don't know what is ddx or modesetting ddx. Google tells me that it is related to intel drivers? But I have...

Hi all, the following patch fixes a race-condition in the nouveau ddx which caused frequent x-server crashes for at least 1 user under some loads when OpenGL triple-buffering is enabled, which it is by default on XOrg 1.12 and later. As a side effect, it provides a small optimization for the common case of bufferswap at next vblank. The other way to avoid the race...

...] >> Cannot find any crtc or sizes - going 1024x768 I don't think I've seen this before. The odd thing about the TK1 (and TX1, I believe), is that the GK20A device doesn't have any display capabilities - those are left up to tegra. Sounds like you're trying to use the nouveau ddx as the primary, which fails as there are no CRTC's. I believe Gnurou's xserver hacks rely on you using glamor (and thus the modesetting xorg ddx). Is that what you're using? Can you provide an xorg log? Cheers, -ilia

https://bugs.freedesktop.org/show_bug.cgi?id=99464 Bug ID: 99464 Summary: openmw - Segfault with the nouveau ddx + DRI3 Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org...