Hi,
KERNEL_AIO, KERNEL_FHANDLE and KERNEL_FANOTIFY makes sense _if_ you're
using some kind of storage device however KERNEL_CGROUPS, config
KERNEL_NAMESPACES, config KERNEL_LXC_MISC, KERNEL_SECCOMP_FILTER are
very limited use cases to my knowledge and more or less only used on
x86*?
Keep
Hey Christoph,
find my comments inline.
Mathias
30/12/2018 10:53, Christoph Krapp:
This patch adds supports for GL-AR750S.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
Hi Christoph,
On 30.12.2018 10:54, Christoph Krapp via openwrt-devel wrote:
This patch adds supports for GL-AR750S.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
This device comes with SPI NOR + NAND combination.
You should at least mention that in your patch and let
While at it rename node name to the generic `leds`.
Signed-off-by: Petr Štetiar
---
target/linux/lantiq/files-4.14/arch/mips/boot/dts/P2812HNUF1.dts | 3 ++-
target/linux/lantiq/files-4.14/arch/mips/boot/dts/TDW8980.dts| 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git
Hi,
> I recently set up an OpenWrt 18.06.1 router at a place where the ISP
> does not provide native IPv6, but does provide their own 6to4
> tunnelling server. I installed 6to4 and ip-full on the router and
> configured WAN6, but was puzzled as to why IPv6 wasn't working until I
> discovered that
Daniel Golle [2018-12-29 06:51:32]:
> config KERNEL_AIO
> config KERNEL_FHANDLE
> config KERNEL_FANOTIFY
> + default y if !SMALL_FLASH
What about `FEATURES += nas` to make it clear and don't abuse SMALL_FLASH.
> config KERNEL_CGROUPS
> config KERNEL_CPUSETS
> config
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
This patch adds supports for
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Changes since v1 (thx Mathias
Hi Christian,
On 11.12.2018 02:10, Christian Lamparter wrote:
On Monday, December 10, 2018 10:28:22 PM CET John Crispin wrote:
On 10/12/2018 16:47, Piotr Dymacz wrote:
> Hi Christian,
>
> On 09.12.2018 16:34, Christian Lamparter wrote:
>> It allows specifying default and Netgear parsers
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" header.
>
> To mitigate this problem, the original message has been wrapped
> automatically by the mailing
30/12/2018 12:35, Tom Psyborg:
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
On 2018-12-30 12:40, Jo-Philipp Wich wrote:
Hi,
I recently set up an OpenWrt 18.06.1 router at a place where the ISP
does not provide native IPv6, but does provide their own 6to4
tunnelling server. I installed 6to4 and ip-full on the router and
configured WAN6, but was puzzled as to why IPv6
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
This patch adds supports for
Hey,
I stumbled of some more stuff. Comments inline.
Am So., 30. Dez. 2018 um 13:27 Uhr schrieb Christoph Krapp via
openwrt-devel :
>
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" header.
>
> To mitigate this
30/12/2018 15:15, Tom Psyborg:
On 30/12/2018, Piotr Dymacz wrote:
Hi Tom,
On 30.12.2018 15:03, Tom Psyborg wrote:
[...]
If it's possible to update from the stock firmware via a webinterface,
it's fine. If not, the way via u-boot works as well.
Mathias
Aren't you embarrassed being such
On 30/12/2018, Mathias Kresin wrote:
> 30/12/2018 12:35, Tom Psyborg:
>> On 30/12/2018, Christoph Krapp via openwrt-devel
>> wrote:
>>> The sender domain has a DMARC Reject/Quarantine policy which disallows
>>> sending mailing list messages using the original "From" header.
>>>
>>> To mitigate
On 30/12/2018, Piotr Dymacz wrote:
> Hi Tom,
>
> On 30.12.2018 15:03, Tom Psyborg wrote:
>
> [...]
>
> If it's possible to update from the stock firmware via a webinterface,
> it's fine. If not, the way via u-boot works as well.
>
> Mathias
>
Aren't you embarrassed
Hi Tom,
On 30.12.2018 15:03, Tom Psyborg wrote:
[...]
If it's possible to update from the stock firmware via a webinterface,
it's fine. If not, the way via u-boot works as well.
Mathias
Aren't you embarrassed being such a hypocrite liar?
Prove your point or troll somewhere else.
30/12/2018 14:51, Tom Psyborg:
On 30/12/2018, Mathias Kresin wrote:
30/12/2018 12:35, Tom Psyborg:
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
On 30/12/2018, Mathias Kresin wrote:
> 30/12/2018 14:51, Tom Psyborg:
>> On 30/12/2018, Mathias Kresin wrote:
>>> 30/12/2018 12:35, Tom Psyborg:
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
> The sender domain has a DMARC Reject/Quarantine policy which disallows
>
Hi Tom,
On 30.12.2018 15:15, Tom Psyborg wrote:
On 30/12/2018, Piotr Dymacz wrote:
Hi Tom,
On 30.12.2018 15:03, Tom Psyborg wrote:
[...]
If it's possible to update from the stock firmware via a webinterface,
it's fine. If not, the way via u-boot works as well.
Mathias
Aren't you
>There is nothing about upgrading U-Boot on the device from this e-mail topic.
but there is about upgrading firmware via u-boot and according to the
above linked kresin comment that procedure is unreliable
On 30/12/2018, Mathias Kresin wrote:
> 30/12/2018 15:15, Tom Psyborg:
>> On 30/12/2018,
- use the blue LED for power, since the red LED is already used by
CFE in emergency mode.
- use the correct code for the wlan button
Signed-off-by: Daniel Gonzalez Cabanelas
---
Changes in v2:
- the v1 patch was truncated, fixed
target/linux/brcm63xx/base-files/etc/diag.sh | 2 +-
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
This patch adds supports for
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Changes since v2:
- removed
On Sun, Dec 30, 2018 at 4:40 AM Jo-Philipp Wich wrote:
>
> Hi,
>
> > I recently set up an OpenWrt 18.06.1 router at a place where the ISP
> > does not provide native IPv6, but does provide their own 6to4
> > tunnelling server. I installed 6to4 and ip-full on the router and
> > configured WAN6,
On Sun, Dec 30, 2018 at 1:38 PM Torbjorn Jansson
wrote:
>
> On 2018-12-30 12:40, Jo-Philipp Wich wrote:
> > Hi,
> >
> >> I recently set up an OpenWrt 18.06.1 router at a place where the ISP
> >> does not provide native IPv6, but does provide their own 6to4
> >> tunnelling server. I installed 6to4
With this commit the TP-Link Archer C58 and Archer C59 use caldata
patching in order to set the correct 5GHz MAC-address.
Tested on TP-Link Archer C59 v1.
For more details see commit 330965b.
Signed-off-by: David Bauer
---
.../ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata | 1 +
This allows some packages like crtmpserver to compile with uClibc++.
Only patches that fix bugs were added. Upstream added a bunch of build
changes that I kept out to keep things simple.
Upstreamed patches start at 100.
Patches sent to upstream start at 200.
Signed-off-by: Rosen Penev
---
Is there any reason this would should fail or brick a 859L A3?
On the D-Link site they don't separate A1 or A3 so I should be fine?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
30 matches
Mail list logo
