638f5ce071
This commit creates the possibility that not only kernel-led-triggers can
be selected but also application-led-triggers from user space.
This is done via a plugin mechanism. The application-led-triggers are scripts
that set kernel-led-triggers on system events or services. Until now this
has not been possible. The package rssileds is a kind of
application-led-trigger.
The following new packages are added:
* luci-app-ledtrig-rssi (application-led-trigger)
* luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices
* luci-app-ledtrig-usport (kernel-led-trigger) optional trigger
Since we have now a plugin mechanism I have added the following triggers
as a dependency. So this triggers are now installed per default on LuCI
installation.
* kmod-ledtrig-default-on
* kmod-ledtrig-heartbeat
* kmod-ledtrig-netdev
* kmod-ledtrig-timer
The kernel trigger kmod-ledtrig-usbdev was removed with the commit
d0b50c2770
So I have not ported the relevant code anymore.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
16 lines
390 B
Makefile
16 lines
390 B
Makefile
#
|
|
# Copyright (C) 2020 TDT AG <development@tdt.de>
|
|
#
|
|
# This is free software, licensed under the Apache License Version 2.0.
|
|
# See https://www.apache.org/licenses/LICENSE-2.0 for more information.
|
|
#
|
|
|
|
include $(TOPDIR)/rules.mk
|
|
|
|
LUCI_TITLE:= LuCI Support for ledtrigger rssi
|
|
LUCI_DEPENDS:=+rssileds
|
|
LUCI_PKGARCH:=all
|
|
|
|
include ../../luci.mk
|
|
|
|
# call BuildPackage - OpenWrt buildroot signature
|