aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bmips/patches-5.10
diff options
context:
space:
mode:
authorKevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>2020-01-14 22:19:06 +0000
committerKevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>2021-03-24 11:51:29 +0000
commit22d2c972c47466ba9e1a59aefeca8d9efa08b335 (patch)
tree58f2fbec3da0dcc9c2a3c37cc318cb41d0d684e4 /target/linux/bmips/patches-5.10
parentd07ac3e37603bac438b21286b14867e7489ed7dd (diff)
downloadupstream-22d2c972c47466ba9e1a59aefeca8d9efa08b335.tar.gz
upstream-22d2c972c47466ba9e1a59aefeca8d9efa08b335.tar.bz2
upstream-22d2c972c47466ba9e1a59aefeca8d9efa08b335.zip
kernel: drop apu2 reboot patch
This patch really annoys me, either it needs to go upstream or be dropped, so it's going to be dropped here. Checking drivers/platform/x86/pcengines-apuv2.c it also appears to be incomplete since it mentions different dmi board names depending on bios version. /* APU2 w/ legacy BIOS < 4.0.8 */ is 'APU2' /* APU2 w/ legacy BIOS >= 4.0.8 */ is 'apu2' /* APU2 w/ mainline BIOS */ is 'PC Engines apu2' So the patch, if applicable at all, only 'works' for legacy BIOS >= 4.0.8 My APU2 on mainline BIOS reboots fine without this patch. So let's see if anyone screams and when they do question why legacy bios. If patch DOES need to be re-introduced then it needs to go upstream first. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Diffstat (limited to 'target/linux/bmips/patches-5.10')
0 files changed, 0 insertions, 0 deletions