| Message ID | 20190703083302.2609-5-tzimmermann@suse.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Unmappable DRM client buffers for fbdev emulation | expand |
Den 03.07.2019 10.33, skrev Thomas Zimmermann: > The bochs driver (and virtual hardware) requires buffer objects to > reside in video ram to display them to the screen. So it can not > display the framebuffer console because the respective buffer object > is permanently pinned in system memory. > > Using a shadow buffer for the console solves this problem. The console > emulation will pin the buffer object only during updates from the shadow > buffer. Otherwise, the bochs driver can freely relocated the buffer > between system memory and video ram. > > Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> > --- Acked-by: Noralf Trønnes <noralf@tronnes.org>
diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c index bc19dbd531ef..47fab4852483 100644 --- a/drivers/gpu/drm/bochs/bochs_kms.c +++ b/drivers/gpu/drm/bochs/bochs_kms.c @@ -172,7 +172,7 @@ bochs_gem_fb_create(struct drm_device *dev, struct drm_file *file, mode_cmd->pixel_format != DRM_FORMAT_BGRX8888) return ERR_PTR(-EINVAL); - return drm_gem_fb_create(dev, file, mode_cmd); + return drm_gem_fb_create_with_dirty(dev, file, mode_cmd); } const struct drm_mode_config_funcs bochs_mode_funcs = {
The bochs driver (and virtual hardware) requires buffer objects to reside in video ram to display them to the screen. So it can not display the framebuffer console because the respective buffer object is permanently pinned in system memory. Using a shadow buffer for the console solves this problem. The console emulation will pin the buffer object only during updates from the shadow buffer. Otherwise, the bochs driver can freely relocated the buffer between system memory and video ram. Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> --- drivers/gpu/drm/bochs/bochs_kms.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)