search for: msaa

On Mon, Sep 7, 2015 at 3:50 PM, Hans de Goede <hdegoede at redhat.com> wrote: > msaa use on nv30 may trigger a (mesa?) bug where dmesg says: > [ 1197.850642] nouveau E[soffice.bin[3785]] fail ttm_validate > [ 1197.850648] nouveau E[soffice.bin[3785]] validating bo list > [ 1197.850654] nouveau E[soffice.bin[3785]] validate: -12 > [ 1201.766955] nouveau E[soffice.bin...

On Thu, Sep 3, 2015 at 7:25 AM, Hans de Goede <hdegoede at redhat.com> wrote: > On nv3x we will likely end up using the cpu to do color resolving for msaa > blits. Disable msaa on these cards so that we do not end up using the cpu. Actually the CPU fallback won't do scaled, so it's stuck with SIFM or assert(false). Which isn't great, but... it's what the HW does. I don't see a reason to shut that off. I'd rather disallow a...

We do not have a generic blitter on nv3x cards, so we must use the sifm object for color resolving. This commit divides the sources and dest surfaces in to tiles which match the constraints of the sifm object, so that color resolving will work properly on nv3x cards. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- Changes in v2: -Use 1024x1024 blocks -Use the sifm on both nv3x

On Tue, May 18, 2010 at 7:04 PM, Roland Scheidegger <sroland at vmware.com> wrote: > Hi, > > I plan to merge the gallium-msaa branch to master soon. > It's actually a bit of a misnomer since the conceptually more important > changes in there are about blits... > > Here's a short summary what this is about: > blits now operate on resources, not surfaces (surface_copy/fill -> > resource_copy/fil...

The sifm object has a limit of 1024x1024 for its input size and 2048x2048 for its output. The code checking this was trying to be clever resulting in it seeing a surface of e.g 1024x256 being outside of the input size limit. This commit fixes this. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_transfer.c | 4 ++-- 1 file changed, 2

...urce->format) && >> !util_format_is_pure_integer(info.src.resource->format)) { >> debug_printf("nv30: color resolve unimplemented\n"); >> return; >> } >> >> Perhaps there's (supposed to be) some magic with the MSAA visual? Do >> you see that print happening? > > > Yes I see that print happening and that explains the misrendering I'm > seeing pretty well, it is not misrendering at all, it is just random > data from the video mem. > > I've had a quick talk about this with Ben,...

Hi All, Here is a bunch of fixes for nv30 cards, the first patch is a resend of a patch I send a while back. AFAICT that one is ready for merging, but it is not entirely clear to me what the process is for getting (nouveau) mesa patches merged. Should I request commit rights, and push my own patches once they have been reviewed ? Regards, Hans

...51 at earthlink.net> >Sent: Oct 12, 2010 7:43 AM >To: Seth Shelnutt <shelnutt2 at gmail.com> >Subject: Re: Accessibility in wine > >Seth Shelnutt <shelnutt2 at gmail.com> wrote: >> >>I can't seem to find much info on this. What is wine's support for MSAA (Microsoft Active Accessibility) or >>the newer UIAutomation? I see that there is the oleacc dll which is the main >>dll for MSAA. According to the API site, is seems there are still 10 stubs. >>Looking at the source code there hasn't been any updates in over a year. We >&g...

...mt->ms_y = 0; > break; > default: > mt->ms_mode = 0x00000000; > mt->ms_x = 0; > mt->ms_y = 0; > break; > } > > So it seems that glretrace is doing a normal rendering which works, > where as ooimpress is doing a 4 way msaa rendering which does not work. > > Interestingly enough nv30_screen_get_param returns 0 for > PIPE_CAP_TEXTURE_MULTISAMPLE and for PIPE_CAP_SAMPLER_VIEW_TARGET > > And this hack: > > --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c > +++ b/src/gallium/drivers/nouveau/nv3...

...t: Split buffer allocation to a separate file Lauri Kasanen (1): intel: Fix build failure in test_decode.c Marek Ol??k (6): radeon: simplify ZS buffer checking on r600 radeon: optimize allocation for depth w/o stencil and stencil w/o depth on EG radeon: force 2D tiling for MSAA surfaces radeon: tweak TILE_SPLIT for MSAA surfaces tests/modetest: fix distcheck configure: bump version for 2.4.38 release Paulo Zanoni (1): intel: add more Haswell PCI IDs Rob Clark (5): omap: clarify dmabuf file descriptor ownership omap: add API to import...

Dave Airlie (1): radeon: add prime import/export support Kenneth Graunke (1): intel: Use VG_CLEAR on the context destroy ioctl as well. Marek Ol??k (3): radeon: fix allocation of MSAA surfaces on r600-r700 radeon: align r600 msaa buffers to a multiple of macrotile size * num samples configure: bump version for 2.4.39 release Tobias Klausmann (1): tests/modetest: Add a forgotten return, needed for opensuse buildservice V?ctor Manuel J?quez Leal (1): omap...

https://bugs.freedesktop.org/show_bug.cgi?id=97568 Bug ID: 97568 Summary: read pixels of MSAAx8 surface stretched horizontally/vertically Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/n...

On Fri, Aug 28, 2015 at 4:54 AM, Hans de Goede <hdegoede at redhat.com> wrote: > Hi, > > On 27-08-15 20:19, Ilia Mirkin wrote: >> >> On Thu, Aug 27, 2015 at 1:59 PM, Alex Deucher <alexdeucher at gmail.com> >> wrote: > > > <snip> > >>>>>> 2) Since the glretrace does work outside of libreoffice impress, I

...vc4: Update kernel headers for getparam addition. Bump version to 2.4.69 for release. Jan Vesely (1): xf86drm.c: Fix mix of tabs and spaces Leo Liu (1): tests/amdgpu: add interface to adapt firmware requirement Marek Olšák (1): radeon: use SAMPLE_SPLIT=2 for better MSAA perf on EG/CM Mike Frysinger (1): pull in sys/sysmacros.h when available Nicolai Hähnle (1): xf86drm: ensure proper alignment of pointers in drmProcessPciDevice Qiang Yu (1): drm: fix multi GPU drmGetDevices only return one device Rob Clark (1): freedreno/msm: fix memory...

...; > return NULL; > } > > + screen = CALLOC_STRUCT(nv30_screen); > + if (!screen) > + return NULL; > + > + pscreen = &screen->base.base; > + pscreen->destroy = nv30_screen_destroy; > + > /* > * Some modern apps try to use msaa without keeping in mind the > * restrictions on videomem of older cards. Resulting in dmesg saying: > @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) > if (screen->max_sample_count > 4) > screen->max_sample_count = 4; > > - pscreen = &...

...LOC_STRUCT(nv30_screen); >>> + if (!screen) >>> + return NULL; >>> + >>> + pscreen = &screen->base.base; >>> + pscreen->destroy = nv30_screen_destroy; >>> + >>> /* >>> * Some modern apps try to use msaa without keeping in mind the >>> * restrictions on videomem of older cards. Resulting in dmesg saying: >>> @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) >>> if (screen->max_sample_count > 4) >>> screen->max_sample_coun...

https://bugs.freedesktop.org/show_bug.cgi?id=96391 Bug ID: 96391 Summary: Payday: The Heist has rendering issues when anti-aliasing enabled Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

...for 0x%02x\n", dev->chipset); - FREE(screen); return NULL; } + screen = CALLOC_STRUCT(nv30_screen); + if (!screen) + return NULL; + + pscreen = &screen->base.base; + pscreen->destroy = nv30_screen_destroy; + /* * Some modern apps try to use msaa without keeping in mind the * restrictions on videomem of older cards. Resulting in dmesg saying: @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) if (screen->max_sample_count > 4) screen->max_sample_count = 4; - pscreen = &screen->base.base; -...

...t;> >> + screen = CALLOC_STRUCT(nv30_screen); >> + if (!screen) >> + return NULL; >> + >> + pscreen = &screen->base.base; >> + pscreen->destroy = nv30_screen_destroy; >> + >> /* >> * Some modern apps try to use msaa without keeping in mind the >> * restrictions on videomem of older cards. Resulting in dmesg saying: >> @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) >> if (screen->max_sample_count > 4) >> screen->max_sample_count = 4; >>...

https://bugs.freedesktop.org/show_bug.cgi?id=98609 Bug ID: 98609 Summary: Firefox right click corrupted with DRI3 Product: Mesa Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at