Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1034880
| From | Elliott Mitchell <ehem+debian@m5p.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#939633: More severe #939633 for RP4 on 5.8? |
| Date | 2020-11-28 05:50 +0100 |
| Message-ID | <Bg0lj-2d5-1@gated-at.bofh.it> (permalink) |
| References | <BfeJI-6Xu-7@gated-at.bofh.it> <yDCRr-2UY-1@gated-at.bofh.it> <BfeJI-6Xu-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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+sigmsg@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#939633: More severe #939633 for RP4 on 5.8? Elliott Mitchell <ehem+debian@m5p.com> - 2020-11-26 03:00 +0100
Bug#939633: More severe #939633 for RP4 on 5.8? Elliott Mitchell <ehem+debian@m5p.com> - 2020-11-28 05:50 +0100
Bug#939633: More severe #939633 for RP4 on 5.8? Ben Hutchings <ben@decadent.org.uk> - 2020-12-13 19:10 +0100
csiph-web