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
  • Johannes Rudolph Johannes Rudolph PowerPan
1 author
  1. May 19, 2015
  3. May 03, 2015
  5. Apr 18, 2015
  7. Apr 16, 2015
  9. Apr 10, 2015
  11. Apr 09, 2015
    • John Crispin's avatar
      base-files: add support for platform_pre_upgrade function · 5d8f9e03
      John Crispin authored 
      
Current NAND sysupgrade process is a bit hard to follow due to the way
of triggering stage1. Currently this is done by leaving a /mark/ in the
form of /tmp/sysupgrade-nand-path during nand_do_platform_check.
Existence of this mark stops standard sysupgrade process (as the result
of sysupgrade_pre_upgrade exit). This may be a bit misleading.

Proposed solution adds a new function that will allow platform.sh
trigger NAND sysupgrade consciously. This will also allow cleaning
nand_do_platform_check limiting it to just checking the image.

Signed-off-by: default avatarRafał Miłecki <zajec5@gmail.com>

SVN-Revision: 45338
      5d8f9e03
  13. Apr 06, 2015
  15. Apr 03, 2015
  17. Apr 02, 2015
  19. Mar 26, 2015
  21. Mar 22, 2015
  23. Mar 17, 2015
  25. Mar 10, 2015
  27. Feb 14, 2015
  29. Feb 11, 2015
  31. Feb 04, 2015
  33. Jan 23, 2015
  35. 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
  37. Jan 17, 2015
  39. Jan 08, 2015
  41. Dec 15, 2014
    • John Crispin's avatar
      add "preinit_regular" diag.sh set_state argument · 019ea725
      John Crispin authored 
      
This new argument is used right after starting regular preinit (which
happens if failsafe wasn't triggered). The main purpose of "preinit"
argument is to indicate that failsafe can be triggered, however we were
missing a way to inform user that we don't wait for a trigger anymore.
With this change it's clear when failsafe mode can be triggered.

Signed-off-by: default avatarRafał Miłecki <zajec5@gmail.com>

SVN-Revision: 43715
      019ea725
  43. Dec 07, 2014
  45. Dec 01, 2014
  47. Nov 24, 2014
  49. Nov 19, 2014
  51. Nov 18, 2014
    • Jonas Gorski's avatar
      base-files: properly fix copying ld*.so with eglibc · 2e95b1fd
      Jonas Gorski authored 
      
r36107 ("base-files: sysupgrade fail with eglibc") tried to fix
sysupgrade by changing the ld-soname to what is expected, but only
fixed MIPS while breaking ARM.

The underlying issue is that the ld.so name varies widely across
different architectures for eglibc:

eglibc-2.19-r25243$ grep -r "ld-soname :=" . | awk '{ print $3 }' | sort -u
ld64.so.1
ld64.so.2
ld-linux-aarch64_be.so.1
ld-linux-aarch64.so.1
ld-linux-armhf.so.3
ld-linux-mipsn8.so.1
ld-linux.so.2
ld-linux.so.3
ld-linux-x32.so.2
ld-linux-x86-64.so.2
ld.so.1

Instead of adding each different soname to check for and copy it,
replace the awk script with a sed script to extract it properly and
drop the hardcoded so-name.

Signed-off-by: default avatarJonas Gorski <jogo@openwrt.org>

SVN-Revision: 43295
      2e95b1fd
  53. Nov 06, 2014
  55. Nov 03, 2014
    • John Crispin's avatar
      license info - revert r43155 · 74a3a77b
      John Crispin authored 
      
turns out that r43155 adds duplicate info.

Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>

SVN-Revision: 43167
      74a3a77b
    • John Crispin's avatar
      Add more license tags with SPDX identifiers · c10d9748
      John Crispin authored 
      
Note, that licensing stuff is a nightmare: many packages does not clearly
state their licenses, and often multiple source files are simply copied
together - each with different licensing information in the file headers.

I tried hard to ensure, that the license information extracted into the OpenWRT's
makefiles fit the "spirit" of the packages, e.g. such small packages which
come without a dedicated source archive "inherites" the OpenWRT's own license
in my opinion.

However, I can not garantee that I always picked the correct information
and/or did not miss license information.

Signed-off-by: default avatarMichael Heimpold <mhei@heimpold.de>

SVN-Revision: 43155
      c10d9748
  57. Nov 02, 2014
  59. Oct 27, 2014
  61. Oct 25, 2014
  63. Oct 20, 2014