Hi Am 25.04.23 um 18:35 schrieb Javier Martinez Canillas:
Thomas Zimmermann <tzimmerm...@suse.de> writes:Use info->screen_buffer when reading and writing framebuffers in system memory. It's the correct pointer for this address space.Maybe can expand the explanation a little bit with something like this? "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. Since the fb_sys_{read,write}() functions operate on the latter address space, it is wrong to use .screen_base and .screen_buffer must be used instead. This also get rids of all the casting needed due not using the correct data type."
Thanks. I'll add this text as-is in the next iteration. Best regards Thomas
Signed-off-by: Thomas Zimmermann <tzimmerm...@suse.de> ---Reviewed-by: Javier Martinez Canillas <javi...@redhat.com>
-- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman HRB 36809 (AG Nuernberg)
OpenPGP_signature
Description: OpenPGP digital signature
