Date: Tue, 14 Apr 2020 10:26:56 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 237642] x11-drivers/xf86-video-ati: Upgrade from 18.1.0 to 19.0.0 results in invisible mouse pointer Message-ID: <bug-237642-7141-PTfjk99dZI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237642-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-237642-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=3D237642 --- Comment #31 from Alexey Dokuchaev <danfe@FreeBSD.org> --- > I'm also curious if this is a problem only with drm-legacy-kmod, > or also with drm-kmod. I've tried building graphics/drm-fbsd11.2-kmod on my 13-CURRENT, which is b= ased on Linux 4.11 code and thus should suck less than 4.16 one, but that was wishful thinking. There were some error messages on the console before the screen went blank and machine locked up, I'd have to see if this contribute= s to the problem. > I wonder if drmIoctl() in libdrm needs to be rewritten on FreeBSD, > to return errno or -errno rather than the return value of the actual > ioctl() call. No. drmIoctl() should follow ioctl() semantics and return -1 while passing= the error code in errno. Introducing DRM_IOCTL() was kind of ugly, but breaking drmIoctl() would be even worse. The previous code was correct; when Michel D=C3=A4nzer decided to bypass ex= isting API and call drmIoctl() directly, he should have updated the code to check = for error condition properly instead of comparing return value with what would = be in the errno. --=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-237642-7141-PTfjk99dZI>