- Jan 20, 2015
-
-
John Crispin authored
Signed-off-by:Luigi Tarenga <luigi.tarenga@gmail.com> SVN-Revision: 44063
-
Steven Barth authored
Signed-off-by:Steven Barth <steven@midlink.org> SVN-Revision: 44062
-
Jo-Philipp Wich authored
Signed-off-by:Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 44060
-
Rafał Miłecki authored
Signed-off-by:Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 44059
-
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Ths will allow us to use early 3xx numbers for patches designed for sending mainline. Signed-off-by: -
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:Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 44056
-
John Crispin authored
this is a mt7621 based board Signed-off-by:wengbj <linux.c@foxmail.com> SVN-Revision: 44055
-
John Crispin authored
Some Huawei mobile broadband sticks utilizing the NCM protocol expose the control channel as a cdc-wdm device node instead of a virtual TTY. This device node does not support the terminal ioctls. This patch adds a check whether the provided device is a TTY or not and does not attempt to use the terminal ioctls if they are not supported. v2: reduce diffstat by simplifying code a little Signed-off-by:Matti Laakso <malaakso@elisanet.fi> SVN-Revision: 44054
-
- Jan 19, 2015
-
-
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Steven Barth authored
Signed-off-by: -
Zoltan Herpai authored
Signed-off-by:Daniel Golle <daniel@makrotopia.org> SVN-Revision: 44048
-
- Jan 18, 2015
-
-
Felix Fietkau authored
Signed-off-by:Felix Fietkau <nbd@openwrt.org> SVN-Revision: 44047
-
Felix Fietkau authored
Signed-off-by:michael lee <igvtee@gmail.com> SVN-Revision: 44046
-
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
* use default timeout value * print more debug ring info * move timeout reset function to workqueue Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Zoltan Herpai authored
Signed-off-by:Zoltan HERPAI <wigyori@uid0.hu> SVN-Revision: 44040
-
Zoltan Herpai authored
Signed-off-by: -
Zoltan Herpai authored
Signed-off-by: -
Luka Perkov authored
Signed-off-by:Claudio Leite <leitec@staticky.com> SVN-Revision: 44037
-
Luka Perkov authored
Signed-off-by: -
Zoltan Herpai authored
Signed-off-by: -
Zoltan Herpai authored
Signed-off-by: -
John Crispin authored
add a led trigger to ath10k based on the ath9k code Signed-off-by:Gianluca Anzolin <gianluca@sottospazio.it> SVN-Revision: 44033
-
John Crispin authored
This patch builds on the previous three to streamline support for the Netgear DGN3500. Signed-off-by:Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> SVN-Revision: 44032
-
John Crispin authored
It seems the call to ltq_get_eth_mac() disappeared at some point. This patch puts it where it currently most makes sense. Signed-off-by: -
John Crispin authored
Somewhere in the conversion of the MIPS architecture code to Device Tree usage, there's been a failure to keep the separate variables holding the kernel command line reconciled between the tree and the bootloader. This patch restores previous functionality that broke. Signed-off-by: -
John Crispin authored
Currently this initscript fails if the macaddr has any leading zeroes. This patch corrects the problem. Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
The swconfig get_link attribute (at least) on AR8327/AR8337 doesn't consider the autonegotiated flow control. AR8327/AR8337 provide the info about autonegotiated rx/tx flow control in bits 10 and 11 of the port status register. Use these values to display info about autonegotiated rx/tx flow control as part of the get_link attribute. Successfully tested on TL-WDR4900 (AR8327 rev.4) and TL-WDR4300 (AR8327 rev.2). Signed-off-by:Heiner Kallweit <hkallweit1@gmail.com> SVN-Revision: 44023
-
Felix Fietkau authored
AR8327/AR8337 allow to read the result of EEE autonegotiation. If EEE is autonegotiated between the link partners, display this as part of the swconfig get_link attribute. eee100: 100MBit EEE supported by both link partners eee1000: 1GBit EEE supported by both link partners Signed-off-by:
-
