search for: mga200

Displaying 12 results from an estimated 12 matches for "mga200".

Did you mean: mgag200
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...om these drivers. For >> bochs, a problem was reported where the driver could not display the console >> because it was pinned in system memory. [1] The patch set fixes 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? F...
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...om these drivers. For >> bochs, a problem was reported where the driver could not display the console >> because it was pinned in system memory. [1] The patch set fixes 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? F...
2019 Jul 03
0
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...framebuffer code from these drivers. For > bochs, a problem was reported where the driver could not display the console > because it was pinned in system memory. [1] The patch set fixes 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 w...
2019 Jul 04
0
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...was reported where the driver could not display the console >>>>> because it was pinned in system memory. [1] The patch set fixes 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() t...
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...ochs, a problem was reported where the driver could not display the console >>>> because it was pinned in system memory. [1] The patch set fixes 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 >>&...
2019 Jul 04
2
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...ochs, a problem was reported where the driver could not display the console >>>> because it was pinned in system memory. [1] The patch set fixes 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 >>&...
2019 Jul 04
0
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...r >>> bochs, a problem was reported where the driver could not display the console >>> because it was pinned in system memory. [1] The patch set fixes 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 sh...
2019 Jul 03
11
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...emoves a large amount of framebuffer code from these drivers. For bochs, a problem was reported where the driver could not display the console because it was pinned in system memory. [1] The patch set fixes this bug by converting bochs to use the shadow fb. The patch set has been tested on ast and mga200 HW. [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: Unmap BO for shadow-buffered framebuffer console drm/ast: Replace struct ast_fbdev with generic framebuffer emulation dr...
2019 Jul 03
11
[PATCH 0/5] Unmappable DRM client buffers for fbdev emulation
...emoves a large amount of framebuffer code from these drivers. For bochs, a problem was reported where the driver could not display the console because it was pinned in system memory. [1] The patch set fixes this bug by converting bochs to use the shadow fb. The patch set has been tested on ast and mga200 HW. [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: Unmap BO for shadow-buffered framebuffer console drm/ast: Replace struct ast_fbdev with generic framebuffer emulation dr...
2019 Jul 05
11
[PATCH v2 0/6] Unmappable DRM client buffers for fbdev emulation
...emoves a large amount of framebuffer code from these drivers. For bochs, a problem was reported where the driver could not display the console because it was pinned in system memory. [1] The patch set fixes this bug by converting bochs to use the shadow fb. The patch set has been tested on ast and mga200 HW. [1] https://lists.freedesktop.org/archives/dri-devel/2019-June/224423.html Thomas Zimmermann (6): drm/client: Support unmapping of DRM client buffers drm/fb-helper: Map DRM client buffer only when required drm/fb-helper: Instanciate shadow FB if configured in device's mode_confi...
2019 Jul 05
11
[PATCH v2 0/6] Unmappable DRM client buffers for fbdev emulation
...emoves a large amount of framebuffer code from these drivers. For bochs, a problem was reported where the driver could not display the console because it was pinned in system memory. [1] The patch set fixes this bug by converting bochs to use the shadow fb. The patch set has been tested on ast and mga200 HW. [1] https://lists.freedesktop.org/archives/dri-devel/2019-June/224423.html Thomas Zimmermann (6): drm/client: Support unmapping of DRM client buffers drm/fb-helper: Map DRM client buffer only when required drm/fb-helper: Instanciate shadow FB if configured in device's mode_confi...
2012 Dec 12
43
[PATCH 00/37] [RFC] revamped modeset locking
Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted