| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
|
|
The kernel module `kmod-usb-ledtrig-usbport` allows for multiple selections of
USB ports to trigger a single LED.
See https://www.kernel.org/doc/html/latest/leds/ledtrig-usbport.html
This simplest of fixes allows for selection one or more USB ports to trigger a LED.
The ASUS RT-AC88U router which is getting ported to OpenWrt by arinc9 has got an
USB 3.0 port at the front which will use different internal USB ports, depending
on if you connect an USB 2.0 device or an USB 3.0 device.
This fix/patch was tested on the mentioned router.
Signed-off-by: Thomas Kupper <thomas.kupper@gmail.com>
|
|
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
|
|
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
|
|
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
https://github.com/openwrt/openwrt/commit/d0b50c2770a0e2d54b37153f2801e2e7dc865fa6
So I have not ported the relevant code anymore.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
|
