diff options
| author | Linmao Li <lilinmao@kylinos.cn> | 2026-08-27 17:39:48 +0800 |
|---|---|---|
| committer | Helge Deller <deller@gmx.de> | 2026-09-10 22:36:31 +0200 |
| commit | 3934185ba63feca6e80cc8b90f7d7f01cde78223 (patch) | |
| tree | 3623f96cf5555517e6919c1c77952fadb1be6914 /scripts/Makefile.thinlto | |
| parent | 3fb13d29cf8eb4502837bff06b2873c5435f6ffd (diff) | |
| download | linux-stable-3934185ba63feca6e80cc8b90f7d7f01cde78223.tar.gz linux-stable-3934185ba63feca6e80cc8b90f7d7f01cde78223.zip | |
fbdev: atafb: Restrict SuperBlitter to supported formats
The SuperBlitter operations derive an integer byte count per pixel. The
accelerated fill path handles only one-, two- and four-byte pixels.
However, the operations are currently installed for every external
framebuffer in SuperVidel RAM, including planar 1/2/4/8-bpp and 24-bpp
truecolor modes accepted by the external video parser.
For 1/2/4-bpp modes, the byte count becomes zero, so accelerated copies do
nothing and fills fall through to 32-bit stores. Planar 8-bpp uses an
incompatible memory layout. For 24-bpp modes, fills also use 32-bit stores
despite advancing addresses by three bytes per pixel. These cases can
corrupt the framebuffer beyond the requested rectangle.
Enable the SuperBlitter operations only for the layouts they implement:
8-bpp packed pixels and 16/32-bpp truecolor. Keep the existing software
operations for all other external formats.
Fixes: d463633d63e6 ("fbdev: atafb: Add support for SuperVidel's SuperBlitter")
Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
Tested-by: Miro Kropáček <miro.kropacek@gmail.com>
Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
Signed-off-by: Helge Deller <deller@gmx.de>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
