search for: drm_fbdev_generic_shadow_setup

...bochs to use the shadow fb. >> >> The patch set has been tested on ast and mga200 HW. >> > > I've been thinking, this enables dirty tracking in DRM userspace for > these drivers since the dirty callback is now set on all framebuffers. > Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a > flag enabling the shadow buffer instead? Fbdev emulation is special wrt framebuffer setup and there's no way to distinguish a regular FB from the fbdev's FB. I've been trying drm_fbdev_generic_shadow_setup(), but ended up duplicating functionality. The problem was th...

...bochs to use the shadow fb. >> >> The patch set has been tested on ast and mga200 HW. >> > > I've been thinking, this enables dirty tracking in DRM userspace for > these drivers since the dirty callback is now set on all framebuffers. > Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a > flag enabling the shadow buffer instead? Fbdev emulation is special wrt framebuffer setup and there's no way to distinguish a regular FB from the fbdev's FB. I've been trying drm_fbdev_generic_shadow_setup(), but ended up duplicating functionality. The problem was th...

...>>> >>> The patch set has been tested on ast and mga200 HW. >>> >> >> I've been thinking, this enables dirty tracking in DRM userspace for >> these drivers since the dirty callback is now set on all framebuffers. >> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >> flag enabling the shadow buffer instead? > > Fbdev emulation is special wrt framebuffer setup and there's no way to > distinguish a regular FB from the fbdev's FB. I've been trying > drm_fbdev_generic_shadow_setup(), but ended up duplicating > func...

...t;> The patch set has been tested on ast and mga200 HW. >>>> >>> >>> I've been thinking, this enables dirty tracking in DRM userspace for >>> these drivers since the dirty callback is now set on all framebuffers. >>> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >>> flag enabling the shadow buffer instead? >> >> Fbdev emulation is special wrt framebuffer setup and there's no way to >> distinguish a regular FB from the fbdev's FB. I've been trying >> drm_fbdev_generic_shadow_setup(), but ended up du...

...t;> The patch set has been tested on ast and mga200 HW. >>>> >>> >>> I've been thinking, this enables dirty tracking in DRM userspace for >>> these drivers since the dirty callback is now set on all framebuffers. >>> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >>> flag enabling the shadow buffer instead? >> >> Fbdev emulation is special wrt framebuffer setup and there's no way to >> distinguish a regular FB from the fbdev's FB. I've been trying >> drm_fbdev_generic_shadow_setup(), but ended up du...

...has been tested on ast and mga200 HW. >>>>> >>>> >>>> I've been thinking, this enables dirty tracking in DRM userspace for >>>> these drivers since the dirty callback is now set on all framebuffers. >>>> Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a >>>> flag enabling the shadow buffer instead? >>> >>> Fbdev emulation is special wrt framebuffer setup and there's no way to >>> distinguish a regular FB from the fbdev's FB. I've been trying >>> drm_fbdev_generic_shadow_setu...

...s this bug > by converting bochs to use the shadow fb. > > The patch set has been tested on ast and mga200 HW. > I've been thinking, this enables dirty tracking in DRM userspace for these drivers since the dirty callback is now set on all framebuffers. Is this OK? Should we add a drm_fbdev_generic_shadow_setup() that sets a flag enabling the shadow buffer instead? Really nice diffstat by the way :-) Noralf. > [1] https://lists.freedesktop.org/archives/dri-devel/2019-June/224423.html > > Thomas Zimmermann (5): > drm/client: Support unmapping of DRM client buffers > drm/fb-helper: Un...

DRM client buffers are permanently mapped throughout their lifetime. This prevents us from using generic framebuffer emulation for devices with small dedicated video memory, such as ast or mgag200. With fb buffers permanently mapped, such devices often won't have enougth space left to display other content (e.g., X11). This patch set introduces unmappable DRM client buffers for framebuffer

DRM client buffers are permanently mapped throughout their lifetime. This prevents us from using generic framebuffer emulation for devices with small dedicated video memory, such as ast or mgag200. With fb buffers permanently mapped, such devices often won't have enougth space left to display other content (e.g., X11). This patch set introduces unmappable DRM client buffers for framebuffer