Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2053729 Information from BlockerBugs App: <img alt="2053729" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2053729" />
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2022-04-04 19:02 UTC and the last processed comment was #comment-790472
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
From the docs: "The Raspberry Pi Model B versions of 2, 3 and 4 are supported for Fedora 25 or newer, without any requirement of third party kernels or scripts to adjust offical images". Since networking is required for a whole bunch of criteria, and this is apparently supported ARM hardware, I don't see how this can be anything but a blocker.
FinalBlocker +1
(edited to change vote to +1 based on feedback from Peter on the ARM mailing list)
The QuickDocs are incorrect, I think. The ARM SIG says Raspberry Pi 4 is not supported. I'm inclined to defer to the ARM SIG and vote
I'll try to get the docs in alignment
ARM list thread to discuss Quick Docs 441
The number of Pi4 users in the wild is fairly large, and the lack of official support is because we do not have accelerated graphics support, which would make for a poor workstation. When you consider the percentage of users currently running their Pi 4 headless, it makes it even more difficult to solve with a 0 day update.
AGREED AcceptedFinalFE
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.