Do this until the watchdog driver is loaded and the user-space watchdog
daemon can start pinging the watchdog.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 36065
None of the boards we support are using it nor have it wired out of the
SoC, just remove it.
Signed-off-by: Florian Fainelli <florian@openwrt.org>
SVN-Revision: 36061
Now that the ethernet switch is working, create firmware
images to make impatient users happy.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36051
The AR8327 switch gets its configuration from platform
data or from the device-tree. This allows to start it
from the probe routine. Doing so makes it usable with
ethernet drivers which only connects to the PHY device
when the ethernet interface is opened.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36050
Move switch starting code into a separate function.
This makes it usable from other places.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36049
Move platform_data specific configuration code
into a separate routine. Do it in preparation
for the upcoming OF support.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36046
Fetch the PORT_STATUS values in ar8327_hw_init and
store those in a private data stucture for later use.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36045
Return with the PORT_STATUS register value instead of
writing that directly into the corresponding register.
Also rename the function to ar8327_get_port_init_status.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36043
The presence of the platform data is already verified in
ar8327_hw_init, and the driver does not start without that
anyway.
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36042
[juhosg: use different profile name for v1 and v2, and add
multi profile to build for both versions]
Signed-off-by: Guilhem Lettron <guilhem@lettron.fr>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36038
Use eeprom (art) from included wifi card, not hard coded in flash.
Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36037
Error in using another MDIO (AP123 platform using only one GE1 device
for eth0 and eth1) for the router mr3420v2.
?onfirmed: https://forum.openwrt.org/viewtopic.php?pid=194779#p194779
Routers in this sense are the same and the only difference is: USB
port, USB led, instead of the GPIO-switch we have GPIO-button.
Signed-off-by: Dmytro <dioptimizer@gmail.com>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
SVN-Revision: 36036
EEPROM is an actial serial EEPROM on the WiFi module, therefore we can remove
ralink_eep from the dts.
USB power-enable GPIO turned out to be GPIO #3 (found via probing/brute-force).
PCI works with default settings as long as the vendor bootloader is used.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
SVN-Revision: 36030
* Introduce "option reload" for includes to specify whether includes should be processed on reload (e.g. when tapping into internal chains)
* Allow "network" and "device" commands while firewall is running (to make them usable in includes)
SVN-Revision: 36009
