search for: drm_fbdev_overalloc

Well...it's been a bit of a mixed bag.? Setting drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to 2160 as opposed to 1080 (My monitor vertical resolution)? This fixed the mmap() problem.? However, it only worked on my main workstation.? My laptop running Intel graphics wasn't affected by the change in kernel cmdline.? My workstation is a custom build fr...

<div dir='auto'>I am not familiar with that setting, but I have really struggled to find documentation on dealing with the framebuffer. Referring to this guide, "http://betteros.org/tut/graphics1.php#doublebuffer", I attempted to set the mmap allocation size to double, but it caused the mmap to fail. I no longer believe that it is a driver issue, though, because I just

...; 5f15257689bfa, which is included in v4.12 and later kernels. > > Hope this helps, > > -ilia > > On Sun, Jul 5, 2020 at 7:02 PM Michael T. Kloos > <michael at michaelkloos.com> wrote: >> Well...it's been a bit of a mixed bag. Setting >> drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to >> 2160 as opposed to 1080 (My monitor vertical resolution) This fixed the >> mmap() problem. However, it only worked on my main workstation. My >> laptop running Intel graphics wasn't affected by the change in kernel >> cmdline. My...

...ded to this emulation layer in commit 5f15257689bfa, which is included in v4.12 and later kernels. Hope this helps, -ilia On Sun, Jul 5, 2020 at 7:02 PM Michael T. Kloos <michael at michaelkloos.com> wrote: > > Well...it's been a bit of a mixed bag. Setting > drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to > 2160 as opposed to 1080 (My monitor vertical resolution) This fixed the > mmap() problem. However, it only worked on my main workstation. My > laptop running Intel graphics wasn't affected by the change in kernel > cmdline. My workstation is a...

Try booting with drm_kms_helper.drm_fbdev_overalloc=200 and see if it works with that. (There's also CONFIG_DRM_FBDEV_OVERALLOC which sets the default.) Cheers, -ilia On Sun, Jul 5, 2020 at 3:41 PM <michael at michaelkloos.com> wrote: > > I am not familiar with that setting, but I have really struggled to find documentation on d...

...ACKDEPOT @@ -56,7 +55,6 @@ config DRM_DEBUG_SELFTEST select PRIME_NUMBERS select DRM_LIB_RANDOM select DRM_KMS_HELPER - default n help This option provides kernel modules that can be used to run various selftests on parts of the DRM api. This option is not @@ -113,7 +111,6 @@ config DRM_FBDEV_OVERALLOC config DRM_FBDEV_LEAK_PHYS_SMEM bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)" depends on DRM_FBDEV_EMULATION && EXPERT - default n help In order to keep user-space compatibility, we want in certain use-cases to keep leaking the fbdev physica...

...BUG_SELFTEST > select PRIME_NUMBERS > select DRM_LIB_RANDOM > select DRM_KMS_HELPER > - default n > help > This option provides kernel modules that can be used to run > various selftests on parts of the DRM api. This option is not > @@ -113,7 +111,6 @@ config DRM_FBDEV_OVERALLOC > config DRM_FBDEV_LEAK_PHYS_SMEM > bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)" > depends on DRM_FBDEV_EMULATION && EXPERT > - default n > help > In order to keep user-space compatibility, we want in certain > use-case...