search for: mcp7x

...et a little further with this issue. Cheers, and >> happy holidays! > Thanks Roy, > > NVIDIA told me that it applied to these boards, but, I can't see NVIDIA > attempting the workaround in your trace, so until there's evidence to > the contrary, I've disabled it for MCP7x for now. > > Ben. Thanks. Since your patch is the exact modification I made to verify the workaround was bugging me, consider it: Tested-by: Roy Spliet <nouveau at spliet.org> Given "no display on HDMI since 4.8" is quite a serious regression (albeit for a small userbase),...

I've observed this regression on my NVAC board; a 1920x1080 TV on HDMI (single monitor set-up) gets no signal with Fedora kernels from 4.8. Trace sent to the mmio dumps mailbox. A brief scan already revealed that register 0xe840 is never touched, so it appears that NVIDIA does something different. VBIOS for this board is in the usual place. Commenting out 0xac from the workaround seems to

Hello Alex, Op 19-11-14 om 06:41 schreef Alexandre Courbot: > Use the newly-introduced NV_VRAM_DOMAIN() macro to support alternative > VRAM domains for chips that do not use dedicated video memory. Should we construct a similar patch for NVAA/NVAC (MCP7x) as well? > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > src/gallium/drivers/nouveau/nouveau_buffer.c | 6 ++---- > src/gallium/drivers/nouveau/nv50/nv50_miptree.c | 4 ++-- > src/gallium/drivers/nouveau/nvc0/nvc0_compute.c...

Attached patch fixes an issue reported by Pierre Moreau, that prevents reclocking of GT21x and MCP7x from working after "the big rewrite". Please review and push forward for kernel 4.3. Thanks! Roy

...> I hope that helps you get a little further with this issue. Cheers, and > happy holidays! Thanks Roy, NVIDIA told me that it applied to these boards, but, I can't see NVIDIA attempting the workaround in your trace, so until there's evidence to the contrary, I've disabled it for MCP7x for now. Ben. > > Roy. > > Op 22-11-16 om 15:04 schreef poma: >> On 20.10.2016 00:46, Ben Skeggs wrote: >> [...] >>> I'd like to see a mmiotrace of the NVIDIA binary driver on a system >>> where this WAR breaks things. I applied it to all the GPUs...

This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of