carl9170fw
mu
| carl9170fw | mu | |
|---|---|---|
| 4 | 5 | |
| 37 | 536 | |
| - | 0.7% | |
| 2.9 | 7.1 | |
| 12 months ago | 23 days ago | |
| C | Python | |
| GNU General Public License v3.0 or later | 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.
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/
mu
- Welcome to Project Mu
-
Purpose: Project Mu Payload
yes kkkkkk, the project mu have a strange way to build, and project mu have a not usable documentation, i think is because microsoft is microsoft, the project mu is a OEM Firmware as Service, the reason for not have a easy documentation can be for seal a service. in the past i have make a question about coreboot support https://github.com/microsoft/mu/issues/121
-
Framework: Open Sourcing Our Firmware
The stock edk2 menu has, like, two items.
System76 have built a more serious setup UI: https://github.com/system76/firmware-setup
Microsoft’s https://github.com/microsoft/mu also probably contains UI from the Surface line or something??
- Surfac-ify
What are some alternatives?
rpitx - RF transmitter for Raspberry Pi
libnklabs - NK Labs Common Library
EmbeddedController - Embedded Controller firmware for the Framework Laptop
fwhunt-scan - Tools for analyzing UEFI firmware and checking UEFI modules with FwHunt rules
InitWare - The InitWare Suite of Middleware allows you to manage services and system resources as logical entities called units. Its main component is a service management ("init") system.
bcm5719-fw - BCM5719 firmware reimplementation
qiling - A True Instrumentable Binary Emulation Framework
open-ath9k-htc-firmware - The firmware for QCA AR7010/AR9271 802.11n USB NICs
firmware-setup - Firmware Setup
MxGPU-Virtualization
Ventoy - A new bootable USB solution.