This is required to use x86/64 in KVM containers with VirtIO disks

Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>

SVN-Revision: 46017

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

SVN-Revision: 46013

It seems that there are maximum timings for mdio accesses that can be
hit when the system is under load and the thread is scheduled during
a read or write access. Since there is no way of knowing if this
happens as there is not even a parity bit, try to work around it
by disabling interrupts during any gpio-mdio accesses.

Performance impact seems to be neglectable, as mdio accesses are not
that often.

Hopefully fixes #19500.

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

SVN-Revision: 46012

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: 46008

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

SVN-Revision: 46007

SVN-Revision: 46006

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

SVN-Revision: 46005

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

SVN-Revision: 46004

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

SVN-Revision: 46003

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

SVN-Revision: 46001

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

SVN-Revision: 45999

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: 45995

On bcm53xx we still need usb-ohci to support USB 1.1 devices and it
obviously needs bcma-hcd.ko that will init controller and register
platform device.

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

SVN-Revision: 45994

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

SVN-Revision: 45992

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

SVN-Revision: 45990

Signed-off-by: Toke Høiland-Jørgensen <toke@toke.dk>

SVN-Revision: 45988

This one cannot possibly work, as it depends on cfg80211, which is built
out of tree.

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

SVN-Revision: 45985

Besides source.tgz, 001-elfutils-portability.patch (provided by upstream
project) where updated.

Other patches where updated to fix hulk warnings and minor conflicts.

Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>

SVN-Revision: 45984

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

pad-to can be used in a pipe to pad the image to a specific chunk-size.
Signed-off-by: Alexander Couzens <lynxis@fe80.eu>

SVN-Revision: 45980

Signed-off-by: Alexander Couzens <lynxis@fe80.eu>

SVN-Revision: 45979

Currently "make clean" only clears the build_dir/target*, but leaves
staging_dir/target* intact. "make clean" should also clean the
staging_dir/target* directories, as in the current situation some old
packages or libraries may be linked into the firmware from staging_dir
despite a "make clean".

The patch reorganises clean / dirclean functionality so that
* "make clean" also clears the staging_dir/target* in addition to
build_dir/target*.
* "make dirclean" clears toolchain and host(=tools) directories from both
build_dir and staging_dir

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

SVN-Revision: 45973

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

SVN-Revision: 45972

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

elfutils is required by perf. So we'll move this package from
packages.git and make it part of the core distribution.

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

SVN-Revision: 45969

bzip2 is required by elfutils, itself required by perf. So we'll move
this package from packages.git and make it part of the core
distribution.

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

SVN-Revision: 45968

argp-standalone is required by elfutils, itself required by perf. So
we'll move this package from packages.git and make it part of the core
distribution.

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

SVN-Revision: 45967

Hello,

I found out that in some rare cases grep can treat Makefile as a binary file. That happened to me on UTF-8 Gentoo if Makefile contained a character which was from extended ASCII table.
Without this patch the output of the grep command in the $(FILELIST) target is not valid (contains line "Binary file matches") and following commands fail to create feed index file.

Best Regards,
Martin Strbacka

Signed-off-by: Martin Strbacka <martin.strbacka@nic.cz>

SVN-Revision: 45966

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

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

SVN-Revision: 45964

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

Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>

SVN-Revision: 45962

This is for security precautions.  As persist_tun and persist_key are
already there, this should not cause compatibility issue.

Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>

SVN-Revision: 45961

As reported in ticket #19104, auth_retry takes a <type> argument with 3
choices: none, nointeract, interact.

Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>

SVN-Revision: 45960

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

SVN-Revision: 45959