diff options
| author | Thomas Zimmermann <tzimmermann@suse.de> | 2024-02-12 10:06:15 +0100 |
|---|---|---|
| committer | Thomas Zimmermann <tzimmermann@suse.de> | 2024-02-14 10:09:21 +0100 |
| commit | 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 (patch) | |
| tree | 5329f0fbf2d241600d9d4b46ca57c13a54e1dcbd /net/kcm/kcmproc.c | |
| parent | 784e27f2811884ab78edc713a4ef0d4deca9b668 (diff) | |
| download | linux-78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371.tar.gz linux-78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371.tar.bz2 linux-78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371.zip | |
firmware/sysfb: Update screen_info for relocated EFI framebuffers
On ARM PCI systems, the PCI hierarchy might be reconfigured during
boot and the firmware framebuffer might move as a result of that.
The values in screen_info will then be invalid.
Work around this problem by tracking the framebuffer's initial
location before it get relocated; then fix the screen_info state
between reloaction and creating the firmware framebuffer's device.
This functionality has been lifted from efifb. See the commit message
of commit 55d728a40d36 ("efi/fb: Avoid reconfiguration of BAR that
covers the framebuffer") for more information.
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240212090736.11464-8-tzimmermann@suse.de
Diffstat (limited to 'net/kcm/kcmproc.c')
0 files changed, 0 insertions, 0 deletions