| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
The previous "link" and "status" functions were non-standard,
and thus less useful for parsing.
Signed-off-by: Claudio Leite <leitec@staticky.com>
SVN-Revision: 46864
|
|
|
|
|
|
|
|
|
| |
Increase space for kernel and also introduce a 8M flash target into the
Makefile.
Signed-off-by: Attila Lendvai <attila@lendvai.name>
SVN-Revision: 46862
|
|
|
|
|
|
|
|
|
| |
prevent compiler errors with gcc 4.9
increase reproducibility
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
SVN-Revision: 46858
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The PBR-M1 and other upcoming MT7621 boards have RTC chips on them. The
PBR-M1 also selects the kmod-rtc-pcf8563 by default. But the module itself
will not be build because CONFIG_RTC_CLASS is currently not enabled for its
kernel.
Enabling this option should fix the problem of the missing rtc device on
these boards.
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46857
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to the AR7242 datasheet section 2.8, AR724X CPUs use a 40MHz
input clock as the REF_CLK instead of 5MHz.
The correct CPU PLL calculation procedure is as follows:
CPU_PLL = (DIV * REF_CLK) / REF_DIV / 2.
This patch is compatible with the current calculation procedure with default
DIV and REF_DIV values.
Test on both AR7240, AR7241 and AR7242.
Signed-off-by: Weijie Gao <hackpascal@gmail.com>
SVN-Revision: 46856
|
|
|
|
|
|
|
|
| |
This adds support for RaspiDAC Rev.3x
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 46854
|
|
|
|
|
|
|
|
|
| |
As usual, this patches were taken (and rebased) from
https://github.com/raspberrypi/linux/commits/rpi-4.1.y
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
SVN-Revision: 46853
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds full support (sans sysupgrading from vendor firmware) for the COMFAST
CF-E316N v2 (aka CF-E316V2, CF-E316N-V2 and CF-E316Nv2.0, no FCC ID) by
Shenzhen Four Seas Global Link Network Technology Co., Ltd (this company is
actively refusing to provide GPL'd sources for the OpenWrt version they ship
with the device, damn them).
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
SVN-Revision: 46852
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In krait_cpufreq_probe, both freq and max_cpu_freq are never
initialized, so the max_cpu_freq will have a random value at the end.
Fix this by properly initializing max_cpu_freq to 0 and storing the clk
frequency in freq as well, to make it similar to how it's calculated in
krait_set_target.
Fixes the following warnings:
In file included from include/linux/clk.h:16:0,
from drivers/cpufreq/cpufreq-krait.c:13:
drivers/cpufreq/cpufreq-krait.c: In function 'krait_cpufreq_probe':
include/linux/kernel.h:714:24: warning: 'freq' may be used uninitialized in this function [-Wmaybe-uninitialized]
_max1 > _max2 ? _max1 : _max2; })
^
drivers/cpufreq/cpufreq-krait.c:217:25: note: 'freq' was declared here
unsigned long freq_Hz, freq, max_cpu_freq;
^
In file included from include/linux/clk.h:16:0,
from drivers/cpufreq/cpufreq-krait.c:13:
include/linux/kernel.h:714:24: warning: 'max_cpu_freq' may be used uninitialized in this function [-Wmaybe-uninitialized]
_max1 > _max2 ? _max1 : _max2; })
^
drivers/cpufreq/cpufreq-krait.c:217:31: note: 'max_cpu_freq' was declared here
unsigned long freq_Hz, freq, max_cpu_freq;
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46839
|
|
|
|
|
|
|
|
|
|
| |
The phy driver has its qcom-dwc3 order switched in contrast to the usb
controller driver.
Signed-off-by: Kaspar Schleiser <kaspar@schleiser.de>
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46838
|
|
|
|
|
|
|
|
|
| |
Obviously the dummy rootfs must be after the kernel (uImage), not
included in it.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46837
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit r30917 ("kernel: bypass all netfilter hooks if the sysctls for that
functionality have been disabled - eliminates the overhead of enabling
CONFIG_BRIDGE_NETFILTER in the kernel config") introduced an optimization
which should reduce/eliminate the overhead for traffic send over bridges on
kernels compiled with CONFIG_BRIDGE_NETFILTER=y. But this optimization
breaks the nf_call_iptables per bridge setting which is more fine grained
than the global sysctl net.bridge.bridge-nf-call-iptables setting.
A test reflecting a real world setup was created to identify if this really
eliminates the overhead and if per-bridge nf_call_iptables could be used in
some setups to increase the throughput. A Qualcomm Atheros QCA9558 based
system with one ethernet and an ath9k wifi 3x3 in HT40 mode was used.
Cables from the AP to the wifi station were used to reduce interference
problems during the tests.
The wlan interface was put in one bridge interface called br-wlan. This
bridge usually contains some more wlan interfaces. The eth0 was put in a
second bridge called br-lan. This usually contains some other privileged
wlan or mesh interfaces. Routing was added between br-lan and br-wlan.
Three kernels were tested:
* (default) OpenWrt kernel for this device
* (brfilter-global) OpenWrt kernel with CONFIG_BRIDGE_NETFILTER=y
* (brfilter-local) OpenWrt kernel with CONFIG_BRIDGE_NETFILTER=y and
without 644-bridge_optimize_netfilter_hooks.patch
The changes to the the netfilter settings of the bridge were done via:
* (brfilter-global) /sbin/sysctl -w net.bridge.bridge-nf-call-iptables=1
* (brfilter-lobal) echo 1 > /sys/class/net/br-lan/bridge/nf_call_iptables
and/or echo 1 > /sys/class/net/br-wan/bridge/nf_call_iptables
A station connected to the wlan0 (AP) interface was used to send traffic to
a PC connected via ethernet. iperf with 3 concurrent transmissions was used
to generate the traffic.
| kernel | br-nf-* global | nf-call* iface | download | upload |
|-----------------|----------------|----------------|----------|----------|
| default | 0 | - | 209 | 268 |
| brfilter-global | 0 | - | 185 | 243 |
| brfilter-local | 0 | - | 187 | 243 |
| brfilter-local | 0 | br-lan | 157 | 226 |
| brfilter-local | 0 | br-lan br-wlan | 139 | 161 |
| brfilter-global | 1 | - | 136 | 162 |
Download/upload results in Mibit/s
It can be seen that the patch doesn't eliminate the overhead. It can also
be seen that the throughput of brfilter-global and brfilter-local with
disabled filtering is the roughly the same. Also the throughput for
brfilter-global and brfilter-local for enabled filtering on all bridges is
roughly the same.
But also the brfilter-local throughput is higher when only br-lan requires
the filtering. This setting would not be possible with
644-bridge_optimize_netfilter_hooks.patch applied and thus can only be
compared with brfilter-global and filtering enabled for all interfaces.
Signed-off-by: Sven Eckelmann <sven@open-mesh.com>
SVN-Revision: 46835
|
|
|
|
|
|
| |
It was initially added in r41367 by nbd.
SVN-Revision: 46828
|
|
|
|
|
|
| |
It was initially added in r30917 by nbd.
SVN-Revision: 46827
|
|
|
|
|
|
| |
It was initially added in r27237 by jow as patch from Jonas.
SVN-Revision: 46826
|
|
|
|
|
|
| |
It was initially added in r25762 by nbd.
SVN-Revision: 46825
|
|
|
|
|
|
| |
It was initially added in r26015 by nbd.
SVN-Revision: 46824
|
|
|
|
|
|
| |
It was initially added in r25095 by nbd.
SVN-Revision: 46823
|
|
|
|
|
|
|
|
|
|
| |
It was corrupted in r38528. The most obvious symptom is repeated messages like this:
Tue Sep 8 08:25:18 2015 kern.warn kernel: [77141.972226] br-lan: received packet on wlan0 with own address as source address
Signed-off-by: Dmitry Ivanov <dima@ubnt.com>
SVN-Revision: 46821
|
|
|
|
|
|
|
|
|
| |
Everything except for blkcipher was already built-in, so make blkcipher
built-in as well.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 46820
|
|
|
|
|
|
|
|
| |
It also uses different block size just like WGR614 V10.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46810
|
|
|
|
|
|
|
|
| |
This ports fix from r46584 to the 4.1.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 46806
|