There’s an entire community that’s willing to ditch Purism and System76 if the Framework Laptop meets these two requirements.
36 Likes
Absolutely. Wholeheartedly agree.
3 Likes
Yep, open source firmware is well aligned to our mission of building products that are better for people and the planet. Our EC firmware is based on chromium-ec, and we will be releasing source. As @Kieran_Levin noted, we’re also exploring coreboot. We’re currently focused on getting the Framework Laptop out into the world in a lower-risk path that uses an off the shelf proprietary BIOS, but we’re looking forward to replacing that with an open alternative in the future.
84 Likes
The future of EC firmware is Zephyr. Please note that Google announced switching from Chromium EC to Zephyr on OSFC 2020. Of course, after investing in Chromium EC switching doesn’t make sense, but in long run (maybe next laptop?) and support available from EC manufacturers, this could be the solution. Also if the platform would be popular enough, schematics reasonably open, then maybe community effort will open the path for Zephyr support. This is what wish to Framework Laptop.
15 Likes
I think releasing firmware is a good step in the right direction, even though it will still have proprietary stuffs and blobs in it.
Coreboot would then be the next logical step, but without a stripped and disabled ME it’s kind of worthless.
Even though you could then have Legacy Boot again, which already is a big improvement to UEFI.
I would love to see a further developed solution of me_cleaner that covers also the latest intel chipsets in the most possible way.
Those two combined in my opinion is the most powerful solution to address privacy as it is needed.
Maybe Zephyr is also great, I just haven’t heard of it until now 
7 Likes
I’m not very familiar with firmware like this, so sorry if this has been answered before, but if you have a Framework laptop that does not have coreboot or another open source firmware on it, and you’d like to install it, how would you do that? And is there a way to check what you have installed?
3 Likes
Until it is officially supported, you can’t install it. So wait until Framework announces support, because they’ll most likely detail how to flash the new bios firmware then.
10 Likes
Looking forward to Coreboot !!!
12 Likes
How much support do you have for people who want to hack the BIOS? Specifically, I wouldn’t mind trying to install CoreBoot and disable the IME. Obviously, I won’t come crying to mommy if I brick my machine, but I wonder if, say, the JTAG port is accessable and relevant documentation is available somewhere.
11 Likes
You will have to wait for Framework to support it! looking forward for it 
4 Likes
I too am putting in my vote for Coreboot at the least.
6 Likes
I think that in the future there should at least be an option for open boot firmware like https://www.coreboot.org/ or https://libreboot.org/. we need to show that there is a demand for this and that framework should consider it.
13 Likes
9 Likes
Always the more open the better. If you guys manage to get open firmware solutions I will change my stance from “well, I don’t endorse anything at this point except for Framework” to “absolutely don’t get anything but Framework,” when people ask me what laptop to get. A whole lot of people ask their technologist family or friend what laptop to get - I tend to be that guy for a whole lot of people. Now I can tell them that I will only support working on it if they get Framework.
Seriously though, I just ordered one for my mother. As a datasec professional, I want to cast a strong, strong vote for open firmware. I will continuing voting with my wallet and suggesting others do as well.
15 Likes
I think a possible future enhancement that would suit this is having dual bios onboard. This is a fairly common feature on motherboards intended to facilitate novel use (like ln2 overclocking).
3 Likes
I think for the end user thats only helpful when they have an eeprom programmer to put the bios image on the new chip unless framworks starts to sell pre-programmed chips. There is also the danger that a DAU would remove the chip for an extended period of time which would reset the enitre bios and system clock. If the boot order gets messed up because of the reset then you might look at a laptop that refuses to boot 
.
Also dual bios for overclocking puposes only makes sense when you have a physical bios switch. Looking a desktop motherboards maybe a feature like a clear CMOS and bios flashback button would be useful. Being able to save your bios setings in a safe profile in case of a reset would also be nice
5 Likes
My thinking with regard to this thread specifically would be for those who seek to modify their open source BIOS. If they were tinkering with the source, adding/changing things, they’d be at substantially less risk of ending up with a bricked system and be substantially easier to test changes.
It’s also interesting to consider novel applications for framework hardware that aren’t a laptop configuration - some kind of custom device that needs an onboard computer. There’s really no way to predict how these components could be used or configured, so leaving the door open as wide as possible with as few tradeoffs as possible to satisfy the intended laptop only makes sense. In a situation where the motherboard/cpu combo is being used in a device, the bios switch could be used to change states of the device, for example - especially with open source bios.
2 Likes
I would love it when the bios is modifiable without the use of a eeprom programer or an method that requires an functional bios. It would make my own modding atempts with laptops bioses easier though i usually only enable hidden bios settings. For a coreboot developer this would probably be a dream feature
1 Like
Not exactly, if SPI controller is supported by flashing tool e.g. flashrom one can hot swap chips. It would work as follows:
- boot your platform to OS with functional BIOS storage
- while system booted remove BIOS storage
- place second chip (spare one) in socket
- flash development/debug version of coreboot/BIOS/UEFI
- reboot the platform and gather logs
- modify you coreboot/BIOS/UEFI code and repeat until you get working firmware
I will teach that technique in free OST2 training called Architecture 4032: coreboot Hands-On
1 Like