-
Notifications
You must be signed in to change notification settings - Fork 0
Source code for the BIOS? #49
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
Comments
Charging is actually controlled from the embedded controller, which we do actually open source the code for.
Yes. |
Note that the system firmware(BIOS) is (majority assumed to be) an intellectual property of Insyde Software and is very likely proprietary and non-redistributable by Framework Computer Inc. It may be possible to access the source code if there's ever a coreboot port of the system firmware, but I won't give high hopes for that. |
@brlin-tw You'll be surprised to see that an experimental port has already landed in Coreboot 24.05 for the AMD Laptop 7040 series, I don't think this port is intended for end users and I don't think it is possible/easy to test it, I haven't heard of anyone trying it. I believe this port was done by an engineer who works at AMD on firmware. There were also 3 laptops that have been apparently given to some Coreboot devs :
However, on Intel's side, I haven't seen much news AFAIK. Sources : |
This is related to another issue I opened, #48, but I think it'd make sense to keep this as a separate issue.
When I had the idea for the issue above, my first thought was that I wanted to try my hand at modifying the BIOS code myself. It's not a high-priority issue by any stretch, but something I'd find useful.
With most of the hardware being open source, I figured the BIOS would be as well. However, based on this issue tracker's existence, I'm assuming it's probably not open source. Is there a reason for this?
All that being said, I realize it might be a bit stupid for me to even think about modifying my BIOS. I would assume custom BIOS work could very easily lead to a bricked laptop, if I mess anything up.
The text was updated successfully, but these errors were encountered: