Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Apr 2020 09:49:53 +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-T3kHkXROVi@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 #26 from Niclas Zeising <zeising@FreeBSD.org> ---
(In reply to Alexey Dokuchaev from comment #25)

So, something we do wrt. return values from the ioctl() is different from w=
hat
linux does.  Is there any way to check the return value and print/log it
somewhere?  I think you can use xf86DrvMsg for this.  You'll find how they =
work
starting here:
https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/hw/xfree86/common=
/xf86Helper.c#L999

Something like xf86DrvMsg(pScrn->scrnIndex, X_INFO, ...) could work, I gues=
s.=20
The rest of the call is a regular printf() format string I think.

I'm wondering if the call DRM_IOCTL_MODE_CURSOR2 is failing, but before your
patch the code path that sets use_set_cursor2 to false isn't taken.  With y=
our
patch we instead fall back to use DRM_IOCTL_MODE_CURSOR, and that ioctl wor=
ks

Thanks for helping out!

--=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-T3kHkXROVi>