Date: Sat, 19 Feb 2022 15:07:03 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 262043] update of drm-*kmod breaks AMD GPU support Message-ID: <bug-262043-7141-42ElFpscpB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262043-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-262043-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262043 --- Comment #2 from Stefan E=C3=9Fer <se@FreeBSD.org> --- Yes, I know that you suspected the bitbang code and I do agree that this is= the most likely cause. I do have the hardware and I'm offering my support to get this resolved, be= fore the --current version is advanced to the level of the -devel version. But I have no idea where to start, whether in the kernel, THE LINUXKPI LAYE= R, the DRM driver, or the AMDGPU driver. I'd guess the best approach is to add trace messages or to actually trace execution (as far as possible for a kernel driver that affect the frame buf= fer) in order to identify the exact point of failure. But as I said, I have no idea where to start ... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262043-7141-42ElFpscpB>