Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Ilia Mirkin
Intel (i915) uses the same fbdev emulation layer, so should be largely identical. Just make sure you're using a v4.12+ kernel -- I believe you mentioned that your Intel system was using 4.9, so that's expected to not support overallocation. You might be interested instead in making a kms client

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Michael T. Kloos
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

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Ilia Mirkin
Check fb_pan_display in drivers/video/fbdev/core/fbmem.c for the argument validation of the FBIOPAN_DISPLAY ioctl. CONFIG_FB_NVIDIA is a dedicated fbdev driver, not compatible with nouveau (it takes over the relevant PCI device). It also won't support your Pascal GPU, I believe -- I think it

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Michael T. Kloos
Oops, the FBIOPAN_DISPLAY ioctl error was a stupid mistake on mistake on my part.  Thanks for the info on where the validation code was.  Comparing against that made it easy to find the mistake.  It's working now, well...where I have been able to get over-allocation working!  Thanks for the

[Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Michael T. Kloos
Does NOUVEAU support mmaping a double-sized Framebuffer? When attempting to run, where fd refers to "/dev/fb0": mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); I get back an invalid argument error. This doesn't happen if I only request a single screensize. Is this a

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread michael
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

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Ilia Mirkin
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 wrote: > > I am not familiar with that setting, but I have really struggled to find >

Re: [Nouveau] Framebuffer double buffering (via FBIOPAN_DISPLAY)

2020-07-05 Thread Ilia Mirkin
Are you setting the overallocation to 200? On Sun, Jul 5, 2020 at 3:41 AM Michael T. Kloos wrote: > > Does NOUVEAU support mmaping a double-sized Framebuffer? > When attempting to run, where fd refers to "/dev/fb0": > > mmap(ptr, screensize * 2, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); > > I