Paul Wratt

`hdmi_force_hotplug=1` should allow later HDMI connection and activation. Not having HDMI become active later implies _no framebuffer allocation_ at boot time.

Was this related to the other RPi Kernel XHCI/USB issues from the time period? Is this still an issue with 1.32?

"Console should properly default to graphical" has been resolved according to the [EDK2 bug 2831 conclusion](https://bugzilla.tianocore.org/show_bug.cgi?id=2831#c22), and the resulting spec update that provides new variables. > This means we can...

It appears the only items left of this "Debian FIXME" list are the WiFi Blob issues, and the "Nice to have" vc4/5 option. Is it possible that the WiFi blob...

Is this one of the variable that can be stored in the RPi4, the way the current "hack" is used for some other variables (or is the "hack" acceptable upstream...

So U-Boot is EFI compliant, and the resulting `RP_EFI.fd` (UEFI) will find everything, including Variables and DeviceTree, to make available to resulting OS? If you still need `bootcode.bin` then this...

@Killertamagotchi in creating a standard i2c Fan Control Driver, some way to define various pins is required, that would be the only way to release something that works across all...

This is not the 1st thread to contain references to the need for GPIO pin management. Is it possible to load a GPIO text file at run time that presets...

FCOS needs DeviceTree to get access to GPIO, according to a docs link in that Tracker reference. I would say most other OS would too, unless there is a known...

With 1.32 reverting to upstream Kernel again, can this be closed? (did the patchs get accepted - there is no mention of it on the Release page)