- May 17, 2015
-
-
Rafał Miłecki authored
Signed-off-by:Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45694
-
- May 16, 2015
-
-
Rafał Miłecki authored
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 authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by:Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 45690
-
- May 13, 2015
-
-
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
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 authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by:
-
- May 12, 2015
-
-
Rafał Miłecki authored
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:
Jonas Gorski <jogo@openwrt.org> SVN-Revision: 45676
-
- May 11, 2015
-
-
Felix Fietkau authored
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
-
- May 10, 2015
-
-
Felix Fietkau authored
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
-
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
This change adds PCIe support to IPQ806x based platforms. The driver is actually cherry-picked from the following LKML thread: *https://lwn.net/Articles/643086/ (patches 110-111) We also add here an additional fix to support multiple PCI controllers on the same platform (patch 112), and to patch the ap148 & dbs149 DTS files (patch 113). Signed-off-by:
Mathieu Olivari <mathieu@codeaurora.org> SVN-Revision: 45663
-
Felix Fietkau authored
This change enable zImage+appended dtb support in ipq806x kernel options. The zImage will now be generated as part of the kernel binaries. Platforms which do not have DT support enabled in U-boot can now make use of it by generating zImage files and appending dtb to it. It is not used yet but it is done as a stepping stone for early IPQ806x platforms, which did not include DT support in U-boot. Signed-off-by: -
Felix Fietkau authored
ARCH_QCOM is using the ARCH_MULTIPLATFORM option, as now recommended on most ARM architectures. This automatically calculate ZRELADDR by masking PHYS_OFFSET with 0xf8000000. On IPQ806x though, the first ~20MB of RAM is reserved for the hardware. In newer bootloader, when DT is used, this is not a problem, we just reserve this memory in the device tree. But if the bootloader doesn't have DT support, then ATAGS have to be used. In this case, the ARM decompressor will position the kernel in this low mem, which will not be in the RAM section mapped by the bootloader, which means the kernel will freeze in the middle of the boot process trying to map the memory. As a work around, this patch allows disabling AUTO_ZRELADDR when ARCH_QCOM is selected. It makes the zImage usage possible on bootloaders which don't support device-tree, which is the case on certain early IPQ806x based designs. Signed-off-by: -
Felix Fietkau authored
This option has been added in kernel 3.17. It shows-up only when both ARCH_QCOM and CRYPTO are enabled. So we'll disable these two by default to avoid stalling the build when these conditions are met. Signed-off-by: -
Luka Perkov authored
Signed-off-by:Catrinel Catrinescu <cc@80211.de> SVN-Revision: 45656
-
Felix Fietkau authored
Signed-off-by:
-
- May 09, 2015
-
-
Felix Fietkau authored
Signed-off-by: -
Rafał Miłecki authored
Signed-off-by:
-
- May 08, 2015
-
-
Felix Fietkau authored
Signed-off-by: -
Luka Perkov authored
Signed-off-by:Luka Perkov <luka@openwrt.org> SVN-Revision: 45648
-
Luka Perkov authored
Add Support for the Seagate GoflexHome <http://wiki.openwrt.org/toh/seagate/goflexhome > Signed-off-by:
L. D. Pinney <ldpinney@gmail.com> SVN-Revision: 45647
-
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
Signed-off-by: -
Felix Fietkau authored
There are 2 images missing: TLWR2543 TLWR1043V2 which have special properties. v2: set correct DEVICE_PROFILES for all images. v2: migrate TP-LINK TL-WR710N v2 which was committed after v1. v2: split very very long line `TARGET_DEVICES +=` into smaller parts Signed-off-by:Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 45643
-
Felix Fietkau authored
Signed-off-by:Michael J. Bazzinotti <mbazzinotti@gmail.com> SVN-Revision: 45640
-
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
Users will now be provided with the inherent wifi toggle functionality of /etc/rc.button/rfkill Signed-off-by: -
Felix Fietkau authored
Originally pressing a button would trigger a release state and vice-versa, as observed from hotplug.d. Signed-off-by: -
Felix Fietkau authored
Most people report broken ethernet with upstream. Last year, user "franz.flasch" authored a working mach-file. His patch is outdated so I modernized it. Original patch and user commentary on page 1: https://forum.openwrt.org/viewtopic.php?pid=260861#p260861 I have figured out what the critical differences are between the two that caused upstream ethernet to break. 1) Both ath79_init_mac() functions calls must be invocated before any GMAC init 2) must init GMAC0 before GMAC1 That was enough to get upstream to function, but I wanted to enjoy my confidence having tested franz's patch for a week sucessfully, so I put his whole function in, which only features more differences in order of function calls. An expert should consider these changes, which could pose potential bugs/issues: 1) No longer using the flag AR934X_ETH_CFG_SW_PHY_SWAP in the ath79_setup_ar934x_eth_cfg() call. 2) Possible consequence of no longer explicitly setting ethernet duplex/speed. Review: With this patch, my ethernet and wireless works. Signed-off-by:
-
