HyperPixel OS Compatibility (NOT compatible with Bullseye/device-tree)

[Gadgetoid]

HyperPixel was developed for a very different Raspbian than the Raspberry Pi OS which now powers Pi's.

Screens have shifted from being a Pi-specific hack in config.txt which causes the VideoCore chip to barf out DPI signals which we could shore up with Python scripts and other such (very very wrong in retrospect) nonsense, to a much more stringent Linux device-tree configuration.

As such we can't support HyperPixel on Bullseye. The conflicting pin assignments make it - if not impossible - extremely contrived.

Support on Buster is possible via a Python tweak found here: #54

For the curious there is some discussion about the complexity of the move from old-style to new-style drivers here: https://forums.raspberrypi.com/viewtopic.php?t=324640

[HughMungis]

Is there a pre-bullseye build that you all recommend as a "most recent working" OS? I don't mind ditching bullseye.

EDIT: this one worked for me https://downloads.raspberrypi.org/raspbian/images/raspbian-2020-02-14/

[theschles]

@Gadgetoid I've incorporated your comments above into PR #61

Please please please consider implementing the "contrived pin assignments" -- or whatever it takes -- for the HyperPixel 2.1 so it will be 100% supported without additional hacking around in Bullseye-based and Bookwarm-based Raspbian OS !

This is a great display. I deliberately bought the display [after watching @MattGrayYes 's video using the HyperPixel 2.1 to display pictures of the "Blue Marble" (a.k.a. "Earth") from the EPIC library]{https://www.youtube.com/watch?v=q4M3cm4ml_c}. My dad's 82nd birthday is on Sunday and I'm making the project [using MattGreyYes's code]{https://github.com/MattGrayYes/epic} as a birthday gift.

Or please design / implement / release a new round HyperPixel which does support Bullseye/Bookworm-based Raspbian OS before Buster goes End of Life on June 30, 2024. I'd gladly buy that and swap out this HyperPixel 2.1.