SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It would be nice to have a public database where package updates can be tracked so this can be avoided. If one finds an update, or patch, submit the URL and version number to the database and it can be tracked. Would avoid a lot of duplication posts here.
Very true. There were some issues with the latest OpenMAX release from omxil-bellagio with the latest GCC which requires some patching, but yes, rounding out support would be a wiser choice since the Free driver for AMD is of very high quality, very similar to the Nvidia OEM driver. I do believe those would give the AMD Mesa driver complete support.
I do hope that for next slackware after this release we won't need to care about omxil-bellagio since there is an suggestion for GSoC to change to Tizonia instead and i think it would make more sense to add it then since omxil-bellagio isn't maintained. http://www.x.org/wiki/SummerOfCodeIdeas/
I hope someone is up for that challenge this summer.
The reason i see for not adding omxil-bellagio is that it's a risk to add not maintained software to an release and should be avoided if possible.
Tizonia is actively maintained and also up to date with latest OpenMAX IL 1.2 specification the not maintained Bellagio is still OpenMAX IL 1.1.
Maybe after this summer it will make more sense to add OpenMAX support.
Very true, but at even the aspect of the fact libomxil-bellagio is currently lacking in maintenance, it can always be replaced with libomxil-tizonia when the switch in Mesa is made. Currently, libomxil-bellagio could be classified as long term stable, but yes it is currently stalled and possibly unmaintained, yes it might seem improbable to add, but as it goes, it can be replaced when the replacement is ready.
However, libclc being added would be more realistic as it brings in a support factor available in OEM drivers that is more widely used.
While we're on the graphics topic, I repeat the request for libvdpau-va-gl.
I don't think we need to bloat Slackware with every little utility or library, that could very well cause considerable hardware conflicts. That's the purpose Slackbuilds.org https://www.slackbuilds.org/reposito...ibvdpau-va-gl/ (not to add bloat but to assist customization )
Example: I use a NVIDIA GPU, libvdpau and the Nvidia binary blob (libvdpau-nvidia.so). If libvdpau-va-gl where present, I would have to remove it and blacklist it.
I don't think we need to bloat Slackware with every little utility or library, that could very well cause considerable hardware conflicts. That's the purpose Slackbuilds.org https://www.slackbuilds.org/reposito...ibvdpau-va-gl/ (not to add bloat but to assist customization )
Example: I use a NVIDIA GPU, libvdpau and the Nvidia binary blob (libvdpau-nvidia.so). If libvdpau-va-gl where present, I would have to remove it and blacklist it.
I wouldn't say it's about bloating with everything. We give suggestions, we discuss them, Pat makes the decision
I don't think we need to bloat Slackware with every little utility or library, that could very well cause considerable hardware conflicts. That's the purpose Slackbuilds.org https://www.slackbuilds.org/reposito...ibvdpau-va-gl/ (not to add bloat but to assist customization )
Example: I use a NVIDIA GPU, libvdpau and the Nvidia binary blob (libvdpau-nvidia.so). If libvdpau-va-gl where present, I would have to remove it and blacklist it.
I agree but for omxil-bellagio things get a bit more complex since SBo shouldn't accept builds that needs mesa to be rebuilt so that one will not be on SBo.
But as an slackware user i don't complain, there should be some things left for the user and mesa is pretty fast to compile, heck i update mesa pretty often these days.
I don't think we need to bloat Slackware with every little utility or library, that could very well cause considerable hardware conflicts. That's the purpose Slackbuilds.org https://www.slackbuilds.org/reposito...ibvdpau-va-gl/ (not to add bloat but to assist customization )
Example: I use a NVIDIA GPU, libvdpau and the Nvidia binary blob (libvdpau-nvidia.so). If libvdpau-va-gl where present, I would have to remove it and blacklist it.
It depends on how the Nvidia package handles the libvdpau-va-gl such as renaming and relinking the library, which is the current behavior. As it is, we have to rebuild and reinstall the Nvidia driver packages when Mesa and such get updated, so one more on the watch list isn't fatal.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
