On Thu, Aug 10, 2023 at 10:15 PM Dave Airlie wrote:
> From: Dave Airlie
>
> With the new uapi we don't have the comp flags on the allocation,
> so we shouldn't be using the first size that works, we should be
> iterating until we get the correct one.
>
> This reduces allocations from 2MB to 64k
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 6.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 4.19-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
drm/nouveau/gr: enable memory loads on helper invocation on all channels
to the 6.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
6.4.9 built with unconn.c from 6.4.6 builds and boots and runs fine.
Thanks everybody.
Dear all,
On Fri, 4 Aug 2023 at 14:15, Karol Herbst wrote:
62aecf23f3d1 drm/nouveau: add nv_encoder pointer check for NULL
fb725beca62d drm/nouveau/dp: check for NULL nv_connector->native_mode
90748be0f4f3 drm/nouveau: don't detect DSM for non-NVIDIA device
5a144bad3e75 nouveau: fix client
Remove duplicated include of chid.h. Resolves checkincludes message.
Signed-off-by: GUO Zihua
---
drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c
b/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chan.c
Use vmemdup_user() rather than duplicating its implementation.
This patch fixes the following Coccinelle warning:
./drivers/gpu/drm/nouveau/nouveau_gem.c:630:7-15: WARNING opportunity for
vmemdup_user
Signed-off-by: Atul Raut
---
drivers/gpu/drm/nouveau/nouveau_gem.c | 9 ++---
1 file
On Sat, 5 Aug 2023 at 01:09, Karol Herbst wrote:
Mind checking if instead of reverting the entire commit that this is
enough to fix it as well?
https://gitlab.freedesktop.org/karolherbst/nouveau/-/commit/f99ae069876f7ffeb6368da0381485e8c3adda43.patch
This patch does fix the problem as well:
On 09/08/23 00:44, Ruan Jinjie wrote:
> The NULL initialization of the pointers assigned by
> kunit_kzalloc() first is not necessary, because if kunit_kzalloc()
> failed, the pointers will be assigned NULL, otherwise it works
> as usual. so remove it.
>
> Signed-off-by: Ruan Jinjie
> ---
>
On Fri, 4 Aug 2023 at 14:15, Karol Herbst wrote:
mind retrying with only fb725beca62d and 62aecf23f3d1 reverted?
I will do this later this day (takes some time, it is a slow machine).
Would be weird if the other two commits are causing it. If that's the
case, it's a bit worrying that
This commit provides the implementation for the new uapi motivated by the
Vulkan API. It allows user mode drivers (UMDs) to:
1) Initialize a GPU virtual address (VA) space via the new
DRM_IOCTL_NOUVEAU_VM_INIT ioctl for UMDs to specify the portion of VA
space managed by the kernel and
On 8/8/2023 8:44 PM, Ruan Jinjie wrote:
The NULL initialization of the pointers assigned by kzalloc() first is
not necessary, because if the kzalloc() failed, the pointers will be
assigned NULL, otherwise it works as usual. so remove it.
Signed-off-by: Ruan Jinjie
---
On Fri, 4 Aug 2023 at 14:51, Karol Herbst wrote:
How are you building the kernel? Because normally from git reverting
one of those shouldn't take long, because it doesn't recompile the
entire kernel. But yeah, you can potentially just revert one of one
for now and it should be fine.
I am
Dear Maintainers,
Hereby I would like to report an apparent bug in the nouveau driver in
linux/6.1.38-2.
Running a current debian stable on a Dell Latitude E6510 with a
"NVIDIA Corporation GT218M" graphic card, the monitor turns black
after the grub screen. Also switching to a console
This patch fixes the following sparse error:
drivers/gpu/drm/nouveau/dispnv50/disp.c:134:31: error: subtraction of different
types can't work (different address spaces)
drivers/gpu/drm/nouveau/dispnv50/disp.c:197:31: error: subtraction of different
types can't work (different address spaces)
On Friday, 4 August 2023 15:11:46 CEST Olaf Skibbe wrote:
> (On the occasion a maybe silly question: am I right assuming that the
> kernel has to be build on the machine we want to reproduce the bug on?
> Otherwise it could use much faster hardware (running also bookworm).)
If that is also an
20 matches
Mail list logo
