From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, daniel@ffwll.ch, sam@ravnborg.org,
kraxel@redhat.com, b.zolnierkie@samsung.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
jani.nikula@intel.com, peda@axentia.se, dan.carpenter@oracle.com,
natechancellor@gmail.com
Cc: linux-fbdev@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [RFC][PATCH 0/5] Support GEM object mappings from I/O memory
Date: Wed, 29 Jul 2020 15:41:43 +0200 [thread overview]
Message-ID: <20200729134148.6855-1-tzimmermann@suse.de> (raw)
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@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-07-29 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 13:41 Thomas Zimmermann [this message]
2020-07-29 13:41 ` [PATCH 1/5] fbdev: Remove trailing whitespace Thomas Zimmermann
2020-07-29 13:47 ` daniel
2020-07-29 13:41 ` [PATCH 2/5] fbdev/core: Export framebuffer read and write code as cfb_ function Thomas Zimmermann
2020-07-29 13:53 ` daniel
2020-07-29 16:36 ` Sam Ravnborg
2020-07-31 9:20 ` daniel
2020-08-02 20:01 ` Sam Ravnborg
2020-08-03 6:46 ` Thomas Zimmermann
2020-08-04 9:27 ` daniel
2020-08-04 9:41 ` Thomas Zimmermann
2020-07-29 13:41 ` [PATCH 3/5] drm: Add infrastructure for vmap operations of I/O memory Thomas Zimmermann
2020-07-29 13:57 ` daniel
2020-07-30 8:14 ` Thomas Zimmermann
2020-07-31 9:22 ` daniel
2020-07-29 13:41 ` [PATCH 4/5] drm/fb_helper: Use I/O-memory mappings if available Thomas Zimmermann
2020-07-29 13:41 ` [PATCH 5/5] drm/vram_helper: Implement struct drm_gem_object_funcs.vmap_iomem Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200729134148.6855-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=natechancellor@gmail.com \
--cc=peda@axentia.se \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).