Currently port 6 is shown as up 10MBit/half in LUCI and swconfig.
Reason is that all bits in the port 6 config are zero.
This means that also the aneg flag is not set and in this case
ar8216_read_port_link hardcodes the link to be up.

This is no real problem but a little annoying.
To fix this initialize port 6 with the aneg bit enabled.
This causes ar8216_read_port_link to evaluate the link status bit which is
always zero for port 6 as no PHY is connected to this port.
And it doesn't hurt as port 6 isn't connected to anything on TL-WDR4900.

Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>

SVN-Revision: 45749

Fix an upstream regression on 3.18+ that causes rt305x based devices
to hang on boot.

Fixes #19715.

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

SVN-Revision: 45747

Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>

SVN-Revision: 45732

Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45731

This change set enables frequency scaling on ipq806x, which speeds-up
the CPU and allows it to achieve its max frequency.

These patches are cherry-picked & backported from the following location:
*130-132: linux-next
*133-143: LKML - https://lkml.org/lkml/2015/3/21/15
*144: derived from other qcom similar dts
*145: derived from https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/drivers/cpufreq/cpufreq-krait.c



Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45730

Patches are cherry-picked from linux-next. We're also adding the
corresponding config option to the kernel.

Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45729

Patch cherry-picked from the following location:
https://chromium-review.googlesource.com/#/c/269931/



Disable the i2c device on gsbi4 and mark gsbi4_h and gsbi4_qup clks as
unused. If they are enabled, clock framework will turn them off at end
of probe. On ipq806x by design gsbi4_qup, gsbi4_h clks and i2c on gsbi4
are meant for RPM usage. So turning them off in kernel is incorrect.

Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45728

Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45727

This patch is to add support for the Meraki MR12 and MR16 Access Points.
Currently everything is working, minus the 2nd NIC interface on the MR12
which is built into the SoC.

Signed-off-by: Chris R Blake <chrisrblake93 at gmail.com>

SVN-Revision: 45726

The diag.sh script lacked an entry for the status led on the RT-N14U,
map it to the asus:blue:power led which is also used by the boot loader
to report boot status (eg. TFTP recovery mode VS normal boot)

Signed-off-by: Matteo Panella <m.panella@level28.org>

SVN-Revision: 45725

MR-102N is a RT3050F based wireless router(32M RAM + 8M NOR flash) with 1 USB
and 1 ethernet port.  The original product information can be found at:
http://www.aximcom.com/en/MR-102N



Signed-off-by: Tai-hwa Liang <atliang@gmail.com>

SVN-Revision: 45724

Signed-off-by: Roman Yeryomin <roman@advem.lv>

SVN-Revision: 45723

This patch adds support for Comfast CF-WR800N, a wall-plug wireless router
based on the MT7620N SoC with one Ethernet port and a 802.11n 2.4 GHz radio.

Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>

SVN-Revision: 45722

There are already ifx_pcie_bios_{map_irq,plat_dev_init} hooks defined in
ifxmips_pcie.c. Instead of defining a new hook we simply re-use the
existing ones (this is basically what the lantiq BSP code does).

Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

SVN-Revision: 45718

The PCIe bus seems to require a hack/workaround when PCI is enabled as
well. Unfortunately this is guarded by an CONFIG_IFX_PCI ifdef, which is
only defined in lantiq's BSP code. The config symbol for the upstream
lantiq PCI driver is CONFIG_PCI_LANTIQ.

Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>

SVN-Revision: 45717

There is also a OHCI controller, activate it for USB 1.1 support.

This should close #19601.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

SVN-Revision: 45716

3.18.13 introduced a bunch of new errata, enable them to be on the
safe side.

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

SVN-Revision: 45715

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

SVN-Revision: 45714

Changelogs:

* https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.12
* https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.13
* https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.14



Build tested on brcm63xx and ipq806x, runtested on brcm63xx.

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

SVN-Revision: 45711

Add it to the appropriate places so the power led properly works
and ethernet is properly configured for failsafe.

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

SVN-Revision: 45709

This patch adds support for the Huawei HG655b.

Nothing much special in this router, it's just another BCM6368 with
a Ralink RT3062 wifi chip and the calibration data embedded in the
main flash chip at offset 0x7c0000. There is also configuration data
used by the OEM firmware before the cal_data partition, this area is
protected by the board_data partition in this patch.

Signed-off-by: Daniel Gonzalez <dgcbueu@gmail.com>
Signed-off-by: Jonas Gorski <jogo@openwrt.org>

SVN-Revision: 45708

Commit 5168c9a5702648eb690d32ec821647aca80aeba9 introduced a regression
during patch application on the 4.0 kernel. Some of the patched content
doesn't match the actual code, therefore leading to the following error:
  Applying patch generic/667-ipv6-Fixed-source-specific-default-route-handling.patch
  patching file net/ipv6/ip6_output.c
  Hunk #1 FAILED at 886.
  1 out of 1 hunk FAILED -- rejects in file net/ipv6/ip6_output.c
  patching file net/ipv6/route.c
  Hunk #1 succeeded at 2247 (offset 2 lines).
  Patch generic/667-ipv6-Fixed-source-specific-default-route-handling.patch does not apply (enforce with -f)

This change just adapts the actual patch to fix what is in kernel 4.0
and make it apply cleanly.

Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>

SVN-Revision: 45705

Signed-off-by: Imre Kaloz <kaloz@openwrt.org>

SVN-Revision: 45704

Signed-off-by: Steven Barth <steven@midlink.org>

SVN-Revision: 45699

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

SVN-Revision: 45694

This device seems to have switch port 7 connected to the CPU:
vlan1ports=1 2 3 5 7*
vlan2ports=0 7u
it should be handled by eth1 and NVRAM seems to confirm that (no
et0macaddr entry, existing et1macaddr & et1phyaddr entries).

One of the remaining ports (4/8?) may be connected to the Quantenna SoC.
Original firmware boot log contains following messages:
(0x00,0x5d)Port 5 States Override: 0xfb
(0x00,0x5f)Port 7 States Override: 0xfb
(0x00,0x0e)Port 8 States Override: 0x0a
(why does it force port 5 state?!)

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

SVN-Revision: 45692

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

SVN-Revision: 45691

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>

SVN-Revision: 45690

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

SVN-Revision: 45686

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

SVN-Revision: 45685

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

SVN-Revision: 45684

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

SVN-Revision: 45683

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

SVN-Revision: 45682

It has 3 Ethernet interfaces, each of them connected to separated switch
port. Default NVRAM uses switch port 8 as CPU which is connected to the
3rd interface (eth2).

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

SVN-Revision: 45681

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

SVN-Revision: 45680

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

SVN-Revision: 45678

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

SVN-Revision: 45677

This chipset has at least 8 usable ports, e.g. Netgear R8000 has ports
5, 7 and 8 connected to Ethernet interfaces:
vlan1ports=0 1 2 3 5 7 8*
vlan2ports=4 8u
Port 6 seems to be always disabled.

Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Acked-by: Jonas Gorski <jogo@openwrt.org>

SVN-Revision: 45676

ar71xx: convert tl-wr741nd v1/v2 to new image building code, add infrastructure for building the loader

Signed-off-by: Felix Fietkau <nbd@openwrt.org>

SVN-Revision: 45672

Since the kernel/rootfs split handling was modified 2 years ago by r37283 (
https://dev.openwrt.org/changeset/37283

 ) and by the subsequent checkins,
users have seen rather scary mtd errors in the log at every boot. The message
ends "-- forcing read-only", which looks a bit error-like. That error has
been mentioned in some forum threads, when users have noticed this message
instead of some actual error.

[    2.940000] 0x000000070000-0x000000ff0000 : "firmware"
[    2.970000] 2 netgear-fw partitions found on MTD device firmware
[    2.970000] 0x000000070000-0x000000188440 : "kernel"
[    2.980000] mtd: partition "kernel" must either start or end on erase
block boundary or be smaller than an erase block -- forcing read-only
[    2.990000] 0x000000188440-0x000000ff0000 : "rootfs"

The patch removes the rather useless warning message.

signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>

SVN-Revision: 45669