The removed patchesd are already inteagrted in the upstream version.
Signed-off-by: Hauke Mehrtens
---
package/network/utils/iperf/Makefile | 6 +-
...n-signal-handling-per-POSIX-calling-.patch | 43 -
...rtup-fix-daemon-mode-per-redirecting.patch | 161 --
.../pa
The following firmware files we use are updated in this change:
ath10k/QCA6174/hw3.0/board-2.bin
ath10k/QCA9888/hw2.0/firmware-5.bin
ath10k/QCA988X/hw2.0/firmware-5.bin
ath10k/QCA9984/hw1.0/firmware-5.bin
mrvl/sd8887_uapsta.bin
mrvl/pcie8897_uapsta.bin
iwlwifi-8000C-36.ucode
iwlwifi-8265-36.ucode
Signed-off-by: Hauke Mehrtens
---
I would prefer to switch back to the tar.bz2 download again as we
download the U-Boot as a tar.bz2 also in other places.
package/boot/uboot-envtools/Makefile | 8
package/boot/uboot-envtools/patches/001-compile.patch | 6 +++---
2 file
This updates the U-Boot which provides the host tools like mkimage to
version 2019.04.
The patches were cleaned up and it was checked if this still compiles
on Linux and FreeBSD.
CONFIG_FIT_SIGNATURE_MAX_SIZE is set to the default value.
The patch for libressl was merged upstream.
Signed-off-by:
On 5/2/19 7:52 PM, Jeffery To wrote:
> This changes the default PKG_BUILD_DIR to take BUILD_VARIANT into
> account (if set), so that packages do not need to manually override
> PKG_BUILD_DIR just to handle variants.
>
> This also updates most base packages with variants to use the updated
> defaul
All of U-Boot scripts repeat the same pattern with only Device Tree blob
name changing for respective device. Therefore create generic scripts
which will be altered on demad by image build process, and create
BOOT_SCRIPT variable which can be added to device recipe and will allow
referencing the sa
This commit adds support for different iterations of ESPRESSObin.
The added variants are:
ESPRESSObin with soldered eMMC,
ESPRESSObin V7, compared to V5 some passive elements changed and ethernet
ports labels positions have been reversed,
ESPRESSObin V7 with soldered eMMC.
Please refer to:
584d
Convert whole target to Device Tree based board detection instead of
identifying devices by dts file name. With this we can drop mvebu.sh
translation script and rely on common method for model detection.
Signed-off-by: Tomasz Maciej Nowak
---
package/boot/uboot-envtools/files/mvebu | 26 ++
Add vendors in device names and also rename few device names, for easier
identyfying potential firmware to flash. The vendor and device string is
mainly derived from model/compatipble string in dts from particular
device, but since not all devices are well described, some of the renames
follow mark
Drop overly complex amount of defines wich are referenced in the same
devices pool and move image recipes to common define, since devices not
using them overwrite it.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 21 ---
target/linux/mvebu/image/corte
Even if dts is not included in upstream Makefile, it is built anyway by
recipe specified in include/image.mk. Also remove Build/dtb, it's not
used since 3f72f3a ("mvebu: clearfog: include DTB for all variants in
image").
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile
All of arm64 devices have part of variables repeatedly defined. Stack
them to common define, and reference it in each device recipe.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 8
target/linux/mvebu/image/cortex-a53.mk | 12 ++--
target/linux
Use make syntax to pass the U-Boot image location and boot with root
partitions size, instead of relying on shell functions and variables.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/mvebu/image/Makefile | 18 ++
.../linux/mvebu/image/gen_mvebu_sdcard_img.sh
This series drops unnecessary cruft and improves image code, so that
it's better aligned with most well maintained targets in OpenWrt.
Additionally it introduces image for three ESPRESSObin variants.
Changes in v3:
Rebase
mvebu: use device-tree board detection:
change also device strings in uboot
On 5/11/19 3:48 PM, Zoltan HERPAI wrote:
> Hi Hauke,
>
> On Sat, 11 May 2019, Hauke Mehrtens wrote:
>
>> The next OpenWrt release will only contain support for kernel 4.14, to
>> still support the ixp4xx target update it to kernel 4.14.
>>
>> This was only build tested, I do not have this device,
Hi Hauke,
On Sat, 11 May 2019, Hauke Mehrtens wrote:
The next OpenWrt release will only contain support for kernel 4.14, to
still support the ixp4xx target update it to kernel 4.14.
This was only build tested, I do not have this device, could someone
please run test it on some device and repor
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 10 +-
target/linux/generic/config-4.19 | 10 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/target/linux/generic/config-4.14 b/target/linux/generic/config-4.14
index 396139cb39..888401376c 1
Instead of maintaining 3 very similar subtargets merge them into one.
This does not use the Arm NEON extension any more, because the SAMA5D3
does not support NEON.
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 26 -
package/boot/uboot-at91/Makefile
This adds support for kernel 4.14 to the target and directly make it the
default kernel version to use.
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/Makefile| 2 +-
target/linux/at91/{config-4.9 => config-4.14} | 45 +-
target/linux/at91/legacy/config-default
This removes some settings which are normally set by the generic
configuration and should not be changed.
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/config-4.9 | 19 +--
target/linux/at91/sama5d2/config-default | 3 ---
2 files changed, 1 insertion(+), 21 de
The next OpenWrt release will only contain support for kernel 4.14, to
still support the at91 target update it to kernel 4.14.
This was only build tested, I do not have this device, could someone
please run test it on some device and report the results back.
The patches are also available in th
The configuration of the sama5d4 subtarget was used as the default
configuration and then the subtarget configurations were adapted.
The resulting kernel configuration without any extra modules selected is
still the same.
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/config-4.9
The configuration of the generic subtarget was used as the default
configuration and then the subtarget configurations were adapted.
Signed-off-by: Hauke Mehrtens
---
target/linux/orion/config-4.9 | 40 +--
.../patches-4.9/210-wn802t_support.patch | 23 ++
This adds support for kernel 4.14 to the target and directly make it the
default kernel version to use.
Signed-off-by: Hauke Mehrtens
---
target/linux/orion/Makefile | 2 +-
.../linux/orion/{config-4.9 => config-4.14} | 28 +--
target/linux/orion/harddisk/con
The next OpenWrt release will only contain support for kernel 4.14, to
still support the orion target update it to kernel 4.14.
This was only build tested, I do not have this device, could someone
please run test it on some device and report the results back.
The patches are also available in t
The next OpenWrt release will only contain support for kernel 4.14, to
still support the ixp4xx target update it to kernel 4.14.
This was only build tested, I do not have this device, could someone
please run test it on some device and report the results back.
The patches are also available in
This adds support for kernel 4.14 to the target and directly make it the
default kernel version to use.
Signed-off-by: Hauke Mehrtens
---
target/linux/ixp4xx/Makefile | 2 +-
.../linux/ixp4xx/{config-4.9 => config-4.14} | 18 +---
target/linux/ixp4xx/harddisk/config-de
The configuration of the generic subtarget was used as the default
configuration and then the subtarget configurations were adapted.
Signed-off-by: Hauke Mehrtens
---
target/linux/ixp4xx/config-4.9 | 7 +++
target/linux/ixp4xx/harddisk/config-default | 23 ++---
This adds support for kernel 4.14 to the target and directly make it the
default kernel version to use.
Signed-off-by: Hauke Mehrtens
---
.../patches-D7.04.03.00/270-4.14_fixes.patch | 51 +++
target/linux/ar7/Makefile | 2 +-
target/linux/ar7/{config-4.9 =>
The configuration of the generic subtarget was used as the default
configuration and then the subtarget configurations were adapted.
Signed-off-by: Hauke Mehrtens
---
target/linux/ar7/config-4.9 | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/ar7/config-4.9 b/target/linux/ar7
The next OpenWrt release will only contain support for kernel 4.14, to
still support the ar7 target update it to kernel 4.14.
This was only build tested, I do not have this device, could someone
please run test it on some device and report the results back.
The patches are also available in thi
show license in `opkg info `.
Signed-off-by: Paul Spooren
---
This patch isn't complete yet. It show the license info as long as the package
isn't installed. Once it's installed it seems to forget the information. I can't
figure out why. Also printing `opkg list` doesn't add the License, neither
32 matches
Mail list logo
