Or that is $0.023647, anyway. :-)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 4/9/19 7:53 AM, Vincent Wiemann wrote:
Hi Bjørn,
routers are critical infrastructure. We should try to achieve the best we can.
One of the reasons for the Lede split was that problems were procrastinated
and accumulated over the release timeline.
That's the reason why we should release less o
Bjørn Mork writes:
> Ingo Feinerer writes:
>
>> anyone willing to review/commit this diff?
>>
>> http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015445.html
>> http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015444.html
>
>
> I assume John is very busy based on cur
On 09/04/19 20:44, Jeff Kletsky wrote:
In going through code used by a port of an IPQ4019 device, I see that
target/linux/ipq40xx/base-files/lib/upgrade/linksys.sh
in platform_do_upgrade_linksys()
writes the image using
get_image "$1" | mtd write - $part_label
This surprises me as I had t
In going through code used by a port of an IPQ4019 device, I see that
target/linux/ipq40xx/base-files/lib/upgrade/linksys.sh
in platform_do_upgrade_linksys()
writes the image using
get_image "$1" | mtd write - $part_label
This surprises me as I had thought that NAND-based flash should use
The extroot mount preparation code for r/w rootfs overlay discovery, and
determining the user-defined /etc/config/fstab location within, would only
discover overlays residing on JFFS2 or UBIFS MTD storage.
This led to attempts at loading the uci fstab configuration without the
required /tmp/overla
Signed-off plain-text patch:
>From 6df03fc450d7f1e2b49791b0d384a7b1ae0d9c69 Mon Sep 17 00:00:00 2001
From: Kenneth Miller
Date: Tue, 9 Apr 2019 19:14:37 +0200
Subject: [PATCH] block: make extroot mount preparation more robust
The extroot mount preparation code for r/w rootfs overlay discovery, a
I had trouble using an ext4 extroot overlay on my Zyxel NBG6817 running
18.06.2, so I took a closer look at the way libfstools and its block
tool setup the extroot overlay during PREINIT and found some things
broke extroot mounting on certain devices.
The issue and logs are documented in the follo
In general, within an OpenWrt DTS that `#include "some_linux_supplied.dtsi"`
is it preferred to refer to a node defined in upstream code by label, or
by path?
For example, with `blsp1_spi2: spi@78b6000` in the upstream-controlled
DTS, prefer
&blsp1_spi2
or (taking into account scope or
Hi Bjørn,
routers are critical infrastructure. We should try to achieve the best we can.
One of the reasons for the Lede split was that problems were procrastinated
and accumulated over the release timeline.
That's the reason why we should release less often, but with a higher quality.
If problem
From: Rafał Miłecki
Dropping this option significantly improves NAT performance on BCM5301X
(bcm53xx) for LAN to WAN traffic with GRO disabled (+14%). It slightly
affects kernel size - it gets bigger by 1,5% - 3% depending on a target.
Unfortunately this change may decrease NAT performance for s
Jo-Philipp Wich writes:
>> Is there any kind of "official" roadmap/checklist available what "needs"
>> to be done?
>
> not that I am aware of, but from the top of my head:
>
> - make sure all targets are ported properly to 4.14
> - disable all devices which cannot cannot handle the increased kern
12 matches
Mail list logo
