glodroid_manifest VS coreboot

GloDroid development seems to have been quite active since I last tried it, so I can’t really comment on how useful it might be right now.

Not sure if you know this but there is an AOSP build for the OG PinePhone running mainline Linux with patches.

Android right? As far as Android, there is the Glodroid project which I do have on a micro SD for my pinephone. It's actually quite smooth, but it doesn't support the baseband or the microphone at the moment, making it unusable as a phone OS.

Modem https://github.com/GloDroid/glodroid_manifest/issues/70 and GPS https://github.com/GloDroid/glodroid_manifest/issues/104 are still open issues on GloDroid. I think Bluetooth does not work either.

Google tracks you through the Google Mobile Services, which come preloaded on almost all Android phones and many custom ROMs like lineage. Projects like Glodroid do not include these, and therefore doesn't have things like the play store, instead you need to install APKs yourself or through F-Droid, but it's still Android and without the Google creepyness.

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