81–90 of 104 posts
Earlier quoted context omitted.
You got it wrong. It isn't ARM's module that was merged into the kernel, it is a complete reverse engineered Gallium based driver made by third party volunteers. This driver offers full OpenGL acceleration and does not depend on the ARM's propriety blobs. They re-created all the, as you call it, "interesting stuff" from the user space library. Edit: I take back what I said, I misunderstood the comment. Indeed, the in…
⠀
Earlier quoted context omitted.
You got it wrong. It isn't ARM's module that was merged into the kernel, it is a complete reverse engineered Gallium based driver made by third party volunteers. This driver offers full OpenGL acceleration and does not depend on the ARM's propriety blobs. They re-created all the, as you call it, "interesting stuff" from the user space library. Edit: I take back what I said, I misunderstood the comment. Indeed, the in…
⠀
⠀
Interesting stuff in userspace? I thought drivers worked in kernel for performance reasons (part of why wireguard performs well). Any where I can learn more about what is in userspace and why? I'm also curious, how does performance compare to the binary blob?
Earlier quoted context omitted.
Linux isn't supposed to be friendly to developers wanting to rob people of their rights.
But as a user, I want to be able to use proprietary applications in a safe way, so that they cannot steal my browser cookies or read my MAC address, or patch my kernel. So I would prefer that Linux distributions support proprietary apps like Android Open Source Project does, rather than tell me what I should use and what I shouldn't.
You shouldn't be telling the developers what they should or shouldn't be doing either.
⠀
Interesting stuff in userspace? I thought drivers worked in kernel for performance reasons (part of why wireguard performs well). Any where I can learn more about what is in userspace and why? I'm also curious, how does performance compare to the binary blob?
⠀
Interesting stuff in userspace? I thought drivers worked in kernel for performance reasons (part of why wireguard performs well). Any where I can learn more about what is in userspace and why? I'm also curious, how does performance compare to the binary blob?
Earlier quoted context omitted.
Linux is much more than general distros and closed source drivers are pain in the ass for everybody. Vendors should just mainline the support for their HW, especially if they benefit from Linux overall.
Maybe there is a way to run them safely. For example, have an open source part running in kernel, and closed source part that is properly isolated in userspace.
Earlier quoted context omitted.
Welcomed and encouraged to submit their driver for consideration . I would guess that the vast majority of vendor-proprietary drivers would get rejected from upstream, so for most cases the viable options for vendors wishing have an driver in mainline are to improve an existing reverse-engineered driver or rewrite the driver to fit the kernel standards.
If they accounted for mainlining from the start and not just as an afterthought, they would not have this issue.
What devices can be used with these drivers? The message says there's two drivers: "Lima covers the older t4xx and panfrost the newer 6xx/7xx series" My perception is that Mali GPUs were just in Android phones where running where it's generally not possible to run a vanilla kernel or the bootloader is locked. Any dev boards?