Commit 254a4fda authored by Thomas Zimmermann's avatar Thomas Zimmermann

fbdev/xen-fbfront: Use struct fb_info.screen_buffer

Use info->screen_buffer when reading and writing framebuffers in
system memory. It's the correct pointer for this address space.

The struct fb_info has a union to store the framebuffer memory. This can
either be info->screen_base if the framebuffer is stored in I/O memory,
or info->screen_buffer if the framebuffer is stored in system memory.

As the driver operates on the latter address space, it is wrong to use
.screen_base and .screen_buffer must be used instead.
Signed-off-by: default avatarThomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230428122452.4856-14-tzimmermann@suse.de
parent 5a2c399d
...@@ -429,7 +429,7 @@ static int xenfb_probe(struct xenbus_device *dev, ...@@ -429,7 +429,7 @@ static int xenfb_probe(struct xenbus_device *dev,
fb_info->pseudo_palette = fb_info->par; fb_info->pseudo_palette = fb_info->par;
fb_info->par = info; fb_info->par = info;
fb_info->screen_base = info->fb; fb_info->screen_buffer = info->fb;
fb_info->fbops = &xenfb_fb_ops; fb_info->fbops = &xenfb_fb_ops;
fb_info->var.xres_virtual = fb_info->var.xres = video[KPARAM_WIDTH]; fb_info->var.xres_virtual = fb_info->var.xres = video[KPARAM_WIDTH];
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment