News for hackers. Stuff that matters.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by Subsentient on Friday September 18, 2020 @02:02PM (#24519928)
I'm expecting this to be another Oracle/Sun acquisition, e.g. annihilates everything the old company's customers ever liked about them. So no, I don't think this FOSS contribution will continue. Nvidia is notoriously hostile to open source.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by DCKing on Friday September 18, 2020 @04:53PM (#24521790)
> Nvidia is notoriously hostile to open source.

I've been very critical of Nvidia and this acquisition, but I don't think this is accurate. Nvidia as a company shows a lot of evidence of a company that does not deal well with community or intercompany collaboration. But I don't believe they're actively hostile to open source.

The reason Nvidia's main graphics driver is closed source is I think merely historical. Closed source drivers were the status quo for the longest time, and the development of Nvidia's driver is built around this. Right now the thing is probably filled to the brim with hacks, (third party) intellectual property, and near zero support for the Mesa standards/architecture that came into existence way late in the driver's life. AMD's driver would also likely still be closed source for similar reasons, were it not that they decided to invest a lot of money (and lost time) to give it a fundamental rewrite - which was necessitated because their closed source driver was much worse than Nvidia's was in the first place.

There's a lot of narrative around characterizing Nvidia as 'evil' and them being actively hostile against open source, but it's just a company with its own faults (maybe moreso than others, sure) and with its own history.

The incentives around having a mainline Linux driver keep on getting stronger, and I'm actually cautiously optimistic that Nvidia knows this and will consider making the investment to make such a driver. Especially if their commitment around Linux-on-ARM has to improve as a result of this acquisition.

Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by izacus on Saturday September 19, 2020 @05:58AM (#24526341)
> Nvidia is notoriously hostile to open source.

Nvidia was the only provider of fully working OGL drivers for Linux and BSDs for decades, so this narrative is just pure FUD.

They're not "notoriously hostile" if they didn't choose to throw a wrench in their drivers and whole business just because Linux kernel people decided to trash the driver APIs one-sidedly. They're also not "hostile" because they refuse to be bullied by Linus' middle fingering into the solution that doesn't work for them.

Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by pjmlp on Saturday September 19, 2020 @04:05AM (#24525967)
Quite the contrary, NVidia is quite willing to contribute when it comes with money attached, like scietific computing and Hollywood studios.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by bazooka_penguin on Friday September 18, 2020 @02:22PM (#24520145)
Nvidia has been contributing to open source scientific computing, ml, and simulation libraries for a while now to support CUDA's adoption
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by wtallis on Friday September 18, 2020 @02:40PM (#24520408)
The userspace vs kernelspace distinction is important here. Nvidia contributing userspace code with dependencies on their hardware and proprietary drivers is part of a lock-in strategy. Contributing open-source drivers would be a very different thing, and would undermine at least some of their product segmentation strategies.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by m4rtink on Friday September 18, 2020 @02:41PM (#24520418)
Yet CUDA is still fully proprietary & total vendor lock-in...
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by londons_explore on Friday September 18, 2020 @03:39PM (#24521052)
Kinda surprising AMD hasn't made their own CUDA compiler and set of libraries.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by tpxl on Friday September 18, 2020 @04:24PM (#24521516)
They have (sort of): https://github.com/ROCm-Developer-Tools/HIP

It just isn't very good yet.

Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by gnufx on Friday September 18, 2020 @05:19PM (#24521974)
However, it features in the preparation for the Frontier supercomputer, I think, though I can't immediately find the OCLF material I saw.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by mikepurvis on Friday September 18, 2020 @03:55PM (#24521224)
I think the theory is that that's what OpenCL is, but for most people if you're building a dedicated cluster, you're buying Nvidia hardware anyway, and if you already are using the hardware for it, you might as well go native and get the best performance and library support.
Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by pjmlp on Saturday September 19, 2020 @04:11AM (#24525986)
OpenCL is no match for CUDA.

Stuck in pure C, printf style debugging with graphical debuggers that never properly handled everything.

CUDA, polyglot GPGPU development environment, graphical debuggers that allow for single stepping and conditional breakpoints in GPGPU code, interoperability with graphical APIs.

OTOY just replaced their rendering code in Octane Render from Vulkan to CUDA (via Optix 7).

Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by pjmlp on Saturday September 19, 2020 @04:07AM (#24525974)
Yet no competition was able to provice a polyglot OpenCL and IDE with graphical GPGPU debuggers.

Failure of execution from the competion is also to blame.

Yes, OpenCL finally adopted SPIR-V, when it was down and the referee started the countdown.

Re:Arm Officially Supports Panfrost Open-Source Mali GPU Dri... by gnufx on Friday September 18, 2020 @05:08PM (#24521890)
What's actually "open source" about what they have made themselves, as possibly opposed to modifying existing stuff? There's a significant effect of being proprietary in that people like me can't distribute packages using it for Fedora, Debian, SUSE, etc.