-
Notifications
You must be signed in to change notification settings - Fork 0
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
[META] 3D acceleration support for LG100/LG110 (LS7A2000 GPU) #77
Comments
Due to some reasons it's highly unlikely the vendor would be able to publish an open-source driver even if its engineers will to do all the work. Caution And if you plan to join the effort reverse-engineering the old-world or new-world closed-source driver: please don't search online or ask others for those reasons. You may be tainted simply by knowing the reasons. YOU ARE WARNED. edited by xen0n: make the alert really stand out |
Preliminary new-world LoongGPU driver package under internal testing, see test results. |
Well they just released the driver package out of nowhere this morning... Kernel components (DKMS): Userspace components (OpenGL, DDX, etc.):
Firmware: |
Note that the license of loonggpu-driver explicitly forbids reverse engineering. |
cat /usr/share/doc/loonggpu-driver/copyrigh
|
Looking at the copyright notice of
Note the "No Separation of Components" part -- this is a leftover from an earlier revision of NVIDIA blob driver EULA that predated the GSP models, which for NVIDIA prohibited the free drivers from re-using the firmware blob distributed with the blob driver, which is problematic because the firmware cannot be built in a legally unencumbered way. NVIDIA has fixed the EULA wording in May 2023 to allow for extraction of separate components from the commercial driver. For Loongson, it's public info that the LoongGPU needs firmware to work (see the |
Update: yesterday evening Loongson maintainers said they "will look into it" regarding the "no separation of components" clause. |
No description provided.
The text was updated successfully, but these errors were encountered: