Master #5
Open
Master #5
+600,591
−787,097
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c-herz
force-pushed
the
be14-and-hostapd
branch
from
dc3ec4e
to
25d6825
Compare
github-actions
bot
added
target/airoha
target/apm821xx
target/archs38
target/armsr
target/ath79
target/bcm27xx
target/bcm4908
target/bcm63xx
target/imx
target/kirkwood
target/lantiq
target/layerscape
target/mediatek
target/mvebu
target/mxs
target/rockchip
target/sifiveu
target/tegra
target/zynq
target/imagebuilder
kernel
core packages
build/scripts/tools
GitHub/CI
labels
88ae8f208dd3 uclient-http: fix a typo Signed-off-by: Felix Fietkau <nbd@nbd.name>
Also remove vmlinuz-initramfs files from final imagebuilder image as these file are not needed. Fixes: c85348d ("imagebuilder: remove initramfs image files") Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
…elper Also supports assigning a VLAN ID based on the PSK Signed-off-by: Felix Fietkau <nbd@nbd.name>
- add support for configuring allowed radios for a vif - add support for monitor mode on multiple channels Signed-off-by: Felix Fietkau <nbd@nbd.name>
Analog to how we handle distfeeds with opkg, have the base feeds defined in a file in repositories.d instead of the base /etc/apk/repositories. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Link: #16940 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Analog to how we handle custom feeds in opkg, add a customfeeds.list for custom package feeds and mark it as a configuration file. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Link: #16940 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Since the start of the Realtek target OpenWrt works with RTL83XX as the target architecture. Upstream is using MACH_REALTEK_RTL instead. To simplify further development align that. Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de> Link: #16963 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Add a patch still under review to fix some errors. Refresh patch: - 003-libintl-compatibility.patch - 005-build_only_libs.patch - 006-Fix-build-on-aarch64-musl.patch Add patch: - 102-fix-potential-deref-of-null-error.patch Release notes are in the link below. Link: https://inbox.sourceware.org/elfutils-devel/CAJDtP-T3+gXqHWp3T0mejWWbPr0_1tHetEXwfB67-o+zz7ShiA@mail.gmail.com/T/#u Signed-off-by: Ryan Keane <the.ra2.ifv@gmail.com> Link: #16886 Signed-off-by: Robert Marko <robimarko@gmail.com>
Add mirrors.kernel.org as mirror, listed on sourceware mirror sites page. Link: https://sourceware.org/mirrors.html Signed-off-by: Ryan Keane <the.ra2.ifv@gmail.com> Link: #16886 Signed-off-by: Robert Marko <robimarko@gmail.com>
On aarch64 musl gcc 14.x compiler, trying compiling elfutils 0.192 with
lto option enabled will cause null-dereference error.
Example error message:
...
elf_compress.c: In function 'elf_compress':
elf_compress.c:675:26: error: potential null pointer dereference [-Werror=null-dereference]
675 | shdr->sh_flags |= SHF_COMPRESSED;
| ^
elf_compress_gnu.c: In function 'elf_compress_gnu':
elf_compress_gnu.c:127:25: error: potential null pointer dereference [-Werror=null-dereference]
127 | shdr->sh_size = new_size;
| ^ ^
...
This is a false postive warning but will abort compilation if gcc has
`-Werror` flag. This commit add a patch for this, see the bugzilla
report below.
This commit backports a series of patches to fix some errors.
Add patch:
- 007-add-libeu-symbols-to-libelf.patch
- 008-fix-autoconf-ENABLE_IMA_VERIFICATION.patch
- 009-fix-null-dereference-with-lto.patch
Link: https://sourceware.org/bugzilla/show_bug.cgi?id=32311
Signed-off-by: Ryan Keane <the.ra2.ifv@gmail.com>
Link: #16886
Signed-off-by: Robert Marko <robimarko@gmail.com>
Currently the build fails due to the following: mv: cannot stat 'linux-mediatek_filogic/target-dir-7872e783/etc/apk/repositories': No such file or directory as the changes done in the commit e031dab ("base-files: move apk distfeeds into directory") forget to adapt image generation part. While looking into this, I've realized, that we don't need this explicit handling in the image generating code since the feeds are solely configured by `base-files` and `apk` packages, so those should always provide the correct feeds content, so lets simply drop this unnecessary code. Moving away /etc/opkg is done to prevent opkg from picking up the remote feeds defined from base-files and only use the local feeds, but for apk we explicitly pass --repositories-file which disables parsing of /etc/apk/repositories and /etc/apk/repositories.d, so we do not need to backup anything. Fixes: #16981 Fixes: e031dab ("base-files: move apk distfeeds into directory") Reported-by: Chen Minqiang <ptpt52@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> [jonas.gorski: add an explicit explanation where the original mv comes from and why we don't need it for apk]. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
Note that the old ad-hoc method did not explicitly align backup data to 64 KiB boundaries. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com> Link: #16505 Signed-off-by: Robert Marko <robimarko@gmail.com>
Note that the old ad-hoc method did not explicitly align backup data to 64 KiB boundaries. Also note that the qnap 301w has a 'rootfs_data' partition in the eMMC that is being ignored by fstools during boot, presumably due to a bug. This is why the partition is also ignored in the sysupgrade code and there is no definition of CI_DATAPART="rootfs_data". Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com> Link: #16505 Signed-off-by: Robert Marko <robimarko@gmail.com>
Alphabetically sort devices in platform.sh Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com> Link: #16505 Signed-off-by: Robert Marko <robimarko@gmail.com>
All ipq807x devices that were using the legacy 'mmc_do_upgrade' eMMC sysupgrade code were ported to the replacement 'emmc_do_upgrade' code. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com> Link: #16505 Signed-off-by: Robert Marko <robimarko@gmail.com>
This tool was build in the phase 2 build, there the TARGET dependencies are probably not meat. Mark it as non shared to build it together with the targets where this option is set. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Link: #16975 Signed-off-by: Robert Marko <robimarko@gmail.com>
This tool was build in the phase 2 build, there the TARGET_mvebu_cortexa9_DEVICE_cznic_turris-omnia dependecy was probably not meat. Mark it as non shared to build it together with the target where this option is set. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Link: #16975 Signed-off-by: Robert Marko <robimarko@gmail.com>
Move settings CONFIG_INTEL_MEI_GSC_PROXY, CONFIG_INTEL_MEI_HDCP and CONFIG_INTEL_MEI_PXP to target generic. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com> Link: #16971 Signed-off-by: Robert Marko <robimarko@gmail.com>
This symbol is no longer present. Signed-off-by: Rosen Penev <rosenp@gmail.com> Link: #16770 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
These get dynamically set based on compiler version. Not relevant for targets. Signed-off-by: Rosen Penev <rosenp@gmail.com> Link: #16770 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
The config_get_bool also works with on/off, yes/no, true/false. Add 'main' section name. This will make it easier to change settings from uci. Add a link to documentation. Signed-off-by: Sergey Ponomarev <stokito@gmail.com> Link: #15579 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Escape special char for package description for APK mkpkg as the description is passed as an args to mkpkg with --info option and can easily escape from the "". Currently escaped char `, $, ", \. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
CONFIG_FB_INTEL is now visible on x86 since i915 driver is packaged as kmod now and it stops compilation, so add it to the generic config. Signed-off-by: Robert Marko <robimarko@gmail.com>
Remove the remaining special handling of procd-ujail in a same way as the rest of the packages was handled in the commit 4c65359 ("build: fix including busybox, procd and apk/opkg in imagebuilder"). Fixes: 44598c2 ("build: remove broken dependency of metadata on toplevel .config variables") Signed-off-by: Petr Štetiar <ynezz@true.cz> Link: #16986 Signed-off-by: Robert Marko <robimarko@gmail.com>
It seems, that handling of DEFAULT_PACKAGES is needed in more places, so lets move it into dedicated include file so it can be easily shared. Signed-off-by: Petr Štetiar <ynezz@true.cz> Link: #16986 Signed-off-by: Robert Marko <robimarko@gmail.com>
Robert reported, that in firmware images generated by ASU, there is `apk` package manager missing after the commit 44598c2 ("build: remove broken dependency of metadata on toplevel .config variables"). That is happening, because apk got removed from `default_packages` list in `profiles.json`, which is being generated by `json_overview_image_info` Make target, which uses `scripts/json_overview_image_info.py` helper script, which gets the information from `DEFAULT_PACKAGES` Make variable. So lets fix it by providing `DEFAULT_PACKAGES` variable when its needed. The reason why we didn't added those packages as a dependency to base-files like any other packages, was to allow disabling them (in order to save space). Fixes: #16969 Fixes: openwrt/asu/issues/1084 Fixes: 44598c2 ("build: remove broken dependency of metadata on toplevel .config variables") Reported-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> Link: #16986 Signed-off-by: Robert Marko <robimarko@gmail.com>
DEFAULT_PACKAGES handling was moved in commit 40be892 ("imagebuilder: move handling of DEFAULT_PACKAGES into shareable place") to `include/default-packages.mk`, but they weren't removed from ImageBuilder's Makefile, so lets remove it now. Once removed, I've noticed, that it stopped working as there is target.mk included later in that file, overriding the DEFAULT_PACKAGES again, so moved it after this target.mk include. Fixes: 40be892 ("imagebuilder: move handling of DEFAULT_PACKAGES into shareable place") Signed-off-by: Petr Štetiar <ynezz@true.cz>
Fix various issues, including potential crashes Signed-off-by: Felix Fietkau <nbd@nbd.name>
Sync patch with upstream version and tag them. Minor changes done to Pinctrl patch to support older kernel. Patch automatically refreshed with make target/linux/refresh. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Add ubihealthd to the nand-utils package, auto-create UCI config for each UBI device and launch the daemon on boot. The default time interval between scrubbing a random PED is 120 seconds which means that a fully used 128 MiB flash chip gets scrubbed in about a day and a half. The interval can be adjusted in UCI using the 'interval' option. Suggested-by: Rodrigo Balerdi <lanchon@gmail.com> Signed-off-by: Daniel Golle <daniel@makrotopia.org> Link: #16973 Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Now that omnia-eeprom is marked nonshared building the cortex-a9 mvebu
subtarget will fail with:
ERROR: unable to select packages:
omnia-eeprom (no such package):
required by: world[omnia-eeprom]
This is because omnia-eeprom depends on TARGET_mvebu_cortexa9_DEVICE_cznic_turris-omnia
which will not be satisfied in buildbots since CONFIG_TARGET_ALL_PROFILES
and CONFIG_TARGET_PER_DEVICE_ROOTFS are set in which case
CONFIG_TARGET_mvebu_cortexa9_DEVICE_cznic_turris-omnia is not set.
So, lets simply depend on the mvebu/cortex-a9 subtarget.
Fixes: 371e7be ("omnia-eeprom: Mark it nonshared")
Link: #17007
Signed-off-by: Robert Marko <robimarko@gmail.com>
The broadcom PHY driver only has to depend upon PTP_1588_CLOCK_OPTIONAL if NETWORK_PHY_TIMESTAMPING is enabled. The PTP functionality is stubbed in this case. Reflect this circumstance in the dependence condition. This allows to build the driver as a built-in module even if PTP is built as a module. This is required to include the broadcom PHY module regardless of the built-setting of the PTP subsystem. On ath79 (and probably more) targets with Broadcom PHY, Gigabit operation is currently broken as the PHY driver is only built as a module in case all kernel-packages are built. Due to this circumstance, affected devices fall back to using the generic PHY driver. Signed-off-by: David Bauer <mail@david-bauer.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for your contribution to OpenWrt!
To help keep the codebase consistent and readable,
and to help people review your contribution,
we ask you to follow the rules you find in the wiki at this link
https://openwrt.org/submitting-patches
Please remove this message before posting the pull request.