-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPi: remove platform #16321
RPi: remove platform #16321
Conversation
@@ -1135,14 +1135,6 @@ const infomap weather[] = {{ "isfetched", WEATHER_IS_FETCHED }, | |||
/// @return **True** if Kodi is running on a linux/unix based computer. | |||
/// <p> | |||
/// } | |||
/// \table_row3{ <b>`System.Platform.Linux.RaspberryPi`</b>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add this to removed infolabels for v19? Search for "@skinning_v18 [Removed Infolabels] The following infolabels have been removed:" in this file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added, I hope I did that correctly!
I believe this PR would remove the RPi specific MAKEFLAGS for kodi and for ffmpeg thus removing the specific optimizations for at least those two components. Any way to allow for these? For example: |
set your |
Yes, but I thought the the cmake scripts also passed some extra flags particularly for building ffmpeg. |
same answer |
this needs a rebase ;) |
@lrusak do you want to progress this? |
Yes this will continue to stay open. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
diff looks good
I think you've removed AESinkPi.cpp/AESinkPi.h from the makefiles but not removed the files themselves. |
nice catch, probably lost in the rebase. Updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look okay.
This is the 404 introduced by the README.RaspberryPi removal: https://github.com/lrusak/xbmc/blob/rpi-removal/docs/README.RaspberryPi.md I would suggest: https://github.com/garbear/xbmc/blob/rpi-removal/docs/README.RaspberryPi.md |
Perfect thanks! I've updated it with this included. |
Does the GBM build for raspberry pi require any pi-specific steps that should be mentioned in the linux readme? |
Not that I can think of. Users will have to use the VC4 DRM and mesa3d driver but using a DRM driver and a mesa3d driver are typical of any platform using GBM (other than some mali platforms). @popcornmix can you think of any other specifics that you would like to add? |
I think it's okay. To run you need kms ( I suspect users building themselves are familiar with this. If it seems to be a common issue I guess the |
@popcornmix your button 😊 |
@lrusak @popcornmix - If all Pis can in fact use gbm moving forward, what the default recommendations for:
Currently, for RPi4, I am using:
|
Use the forum for these questions. |
Upstream dropped support for RPi platform since gbm matured and is stable[1]. This package should support RPi2+ hardware. 1. xbmc/xbmc#16321
Similar to #16043
To be clear for people. This does not remove support for the Raspberry Pi. It simply removes the RPi specific platform in Kodi. Raspberry Pi users can move to use GBM. The Raspberry Pi 4 will only ever use GBM and the older models can use it as well.
There as some things that aren't up to feature parity but it will be a level playing field for RPi, amlogic, rockchip, allwinner, etc. If someone submits improvements for one platform it will benefit all the platforms. That is the biggest reason for this removal.
This removal has been pushed off for some time now. I feel it is best to do this early in our V19 release cycle as to give other developers early warning that they will have to make changes to their development and OS's. This PR removes over 10,000 lines of platform specific code.
The entire goal of this (and what I have been working towards for over two years now) is to unify the code base into a more platform agnostic way. Developers are encouraged to move to GBM and ask as many questions as they would like about it.
Thanks to everyone that has made this possible so far. @popcornmix @6by9 @anholt @Kwiboo @chewitt and anyone else that I missed. There is still a lot to do but we will get there and when we do it will work on all platforms.
I am always available to answer any questions as they come up and can always be pinged in the #kodi-dev or #kodi-linux IRC rooms on freenode.