| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
QCA9563 and QCA9561 are two series of Qualcomm SoC Dragonfly. The only different
is QCA9563 w/o internal switch. It has one GMAC with SGMII interface. But they
have the same device ID(0x1150). So they share the same codes.
Signed-off-by: Miaoqing Pan <miaoqing@codeaurora.org>
SVN-Revision: 46971
|
|
|
|
|
|
| |
Signed-off-by: Miaoqing Pan <miaoqing@codeaurora.org>
SVN-Revision: 46970
|
|
|
|
|
|
|
|
|
| |
the lantiq dsl hack to struct atm_trafprm broke the ABI fix this by moving
the variables to the end of the struct
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46964
|
|
|
|
|
|
|
|
|
| |
The pinctrl-rt2880 code doesn't support multiple functions with the same
name. This will result in a incorrect pinmux configuration.
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46963
|
|
|
|
|
|
|
|
| |
This patch adds kernel and userspace support for the Ubiquiti Networks airGateway Pro.
Signed-off-by: Matthew Reeve <mreeve at tenxnetworks.com>
SVN-Revision: 46961
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46959
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46958
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46957
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46956
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46955
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46954
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46953
|
|
|
|
|
|
|
|
| |
newer socs have 2 mux registers
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46952
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46951
|
|
|
|
|
|
|
|
| |
only tested on mt7628
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 46950
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 46947
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're in process of cleaning nand_do_platform_check. Currently is leaves
a special mark in /tmp/sysupgrade-nand-path triggering some diffent code
path in nand_upgrade_stage1. This can be a bit confusing.
The plan is to have the check function only check the image and nothing
else. Then platform code (platform_pre_upgrade) should trigger NAND
specific upgrade path. This is what this patch implements.
This follows ar71xx, lantiq and partially bcm53xx.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46945
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're in process of cleaning nand_do_platform_check. Currently is leaves
a special mark in /tmp/sysupgrade-nand-path triggering some diffent code
path in nand_upgrade_stage1. This can be a bit confusing.
The plan is to have the check function only check the image and nothing
else. Then platform code (platform_pre_upgrade) should trigger NAND
specific upgrade path. This is what this patch implements.
This follows ar71xx, lantiq and partially bcm53xx.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46944
|
|
|
|
|
|
|
|
| |
Meanwhile BTHOMEHUBV5A board was added.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46941
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As explained in recent sysupgrade/nand.sh commits, current NAND
sysupgrade is a bit misleading because of nand_do_platform_check
behavior. It leaves a special mark in /tmp/sysupgrade-nand-path
triggering some diffent code path in nand_upgrade_stage1.
The plan is to have the check function only check the image and nothing
else. Then platform code (platform_pre_upgrade) should trigger NAND
specific upgrade path. This is what this patch implements.
Please note that because of current nand_upgrade_stage1 implementation
this patch doesn't change any behaior yet. It only prepares lantiq
target for changing nand_do_platform_check (it will be possible after
preparing all other targets as well).
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46939
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for TP-LINK TL-WDR3320 v2.
This router uses a chinese version 2 firmware header,.
Signed-off-by: Weijie Gao <hackpascal@gmail.com>
SVN-Revision: 46934
|
|
|
|
|
|
| |
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46933
|
|
|
|
|
|
| |
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46932
|
|
|
|
|
|
| |
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46929
|
|
|
|
|
|
| |
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46927
|
|
|
|
|
|
| |
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46926
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enables a real rootfs with custom size
use qemu with:
qemu-system-arm -M realview-pbx-a9 \
-kernel openwrt-realview-vmlinux.elf \
-nographic -m 1024M \
-sd openwrt-realview-sdcard.img \
--append "console=ttyAMA0 root=/dev/mmcblk0p1"
modified script from brcm2708 target
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
SVN-Revision: 46924
|
|
|
|
|
|
|
|
| |
qemu can be run with -sd <imagename>
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
SVN-Revision: 46923
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The GPIO pins for "POE passthrough" of Ubiquiti Nanostation models are the
following:
* Ubiquiti Nanostation M XM: Pin 8
* Ubiquiti Nanostation M XW: Pin 2
The previous definition of the pins was mixed up between XM and XW model.
Signed-off-by: Lars Kruse <lists@sumpfralle.de>
SVN-Revision: 46922
|
|
|
|
|
|
|
|
| |
This patch is to add the WIZnet WizFi630A board as a new platform. The board is in mini pci express form factor.
Signed-off-by: Tobias Welz <tw@wiznet.eu>
SVN-Revision: 46921
|
|
|
|
|
|
|
|
|
|
| |
This patch add support for Planex DB-WRT01. DANBOARD route on
the MT7620A SoC with two Ethernet port and a 802.11n 2.4 GHz radio.
DANBOARD is Cartoon character.
Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com>
SVN-Revision: 46918
|
|
|
|
|
|
|
|
|
| |
Signed-off-by: Florian Eckert <Eckert.Florian@googlemail.com>
Signed-off-by: Helge Mader <hmader@tdt.de>
Tested-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Tested-by: Andre Heider <a.heider@gmail.com>
SVN-Revision: 46917
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add AR9 DTS definition to be recognized by the DWC2 driver.
The same driver parameters can be mostly used except that some boards
seem to erroneously report OTG HNP/SRP capability of the USB HCD.
Forcing the HNP/SRP off allows these boards to work with the DWC2 as well.
Signed-off-by: Antti Seppälä <a.seppala@gmail.com>
SVN-Revision: 46915
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the AR9 USB is very similar to the VR9 USB it too can be used with
the upstream DWC2 driver.
Here are the DTS definitions which make it compatible with the DWC2
driver.
Signed-off-by: Antti Seppälä <a.seppala@gmail.com>
SVN-Revision: 46914
|
|
|
|
|
|
|
|
|
|
| |
Based on the ltq-hcd driver the AR9 USB can be initialized the same way
as the VR9 platform. Use the same initialization bits for both
platforms.
Signed-off-by: Antti Seppälä <a.seppala@gmail.com>
SVN-Revision: 46913
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 46904
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To make the lzma-loader build with binutils 2.25.1 it is needed to
remove the .MIPS.abiflags section otherwise I get the following compile
error:
mips-openwrt-linux-musl-objcopy -O binary -R .reginfo -R .note -R .comment -R .mdebug -S loader loader.bin
mips-openwrt-linux-musl-objcopy: Warning: Writing section `.text' to huge (ie negative) file offset 0xffffffff80a00000.
mips-openwrt-linux-musl-objcopy:loader.bin[.text]: File truncated
This should close #20487.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46893
|
|
|
|
|
|
|
|
| |
This should fix #20492.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46892
|
|
|
|
|
|
|
|
| |
Attempt to boost the 2.4 GHz signal, currently very low.
Signed-off-by: D. Andrei Măceș <dmaces@nd.edu>
SVN-Revision: 46891
|
|
|
|
|
|
|
|
|
|
| |
This moves arch patches affecting many DTS files. Thanks to this change
we can put some ready-to-mainline patches at 300-319 and simplify
backporting process.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46889
|
|
|
|
|
|
|
|
| |
This driver was added in kernel 4.1.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46881
|
|
|
|
|
|
|
|
| |
It's still far from complete support.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46880
|
|
|
|
|
|
|
|
|
|
|
|
| |
As requested here #20432 I've
tried to fix the missing symbols from the specified default kernel
config files.
I ran into this problem trying to build an image for x86_64 target
with a custom kernel configuration.
Signed-off-by: Manganini Mirko <mmanganini@gmail.com>
SVN-Revision: 46879
|
|
|
|
|
|
|
|
| |
This makes bcm53xx use kernel 4.1 by default now.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46878
|
|
|
|
|
|
|
|
| |
This makes bcm53xx use kernel 4.1 by default now.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46877
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the trx utile uses a maximum image size of 7.2MB. There are brcm47xx
devices even with serial flash with bigger flash chips, but OpenWrt was
not able to create images for these devices. This patch provides an
additional parameter which increases this limit to 32 MB. There is a
warning in the trx utile code which suggests that bigger images could
overwrite the nvram partition on some devices, but normally the program
writing the image should make sure that it is safe to write it to the
flash.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46872
|
|
|
|
|
|
|
|
|
| |
This patch changes nothing on the behaviour, it just breaks long lines
with bin/trx to make it easier to add additional parameters.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
SVN-Revision: 46871
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 46870
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes support for AR9287 on TP-Link TD-W8980 and possibly other devices
which have an ath wifi chip at a PCI address other than 0xb8000000
(TD-W8980 for example has it's wifi chip at 0xbc000000).
Signed-off-by: Geoffrey McRae <geoff@spacevs.com>
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 46869
|
|
|
|
|
|
| |
Signed-off-by: Claudio Leite <leitec@staticky.com>
SVN-Revision: 46865
|