| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Changelogs:
* https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.15
* https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.16
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 46011
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 46007
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This stabilizes USB support. The old patch was handling initialization
in a different order that was causing some problems with few USB 3.0
devices. Some weren't detected, some were working unstable, sometimes
USB 3.0 could hang the whole controller.
A still known issue (but not a regression) is controller hang triggered
by connecting USB 1.1 device when not having OHCI controller enabled
(kmod-usb-ohci).
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45997
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45992
|
|
|
|
|
|
| |
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
SVN-Revision: 45983
|
|
|
|
|
|
| |
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
SVN-Revision: 45982
|
|
|
|
|
|
| |
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
SVN-Revision: 45981
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45971
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AR8337 supports a configuration bit to swap MAC0 and MAC6.
Currently this is set in general if an AR8337 is detected and causes
issues with devices using an AR8334 (internally an AR8337, just
less chip pins).
And it might even cause issues with AR8337-based devices with
different board designs.
Swapping the MAC's however isn't needed for AR8337 in general.
It's just needed in case of certain board designs (affected devices
seem to be based on Atheros reference board AP135/136-010).
Therefore this configuration bit should be moved to platform data.
The patch includes the needed changes to the device initialization
code of affected devices. Hopefully I didn't miss any ..
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
SVN-Revision: 45970
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the pll_1000 value for eth0 interface. This makes the Rocket M
XW image compatible with other Ubiquiti devices with similar hardware with a
Gigabit Ethernet port.
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
SVN-Revision: 45965
|
|
|
|
|
|
|
|
|
|
| |
The *u-boot-initramfs* images are not ITB/FIT images but are rather
supposed to be loaded to RAM and jumped-into.
To avoid confusion, change the file extension from itb to bin.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
SVN-Revision: 45963
|
|
|
|
|
|
|
|
|
| |
In new firmware-4.bin (for ath10k) mac offset is 0x114 (276), not 0x118 (280).
This also closes #19751, bug introduced in #45624
Signed-off-by: Cezary Jackiewicz <cezary.jackiewicz@gmail.com>
SVN-Revision: 45958
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The mynet range extender hardware is suffering from ethernet
link loss when booting with a recent openwrt image. This only
happens on 100mbps links, with 1Gbps speed the link was fine.
The cause of the problem is that the AR8035 PHY (aka F1E)
requires turning on and off the special TX delay setting
depending on the speed of the link.
The 10mbps mode only needed the proper pll value, which was
extracted from the vendor code.
Reported-by: Pascal Paradis
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
SVN-Revision: 45954
|
|
|
|
|
|
|
|
|
|
|
|
| |
When r42245 moved A4001N to DT based detection the image padding size
was accidentally increased from 4 to 8 MiB. This made images unflashable
on these devices.
Fixes #19836.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 45945
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45943
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45942
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On device reset the sizes for the vlan and port tables were wrongly
calculated based on the pointer size instead of the struct size. This
causes buffer overruns on 64 bit targets, resulting in panics.
Fix this by dereferencing the pointers.
Reported-by: Fedor Konstantinov <blmink@mink.su>
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 45938
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At least on my b53 chip, the mask is 3 bits wide, and because
of this some STP states are not set properly and discarded when read.
Maybe for some other chips it makes sense to have just 2 bits width,
but I don't have other versions around to test/validate.
If that's the case then maybe we could add another STP state mask.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 45937
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45930
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45927
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45922
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45921
|
|
|
|
|
|
|
|
| |
being nuked by make kernel_oldconfig
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45920
|
|
|
|
|
|
|
|
|
|
|
| |
They are useless, as the platform already selects the right options for
NAND support. The main reason for removing them is the fact that it
makes kernel configs more annoying to maintain on platforms that provide
NAND drivers but disable them (e.g. ramips)
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45919
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 45918
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45916
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45915
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45914
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45913
|
|
|
|
|
|
|
|
|
| |
Extracting TRX to separated file in /tmp/ just wastes some RAM while we
can just pass a proper extracting command to the default_do_upgrade.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45912
|
|
|
|
|
|
|
|
|
| |
Extracting full TRX out of vendor format is not needed as otrx supports
passing TRX offset. This saves some RAM during sysupgrade.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45911
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45907
|
|
|
|
|
|
| |
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45906
|
|
|
|
|
|
|
|
|
| |
The v1 identifies as v10 internally. As there is no TL-WA830RE v10, add a
workaround to avoid confusing users.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
SVN-Revision: 45903
|
|
|
|
|
|
|
|
|
|
|
| |
Version 2 : White spaces and alphabetical order problems
fixed
Support for Olimex RT5350F-OLinuXino Boards, tested with RT5350F-OLinuXino and RT5350F-OLinuXino-EVB boards. More Info :
https://www.olimex.com/Products/OLinuXino/RT5350F/RT5350F-OLinuXino/open-source-hardware
Signed-off-by: Dimitar Gamishev HeHoPMaJIeH <gamishev@gmail.com>
SVN-Revision: 45902
|
|
|
|
|
|
|
|
|
|
| |
Extracting TRX to separated file in /tmp/ requires extra RAM which may
not be available on some chepaer devices. Instead of that lets pass a
proper extracting command to the default_do_upgrade.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
SVN-Revision: 45901
|
|
|
|
|
|
| |
This fixes the LAN2 LED on Arcadyan VGV7510KW22.
SVN-Revision: 45899
|
|
|
|
| |
SVN-Revision: 45897
|
|
|
|
|
|
|
|
|
|
| |
if there is any new tx need to clean up. do it in next napi poll.
collect tx related members to fe_tx_ring struct. for better
cache usage and more readable.
Signed-off-by: michael lee <igvtee@gmail.com>
SVN-Revision: 45895
|
|
|
|
|
|
|
|
|
|
| |
when open device. first ready napi software rx.
then enable hardware interrupt.
final start software tx queue to send data.
Signed-off-by: michael lee <igvtee@gmail.com>
SVN-Revision: 45894
|
|
|
|
|
|
| |
Signed-off-by: michael lee <igvtee@gmail.com>
SVN-Revision: 45893
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Avoid the use of memory marked as reserved
MT7621 support 512MB memory.
According to "MT7621_ProgrammingGuide_Preliminary_Platform.pdf"
0x0~0x1c000000 448MB
0x20000000~0x4000000 64MB
total 512MB
Signed-off-by: wengbj <fl.service@t-firefly.com>
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45892
|
|
|
|
|
|
|
|
| |
systems with >256M RAM
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45891
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45890
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45889
|
|
|
|
|
|
|
|
| |
with kernel_menuconfig
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 45888
|
|
|
|
|
|
|
|
|
| |
This also adds the old hardcoded value to the VGV7519BRN profile to make
sure that images are still generated correctly.
Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
SVN-Revision: 45882
|
|
|
|
|
|
| |
Signed-off-by: John Crispin <blogic@openwrt.org>
SVN-Revision: 45880
|
|
|
|
|
|
|
|
|
| |
Livebox does need the uncompressed kernel, so just create it during
image generation.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
SVN-Revision: 45875
|
|
|
|
|
|
|
|
|
|
| |
Ethernet GMAC is built-in the SoC, so there is no need to enable it as a
module. We'll just assume we need it. That's what is done for other
platform where this driver is used so it'll make things more consistent.
Signed-off-by: Mathieu Olivari <mathieu@codeaurora.org>
SVN-Revision: 45871
|