Sehr geehrte Damen und Herren,
Wir sind froh, Ihnen mitteilen zu können das der Domain onlinedoc.at zur
möglichen Abgabe steht.
Würden Sie mir bitte eine kurze Rückmeldung geben ob wir Ihre Interesse geweckt
haben?
Ich wünsche einen guten Start in die neue Woche.
Maria Daniello
_
On 2018-01-15 at 06:17 +0300, Ivan Shapovalov wrote:
> Hello,
>
> I've noticed a bug in LEDE's handling of USB 3G modems using QMI
> protocol (at least), which leads to broken hotplug. It's actually
> been
> present for quite long (since BB or CC). I've tracked down the root
> cause but I'm unsure
Hello,
I'm currently porting LEDE(wait, OpenWRT now?) on Intel Galileo.
Since not every Intel Quark board has GPIO multiplexer chips like
Galileo, I think I have to separate board specific components into
separate Kconfig and keep platform Kconfig clean.
Is there any documentation about this kin
On 01/21/2018 07:54 AM, Christian Lamparter wrote:
On Saturday, January 20, 2018 1:27:04 AM CET gree...@candelatech.com wrote:
From: Ben Greear
Initial beta release of the CT IPQ4019 firmware. Features are
similar to the CT 9984 firmware
+$(eval $(call BuildPackage,ath10k-firmware-qca401
On 21-01-18 19:21, Jo-Philipp Wich wrote:
> Hi,
>
> ACK from me as well.
>
>> ACK to enable it for packages, not sure if it makes sense for core as we
>> enforce this in the project git repo already, and Github is just a mirror.
> It does make sense to provide immediate feedback on Github pull requ
The interesting part is that for ipq806x there has been an extra definition
for Winbond W25N01GV where the pagesize has been finetuned:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ipq806x/patches-4.9/104-mtd-nand-add-Winbond-manufacturer-and-chip.patch;hb=HEAD
That has
Small update on this: It seems that all of the removed CONFIG settings
are set anyways. That is, there is no difference in the final kernel
.config file. Which leads me to believe that this issue was fixed
upstream somehow. I'll be doing further testing to verify.
On Mon, Jan 15, 2018 at 1:37 PM,
Sorry, my fingers might have been quicker than my thoughts. Was the
first tthing I thought about, but haven't thoroughly checked the
WRT3200ACM issue.
Stijn
Op zo, 21 jan 2018 om 9:04 , schreef Stijn Segers
:
Hi Hannu,
See
http://lists.infradead.org/pipermail/lede-dev/2018-January/010870.h
Hi Hannu,
See
http://lists.infradead.org/pipermail/lede-dev/2018-January/010870.html
Apparently supported as from 4.11
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hauke Mehrtens kirjoitti 21.1.2018 klo 19:53:
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 wonder if 4.14 adds support for the
Instead of creating an ubifs file system with format version 5 by
default on empty UBI volumes use the older format 4 by default. This
will make it possible to mount these file systems also on older kernel
versions.
When a user wants to do a sysupgrade from kernel 4.14 to kernel 4.9 the
old kernel
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
.../{files
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 have any of the currently supported boards so I can not runtime
test this
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-4.4 =
The name of the PCIe controller node in device tree changed between
kernel 4.9 and kernel 4.14. Migrate the configuration when an update
from kernel 4.9 to 4.14 is done to the new name to make the existing
wifi configuration compatible with the new names.
This replaces the "pcie-controller" part w
On 19-01-18 15:02, Piotr Dymacz wrote:
>
>
> On 19.01.2018 13:09, Etienne Champetier wrote:
>
>> We can also make it mandatory (show "required" on the fail test line)
>> Also this is a good minimum check to have on ALL repo
>> There are many ways to do it, enabling DCO is a 2 minutes job (if
>> som
Hi,
ACK from me as well.
> ACK to enable it for packages, not sure if it makes sense for core as we
> enforce this in the project git repo already, and Github is just a mirror.
It does make sense to provide immediate feedback on Github pull requests
I assume.
~ Jo
__
Yup, this affects both 4.4.112 and 4.9.77
A fix for this has been queued by Greg for both 4.4.113 and 4.9.78
It does not affect 4.14.14
Cheers,
Nick
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/le
Ironically, 4.4.112 is reporting similar behaviour:
# grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable
root@PC En
(Readded: Hauke Mehrtens )
On Saturday, January 20, 2018 5:40:08 PM CET Ben Greear wrote:
>
> On 01/20/2018 02: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, 20
Hi,
Thanks! I have done so and this is now queued for 4.9.y and 4.4.y
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=d28663e54705568523979ab8097b9672ee79b17f
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=8ea729c00403414d744
On Saturday, January 20, 2018 1:27:04 AM CET gree...@candelatech.com wrote:
> From: Ben Greear
>
> Initial beta release of the CT IPQ4019 firmware. Features are
> similar to the CT 9984 firmware
>
> Signed-off-by: Ben Greear
> ---
> package/firmware/ath10k-firmware/Makefile | 74
> ++
Citeren Jonas Gorski :
Hi,
On 18 January 2018 at 10:50, Koen Vandeputte
wrote:
A lot of targets have more than sufficient space to allow
building the kernel for speed iso size.
Export this performance option to the main config:
- Making it easy accessable for users
- Discarding the need to
Hi,
On 18 January 2018 at 10:50, Koen Vandeputte
wrote:
> A lot of targets have more than sufficient space to allow
> building the kernel for speed iso size.
>
> Export this performance option to the main config:
>
> - Making it easy accessable for users
> - Discarding the need to adjust it in th
On 01/21/2018 01:07 PM, Nick Lowe wrote:
> Hi Arjen,
>
> The point I was making is that we see:
>
> root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat meltdown
> Vulnerable
>
> This should not be marked as vulnerable and it is being.
>
> Cheers,
>
> Nick
>
> On Sun, Jan 21, 2018 at 12:04
Hi Arjen,
The point I was making is that we see:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat meltdown
Vulnerable
This should not be marked as vulnerable and it is being.
Cheers,
Nick
On Sun, Jan 21, 2018 at 12:04 PM, Arjen de Korte
wrote:
> Citeren Nick Lowe :
>
>
>> Yes, compiler
Citeren Nick Lowe :
Yes, compiler updates will ultimately be necessary to properly close this.
We can see for now with 4.9.77:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat spectre_v2
Vulnerable: Minimal AMD ASM retpoline
AMD processors are also incorrectly being marked as being vuln
Yes, compiler updates will ultimately be necessary to properly close this.
We can see for now with 4.9.77:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat spectre_v2
Vulnerable: Minimal AMD ASM retpoline
AMD processors are also incorrectly being marked as being vulnerable
to Meltdown. On
> On 18 Jan 2018, at 09:50, Koen Vandeputte
> wrote:
>
> A lot of targets have more than sufficient space to allow
> building the kernel for speed iso size.
>
> Export this performance option to the main config:
>
> - Making it easy accessable for users
> - Discarding the need to adjust it i
John Crispin wrote:
On 17/01/18 20:41, Zoltan HERPAI wrote:
Hi,
This series will add support for microcode update on x86 targets,
in light of the recent security issues.
While other distributions use an early initramfs approach to update
the microcode as early as possible, in OpenWrt the ear
30 matches
Mail list logo
