Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v17.01.1
  • v17.01.0
  • v17.01.0-rc2
  • v17.01.0-rc1
  • reboot
6 results
Search by author
  • Any Author
0 authors
  1. Oct 22, 2016
    • Rafał Miłecki's avatar
      base-files: add ucidef_set_led_usbport for full usbport support · 2187f57d
      Rafał Miłecki authored 
      
This helper allows using usbport trigger directly. It requires usbport
compatible syntax and supports specifying multiple USB ports, e.g.:
ucidef_set_led_usbport "usb" "USB" "devicename:colour:function" "usb1-port1" "usb2-port1"

This adds a proper object to the board.json, e.g.
"usb": {
	"name": "USB",
	"type": "usbport",
	"sysfs": "devicename:colour:function",
	"ports": [
		"usb1-port1",
		"usb2-port1"
	]
}
and supports translating it into uci section.

Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      2187f57d
  3. Aug 13, 2016
  5. Aug 04, 2016
  7. Jun 07, 2016
  9. Mar 10, 2016
  11. Mar 07, 2016
  13. Feb 26, 2016
  15. Feb 25, 2016
  17. Dec 19, 2015
  19. Dec 11, 2015
  21. Dec 04, 2015
  23. Dec 03, 2015
  25. Nov 30, 2015
  27. Nov 26, 2015
  29. Nov 25, 2015
  31. Nov 24, 2015
  33. Sep 21, 2015
  35. Sep 04, 2015
  37. Jul 14, 2015
  39. Jul 08, 2015
  41. Feb 14, 2015
  43. Jan 20, 2015
    • John Crispin's avatar
      base-files: Use 200ms LED timing as before for the new phase preinit_regular. · 29207748
      John Crispin authored 
      
This restores normal pre-r43715 200ms blink-period for the System LED we're all accustomed to see while our OpenWrt routers are booting.

Failsafe possibility will now be signalled with a new 100ms blinking, which is easily recognizable from the normal 200ms booting.

So no existing user will be scared by a new 500ms LED pattern, since such a slow pattern could easily be mistaken for something wrong... I was like "ok why my router is collapsing now, is this a bad flash, a kernel panic, or what else" when I've seen it for the first time ;)

Sorry for not having explained myself better in v1 of this patch.

Original:
Preinit, failsafe is possible: 200ms
Preinit, failsafe not possible anymore, booting normally: 200ms
Failsafe entered: 50ms

Now (after preinit_regular has been introduced):
Preinit, failsafe is possible: 200ms
Preinit, failsafe not possible anymore, booting normally: 500ms *here is the "offending" change*
Failsafe entered: 50ms

With my proposed patch:
Preinit, failsafe is possible: 100ms *indicate this condition with a new timing, that prompts the user to press the key if they want to start failsafe*
Preinit, failsafe not possible anymore, booting normally: 200ms *keep this as before*
Failsafe entered: 50ms

Signed-off-by: default avatarVittorio Gambaletta <openwrt@vittgam.net>

SVN-Revision: 44056
      29207748