summaryrefslogtreecommitdiffstats
path: root/target/linux/generic-2.6/patches-2.6.23/402-ledtrig_default_on.patch
Commit message (Collapse)AuthorAgeFilesLines
* remove 2.6.23 support, as the last target using that has been nuked, tookaloz2009-06-011-21/+0
| | | | git-svn-id: svn://svn.openwrt.org/openwrt/trunk@16275 3c298f89-4303-0410-b956-a3cf2f4a3e73
* [kernel] generic-2.6/2.6.23: refresh patchesjuhosg2009-02-081-2/+2
| | | | git-svn-id: svn://svn.openwrt.org/openwrt/trunk@14448 3c298f89-4303-0410-b956-a3cf2f4a3e73
* refresh generic 2.6.23 patches in upstream stylekaloz2008-06-051-10/+6
| | | | git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11366 3c298f89-4303-0410-b956-a3cf2f4a3e73
* [kernel] refresh generic 2.6.23 patchesjuhosg2008-05-181-8/+10
| | | | git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11187 3c298f89-4303-0410-b956-a3cf2f4a3e73
* "default-on" LED Triggernbd2008-02-021-0/+23
The current LED subsystem always initialises LEDs in the OFF state. This is fine for most LEDs but some should be on right from boot (e.g. POWER LED). Following some discussion with the LED subsystem maintainers, a trigger was recommended as the best way to implement this functionality. Here is a patch to add a new trigger "default-on" which will initialise an LED in the ON state. It is not compiled by default. Particular thanks to Rod Whitby for all his help with this. Signed-off-by: Nick Forbes <nick.forbes@incepta.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10348 3c298f89-4303-0410-b956-a3cf2f4a3e73