vimuser (Leah Rowe)

vimuser pushed to master at libreboot/libreboot

6e2b8e44e0 xbmk: cache builds in XBMK_CACHE/elf/ not elf/ this way, release builds will go faster because we re-use cached builds which are, due to recent design improvements, always reliably re-built and we can be sure that what's cached matches what's currently in config/ if ./mk release is done with uncommitted changes, that's OK because the hash checking is still done in the release directory, which would still make builds be re-done, and this would then update the hashes so the master tree would then re-build them later on, when doing a non-release build. this change enables more rapid release build testing, because we don't needlessly repeat certain builds. we still generate the source archive from a clean slate. Signed-off-by: Leah Rowe <leah@libreboot.org>

2 days ago

vimuser pushed to master at libreboot/lbmk

6e2b8e44e0 xbmk: cache builds in XBMK_CACHE/elf/ not elf/ this way, release builds will go faster because we re-use cached builds which are, due to recent design improvements, always reliably re-built and we can be sure that what's cached matches what's currently in config/ if ./mk release is done with uncommitted changes, that's OK because the hash checking is still done in the release directory, which would still make builds be re-done, and this would then update the hashes so the master tree would then re-build them later on, when doing a non-release build. this change enables more rapid release build testing, because we don't needlessly repeat certain builds. we still generate the source archive from a clean slate. Signed-off-by: Leah Rowe <leah@libreboot.org>

2 days ago

vimuser pushed to master at libreboot/libreboot

6e2b8e44e0 xbmk: cache builds in XBMK_CACHE/elf/ not elf/ this way, release builds will go faster because we re-use cached builds which are, due to recent design improvements, always reliably re-built and we can be sure that what's cached matches what's currently in config/ if ./mk release is done with uncommitted changes, that's OK because the hash checking is still done in the release directory, which would still make builds be re-done, and this would then update the hashes so the master tree would then re-build them later on, when doing a non-release build. this change enables more rapid release build testing, because we don't needlessly repeat certain builds. we still generate the source archive from a clean slate. Signed-off-by: Leah Rowe <leah@libreboot.org>

2 days ago

vimuser pushed to master at libreboot/lbmk

6e2b8e44e0 xbmk: cache builds in XBMK_CACHE/elf/ not elf/ this way, release builds will go faster because we re-use cached builds which are, due to recent design improvements, always reliably re-built and we can be sure that what's cached matches what's currently in config/ if ./mk release is done with uncommitted changes, that's OK because the hash checking is still done in the release directory, which would still make builds be re-done, and this would then update the hashes so the master tree would then re-build them later on, when doing a non-release build. this change enables more rapid release build testing, because we don't needlessly repeat certain builds. we still generate the source archive from a clean slate. Signed-off-by: Leah Rowe <leah@libreboot.org>

2 days ago

vimuser pushed to master at libreboot/libreboot

dac3d6d06a rom.sh: Don't build coreboot utils if dry=":" This fixes a build error when doing ./mk release, after a regression caused by the last few commits. Signed-off-by: Leah Rowe <leah@libreboot.org>
6f7525a5b3 cache coreboot builds in elf/ again This was a problem when I did it before, because individual target builds weren't automatically re-compiled when needed. The recent design improvements in lbmk enable this to be done again. Cached images in elf/ have no payloads, so they are a liability, therefore they are padded by one byte to prevent flashing. This solves the problem that the previous caching had. With this change, modifying payloads can be tested without needing to re-build coreboot each time. The cached coreboot builds are also automatically re-built when needed, which is another improvement this time, compared to the last time coreboot builds were cached in this manner. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

2 days ago

vimuser pushed to master at libreboot/lbmk

dac3d6d06a rom.sh: Don't build coreboot utils if dry=":" This fixes a build error when doing ./mk release, after a regression caused by the last few commits. Signed-off-by: Leah Rowe <leah@libreboot.org>
6f7525a5b3 cache coreboot builds in elf/ again This was a problem when I did it before, because individual target builds weren't automatically re-compiled when needed. The recent design improvements in lbmk enable this to be done again. Cached images in elf/ have no payloads, so they are a liability, therefore they are padded by one byte to prevent flashing. This solves the problem that the previous caching had. With this change, modifying payloads can be tested without needing to re-build coreboot each time. The cached coreboot builds are also automatically re-built when needed, which is another improvement this time, compared to the last time coreboot builds were cached in this manner. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

2 days ago

vimuser pushed to master at canoeboot/cbmk

2e906fb4d3 tree.sh: delete individual target builds if needed Detect when a config changes. This is done even if the entire tree doesn't change. This is already done per-tree if files change, but individual project files don't change. For example, if a grub.cfg changes, the given cached build for that GRUB tree isn't deleted. Same thing if a given U-Boot config doesn't change. This patch fixes a longstanding design flaw of lbmk, making auto-re-builds more reliable. This complements another recent change, that deletes all target builds of a given tree when the tree changes. Signed-off-by: Leah Rowe <leah@libreboot.org>
d4cf50173c tree.sh: Remove redundant deletion Target builds go inside a common directory for the given tree now, which gets deleted, thus deleting all target builds of that given tree. Therefore, the deletion being removed is redundant. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

2 days ago

vimuser pushed to master at libreboot/libreboot

7c6c9ff547 tree.sh: delete individual target builds if needed Detect when a config changes. This is done even if the entire tree doesn't change. This is already done per-tree if files change, but individual project files don't change. For example, if a grub.cfg changes, the given cached build for that GRUB tree isn't deleted. Same thing if a given U-Boot config doesn't change. This patch fixes a longstanding design flaw of lbmk, making auto-re-builds more reliable. This complements another recent change, that deletes all target builds of a given tree when the tree changes. Signed-off-by: Leah Rowe <leah@libreboot.org>
fb95230a4c tree.sh: Remove redundant deletion Target builds go inside a common directory for the given tree now, which gets deleted, thus deleting all target builds of that given tree. Therefore, the deletion being removed is redundant. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

2 days ago

vimuser pushed to master at libreboot/lbmk

7c6c9ff547 tree.sh: delete individual target builds if needed Detect when a config changes. This is done even if the entire tree doesn't change. This is already done per-tree if files change, but individual project files don't change. For example, if a grub.cfg changes, the given cached build for that GRUB tree isn't deleted. Same thing if a given U-Boot config doesn't change. This patch fixes a longstanding design flaw of lbmk, making auto-re-builds more reliable. This complements another recent change, that deletes all target builds of a given tree when the tree changes. Signed-off-by: Leah Rowe <leah@libreboot.org>
fb95230a4c tree.sh: Remove redundant deletion Target builds go inside a common directory for the given tree now, which gets deleted, thus deleting all target builds of that given tree. Therefore, the deletion being removed is redundant. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

2 days ago

vimuser pushed to master at libreboot/libreboot

e25bca2ef7 T480/T480: Drop redundant PcieRpEnable from dt Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/lbmk

e25bca2ef7 T480/T480: Drop redundant PcieRpEnable from dt Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at canoeboot/cbmk

82b0b05ed3 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>
4dda8a24f3 rom.sh: bump pcsx-redux copyright date to 2025 it's 2019-2025 now, not 2019-2024, because i recently imported new pcsx-redux upstream changes that go up to June 2025. Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

4 days ago

vimuser pushed to master at libreboot/libreboot

cc82b733d3 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>
a5ddc1c4a6 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

4 days ago

vimuser pushed to master at libreboot/lbmk

cc82b733d3 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>
a5ddc1c4a6 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>
View comparison for these 2 commits »

4 days ago

vimuser pushed to master at libreboot/libreboot

a5ddc1c4a6 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/lbmk

a5ddc1c4a6 tree.sh: Place target builds under tree/target/ as opposed to target/ for example: image the command: ./mk -b u-boot amd64coreboot This would put the U-Boot binaries here: elf/u-boot/amd64coreboot/default/ With this change, they now go here: elf/u-boot/x86_64/amd64coreboot/default/ This solves a problem that existed previously, where you could modify a given tree in a multi-tree project, but cached builds for targets branching separately off of each tree would not be deleted, and thus not re-built. This accomplishes such a result, without needing to further check hashes of individual targets. The latter will still be done, in a future change, because this change doesn't fix another problem: If you change a given config, e.g. targetname "foo" which uses tree "bar", elf/foo/ would not be removed automatically for re-build. So this change only deletes individual target builds when their master tree changes. Where the target and tree are the same, this also means elf/tree/target/ for example: seabios/default would create binaries in: elf/seabios/default/default/ not: elf/seabios/default/ Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/libreboot

9541dfcefa rom.sh: bump pcsx-redux copyright date to 2025 it's 2019-2025 now, not 2019-2024, because i recently imported new pcsx-redux upstream changes that go up to June 2025. Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/lbmk

9541dfcefa rom.sh: bump pcsx-redux copyright date to 2025 it's 2019-2025 now, not 2019-2024, because i recently imported new pcsx-redux upstream changes that go up to June 2025. Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/libreboot

91a63ccd1f hppro3500: enlarge CBFS to match the BIOS region i enlarged the BIOS region in a previos commit, but I forgot to enlarge CBFS. it's the policy of lbmk to enlarge CBFS when possible, after applying a truncated ME configuration. Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago

vimuser pushed to master at libreboot/lbmk

91a63ccd1f hppro3500: enlarge CBFS to match the BIOS region i enlarged the BIOS region in a previos commit, but I forgot to enlarge CBFS. it's the policy of lbmk to enlarge CBFS when possible, after applying a truncated ME configuration. Signed-off-by: Leah Rowe <leah@libreboot.org>

4 days ago