DRM's fbdev console uses regular load and store operations to update framebuffer memory. The bochs driver on sparc64 requires the use of I/O-specific load and store operations. We have a workaround, but need a long-term sulotion tothe problem. This patchset adds a GEM object function that returns framebuffers as I/O memory. It further updates fbdev to use the new functionality and implements vmap_iomem for VRAM helpers. This is an RFC patchset to discuss the approach. It still needs testing and polish. Patch #4 has to be rebased onto the recent workaround. Thomas Zimmermann (5): fbdev: Remove trailing whitespace fbdev/core: Export framebuffer read and write code as cfb_ function drm: Add infrastructure for vmap operations of I/O memory drm/fb_helper: Use I/O-memory mappings if available drm/vram_helper: Implement struct drm_gem_object_funcs.vmap_iomem drivers/gpu/drm/ast/ast_cursor.c | 12 ++- drivers/gpu/drm/drm_client.c | 52 +++++++++- drivers/gpu/drm/drm_fb_helper.c | 132 ++++++++++++++++++++++---- drivers/gpu/drm/drm_gem.c | 19 ++++ drivers/gpu/drm/drm_gem_vram_helper.c | 106 +++++++++++++++++++-- drivers/gpu/drm/drm_internal.h | 1 + drivers/video/fbdev/core/fbmem.c | 61 ++++++++---- include/drm/drm_client.h | 8 +- include/drm/drm_gem.h | 17 +++- include/drm/drm_gem_vram_helper.h | 1 + include/linux/fb.h | 23 +++-- 11 files changed, 369 insertions(+), 63 deletions(-) -- 2.27.0 _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
