search for: nv30_miptree_from_handl

...39;s all in a >>> line. That means that it expected some locality and instead it got >>> drawn all on a line. If it were merely a stride problem, I'd expect to >>> see strips of the moon below and offset from one another. >>> >>> So... take a look at nv30_miptree_from_handle -- I wonder if it can >>> now receive swizzled textures where it couldn't before. >> >> >> Ok, that does go in the direction I am expecting the problem to be, >> but I'm afraid I'm going to need a bit more guidance, what exactly >> am I looking fo...

...at the white pattern of the moon -- it's all in a > line. That means that it expected some locality and instead it got > drawn all on a line. If it were merely a stride problem, I'd expect to > see strips of the moon below and offset from one another. > > So... take a look at nv30_miptree_from_handle -- I wonder if it can > now receive swizzled textures where it couldn't before. Ok, that does go in the direction I am expecting the problem to be, but I'm afraid I'm going to need a bit more guidance, what exactly am I looking for in that function / which "knobs" should...

On Thu, Aug 27, 2015 at 1:59 PM, Alex Deucher <alexdeucher at gmail.com> wrote: > On Thu, Aug 27, 2015 at 1:55 PM, Hans de Goede <hdegoede at redhat.com> wrote: >> Hi, >> >> On 27-08-15 15:46, Marek Olšák wrote: >>> >>> On Thu, Aug 27, 2015 at 3:09 PM, Hans de Goede <hdegoede at redhat.com> >>> wrote: >>>>

...reoffice and > mesa use the system llvm, so there should be no problems with them > expecting different llvm versions. > > I've done some further debugging adding some debug printf-s to the > texture creation paths for nv3x, this bit is interesting, glretrace > does: > > nv30_miptree_from_handle 1350x863 uniform_pitch 6144 usage 0 flags 0 > nv30_miptree_create 1350x863 uniform_pitch 5440 usage 0 flags 0 bind 1 > target 2 > > So it gets a texture from a handle, which I believe is the child-window > in which the animation will be shown, and then create another texture > wi...

Hi, On 30-07-15 16:09, Ilia Mirkin wrote: > FWIW this is a fail on nv50+ as well. See for example > https://bugs.freedesktop.org/show_bug.cgi?id=91445 > > My suspicion is that this is due to the lack of PUSH_KICK in the *Done > exa handlers -- works fine with DRI2, but DRI3 has no synchronization > and so the commands never get flushed out. Easily verified by sticking >

...uld be no problems with them >>> expecting different llvm versions. >>> >>> I've done some further debugging adding some debug printf-s to the >>> texture creation paths for nv3x, this bit is interesting, glretrace >>> does: >>> >>> nv30_miptree_from_handle 1350x863 uniform_pitch 6144 usage 0 flags 0 >>> nv30_miptree_create 1350x863 uniform_pitch 5440 usage 0 flags 0 bind 1 >>> target 2 >>> >>> So it gets a texture from a handle, which I believe is the child-window >>> in which the animation will be shown,...

https://bugs.freedesktop.org/show_bug.cgi?id=90871 Bug ID: 90871 Summary: NV30: Xfwm4 use_compositing - garbled display Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee: