similar to: [PATCH AUTOSEL 4.4 048/174] drm/nouveau/bios/ramcfg: fix missing parentheses when calculating RON

From: Colin Ian King <colin.king at canonical.com> Currently, the expression for calculating RON is always going to result in zero no matter the value of ram->mr[1] because the ! operator has higher precedence than the shift >> operator. I believe the missing parentheses around the expression before appying the ! operator will result in the desired result. [ Note, not tested ]

From: Colin Ian King <colin.king at canonical.com> [ Upstream commit 13649101a25c53c87f4ab98a076dfe61f3636ab1 ] Currently, the expression for calculating RON is always going to result in zero no matter the value of ram->mr[1] because the ! operator has higher precedence than the shift >> operator. I believe the missing parentheses around the expression before appying the !

From: Colin Ian King <colin.king at canonical.com> [ Upstream commit 13649101a25c53c87f4ab98a076dfe61f3636ab1 ] Currently, the expression for calculating RON is always going to result in zero no matter the value of ram->mr[1] because the ! operator has higher precedence than the shift >> operator. I believe the missing parentheses around the expression before appying the !

From: Colin Ian King <colin.king at canonical.com> [ Upstream commit 13649101a25c53c87f4ab98a076dfe61f3636ab1 ] Currently, the expression for calculating RON is always going to result in zero no matter the value of ram->mr[1] because the ! operator has higher precedence than the shift >> operator. I believe the missing parentheses around the expression before appying the !

Signed-off-by: Roy Spliet <rspliet at eclipso.eu> --- drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/ramcfg.h | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/bios/rammap.c | 3 ++- drivers/gpu/drm/nouveau/nvkm/subdev/bios/timing.c | 2 ++ drivers/gpu/drm/nouveau/nvkm/subdev/fb/gddr3.c | 6 ++++-- 4 files changed, 9 insertions(+), 3 deletions(-) diff --git

Hi, Static Analysis with CoverityScan as detected an issue with the setting of the RON pull value in function nvkm_gddr3_calc in drm/nouveau/bios/ramcfg.c This was introduced by commit: c25bf7b6155cb ("drm/nouveau/bios/ramcfg: Separate out RON pull value") CoverityScan reports the issue as follows: 84 case 0x20: 85 CWL = (ram->next->bios.timing[1] &

Adds reclocking for NVA0, and a whole lot of work for other cards. Had these patches collecting dust for a little, but tested them with both my NVA0, and Martin's a while back. Success not guaranteed, but should be quite a leap forward. Happy reviewing and testing. Cheers, Roy

In correspondence with the other ram_calc implementations. Signed-off-by: Roy Spliet <nouveau at spliet.org> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c | 37 ++++++++++++----------- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c b/drivers/gpu/drm/nouveau/nvkm/subdev/fb/ramgf100.c index 093223d..fffd01a 100644 ---

https://bugs.freedesktop.org/show_bug.cgi?id=91523 Bug ID: 91523 Summary: [NVE7] driver cannot initialize gpu(failed to parse ramcfg data) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium

Signed-off-by: Roy Spliet <rspliet at eclipso.eu> --- drivers/gpu/drm/nouveau/Makefile | 1 + drivers/gpu/drm/nouveau/core/subdev/fb/gddr3.c | 117 +++++++++++++++++++++++++ drivers/gpu/drm/nouveau/core/subdev/fb/priv.h | 1 + 3 files changed, 119 insertions(+) create mode 100644 drivers/gpu/drm/nouveau/core/subdev/fb/gddr3.c diff --git

In bulletpoints: - Add some support for G94 and G96 reclocking. Has been tested on literally two cards, which is hardly adequate as "full coverage". On the other hand, the changes were small enough to make me confident this might work for others as well. - Fix NV50 wait for VBLANK when no monitor is plugged in. - Voltage related inprovements for GT21x. - Slightly improve Keplers

Following a series of patches that implement memory reclocking for NVA3/5/8 with DDR2, DDR3 and GDDR3 on board. I tested these patches on 6 different graphics cards, but I expect reclocking now to work on many more. Testers can pick up these patches and test it by enabling pstate (nouveau.pstate=1). They should then be able to change clocks by writing to /sys/class/drm/card0/device/pstate. Correct

https://bugs.freedesktop.org/show_bug.cgi?id=89273 Bug ID: 89273 Summary: [NVA8] nouveau screen corruption and X lockup when reclocking Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

hello nouveau devs! I have two nvidia cards lying around that are no longer in use: * Nvidia GeForce GTS250 E-Green, 512MB GDDR3 (NV92/G92 - NV50 family) * Nvidia GeForce 6600, 256MB (NV43 - NV40 family) They both are already well supported by the nouveau driver as far as I can tell. But if any dev can make use of them, please let me know, I would gladly donate them. Patrick

hello im new here i want to swich to Ubuntu 9.04 my pc is: Code: 2 gb dual ram 800 mhz intel e1600 @2.40 ghz 2.40 ghz 9600 GT 512 mb gddr3 256 bit hdd sata drive i play some games on Windows Vista but id like to know how some games would work.. when i had 7300gt 256mb ddr3 i had some lag in "last chaos" but only when i was surounded by a lot of monsters these are the list of games

https://bugs.freedesktop.org/show_bug.cgi?id=97505 Bug ID: 97505 Summary: X11 does not detect nouveau when using the linux kernel EFI Loader (GRUB loader works fine) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium

Hello Everyone, I am currently having a problem with dual display while running a windows game in full screen which I believe might be a Wine issue. First my system specs: ATI Radeon HD 4850 GDDR3 993MHz 512MB <- according to Catalyst Control Center Intel Dual Core E2160 Gigabyte Motherboard Ubuntu 10.04 LTS w/Kernel 2.6.32-22-generic-pae The problem I am having is when I load up a game

Hi folks - Hoping someone might be able to help steer me. I’ve installed CentOS 7 to an older MacbookPro with Nvidia graphics. X11 fails to come up. I believe the Nouveau driver is bombing... ‘dmesg | grep nouv’: [ 2.473768] nouveau 0000:01:00.0: enabling device (0002 -> 0003) [ 2.473869] nouveau 0000:01:00.0: NVIDIA G84 (084700a2) [ 2.473907] nouveau 0000:01:00.0: irq 31 for

Please keep me in the CC. I am not subscribed to this list. When booting 4.4.0 on one of my systems, when nouveau loads, the screen goes into powersave. It doesn't appear to register the fb0 device. When X starts up, the screen comes back and I'm able to login. When launching anything that accesses 3D, the screen freezes. Nothing is logged in either X or dmesg. This same system works

Hello, I'm willing to donate hardware, see the IRC log below for a few details. If you are interested, reply to "christoph at alte-pflasterei.de", I'll send an Open Document Spreadsheet then with the complete card list containing all details I know. -8<---- IRC chat log --------------------------------- (2019-09-04 16:50:54) chf: Hi, is any of the developers interested in