search for: maxwell1

A quick look over the memory reclocking part inside the maxwell mmiotraces kind of reminded me of the kepler memory reclocking, it looks for most parts the same. I didn't do a deep inspection so treat this with great care, but it seems to work at least on those maxwell gpus this was tested on. It depends on the PMU fixes for the fuc5 though, otherwise the PMU might not work as expected and

I begin to find a way that help me investigate fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] errors. See https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/339 I believe this affects mostly Fermi, Kepler and Maxwell1 graphic cards. I'd like first to describe a bit how I proceed, then talk about separating this issue in many. I am working on Gnome Debian Testing. This environment react well (no freeze) when programs or XWayland are killed from the error. I am using drm-misc, from: https://cgit.freedesktop...

...es fixes a lot of Engine reclocking issues found on Fermi, Kepler and all Maxwell generation GPUs. It does _not_ fix memory reclocking on Fermi. It mostly contains of simple fixes or simple patches without affecting current code. As a bonus point, it indeed enables memory and engine reclocking on maxwell1 GPUs (maxwell2 works, too, but it is currently a bit too messy to actually do it, but it works). Have fun. Karol Herbst (20): clk: Fix potential NULL pointer access when there is no fb subdev fb/ramgk104: Touch 0x62c000 only when there is a display engine bios/volt: Handle voltage table ver...