similar to: EVO class header files

On Sat, Dec 13, 2014 at 6:42 PM, Andy Ritger <aritger at nvidia.com> wrote: > On Wed, Dec 10, 2014 at 07:46:16AM +1000, Ben Skeggs wrote: >> On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: >> > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: >> >> Hi, >> > Hey Andy, >> > >>

On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: >> Hi, > Hey Andy, > >> >> The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. >> I've posted an updated DCB spec here: >> >>

Abuse of function pointer was noticed by sparse. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/nv50_evo.c | 18 ++++++++++++------ 1 files changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_evo.c b/drivers/gpu/drm/nouveau/nv50_evo.c index 0f53416..0483cbd 100644 --- a/drivers/gpu/drm/nouveau/nv50_evo.c +++

Since upgrading to linux-next based on 5.9.0-rc1 and 5.9.0-rc2 I have had my mouse pointer disappear soon after logging in, and I have observed the system freezing temporarily when clicking on objects and when typing text. I have also found records of push buffer errors in dmesg output: [ 6625.450394] nouveau 0000:01:00.0: disp: ERROR 1 [PUSHBUFFER_ERR] 02 [] chid 0 mthd 0000 data 00000400 I

On Tue, 25 Aug 2020 at 17:21, Alexander Kapshuk <alexander.kapshuk at gmail.com> wrote: > > Since upgrading to linux-next based on 5.9.0-rc1 and 5.9.0-rc2 I have > had my mouse pointer disappear soon after logging in, and I have > observed the system freezing temporarily when clicking on objects and > when typing text. > I have also found records of push buffer errors in

On Wed, Dec 10, 2014 at 07:46:16AM +1000, Ben Skeggs wrote: > On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: > >> Hi, > > Hey Andy, > > > >> > >> The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. > >>

It is not advisable to perform devinit if it has already been done. VBIOS will very likely have invoked devinit if the GPU is the primary graphics device, but there is no accurate way to detect this fact yet. This patch adds such a method for gf100 and later chips, by means of the NV_PTOP_SCRATCH1_DEVINIT_COMPLETED bit. This bit is set to 1 by devinit, and reset to 0 when the GPU is powered.

From: Ben Skeggs <bskeggs at redhat.com> The kernel previously exposed incorrect classes for some of the chipsets that this code supports. It no longer does, but the older object ioctls have compatibility to avoid breaking userspace. This needs to be fixed before switching over to the newer interfaces. Rather than hardcoding chipset->class like the rest of the driver does, this makes

https://bugs.freedesktop.org/show_bug.cgi?id=99921 Bug ID: 99921 Summary: [NVE4] [regression, bisected] 4.10 (atomic): X shows black screen with cursor after monitors turn off Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority:

Hi, The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. I've posted an updated DCB spec here: ftp://download.nvidia.com/open-gpu-doc/DCB/2/DCB-4.x-Specification.html You can diff it against the previous version: ftp://download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html to see what changed (sorry for having to diff html files). The biggest differences are

https://bugs.freedesktop.org/show_bug.cgi?id=71035 Priority: medium Bug ID: 71035 Assignee: nouveau at lists.freedesktop.org Summary: EVO engine failure, probably (not?) related to EDID corruption QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)

Is this possibly a problem with dovecot 0.99.10.9? Maybe it's been fixed in a later release? Might it be a security issue? Thanks! -------------- next part -------------- An embedded message was scrubbed... From: Not Zed <notzed at ximian.com> Subject: Re: [Evolution] evo confused when searching message bodies on large folders? Date: Fri, 19 Nov 2004 08:11:15 +0800 Size: 3444 URL:

We have used that drive for 2 years with no issues. Amazing how much trouble people can get into when they tweak stuff... -Joe -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 03:01 PM To: centos at centos.org Subject: Re: [CentOS] Samsung evo 840 fixes On 10.11.2015 20.18,

Yeah, I have about 50 of them in raid cards and doing software raid. Never done that. :) No need. We have yet to have one fail in 2 years :) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 06:17 PM To: centos at centos.org Subject: Re: [CentOS] Samsung evo 840 fixes On

On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: > Hi, Hey Andy, > > The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. > I've posted an updated DCB spec here: > > ftp://download.nvidia.com/open-gpu-doc/DCB/2/DCB-4.x-Specification.html > > You can diff it against the previous version: > >

This fix a GPU lockup on 9400M (NVAC) when using acceleration, see #27501. Signed-off-by: Pierre Moreau <pierre.morrow at free.fr> --- drivers/gpu/drm/nouveau/core/engine/disp/nv50.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c b/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c index a7efbff..e425604 100644 ---

nv92 hardware has only 16 interrupt lines, while nv94 and later has 32. Accessing 0xe0c{0,4} registers on nv92 can lead to incorrect PDISP setup. This is a regression introduced with commit 9d0f5ec9ee0fd5dc5fc1cc2cf559286431e406e3 Author: Ben Skeggs <bskeggs at redhat.com> Date: Mon May 12 15:22:42 2014 +1000 gpio: split g92 class from nv50 Reported-by: estece on #nouveau Cc: stable

This fixes kms for 9800M and possibly 9600M Signed-off-by: Maxime COSTE <frrrwww at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_dma.h | 8 ++++++++ drivers/gpu/drm/nouveau/nv50_crtc.c | 5 +++++ drivers/gpu/drm/nouveau/nv50_cursor.c | 2 ++ drivers/gpu/drm/nouveau/nv50_display.c | 2 ++ 4 files changed, 17 insertions(+), 0 deletions(-) diff --git

Hello everyone, I would need testers to check that this patch doesn't break working NVAA/NVAC configurations. It fixes an issue where some NVAC would hang on boot; if similar issues exist on NVAA, it may fix them too. You will find the patch below in two different versions: one will apply on Ben Skeggs' repository, the other one will apply on a regular Linux tree. Thanks in advance,

The commit commit 476e84e126171d809f9c0b5d97137f5055f95ca8 Author: Ben Skeggs <bskeggs at redhat.com> Date: Mon Feb 11 09:24:23 2013 +1000 drm/nv50-/disp: initial supervisor support for off-chip encoders changed the write mask in one of the interrupt functions for on-chip encoders, causing a regression in certain VGA dual-head setups. This commit reintroduces the mask