thinkpad-ec VS coreboot

Hi all, some of you might be familiar with the T430 classic keyboard hack. I seem to be stuck. I followed the instructions here to physically modify the keyboard. I downgraded my BIOS to the 2.81 version. I installed Linux Mint on a spare SSD, booted into it, and followed the github instructions here to create the bootable USB. However, when I boot the USB to modify the firmware, I run into an error message before it starts. I'm not quite sure what it means or how to get it to proceed. Does anyone have any experience with this?

If your notebook is a thinkpad from the xx30 series you can do a custom keymap for the embedded controller with thinpad-ec - you'd need to flash back bios, update EC, flash back coreboot. I've done that to have a native dvorak keyboard with control on the right position.

In regards to unlocking third-party batteries on the Ivy Bridge ThinkPad laptops, this is handled by the embedded controller firmware, stored on a completely separate chip from the system firmware. On these systems, coreboot is not concerned with the embedded controller functionality at all. There is a separate project that handles this: thinkpad-ec

Link to EC Flash: https://github.com/hamishcoleman/thinkpad-ec

I bought an aliexpress battery and have gone through the process of the battery patch. I can now run with the battery, and get a decent 6ish hours off of it. Fantastic.

Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.

1: https://www.coreboot.org/

Coreboot is 0.6% C++.

NovaCustom ; some models come with Dasharo a coreboot distribution.

You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.

Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.

why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c

use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos

There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.

does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c

Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid