coreboot VS howdy

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

you can even use facial recognition with IR webcam

Source

I just bought a go 2 (not laptop go) this weekend and installed fedora 37 on it. Almost everything worked without the surface kernel except the camera requires v4l2loopback kernel drivers to create a gstreamer device for apps that don’t support libcamera. There were only old versions available in copr but no surface kernel headers available so I couldn’t build the kernel modules. I switched to ubuntu 22.10 and got similar hardware support but more available packages. I’m still trying to figure out how to get the IR sensors to work so I can use howdy for login/sudo. https://github.com/boltgolt/howdy

First, you'll need to install Howdy.

I've tried using Howdy, but that doesn't seem to work. It's probably because of this issue

Just like with digicams, it is not just about the sensor, but also the image processing itself. Should we omit the IR sensor to replace it with a better firmware-based noise-reduction system? But what about "Howdy" / "Hello" users, if we go this route?