gimp VS coreboot

GIMP: C, not C++

GIMP - https://gitlab.gnome.org/GNOME/gimp

GIMP

How are they implement? https://gitlab.gnome.org/GNOME/gimp https://github.com/figma

As u/schumaml said already, we have an issue tracker: https://gitlab.gnome.org/GNOME/gimp/

The former might be something you want to report as an issue at https://gitlab.gnome.org/GNOME/gimp, with the XCF file used for your cover image - or a mockup exhibiting the same issue - attached.

As Gimp is open source, I already had a look in the source code but it's written in C, which is different enough from C++ or C# that I have a rather difficult time understanding it, at least in terms of project structure. I'm pretty sure I found the handling of the tool itself in gimpoperationcolorize.c but I don't know where to go from here.

> Gotta be real, Gimp's not that far off from just one guy (https://github.com/GNOME/gimp/graphs/contributors)

GitHub only shows people with an email address linked to a GitHub account in that chart; the last time I checked it was 4 or 5 people working on it regularly, which is still a very small team (none are working on it full-time) so your point still stands (it's a point I've made myself a few times before when people compare GIMP to Photoshop or the like).

Maybe not the best example. The one on github is just a mirror of this one.

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