staging/stintel/include/target.mk, branch master

targets: add REGULATOR_SUPPORT auto-feature

2026-03-01T09:59:19Z

Not all targets need regulator support, so they dont enable it as its disabled in the generic config by default. So, in order to allow kernel modules to depend on regulator support lets add a new feature flag "regulator" and set it automatically if target kernel config enables CONFIG_REGULATOR. Link: https://github.com/openwrt/openwrt/pull/22172 Signed-off-by: Robert Marko

build: purge DESCRIPTION

2026-01-24T10:03:40Z

DESCRIPTION field has been deprecated since 2007, yet internal exporting causes intermittent package build failures due to the deprecation check, even with packages that don't have that fields set. Replace all DESCRIPTION exports with alternative variables defined through shexport and shvar helpers and remove the check. Fixes: 547b127d ("make kernel module packaging code reusable and use it in madwifi") Fixes: 7558f028 ("DESCRIPTION:= is obselete, so complain if it is used and use TITLE if no description is set") Fixes: cc435322 ("build: optimize target metadata dump") Fixes: d081edf7 ("build: clean up and optimize ipkg control generator code") Signed-off-by: George Sapkin Link: https://github.com/openwrt/openwrt/pull/21668 Signed-off-by: Robert Marko

build: remove iwinfo dependency

2025-09-27T20:04:57Z

Do not always try to include iwinfo in the images when wpa supplicant or Broadcom nas is also included. iwinfo is incompatible with current default configuration. iwinfo is only build when CONFIG_WIFI_SCRIPTS_UCODE is not set. If CONFIG_WIFI_SCRIPTS_UCODE is not set kmod-cfg80211 depends on iwinfo, so it should be included in all images with wifi drivers. The CONFIG_WIFI_SCRIPTS_UCODE option was recently changed to be active by default. This should fix the current buildbot build failures. This reverts commit 6435b8bb27ea ("build: include iwinfo by default if nas or wpad(-mini) is selected") Fixes: 04e9929c47e9 ("wifi-scripts: enable ucode scripts by default") Link: https://github.com/openwrt/openwrt/pull/20211 Signed-off-by: Hauke Mehrtens

build: use --no-print-directory for dumping subtargets

2025-07-30T21:31:26Z

Or else we end up with "Entering directory" and "Leaving directory" from make in tmp/.targetinfo Signed-off-by: Sven Wegener Link: https://github.com/openwrt/openwrt/pull/19326 Signed-off-by: Robert Marko

targets: add USES_PM auto-feature

2025-07-20T11:16:13Z

Not all targets support power management, some older or more simple targets don't have CONFIG_PM set. Allow kernel module packages to depend on USES_PM to only be available on targets which got CONFIG_PM=y in their kernel config. Signed-off-by: Daniel Golle

targets: add PINCTRL_SUPPORT auto-feature

2025-07-19T12:54:22Z

Not all targets have CONFIG_PINCTRL=y set in their kernel config. Let's introduce a feature for that so kernel module packages which select or depend on CONFIG_PINCTRL=y may depend on that, so we can try to prevent leaking CONFIG_PINCTRL=y also into targets which do not require it. Signed-off-by: Daniel Golle

kernel: Fix patch folders setting for test kernel

2025-04-23T08:29:14Z

Move kernel-version.mk include to proper place to properly set patch folders for test kernel. Fixes: 8865dadea7b94e7859b416d3b1931b897ea43c48 Signed-off-by: Mieczyslaw Nalewaj

kernel: move kernel version files to linux/generic directory

2025-04-22T17:22:44Z

To further improve cleanup and maintenance usage, move the kernel version files to target/linux/generic directory. This permits to self contain any change to the specific generic directory instead of having to bload the include directory of periodic changes. In kernel-version.mk we now use GENERIC_PLATFORM_DIR provided by target.mk. To make this work, we need to move the inclusion of kernel-version.mk in target.mk right after GENERIC_PLATFORM_DIR is defined. This also comes to permit downstream project to provide a custom generic directory and specify the kernel version complete of the hash and the minor version without having to affect other feeds. In such case both generic and the target directory are provided as feeds and OpenWrt reference these specific one instead of the generic one. For downstream it's still suggested and preferable to all match the shipped generic kernel minor version but this change permits to at least enforce good practice instead of having to bloat OpenWrt include file of all kind of downstream changes (making porting to OpenWrt mainline even more difficult) Link: https://github.com/openwrt/openwrt/pull/18537 Signed-off-by: Christian Marangi

include: move generic riscv64 ISA to rv64gc

2025-04-13T14:43:31Z

The current CFLAGS (rv64imafdc) for the riscv64 targets do not contain the full generic compute extension (g), as that also includes the zicsr and zifencei extensions/instructions. Rename the default ISA to 'generic' to add distinction to the current binaries (although it's very minimal), and use rv64gc for CFLAGS. This is also a prep step for the upcoming gcv (vector-extension supporting) targets like the Spacemit K1, and the thead-cores like the TH1520. Compile-tested: all riscv64 targets Runtime-tested: - SiFive Unleashed (FU540) - SiFive Unmatched (FU740) - Nezha D1 (D1) - VisionFive2 (JH7110) Link: https://github.com/openwrt/openwrt/pull/18094 Tested-by: Chuanhong Guo # siflower target Signed-off-by: Zoltan HERPAI

target.mk: Fix features detection for PWM

2025-03-28T11:38:33Z

kmod-leds-pwm depends on @PWM_SUPPORT, instead of adding pwm to the features env for specific targets, use the existing detection method. Signed-off-by: Weikai Kong Link: https://github.com/openwrt/openwrt/pull/18185 Signed-off-by: Robert Marko