Bug#939633: More severe #939633 for RP4 on 5.8?
On Fri, 2020-11-27 at 20:41 -0800, Elliott Mitchell wrote: > found 935456 5.9.6-1~bpo10+1 > quit > > After having spent several hours on kernel compiles and experimenting > with the situation, I'm fairly sure this also applies to > linux-source-5.9. > > Odd thing is, when I booted the device using the Tianocore implementation > it came right up with no problems. I'm getting this odd suspicion > someone deliberately broke the device-trees in Debian's kernel source. > The goal being to force everyone onto the Tianocore/ACPI implementation > and try to kill device-trees. > > Right now I think this is conspiracy theory territory, but I'm left > wondering how such a serious bug could hang around so long... We don't patch any of this stuff. Any bugs in the device trees that we ship come from the upstream kernel, and need to be fixed there. No- one's deliberately breaking this in Debian, and you had better stop making accusations like that. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#939633: More severe #939633 for RP4 on 5.8?
found 935456 5.9.6-1~bpo10+1 quit After having spent several hours on kernel compiles and experimenting with the situation, I'm fairly sure this also applies to linux-source-5.9. Odd thing is, when I booted the device using the Tianocore implementation it came right up with no problems. I'm getting this odd suspicion someone deliberately broke the device-trees in Debian's kernel source. The goal being to force everyone onto the Tianocore/ACPI implementation and try to kill device-trees. Right now I think this is conspiracy theory territory, but I'm left wondering how such a serious bug could hang around so long... -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Bug#939633: More severe #939633 for RP4 on 5.8?
found 939633 5.8.10-1~bpo10+1 severity 939633 important merge 935456 939633 quit I'm left suspecting bugs #935456 and #939633, are in reality a single bug: Raspberry Pi device trees were garbled during Debian's 5.2 kernel development. They appear to remain very garbled, to the point of being pretty well useless. I've built a kernel from Debian's 5.8 kernel source and the device tree binary produced doesn't appear to allow a Raspberry PI 4B to complete its boot. Might be USB functionality is operational, but neither ethernet interface nor display function. Ironically, the additional ACPI/EFI support DOES function. This means the Tianocore image for Raspberry PI 4B works better with the current source. I'm unsure whether badly breaking all Raspberry PI variants quite justifies critical or grave (popular machine, but kernel issues by nature cause 10x the damage so severities should be somewhat damped). I certainly hope to see the 5.9 release since that has additional high-value improvements... -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
