diff options
| author |   Bruce Ashfield <bruce.ashfield@gmail.com> | 2022-04-28 09:47:54 -0400 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-05-01 21:55:58 +0100 |
| commit | f69fca36ef10f7345bba08c55d8af2628d250a32 (patch) | |
| tree | 094739c69f95f1c7a5bc7c3a8f9b3f6d464d3abc /meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb | |
| parent | a9075595074609c80af3530d4660b88ce0f76744 (diff) | |
| download | openembedded-core-contrib-f69fca36ef10f7345bba08c55d8af2628d250a32.tar.gz | |
linux-yocto/5.15: fix ppc boot
The 5.15-stable series pulled in the following commit:
commit c894ac44786cfed383a6c6b20c1bfb12eb96018a
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date: Tue Jan 25 10:12:18 2022 +0100
fbdev: Hot-unplug firmware fb devices on forced removal
commit 27599aacbaefcbf2af7b06b0029459bbf682000d upstream.
Hot-unplug all firmware-framebuffer devices as part of removing
them via remove_conflicting_framebuffers() et al. Releases all
memory regions to be acquired by native drivers.
Firmware, such as EFI, install a framebuffer while posting the
computer. After removing the firmware-framebuffer device from fbdev,
a native driver takes over the hardware and the firmware framebuffer
becomes invalid.
Firmware-framebuffer drivers, specifically simplefb, don't release
their device from Linux' device hierarchy. It still owns the firmware
framebuffer and blocks the native drivers from loading. This has been
observed in the vmwgfx driver. [1]
Initiating a device removal (i.e., hot unplug) as part of
remove_conflicting_framebuffers() removes the underlying device and
returns the memory range to the system.
[1] https://lore.kernel.org/dri-devel/20220117180359.18114-1-zack@kde.org/
v2:
* rename variable 'dev' to 'device' (Javier)
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reported-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Reviewed-by: Zack Rusin <zackr@vmware.com>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
CC: stable@vger.kernel.org # v5.11+
Link: https://patchwork.freedesktop.org/patch/msgid/20220125091222.21457-2-tzimmermann@suse.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
And this is causing qemuppc to panic during boot when manipulating
the fbdev.
Reverting it fixes the problem, and won't cause issues for other
platforms, so we revert it.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb')
| -rw-r--r-- | meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb index bba1200fe7..d7250ca4d5 100644 --- a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb +++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb @@ -11,8 +11,8 @@ python () { raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it") } -SRCREV_machine ?= "85ebb3e98ee184fad92eedd79f006df9809f01ff" -SRCREV_meta ?= "645b337371e7e080e71f7d7f2435326242451a95" +SRCREV_machine ?= "ec729d37e4036fe80d0294684aa779c091466307" +SRCREV_meta ?= "71a82e181708bc619684cc9f1eea01ec2595c2ff" SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}" |