Some Kepler cards have no usefull header in the voltage table, which means
nouveau has to read the voltages out of the entries directly.
This patch fixes volting issues on those cards enabling them to switch cstates
---
drm/nouveau/nvkm/subdev/bios/volt.c | 3 +++
1 file changed, 3 insertions(+)
To support boosting, vbios' seems to have fasters cstate than the actual base
clock.
We should definitly drop all those with a higher voltage than the max voltage
stated in the vbios.
This fixes reclocking issues mostly on high-end kepler cards where the highest
cstates goes way beyond the max
this series solves different issues we encounter on kepler cards while
reclocking:
1. core clock doesn't change at all and produces a volting error (patch 1)
this can happen when the voltage table has only 0ed values in the header
so we have to parse the entries itself, which
---
drm/nouveau/include/nvkm/subdev/bios/baseclock.h | 23 +++
drm/nouveau/nvkm/subdev/bios/Kbuild | 1 +
drm/nouveau/nvkm/subdev/bios/baseclock.c | 79
3 files changed, 103 insertions(+)
create mode 100644
0: disable boosting (use fixed clocks from PM_Mode table)
1: boost only to base clock from the vbios (default)
2: boost only to boost clock from the vbios
3: boost to max clock available (still limited by gpu and boost voltage)
---
drm/nouveau/include/nvkm/subdev/clk.h | 10 +-
---
drm/nouveau/include/nvkm/subdev/bios/vmap.h | 1 +
drm/nouveau/include/nvkm/subdev/volt.h | 2 ++
drm/nouveau/nvkm/subdev/bios/vmap.c | 5 -
drm/nouveau/nvkm/subdev/volt/base.c | 8
4 files changed, 15 insertions(+), 1 deletion(-)
diff --git
On 01-12-15, Samuel Pitoiset wrote:
>>> Ok, here is a MMT trace of vectorAdd:
>>>
>>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz
>>
>> Hi Hans,
>>
>> Thanks a lot.
>
> Well, I didn't know but Martin has a GK208...
> I just tested the compute support on his card and ... it works
On 02.12.2015 09:55, Daniel Vetter wrote:
> On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote:
>> On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner
>> wrote:
>>> When we are at it, the one with the title "[PATCH] drm/nouveau: Use
>>> drm_vblank_on/off consistently" from
---
drm/nouveau/nvkm/subdev/clk/base.c | 16
1 file changed, 16 insertions(+)
diff --git a/drm/nouveau/nvkm/subdev/clk/base.c
b/drm/nouveau/nvkm/subdev/clk/base.c
index 43abca7..7cb9dd8 100644
--- a/drm/nouveau/nvkm/subdev/clk/base.c
+++ b/drm/nouveau/nvkm/subdev/clk/base.c
@@
On Wed, Dec 2, 2015 at 1:33 PM, Samuel Pitoiset
wrote:
>
>
> On 12/02/2015 04:34 PM, Hans de Goede wrote:
>>
>> On 01-12-15, Samuel Pitoiset wrote:
>>
>> >>> Ok, here is a MMT trace of vectorAdd:
>> >>>
>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz
>>
https://bugs.freedesktop.org/show_bug.cgi?id=93197
--- Comment #2 from Marcin Slusarz ---
Temporary workaround:
./warsow +set r_multithreading 0
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92307
--- Comment #19 from Stefan Huehner ---
No compositor just old fvwm2 as window manager. For this quick test i did
either just startx or via lightdm.
Note: was just quick test using blob for now and not nouveau mainly on that
https://bugs.freedesktop.org/show_bug.cgi?id=92307
--- Comment #18 from poma ---
Stefan, what DE/compositor are you running?
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing
On 12/02/2015 04:34 PM, Hans de Goede wrote:
On 01-12-15, Samuel Pitoiset wrote:
>>> Ok, here is a MMT trace of vectorAdd:
>>>
>>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz
>>
>> Hi Hans,
>>
>> Thanks a lot.
>
> Well, I didn't know but Martin has a GK208...
> I just
https://bugs.freedesktop.org/show_bug.cgi?id=92307
--- Comment #20 from poma ---
nouveau & fvwm-2.6.5-10.fc23.x86_64,
except ever-present warnings, no problemos for both - S3 RESUME and xrandr.
--
You are receiving this mail because:
You are the assignee for the
On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote:
> On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner
> wrote:
> > When we are at it, the one with the title "[PATCH] drm/nouveau: Use
> > drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested
> >
https://bugs.freedesktop.org/show_bug.cgi?id=71659
--- Comment #31 from Viorel-Cătălin Răpițeanu ---
Created attachment 120290
--> https://bugs.freedesktop.org/attachment.cgi?id=120290=edit
dmesg log after the freeze occured.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=93201
--- Comment #6 from Marcos Souza ---
(In reply to Chris Wilson from comment #5)
> I'm going to assume the DRICloseScreen in the middle of the stack is just
> the unwinder getting confused and so this looks like a
https://bugs.freedesktop.org/show_bug.cgi?id=93201
Chris Wilson changed:
What|Removed |Added
Component|Driver/intel|Driver/nouveau
On 2 December 2015 at 12:21, Karol Herbst wrote:
>> Pierre Moreau hat am 2. Dezember 2015 um 02:34
>> geschrieben:
>>
>> Hi,
>>
>> On 05:42 PM - Dec 01 2015, Karol Herbst wrote:
>> > this is just a nice thing to know and there is no harm in printing
https://bugs.freedesktop.org/show_bug.cgi?id=92307
--- Comment #16 from poma ---
Tested kernels:
4.4.0-0.rc3.git0.1.fc24.x86_64+debug
&
4.4.0-0.rc3.git0.1.fc24.x86_64+debug with updated nouveau from
http://cgit.freedesktop.org/~darktama/nouveau - up to commit 115ed46
> Pierre Moreau hat am 2. Dezember 2015 um 02:34
> geschrieben:
>
> Hi,
>
> On 05:42 PM - Dec 01 2015, Karol Herbst wrote:
> > this is just a nice thing to know and there is no harm in printing them
> > ---
> > drm/nouveau/nvkm/subdev/clk/base.c | 16
> >
> Pierre Moreau hat am 2. Dezember 2015 um 02:26
> geschrieben:
>
> Hi Karol,
>
> I have some comments below.
>
> On 05:42 PM - Dec 01 2015, Karol Herbst wrote:
> > 0: disable boosting (cap to base clock from the vbios)
> > 1: boost only to boost clock from the vbios
> >
On 2 December 2015 at 12:24, Karol Herbst wrote:
>> Pierre Moreau hat am 2. Dezember 2015 um 02:26
>> geschrieben:
>> You only listed values 0, 1, 2 in the commit message, so what is -1 for?
>> Disabling nvboost is already taken care by 0, so it's
https://bugs.freedesktop.org/show_bug.cgi?id=92307
--- Comment #17 from poma ---
However with the xrandr routine:
xrandr --output DVI-I-1 --off ; xrandr --auto
is still problematic,
the mouse cursor is visible and motile, but the rest of the screen is as
blanked.
25 matches
Mail list logo