[LEDE-DEV] (V)HT mode selection for meshpoint (was "ath10k + ap + encryption")

2018-04-09 Thread Sven Eckelmann
On Mittwoch, 6. Dezember 2017 22:26:09 CEST Sven Eckelmann wrote: > On Mittwoch, 6. Dezember 2017 18:52:01 CET Daniel Hernandez wrote: > > So been running this mesh patch on 4 routers in my home for over a > > month and it works great ! > > Reporting my feedback to see if it can be

Re: [LEDE-DEV] [PATCH 0/4] Gemini forward-port to kernel v4.14

2018-04-09 Thread Roman Yeryomin
On 2018-04-04 23:34, Linus Walleij wrote: This patch set forward-ports Gemini to v4.14 with as good support as I can get. I don't know if all or any patches actually make it through to the devel list. They are also posted here: https://dflund.se/~triad/krad/gemini/openwrt/ It would be nice if

Re: [LEDE-DEV] [OpenWrt-Devel] kernel version status

2018-04-09 Thread Roman Yeryomin
On 2018-04-01 17:48, Hauke Mehrtens wrote: The next OpenWrt release will use kernel 4.9 and kernel 4.14 depending on the target. All targets that are *not* on either kernel 4.9 or 4.14 will not be included in the next release. The following targets are on kernel 4.4 and will probably not be incl

Re: [LEDE-DEV] [PATCH 2/3] x86: add intel microcode entries to grub config

2018-04-09 Thread Philip Prindeville
Inline. Has this been tested with UEFI? > On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote: > > Create initrd enries for x86 images, that'll load intel microcode as > early as possible. Also restrict the late load of microcode to AMD > processors. > > Signed-off-by: Tomasz Maciej Nowak

Re: [LEDE-DEV] [PATCH 3/3] intel-microcode: create early load microcode image

2018-04-09 Thread Philip Prindeville
Inline > On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote: > > Create initrd image with packed microcode. This'll allow to load it at > early boot stage. Unfortunately the package can't install files directly > to /boot directory, therefore additional installation hooks are placed > for sta

Re: [LEDE-DEV] [PATCHv2] firewall: fix logging of dropped & rejected packets

2018-04-09 Thread Philip Prindeville
“guest” or “salon”? > On Apr 3, 2018, at 8:51 AM, Alin Nastac wrote: > > From: Alin Nastac > > Reproduction scenario: > - use 3 interfaces with 3 different zones - lan, wan and guest > - configure firewall to allow forwarding from lan to wan > - add DROP rule to prevent forwarding from lan t

Re: [LEDE-DEV] [OpenWrt-Devel] 18.03/4

2018-04-09 Thread Philip Prindeville
> On Feb 16, 2018, at 1:32 PM, Philip Prindeville > wrote: > > > >> On Feb 16, 2018, at 5:46 AM, John Crispin wrote: >> >> Hi, >> >> whats on the critical todo list for the upcoming release ? i still have a >> few minor things that I'll be adding shortly, apart from that I am currently

Re: [LEDE-DEV] [PATCH 2/3] x86: add intel microcode entries to grub config

2018-04-09 Thread Tomasz Maciej Nowak
W dniu 09.04.2018 o 21:00, Philip Prindeville pisze: Inline. Has this been tested with UEFI? No, I don't have any UEFI system which can be employed for testing. On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote: Create initrd enries for x86 images, that'll load intel microcode as ea

Re: [LEDE-DEV] [PATCH 3/3] intel-microcode: create early load microcode image

2018-04-09 Thread Tomasz Maciej Nowak
W dniu 09.04.2018 o 21:05, Philip Prindeville pisze: Inline On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote: Create initrd image with packed microcode. This'll allow to load it at early boot stage. Unfortunately the package can't install files directly to /boot directory, therefore addi

Re: [LEDE-DEV] [PATCH 3/3] intel-microcode: create early load microcode image

2018-04-09 Thread Philip Prindeville
Inline > On Apr 9, 2018, at 2:11 PM, Tomasz Maciej Nowak wrote: > > W dniu 09.04.2018 o 21:05, Philip Prindeville pisze: >> Inline >>> On Apr 3, 2018, at 7:13 AM, Tomasz Maciej Nowak wrote: >>> >>> Create initrd image with packed microcode. This'll allow to load it at >>> early boot stage. Unf

[LEDE-DEV] [PATCH netifd] interface: fix "ifup-failed" hotplug event handling

2018-04-09 Thread Martin Schiller
The ifup-failed event should only be triggered when the former interface state is IFS_SETUP. Otherwise, there will also be an ifup-failed event in the IFS_TEARDOWN stateif you do an manual ifdown . Signed-off-by: Martin Schiller --- interface.c | 10 -- 1 file changed, 8 insertions(+),