@libreleah
My point, here again dismissed, I don't know why, is that there is "black magic" or a "voodoo dance" that is not needed in libreboot flashing documentation for t480 (and I expect the same for t480s).
Science/engineering requires to repro things. t480 board owners, and myself challenging libreboot instructions, concluded that it was not needed to do aforementioned steps (erase spi through flash tool, then flash zeroed file, then tb.bin which is the only step needed, really), point still dismissed in your previous answers: stating libreboot docs can be referred as is. They should be corrected, and then Heads could refer to libreboot docs.
By lack of possible collababoration with libreboot, with attempts (plural) by board owners to chat in libreboot channel, me here: Heads documentation for t480 removed unneeded steps, board owner hacked upstream patchset used under libreboot. And this is why I call for upstream collaboration in the future.
I repeat, in this case, upstream code reference is libreboot until coreboot merges code. Documentation is libreboot for now until there is effort upstreaming our docs under coreboot docs: https://doc.coreboot.org/
Heads effort on t480 will not extend to t480s because there is no board owner technical enough that showed leadership to redo what was done for t480 (40h of unpaid/properly compensated time on my side here), while future might be brighter with mentorship done here, while I do not have the board nor plan to have all coreboot supported boards: Heads is a community effort; Heads requires technical board owners to take port lead/co-maintainership to thrive and propel other boards ports. In that regard, Heads is a coreboot payload; a linux based bootloader replacement with its own features and agenda. I repeat once more; there needs to be proper seperation of duties and understanding of who does what. Heads is not coreboot/libreboot/skulls as those are coreboot distributions packing already supported payloads; Heads is that payload with its own buildsystem to arrive to that goal, with reproducible build approach where roms are built reproducibly from CI is a directly flashable form. Heads doesn't pretend to be a coreboot distribution in the large sense of things, but needs to build coreboot to have its payload stitched in it, alongside all other blobs needed to have fully externally flashable roms/internally upgradable roms. Therefore, Heads needs to collaborate upstream/downstream for all its dependencies/forks/OEMs/rebrandings and time is limited.
TLDR: my suggestion, not demand, is that libreboot reviews its documentation for t480 in regard of tb.bin flashing from downstream Heads effort, which corrected the facts with lots of duplicated effort, reviews, iterations to arrive to its merged state, including participation upstream where it was possible.
Correction of facts:
This is not something personal, caprice. Its politics. To better the ecosystem if the real goal is to make this easy for users to flash, code to review/better, use, and ease support without constantly reinventing the wheel, duplicating efforts, etc. Otherwise we won't fill what I still believe is our common vision: to have coreboot on a maximum number of platforms out there, while easing developers onboarding on our projects. We need to unite here, not be enemies picking stupid ego fights. We need to take time and reflect on what we do and how we do it, if, of course, the mission is aligned with vision.
Leah Rowe is not a Rowebot
Thierry Laurion
All GNU social JP content and data are available under the