MxGPU-Virtualization
carl9170fw
| MxGPU-Virtualization | carl9170fw | |
|---|---|---|
| 3 | 4 | |
| 176 | 37 | |
| 0.0% | - | |
| 10.0 | 2.9 | |
| about 4 years ago | 12 months ago | |
| C | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
MxGPU-Virtualization
-
AMD V620 PRO
https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization - on github we have the old driver, but not support v620 card.
-
Hit and miss GIM module runtime configuration
I have configured the GIM module following this. I am able to pass VFs through to VMs and it works great. However, I have been trying to modify the runtime options as indicated here. Some seem to work, and some don't.
-
Nvidia releases open-source GPU kernel-modules
> And I understand NVIDIA is even worse re: GPU virtualization.
Nope, it’s much better on the nvidia side actually. The latest AMD GPU with a publicly accessible GIM driver is the AMD S7150, which was released in 2016. (https://github.com/GPUOpen-LibrariesAndSDKs/MxGPU-Virtualiza...)
> The good news is that I understand this support is actually good on the Intel side
Not anymore. GVT-g is gone on Ice Lake (Intel 10th generation mobile, 11th gen desktop) so that you can no longer do hardware vGPU on newer Intel parts at all.
Sad thing is that what you said used to be true.
Meanwhile NVIDIA GRID needs licensing fees but actually works, with high end GPU options being available.
carl9170fw
-
Nvidia releases open-source GPU kernel-modules
The carl firmware at https://github.com/chunkeey/carl9170fw should put that argument to rest. That is Wifi firmware source code for the Wifi I currently use.
Easily changed likely means there's a physical knob somewhere that you could accidentially poke as a layperson.
Not that you get a three year CS education, figure out how your distribution packages dependencies, install the correct embedded toolchain (good luck), find out exactly which chip is in your device, fetch the proper firmware source code in the right version, build the thing, figure out how to flash the result onto the chip / read the Linux kernel sources to figure out the filename inside /lib/firmware. That's not easy.
Even if this entire process was packaged (it is--see <https://packages.debian.org/sid/firmware-linux-free>), it probably still doesn't count (or at least shouldn't count) as "easily" changed.
- The FSF’s relationship with firmware is harmful to free software users
- Framework: Open Sourcing Our Firmware
-
GNU Radio
There are some cards with open source firmware, you might be able to modify it to do something like that.
https://github.com/chunkeey/carl9170fw/
What are some alternatives?
open-gpu-kernel-modules - NVIDIA Linux open GPU kernel module source
rpitx - RF transmitter for Raspberry Pi
gamescope - SteamOS session compositing window manager [Moved to: https://github.com/ValveSoftware/gamescope]
EmbeddedController - Embedded Controller firmware for the Framework Laptop
gamescope - SteamOS session compositing window manager
libnklabs - NK Labs Common Library
MxGPU-Virtualiza
bcm5719-fw - BCM5719 firmware reimplementation
open-ath9k-htc-firmware - The firmware for QCA AR7010/AR9271 802.11n USB NICs
mu - Project Mu Documentation
sverchok - Sverchok
firmware-setup - Firmware Setup