029cd092f2
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. This also gets rid of casting needed due to not using the correct data type. Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230428122452.4856-3-tzimmermann@suse.de |
||
---|---|---|
.. | ||
arm-charlcd.c | ||
cfag12864b.c | ||
cfag12864bfb.c | ||
charlcd.c | ||
charlcd.h | ||
hd44780_common.c | ||
hd44780_common.h | ||
hd44780.c | ||
ht16k33.c | ||
img-ascii-lcd.c | ||
Kconfig | ||
ks0108.c | ||
lcd2s.c | ||
line-display.c | ||
line-display.h | ||
Makefile | ||
panel.c |