I created dtsi file for a family that will have a shared depthcharge across models, but with varying coreboot values. The chromeos-bootimage ebuild currently breaks for this case, as it relies on using the coreboot build target to find depthcharge.

Consider the following example model.dtsi:

&models {
        variant: variant {
                powerd-prefs = "variant";
                test-label = "variant";
                firmware {
                        bcs-overlay = "overlay-baseboard-private";
                        /* No Firmware URIs ready yet. */
                        no-firmware = "true";
                        build-targets {
                                coreboot = "variant";
                                ec = "variant";
                                depthcharge = "baseboard";
                                libpayload = "baseboard";
                        };
                };
        };
};

Iterating over just the coreboot build targets in src_compile() and src_install() will give the wrong path or target for depthcharge.

I have a local fix that seems to work to fix this, which I'll mail out.