Kernel 4.14 has the version number 4.14 and not 4.14.0. This changed
again with some more recent kernel versions. This change makes it
possible to use kernel 4.14 without any minor version.
Signed-off-by: Hauke Mehrtens
---
include/kernel.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion
This deactivates the following options which were introduced between
kernel 4.9 and 4.14 in some kernel packages:
CONFIG_INET_ESP_OFFLOAD
CONFIG_INET6_ESP_OFFLOAD
CONFIG_LWTUNNEL_BPF
CONFIG_NET_9P_XEN
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/netsupport.mk | 8 ++--
1
The snd-seq-device.ko kernel module was moved with kernel 4.13.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/sound.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/sound.mk
b/package/kernel/linux/modules/sound.mk
index
CONFIG_FRAMEBUFFER_CONSOLE does not activate new modules any more in
kernel 4.14, but CONFIG_FRAMEBUFFER_CONSOLE is now a boolean option
which change the kmod-fb package. kmod-fbcon should be split up.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/video.mk | 2 +-
1 file
This package also compiles with kernel 4.14.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/iio.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/iio.mk
b/package/kernel/linux/modules/iio.mk
index 396ee7fbe4..8990e54813 100644
mmc_block.ko was moved with kernel 4.10.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/other.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/kernel/linux/modules/other.mk
b/package/kernel/linux/modules/other.mk
index b3ad4a051e..ef2740296a
In kernel 4.14 kmod-bluetooth depends on kmod-crypto-ecdh, add
kmod-crypto-ecdh to LEDE.
Both packages also depend on the kmod-crypto-kpp package. To build this
we have to fix the dependency of CRYPTO_ECDH which has a typo.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules
This just copies the configuration and the patches from kernel 4.9 to
the places where they are expected for kernel 4.14 without modifying
them.
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/{config-4.9 => config-4.14} | 0
.../linux/x86/{patches-4.9 => p
This is the initial step to add kernel 4.14 support by copying the
patches and configuration used for kernel 4.9 to the folders which
should be used for kernel 4.14. I did no modifications to the code.
Signed-off-by: Hauke Mehrtens
---
.../010-Kbuild-don-t-hardcode-path-to-awk-in-scripts-ld
This updates the configuration and makes the kernel patches apply
against kernel 4.14.
The subtarget configuration was refresh with kernel 4.14 and the
options needed to make it compile on kernel 4.9 were added manually.
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/64/config-default
On 12/10/2017 11:12 PM, Hauke Mehrtens wrote:
> This adds support for kernel 4.14 to LEDE.
> This ports the generic patches to kernel 4.14 and also adds support for
> kernel 4.14 to the x86 target, I am also working on adding support for
> the lantiq target, but there are still s
On 12/14/2017 10:53 PM, Roman Yeryomin wrote:
> Signed-off-by: Roman Yeryomin
Please extend your description, why you need flock and also do a small
size comparison on one target between a busybox with the default config
and the one with your patch applied.
Hauke
> ---
> package/utils/busybox/
On 12/13/2017 09:05 PM, Etienne Haarsma wrote:
> Refreshed all patches.
>
> Made the following patch for Mediatek and Oxnas compatible with kernel
> 4.4.105:
> 0072-mtd-backport-v4.7-0day-patches-from-Boris.patch
>
> Compile-tested: ar71xx
> Run-tested: ar71xx
>
> Signed-off-by: Etienne Haarsma
tement did instead of 1 like it should.
This did not happen when the -funroll-loops option was given to GCC.
Signed-off-by: Hauke Mehrtens
---
.../7.2.0/300-mips_Os_cpu_rtx_cost_model.patch | 21 -
1 file changed, 21 deletions(-)
delete mode 100644
toolchain/gcc/patches
On 12/17/2017 10:21 PM, Hauke Mehrtens wrote:
> This patch made GCC produce broken code, remove it.
> In mp_cmp_d() function in th libtommath shipped with dropbear the
> following code was compiled wrong:
>
> /* compare based on magnitude */
> if (a->used > 1) {
>
On 12/18/2017 10:34 AM, Syrone Wong wrote:
> I agree with Felix. I found libtommath issue in dropbear several
> months before. I can confirm the issue fixed by upgrading libtommath
> and libtomcrypt. The update is already done by upstream, but not
> released yet.
With this patch libtommath will be
;
> Cheers,
>
> Kevin D-B
Hi,
The attached patch also made the problem disappear.
This patch builds the code with -funroll-loops in addition, otherwise
only the default settings are used.
Hauke
From 2b58f2cac799c4eca511b12d068bd043c7f8b014 Mon Sep 17 00:00:00 2001
From: Hauke Mehrtens
Date
On 12/18/2017 11:38 PM, Hauke Mehrtens wrote:
> On 12/18/2017 03:07 PM, Kevin Darbyshire-Bryant wrote:
>>
>>
>>> On 18 Dec 2017, at 10:12, Felix Fietkau wrote:
>>>
>>> On 2017-12-18 11:07, Kevin Darbyshire-Bryant wrote:
>>>> Hi Felix,
>>
On 12/19/2017 12:01 AM, Hauke Mehrtens wrote:
> On 12/18/2017 11:38 PM, Hauke Mehrtens wrote:
>> On 12/18/2017 03:07 PM, Kevin Darbyshire-Bryant wrote:
>>>
>>>
>>>> On 18 Dec 2017, at 10:12, Felix Fietkau wrote:
>>>>
>>>> On
On 12/17/2017 06:56 PM, Kevin Darbyshire-Bryant wrote:
>
>
>> On 17 Dec 2017, at 17:22, Etienne Haarsma wrote:
>>
>> uint8_t *oob = ops->oobbuf;
>> uint8_t *buf = ops->datbuf;
>> -@@ -2662,7 +2697,7 @@ err_out:
>> - static int panic_nand_write(struct mtd_info *mtd, loff_t to, size_t le
On 12/12/2017 11:08 PM, Sandeep Sheriker Mallikarjun wrote:
> create sdcard image using gen_at91_sdcard_img.sh for sama5 platform
> and sdcard image partition layout is:
> P0: Boot (fat32) - contains(at91bootstrap,u-boot,zImage & dtb)
> p1: Rootfs (ext4)
>
> Signed-off-by: Sandeep Sheriker M
Hi Yangbo Lu,
We see some build problem for the layerscape target sine some months:
http://phase1.builds.lede-project.org/builders/layerscape%2Farmv8_32b
http://phase1.builds.lede-project.org/builders/layerscape%2Farmv8_64b
I think I fixed one problem with the tar downloads here, see:
https://git
l request. Please help to review.
> https://github.com/lede-project/source/pull/1604
>
> Thank you very much.
>
> Best regards,
> Yangbo Lu
>
>> -Original Message-
>> From: Y.b. Lu
>> Sent: 2017年12月22日 18:05
>> To: 'Hauke Mehrtens'
This adds support for kernel 4.14 to the sunxi target, It is still build
with kernel 4.9 by default. This allows to remove a lot of patches.
This was tested on a PINE64 and an Orange Pi R1.
Hauke Mehrtens (3):
sunxi: refresh kernel configuration
sunxi: Add support for kernel 4.14
sunxi
This is based on the code for kernel 4.9, but a lot of 4.9 patches are
backports from more recent kernel version and can be removed now.
Signed-off-by: Hauke Mehrtens
---
target/linux/sunxi/config-4.14 | 607 +
target/linux/sunxi/cortexa53/config-default
Just refresh the sunxi kernel configuration.
Signed-off-by: Hauke Mehrtens
---
target/linux/sunxi/config-4.9 | 3 ++-
target/linux/sunxi/cortexa53/config-default | 2 --
target/linux/sunxi/cortexa7/config-default | 1 -
target/linux/sunxi/cortexa8/config-default | 1 -
4 files
Ethernet support was initial added in kernel 4.13, but deactivated
before the final release. This is backported from kernel 4.15.
Signed-off-by: Hauke Mehrtens
---
...snps-dwmac-mdio-MDIOs-are-automatically-r.patch | 33 ++
...dwmac-sun8i-Handle-integrated-external-MD.patch | 506
es the amount of testing needed. Do you need the features added
by these patches in some other target?
I think also OMAP and probably more SoCs are using this Synopsis MAC.
Hauke
>
> On Thu, Dec 28, 2017 at 2:43 PM, Hauke Mehrtens wrote:
>> Ethernet support was initial added i
Hi antony,
On 12/28/2017 06:21 PM, Antony Antony wrote:
> Hi Hauke,
>
> This will add initial LEDE support for a new board, NanoPi NEO Plus2 board.
>
> LEDE menu options, u-boot, and kernel DT files. The patches are against
> hauke/kernel-4.14-sunxi branch.
Ok this is my development branch, no
On 11/23/2017 06:44 AM, Moritz Warning wrote:
> Hi,
>
> I've put online a firmware wizard for LEDE:
>
> http://mwarning.de/firmware-wizard/
> (Sources: https://github.com/freifunk-bielefeld/firmware-wizard)
>
> Build with rather plain HTML5/CSS/JS. Merge requests are welcome.
> Everything is s
This activates neon and VFPv4 support for this target. The CPU support
these feature so also use them.
Signed-off-by: Hauke Mehrtens
---
I do not have the hardware, could some please test if this still works
on a at91 compatible board.
target/linux/at91/sama5/target.mk | 2 ++
1 file
The CPU sub type was set to a CPU version with FPU, but the FPU feature
was not activated before, so a soft float toolchain was created.
Activate also the FPU feature to create the correct toolchain.
Signed-off-by: Hauke Mehrtens
---
This probably fixes a problem, but I do not have any
]: Recipient address rejected: Access denied
[DB5EUR01FT058.eop-EUR01.prod.protection.outlook.com] (in reply to RCPT
TO command)
Are you the current maintainer? If so can you please send a patch to fix
this please.
Hauke
On 01/01/2018 04:58 PM, Hauke Mehrtens wrote:
> The CPU sub type was set to a
On 01/01/2018 08:04 PM, perillamint wrote:
> BTW, it seems Intel Quark X1000 SoC may affected by Pentium F00F bug or
> its variant (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738575)
>
> I wonder LEDE build system can workaround this kind of bug. It seems
> appending NOP before every LOCK i
enwrt.git;a=commitdiff;h=597de6904c39e02a8aa008f50ff19c6793117194
Mathew McBride also tested this on his LS1043 board and did not notice
any problems.
Hauke
>
> I will send related patches to community after release.
> Thanks a lot.
>
>
> Best regards,
> Yangbo Lu
>
>
>> -Original
On 12/15/2017 03:10 PM, Roman Yeryomin wrote:
> There is a race between `cp -a /tmp/root/* /rom/overlay` from
> libfstools/overlay.c and a process creating new file(s) before
> pivot(/rom, /mnt) occured.
> That is a process can create a file and it will not be copied.
>
> To workaround this, do ad
Use the default build definitions instead of some custom one. The custom
one added -mfloat-abi=soft which is used in the kernel build and the
normal -mfloat-abi=hard was added in addition which caused a build
problem.
Fixes: 01cc6bd495f31 ("at91: sama5: activate fpu")
Signed-off
directory '/home/sandeep/microchip/arm/lede'
> /home/sandeep/microchip/arm/lede/include/toplevel.mk:216: recipe for
> target 'world' failed
> make: *** [world] Error 2
The patch was already merged, but I was able to reproduce this problem
and fixed in in the u-boot build
-off-by: Hauke Mehrtens
---
...compat-add-fallback-for-unsupported-libcs.patch | 147 +
...pi-libc-compat.h-do-not-rely-on-__GLIBC__.patch | 107 ---
...er.h-prevent-redefinition-of-struct-ethhd.patch | 46 +++
.../pending-3.18/002-phy_drivers_backport.patch
The OpenWrt and the LEDE project are happily announcing the unification
of both projects under the OpenWrt name.
After long and sometimes slowly moving discussions about the specifics
of the re-merge, with multiple similar proposals but little subsequent
action, we're happy to announce that both p
On 01/04/2018 08:43 PM, Sandeep Sheriker Mallikarjun wrote:
> neon and VFPv4 support is added to this target and uboot-at91 build
> fails due to TARGET_CFLAGS -mfloat-abi set to hard. as a fix, setting
> uboot-at91 CFLAGS -mfloat-abi=soft.
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> ---
On 01/05/2018 09:16 AM, Nishant Sharma wrote:
> Hi,
>
> First of all, congratulations on re-merge of OpenWrt and LEDE.
>
> Now to the problem being faced. I am trying to build OpenWrt for
> Espressobin (http://espressobin.net) as described in their wiki at
> http://wiki.espressobin.net/tiki-index
With Linux kernel 4.16 it will be possible to guard more parts of the
Linux header files from a libc. Make use of this in musl to guard all
the structures and other definitions from the Linux header files which
are also defined by the header files provided by musl. This will make
musl compile with
Previously this was only activated for ADSL, this patch activates the
same setting also for VDSL.
Signed-off-by: Hauke Mehrtens
---
package/network/config/ltq-vdsl-app/files/dsl_control | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app
This is needed to prevent copying it into kernel 4.14.
These device tree files are already integrated into kernel 4.14 and we
would like to use the upstream versions only.
Signed-off-by: Hauke Mehrtens
---
.../{files => files-4.4}/arch/arm/boot/dts/armada-385-linksys-rango.dts | 0
.../{fi
kernel 4.9 please report
this.
Hauke Mehrtens (3):
mvebu: move files to files-4.9 and files-4.4 folder
mvebu: copy config and patches from 4.9 to 4.14
mvebu: Make kernel 4.14 patches apply
target/linux/mvebu/config-4.14 | 489 ++
.../arch/arm/boot/dts/armada
This is in preparation for the 4.14 port, this is just coping all the
files to make it easier to see the differences between kernel 4.9 and
kernel 4.14.
Signed-off-by: Hauke Mehrtens
---
target/linux/mvebu/{config-4.9 => config-4.14}| 0
.../linux/mvebu/{patches-
Without this patch one sdcard image with the following name is created
for all devices:
openwrt-at91-sama5--sdcard.img.gz
This makes the build system create device specific versions like:
openwrt-at91-sama5-at91-sama5d2_xplained-sdcard.img.gz
Signed-off-by: Hauke Mehrtens
---
target/linux/at91
These packages are needed to generate the image, better mark them hidden
so we will activate them based on which boards gets build and they will
be activated always when the board which needs then gets build.
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 1 +
1 file
The default configuration file for sama5d4_xplainednf_uboot does not
exist, but a default configuration file for
sama5d4_xplainednf_uboot_secure exists, fix the name.
Fixes: 670448a002 ("at91bootstrap: New package at91bootstrap")
Signed-off-by: Hauke Mehrtens
---
package/boot/at9
: New package at91bootstrap")
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/package/boot/at91bootstrap/Makefile
b/package/boot/at91bootstrap/Makefile
index a0b0594fb2..002c68b138 10
It is sufficient to define this in AT91Bootstrap/Default as this is not
used for all.
Signed-off-by: Hauke Mehrtens
---
package/boot/at91bootstrap/Makefile | 8
1 file changed, 8 deletions(-)
diff --git a/package/boot/at91bootstrap/Makefile
b/package/boot/at91bootstrap/Makefile
index
These packages are needed to generate the image, better mark them hidden
so we will activate them based on which boards gets build and they will
be activated always when the board which needs then gets build.
Signed-off-by: Hauke Mehrtens
---
package/boot/uboot-at91/Makefile | 1 +
1 file
On 01/09/2018 12:07 AM, Sandeep Sheriker wrote:
> Hi Hauke,
> I have already fixed this and submitted this patch. below is the
> patch link for references.
>
> https://patchwork.ozlabs.org/patch/855788/
>
> Regards,
> Sandeep Sheriker M
Thanks for the hint, I applied this patch now.
Hauke
On 01/05/2018 12:14 AM, Sandeep Sheriker Mallikarjun wrote:
> 1. enabled DMA controller options
> 2. Enabled CMA options
> 3. enabled VFP options
> 4. Add Atmel SD/MMC Driver
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> ---
> target/linux/at91/sama5/config-default | 43
> +++
Boot has some code which should add the needed
compiler settings independently of the build system and we do not need
to provide it some special settings.
Hauke
> On 01/04/2018 04:23 PM, Hauke Mehrtens wrote:
>> On 01/04/2018 08:43 PM, Sandeep Sheriker Mallikarjun wrote:
>>> neo
On 01/08/2018 06:57 AM, Felix Fietkau wrote:
>
>
>> On 8. Jan 2018, at 10:31, Florian Fainelli wrote:
>>
>> When building with an external kernel tree, do not check the different
>> platform files since this is almost guaranteed they are going to differ.
>>
>> Signed-off-by: Florian Fainelli
>
On 01/17/2018 08:41 PM, Zoltan HERPAI wrote:
> Signed-off-by: Zoltan HERPAI
> ---
> package/firmware/linux-firmware/x86.mk | 9 +
> 1 file changed, 9 insertions(+)
> create mode 100644 package/firmware/linux-firmware/x86.mk
>
> diff --git a/package/firmware/linux-firmware/x86.mk
> b/pa
On 01/18/2018 01:51 PM, Nick Lowe wrote:
> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
> properly address this? There are fixes to mitigate Spectre.
We even need a patch for GCC which will be in GCC 8 and 7.3.
For master we should backport it to GCC 5.5, but what do we want
On 01/09/2018 12:23 AM, Sandeep Sheriker Mallikarjun wrote:
> Add support for SAMA5D27 SOM1 EK board.
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> ---
> package/boot/uboot-at91/Makefile | 13 ++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/package/boot/
On 01/09/2018 12:23 AM, Sandeep Sheriker Mallikarjun wrote:
> 1. Add support for SAMA5D27 SOM1 EK board
> 2. version update to v3.8.9
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> ---
> package/boot/at91bootstrap/Makefile | 20 +---
> 1 file changed, 17 insertions(+), 3 de
On 01/20/2018 11:15 AM, Christian Lamparter wrote:
> On Friday, January 19, 2018 10:06:50 PM CET Ben Greear wrote:
>> On 01/19/2018 01:03 PM, Christian Lamparter wrote:
>>> On Friday, January 19, 2018 9:12:04 PM CET gree...@candelatech.com wrote:
From: Ben Greear
This will allow us
On 01/18/2018 11:41 PM, Zoltan HERPAI wrote:
>
>
> On Thu, 18 Jan 2018, Hauke Mehrtens wrote:
>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address this? There are fixes to
Hi,
I updated the patches which are making the kernel headers compatible
with musl libc in this commit:
https://git.openwrt.org/4336efe14b61e47177a2d0863f8391c48cf4a9f5
These are now the versions which are included in upstream Linux kernel 4.15.
This could cause some compile problems in iproute2
/git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.9.77&id=43fe95308d276bdfd133f5951cc25565e39982ec
>>>
>>> Can we backport this?
>>
>>
>> No, it's not missing, it's just in a different location:
>>
>> http
quot; part with "pcie" on all nodes if the
file exists in sys fs.
This will not do anything with on kernel 4.9.
The configuration will not be fixed when migrating back from kernel 4.14
to kernel 4.9.
Signed-off-by: Hauke Mehrtens
---
.../base-files/etc/uci-defaults/05-
This is in preparation for the 4.14 port, this is just coping all the
files to make it easier to see the differences between kernel 4.9 and
kernel 4.14.
Signed-off-by: Hauke Mehrtens
---
target/linux/mvebu/{config-4.9 => config-4.14}| 0
.../linux/mvebu/{patches-
This is needed to prevent copying it into kernel 4.14.
These device tree files are already integrated into kernel 4.14 and we
would like to use the upstream versions only.
Signed-off-by: Hauke Mehrtens
---
.../{files => files-4.4}/arch/arm/boot/dts/armada-385-linksys-rango.dts | 0
.../{fi
(downgrade) from kernel 4.14 to 4.9
* rename the wireless driver path when upgrading
Hauke Mehrtens (5):
kernel: ubifs: create use file system format 4 by default
mvebu: move files to files-4.9 and files-4.4 folder
mvebu: copy config and patches from 4.9 to 4.14
mvebu: Make kernel 4.14
just not be used when a ubifs partition is created
implicitly on an empty UBI volume.
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 1 +
...ption-to-create-UBI-FS-version-4-on-empty.patch | 63 ++
2 files changed, 64 insertions
On 01/24/2018 06:26 PM, Evgeniy Didin wrote:
> This commit finally bumps ARC tools to the most recent arc-2017.09 release
> version.
>
> ARC GNU tools of version arc-2017.09 bring some quite significant changes
> like:
> * Binutils v2.29 with additional ARC patches
> * GCC 7.1.1 with additiona
On 01/24/2018 05:28 AM, Rosen Penev wrote:
> At least one application (transmission) depends on CURL_CA_BUNDLE being
> set in order to operate properly (Could not connect to tracker errors).
> As far as I can tell, there's no real drawback to doing this for all
> TLS libraries supported by curl.
D
Hi,
On 01/23/2018 05:48 PM, Evgeniy Didin wrote:
> Update Linux kernel version from 4.9 to 4.14 for archs38.
> config-4.14 was simply regenerated with "make kernel_menuconfig".
>
> Signed-off-by: Evgeniy Didin
> Cc: Alexey Brodkin
> Cc: John Crispin
> ---
> target/linux/archs38/Makefile
On 01/29/2018 04:35 PM, Evgeniy Didin wrote:
> Hello Hauke,
>
> There are two patches, which solves problem with undefined "Abort":
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm
> it/?id=7c2c11b208be09c156573fc0076b7b3646e05219
> https://git.kernel.org/pub/scm/linux/ker
t;> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc8635b78cd8669c37e230058d18c33af7451ab1
>
>> So lets add backport patches until these fixes
>> are not applied in stable version.
>
>> Signed-off-by: Evgeniy Didin
>> Cc: Alexey Brodkin
>> CC:
On 02/09/2018 12:27 AM, Lucian Cristian wrote:
> On 21.01.2018 19:53, Hauke Mehrtens wrote:
>> This add support for kernel 4.14 to the mvebu target. My main reason to
>> add kernel 4.14 support is to make it easier to also add support for the
>> Marvell Armada 3700LP ARM6
On 01/21/2018 06:53 PM, Hauke Mehrtens wrote:
> This add support for kernel 4.14 to the mvebu target. My main reason to
> add kernel 4.14 support is to make it easier to also add support for the
> Marvell Armada 3700LP ARM64 SoCs especially the ESPRESSObin board.
>
> I do not
On 02/09/2018 09:46 PM, Philip Prindeville wrote:
>
>
>> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote:
>>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address
On 02/09/2018 11:57 PM, Rosen Penev wrote:
> On Fri, Feb 9, 2018 at 1:52 PM, Hauke Mehrtens wrote:
>> On 01/21/2018 06:53 PM, Hauke Mehrtens wrote:
>>> This add support for kernel 4.14 to the mvebu target. My main reason to
>>> add kernel 4.14 support is to make it eas
This config option was renamed in upstream Linux commit 681bec0367
("tracing: Rename update the enum_map file")
Reported-by: Rosen Penev
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/lin
pu feature flag set. If this toolchain is reused by other targets
this will even affect other targets.
Signed-off-by: Hauke Mehrtens
---
target/linux/mediatek/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mediatek/Makefile b/target/linux/mediatek
Make it easily possible to add a custom script in front of this hotplug
script which adds new devices. This is needed for the mvebu target in
which we want to migrate the old configuration before new devices are
getting detected.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211
vfs_write() is not exported on kernel 4.14 any more and kernel_write()
should be used instead.
Signed-off-by: Hauke Mehrtens
---
.../mwlwifi/patches/001-remove-vfs_write.patch | 92 ++
1 file changed, 92 insertions(+)
create mode 100644 package/kernel/mwlwifi/patches
From: Chris Breuer
Changes since last merge into OpenWrt since 2017-12-14:
- Added debugfs file tx_hist.
- Added debugfs file fixed_rate.
- Added debugfs file ba_hist.
- Modified the way to establish BA stream.
- Added code to control BF type.
- Added functions to check/dump dhcp packet.
-
-by: Hauke Mehrtens
---
package/kernel/mwlwifi/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/kernel/mwlwifi/Makefile b/package/kernel/mwlwifi/Makefile
index fca2a386aa..48de8da41f 100644
--- a/package/kernel/mwlwifi/Makefile
+++ b/package/kernel/mwlwifi
latest commit 20180208
Hauke Mehrtens (9):
kernel: ubifs: create use file system format 4 by default
mac80211: move wifi detect hotplug script to later
mvebu: move files to files-4.9 and files-4.4 folder
mvebu: copy config and patches from 4.9 to 4.14
mvebu: Make kernel 4.14 patches apply
d
it will trigger an event via hotplug to detect new devices and as the
paths are not in the uci configuration they will be added again.
When the migration is done before the script will detect that they are
already there.
Signed-off-by: Hauke Mehrtens
---
.../etc/hotplug.d/ieee80211/00-wifi
This is in preparation for the 4.14 port, this is just coping all the
files to make it easier to see the differences between kernel 4.9 and
kernel 4.14.
Signed-off-by: Hauke Mehrtens
---
target/linux/mvebu/{config-4.9 => config-4.14}| 0
.../linux/mvebu/{patches-
This switches to kernel 4.14 by default.
Signed-off-by: Hauke Mehrtens
---
target/linux/mvebu/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mvebu/Makefile b/target/linux/mvebu/Makefile
index a07aa7cf2d..6f0c1925c2 100644
--- a/target/linux/mvebu
This is needed to prevent copying it into kernel 4.14.
These device tree files are already integrated into kernel 4.14 and we
would like to use the upstream versions only.
Signed-off-by: Hauke Mehrtens
---
.../{files => files-4.4}/arch/arm/boot/dts/armada-385-linksys-rango.dts | 0
.../{fi
just not be used when a ubifs partition is created
implicitly on an empty UBI volume.
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 1 +
...ption-to-create-UBI-FS-version-4-on-empty.patch | 63 ++
2 files changed, 64 insertions
On 02/01/2018 11:35 PM, Tim Harvey wrote:
> Signed-off-by: Tim Harvey
> ---
> target/linux/generic/config-4.14 | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/target/linux/generic/config-4.14
> b/target/linux/generic/config-4.14
> index fa389bf..89f2f43 100644
>
Hi Tim,
sorry that I haven't reviewed this earlyer, but now I saw some problems,
see my comments inline.
Can you please create a follow up patch based on current master branch.
On 01/24/2018 12:15 AM, Tim Harvey wrote:
> The Cavium OCTEON TX is an ARM 64-bit SoC leveraging CPU cores and
> peripe
On 02/13/2018 09:46 PM, Hauke Mehrtens wrote:
> Hi Tim,
>
> sorry that I haven't reviewed this earlyer, but now I saw some problems,
> see my comments inline.
>
> Can you please create a follow up patch based on current master branch.
>
> On 01/24/2018 12:15 AM, Ti
Remove this old patch which prevents showing the xfrm ports for SCTP
This was added in commit 60c1f0f64d23 ("finally move buildroot-ng to trunk")
---
.../network/utils/iproute2/patches/006-no_sctp.patch | 18 --
1 file changed, 18 deletions(-)
delete mode 100644 package/network
On 02/15/2018 05:34 PM, Tim Harvey wrote:
> Testted on a Gateworks GW54xx. Does not support enabling imx-drm modules
> yet as those will need some adjustments based on kernel configs.
>
> v3:
> - included missing patch for pcie enumeration fix
>
> v2:
> - move dwc pci patch to generic (Koen)
>
On 02/15/2018 05:34 PM, Tim Harvey wrote:
> Backport of: http://patchwork.ozlabs.org/patch/860701/
>
> Signed-off-by: Tim Harvey
> ---
> .../generic/pending-4.14/812-pci-dwc-fix-enumeration.patch| 11
> +++
> 1 file changed, 11 insertions(+)
> create mode 100644
> target/linux/ge
On 02/15/2018 06:42 PM, Tim Harvey wrote:
> On Tue, Feb 13, 2018 at 12:51 PM, Hauke Mehrtens wrote:
>> On 02/13/2018 09:46 PM, Hauke Mehrtens wrote:
>>> Hi Tim,
>>>
>>> sorry that I haven't reviewed this earlyer, but now I saw some problems,
>>&
Hi,
I would like to use kernel 4.14 by default on the mvebu target soon.
If you are aware of any regressions compared to kernel 4.9 then please
report them, now.
I only have a Linksys device here for testing and I haven't tested the
SFP functionality, would be nice if someone could test if that s
On 02/18/2018 12:35 PM, John Crispin wrote:
>
>
> On 17/02/18 13:30, Hauke Mehrtens wrote:
>> On 02/15/2018 05:34 PM, Tim Harvey wrote:
>>> Testted on a Gateworks GW54xx. Does not support enabling imx-drm modules
>>> yet as those will need some adjustments ba
201 - 300 of 453 matches
Mail list logo
