RepoMirrors
/
linux-firmware
mirror of git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
linux-firmware/Makefile

49 lines
1.1 KiB
Makefile
Raw Normal View History

build: Implement minimal GNOME Build API One more step on the road to entirely eliminating the concept of packages. I adapted the installation rules from the Fedora spec file. They should clearly be less lame, but to do so we'd need more formal rules about which files should be installed. Maybe just limit it to things ending in ".bin" or ".fw"? See http://people.gnome.org/~walters/docs/build-api.txt Signed-off-by: Colin Walters <walters@verbum.org> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
2012-05-21 22:37:20 +00:00
# This file implements the GNOME Build API:
# http://people.gnome.org/~walters/docs/build-api.txt
FIRMWAREDIR = /lib/firmware
all:
Add a metadata consistency check script The script compares the files listed in WHENCE (or otherwise expected) and the files known to git, and reports all differences as errors. Add a 'check' rule to the Makefile that runs this. Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2016-09-18 00:44:04 +00:00
check:
Makefile, copy-firmware: Use portable "command -v" to detect installed programs The "which" utility is not guaranteed to be installed either, and if it is, its behavior is not portable either. This means that when rdfind / pre-commit are installed, the `which` check will report a fatal error because the which tool did not exist and the shell returned a nonzero status when attempting to fork+exec. If it did exist, it might not be an implementation of `which` that returns nonzero when commands do not exist. Conversely, the "command -v" shell builtin is required to exist in all POSIX 2008 compliant shells, and is thus guaranteed to work everywhere. For some in-depth discussions on the topic, see: - https://mywiki.wooledge.org/BashFAQ/081 - https://unix.stackexchange.com/questions/85249/why-not-use-which-what-to-use-then/85250#85250 Examples of open-source shells likely to be installed as /bin/sh on Linux, which implement the 15-year-old standard: ash, bash, busybox, dash, ksh, mksh and zsh. A side benefit of using the POSIX portable option is that it requires neither an external disk executable, nor (because unlike "which", the exit code is reliable) a subshell fork. This therefore represents a mild speedup. Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
2023-11-26 17:01:51 +00:00
@if ! command -v pre-commit >/dev/null; then \
Wire up pre-commit to `make check` This will let `make check` cover more things than just `WHENCE`. Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
2023-08-15 17:52:13 +00:00
echo "Install pre-commit to check files"; \
exit 1; \
fi
@pre-commit run --all-files
Add a metadata consistency check script The script compares the files listed in WHENCE (or otherwise expected) and the files known to git, and reports all differences as errors. Add a 'check' rule to the Makefile that runs this. Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2016-09-18 00:44:04 +00:00
Add new toplevel 'make dist' target. This target produces a tarball following the most recent git tag. The tarball contains firmware binaries that have been de-duped. Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
2023-08-31 03:50:40 +00:00
dist:
@mkdir -p release dist
./copy-firmware.sh release
@TARGET=linux-firmware_`git describe`.tar.gz; \
cd release && tar -czf ../dist/$${TARGET} *; \
echo "Created dist/$${TARGET}"
@rm -rf release
Add new Makefile target to build a deb and rpm package The package would put all files into /lib/firmware/updates to avoid conflicting with distro packages. The package is also intentionally named to avoid conflicts with distro packages. Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
2023-09-18 21:15:35 +00:00
deb:
./build_packages.py --deb
rpm:
./build_packages.py --rpm
make: separate installation and de-duplication targets For better or worse some distributions cannot have the firmware de-duplication happen automatically. In addition, when it was introduced it changed the default behaviour leaving people with no firmware in their systems. Revert to the original behaviour: in the worst case, people will have a few MB extra of duplicate firmware, yet their systems will continue to work. To make things stand out, we print a message at the end of install so that everyone can opt-in as needed. In addition, I've went ahead and opened tentative MR/PR with Alpine, Arch, CentOS Stream, Debian, Gentoo, informing them of this change. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-10-15 17:56:03 +00:00
dedup:
copy-firmware.sh: flesh out and fix dedup-firmware.sh Flesh out the de-duplication logic in separate script. The copy-firmware.sh is already complex enough and de-duplication doesn't really fit in there. In the process we migrate away from the open-coded `ln --relative`. We also avoid touching symlinks, which are not created by rdfind. Otherwise we end up "fixing" the folder to folder symlinks (created earlier in the process) and things explode. As result we also get a few bonuses: - the COPYOPTS shell injection is gone - the variable was never used - people can dedup as separate step if/when they choose to do so Aside: based on the noise in git log and around distros ... I'm wondering if having the de-duplication as opt-in, would have been better. Is it too late to change or the ship has sailed? Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-09-22 15:21:44 +00:00
./dedup-firmware.sh $(DESTDIR)$(FIRMWAREDIR)
Makefile, copy-firmware: support xz/zstd compressed firmware The kernel has supported compressed firmware for quite some time. So let's add a couple of targets to produce that. In practical terms this means it we'll use ~5x times less space on disk. Reportedly the amd ucode, needs to be uncompressed _within_ the initrd in order to work. Using compressed ucode in late load just works. Ideally this will be addressed by the initrd generators, but considering the files are tiny in size let's skip the compression. v2 - commit message, skip compression for files annotated as Raw v3 - rebase [Drop extra verbose statement in zstd case, Josh Boyer <jwboyer@kernel.org>] Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2023-06-05 13:58:12 +00:00
make: separate installation and de-duplication targets For better or worse some distributions cannot have the firmware de-duplication happen automatically. In addition, when it was introduced it changed the default behaviour leaving people with no firmware in their systems. Revert to the original behaviour: in the worst case, people will have a few MB extra of duplicate firmware, yet their systems will continue to work. To make things stand out, we print a message at the end of install so that everyone can opt-in as needed. In addition, I've went ahead and opened tentative MR/PR with Alpine, Arch, CentOS Stream, Debian, Gentoo, informing them of this change. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-10-15 17:56:03 +00:00
install:
Make rdfind optional A number of distributions don't include rdfind by default. This is an optimization, so make it optional via a --ignore-duplicates option and a new make target. Distributions that include rdfind should add it as a dependency for their linux-firmware package. Those that don't should use the new target or option. Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2023-11-27 15:13:42 +00:00
install -d $(DESTDIR)$(FIRMWAREDIR)
copy-firmware.sh: flesh out and fix dedup-firmware.sh Flesh out the de-duplication logic in separate script. The copy-firmware.sh is already complex enough and de-duplication doesn't really fit in there. In the process we migrate away from the open-coded `ln --relative`. We also avoid touching symlinks, which are not created by rdfind. Otherwise we end up "fixing" the folder to folder symlinks (created earlier in the process) and things explode. As result we also get a few bonuses: - the COPYOPTS shell injection is gone - the variable was never used - people can dedup as separate step if/when they choose to do so Aside: based on the noise in git log and around distros ... I'm wondering if having the de-duplication as opt-in, would have been better. Is it too late to change or the ship has sailed? Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-09-22 15:21:44 +00:00
./copy-firmware.sh $(DESTDIR)$(FIRMWAREDIR)
make: separate installation and de-duplication targets For better or worse some distributions cannot have the firmware de-duplication happen automatically. In addition, when it was introduced it changed the default behaviour leaving people with no firmware in their systems. Revert to the original behaviour: in the worst case, people will have a few MB extra of duplicate firmware, yet their systems will continue to work. To make things stand out, we print a message at the end of install so that everyone can opt-in as needed. In addition, I've went ahead and opened tentative MR/PR with Alpine, Arch, CentOS Stream, Debian, Gentoo, informing them of this change. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-10-15 17:56:03 +00:00
@echo "Now run \"make dedup\" to de-duplicate any firmware files"
Make rdfind optional A number of distributions don't include rdfind by default. This is an optimization, so make it optional via a --ignore-duplicates option and a new make target. Distributions that include rdfind should add it as a dependency for their linux-firmware package. Those that don't should use the new target or option. Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2023-11-27 15:13:42 +00:00
Makefile, copy-firmware: support xz/zstd compressed firmware The kernel has supported compressed firmware for quite some time. So let's add a couple of targets to produce that. In practical terms this means it we'll use ~5x times less space on disk. Reportedly the amd ucode, needs to be uncompressed _within_ the initrd in order to work. Using compressed ucode in late load just works. Ideally this will be addressed by the initrd generators, but considering the files are tiny in size let's skip the compression. v2 - commit message, skip compression for files annotated as Raw v3 - rebase [Drop extra verbose statement in zstd case, Josh Boyer <jwboyer@kernel.org>] Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2023-06-05 13:58:12 +00:00
install-xz:
install -d $(DESTDIR)$(FIRMWAREDIR)
./copy-firmware.sh --xz $(DESTDIR)$(FIRMWAREDIR)
make: separate installation and de-duplication targets For better or worse some distributions cannot have the firmware de-duplication happen automatically. In addition, when it was introduced it changed the default behaviour leaving people with no firmware in their systems. Revert to the original behaviour: in the worst case, people will have a few MB extra of duplicate firmware, yet their systems will continue to work. To make things stand out, we print a message at the end of install so that everyone can opt-in as needed. In addition, I've went ahead and opened tentative MR/PR with Alpine, Arch, CentOS Stream, Debian, Gentoo, informing them of this change. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-10-15 17:56:03 +00:00
@echo "Now run \"make dedup\" to de-duplicate any firmware files"
Makefile, copy-firmware: support xz/zstd compressed firmware The kernel has supported compressed firmware for quite some time. So let's add a couple of targets to produce that. In practical terms this means it we'll use ~5x times less space on disk. Reportedly the amd ucode, needs to be uncompressed _within_ the initrd in order to work. Using compressed ucode in late load just works. Ideally this will be addressed by the initrd generators, but considering the files are tiny in size let's skip the compression. v2 - commit message, skip compression for files annotated as Raw v3 - rebase [Drop extra verbose statement in zstd case, Josh Boyer <jwboyer@kernel.org>] Cc: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2023-06-05 13:58:12 +00:00
install-zst:
install -d $(DESTDIR)$(FIRMWAREDIR)
./copy-firmware.sh --zstd $(DESTDIR)$(FIRMWAREDIR)
make: separate installation and de-duplication targets For better or worse some distributions cannot have the firmware de-duplication happen automatically. In addition, when it was introduced it changed the default behaviour leaving people with no firmware in their systems. Revert to the original behaviour: in the worst case, people will have a few MB extra of duplicate firmware, yet their systems will continue to work. To make things stand out, we print a message at the end of install so that everyone can opt-in as needed. In addition, I've went ahead and opened tentative MR/PR with Alpine, Arch, CentOS Stream, Debian, Gentoo, informing them of this change. Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
2024-10-15 17:56:03 +00:00
@echo "Now run \"make dedup\" to de-duplicate any firmware files"
Add new toplevel 'make dist' target. This target produces a tarball following the most recent git tag. The tarball contains firmware binaries that have been de-duped. Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
2023-08-31 03:50:40 +00:00
clean:
rm -rf release dist