[Bug 203201] New: [mgag200] Unable to do mmap call on mgadrmfb device - Returns -EINVAL
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Apr 9 15:11:56 UTC 2019
https://bugzilla.kernel.org/show_bug.cgi?id=203201
Bug ID: 203201
Summary: [mgag200] Unable to do mmap call on mgadrmfb device -
Returns -EINVAL
Product: Drivers
Version: 2.5
Kernel Version: 4.4 LTS
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri at kernel-bugs.osdl.org
Reporter: olivier at bonhomme.io
Regression: No
Hello dear kernel maintainers,
I'm trying to map memory on the frame buffer device fb0 provided by the mgag200
driver. However, that mmap call always returns -EINVAL code while the same
mmmap call works with other drivers (uvesafb for example).
After some investigations, I discovered that a patch which resolves that
problem has been produced by SuSe guys. The patch is available here :
https://lists.freedesktop.org/archives/dri-devel/2017-July/147650.html
I tested that patch on my 4.4.150 kernel and it resolved the problem.
I checked in the GIT kernel tree and it seems that this patch hasn't been
included in 4.4 branch nor in the current kernel branch while the same kind of
patch has been done for ast driver
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/ast?h=linux-4.4.y&id=28fb4cb7fa6f63dc2fbdb5f2564dcbead8e3eee0)
It would be nice if that patch for mgag200 would be imported in the kernel
source tree.
Thanks
Regards,
Olivier Bonhomme
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list