Pi 4 support progress and other package infos

fluffypillow

Also in case this affects the main devs negatively, feel free to close this thread.

BuZz

@fluffypillow actually quite interesting. Some stuff will always be platform specific of course. And some stuff although supported may not build still on certain platforms.

Cheers.

muldjord

Data is beautiful. This is pretty cool :) Nice work.

simpleethat

And here I thought this was going to be another "when's it going to be ready" thread and was pleasantly surprised by what I found.

BuZz

It also nicely illustrates the number of packages we include in RetroPie and have to manage. It's a very small number of people who have complained loudly about progress. I am thankful for the patience and support of the majority of users.

AndrewH

As someone who’s keenly awaiting an “official” Pi4 release, who doesn’t want to be a bother (and I’ve pretty successfully followed the manual install steps anyway), I think this is really interesting.

I’d like to understand a little more what I’m looking at in the individual package sections; with respect to the Pi4, which columns are important and which aren’t?

Thanks, and keep up the great work!

herb_fargus

I've said it and ill keep saying it. Fluffypillow is brilliant.

BuZz

@herb_fargus fanboy!

(I agree)

simpleethat

@BuZz said in Pi 4 support progress and other package infos:

@herb_fargus fanboy!

(I agree)

HAHAHA!

BuZz

@fluffypillow could be handy to have this as part of RetroPie as an admin module (in the same manner we have for other things like API docs).

I had an info module which could output package licenses (was intending to expand it to incorporate other information also) - don't think I committed it actually, but something like this could be included in a similar manner.

Just an idea, no pressure to submit anything :-)

cyperghost

@BuZz Are there are any plans to integrate Pegasus into RetroPie (for Pi4) as default frontend?

fluffypillow

Well I couldn't stop myself and ended up making a page for the licences too: https://mmatyas.github.io/retropie-pkglicences/

Now since we're talking about licences, there can even more real life inaccuracies compared to the package flags. The page uses only the info listed in the install scripts, and it cannot decide whether a package has, for example, dual licensing or mixed licences, or cases where a script downloads something (eg. most ES themes are noncommercial).

@BuZz sure, I'll see if I can make that the weekend.

@AndrewH in the case of Pi 4 the DRM/KMS and the ARMv8 columns are checked. For the others you can see them when you hover over the progress bars (yeah, that part isn't mobile friendly yet).

mitu

@fluffypillow That's very cool ! I clicked every link possible and found a few missing/wrong ones. I've also hunt down a few missing license and we'll try to add in a PR.

herb_fargus

Now all we need is a graph of the download counts ;)

https://api.github.com/repos/RetroPie/RetroPie-Setup/releases

Swampy

@fluffypillow, here is an possible extension for your listing of the packages:

configuration/splash screens (not implemented in Pi 4 yet)
https://github.com/RetroPie/RetroPie-Setup/pull/2849
https://github.com/RetroPie/RetroPie-Setup/pull/2852
Sorry, found it!

Thank you very much for your hard work!

Swampy

@fluffypillow, frotz is working with rpi4 now.

fluffypillow

Ok, both pages now follow the master branch.

dmikester1

On the visual support progress page, do each of the columns with a specific architecture relate to one of the computers in the top chart? Or are they not related like that?

As a follow-up question, so if I wanted to see specifically which pieces still needed to be implemented for full rPI 4 support, which column would I need to look at?

mitu

@dmikester1 said in Pi 4 support progress and other package infos:

On the visual support progress page, do each of the columns with a specific architecture relate to one of the computers in the top chart? Or are they not related like that?

They are related, but there's not a 1:1 mapping - for instance ARMv7 covers both PI2 and Pi3, X11 and x86 are also related but not exclusive.

As a follow-up question, so if I wanted to see specifically which pieces still needed to be implemented for full rPI 4 support, which column would I need to look at?

The PI4 will rely on the KMS/DRM subsystem, so you can take a look at that column. Note that some packages are not working with KMS/DRM and it doesn't mean they'll be implemented for the PI4, so don't take that column as a 'progress'.

fluffypillow

For the record, here are the columns that affect the progress bars:

Raspberry Pi 0/1: VideoCore + ARMv6
Raspberry Pi 2: VideoCore + ARMv7
Raspberry Pi 3: VideoCore + ARMv8
Raspberry Pi 4: DRM/KMS + ARMv8
Odroid C1/XU3/XU4: Mali + ARMv7
Odroid C2: Mali + AArch64
Desktop Linux: X11 + x68

(This info is also visible when hovering on the progress bars with a mouse.)