From: Ye Holmes
wrap around chown with `assert, this avoids unused result
warnings being treated as errors by prebuilt GCC (with
glibc-2.31, version 10.2):
procd-2020-12-12-7f12c89d/state.c: In function 'state_enter':
procd-2020-12-12-7f12c89d/state.c:147:4: error: ignoring
return value of
Port and adapt Nick Piggin's original patch [1]. This enables dead code and
data elimination at linking time (gc-sections) on x86(-64).
openwrt-x86-64-generic-kernel.bin size, with my config:
Before: 3138048 bytes
After: 2937344 bytes
In other words, we save about 100 kB.
[1]
For glibc, lua needs an explicit link to libdl as glibc has it separate
Fixes the following error in at least collectd:
ld: usr/lib/liblua.so: undefined reference to `dlopen'
ld: usr/lib/liblua.so: undefined reference to `dlclose'
ld: usr/lib/liblua.so: undefined reference to `dlerror'
ld:
From: Nick Hainke
"valid_lft" and "preferred_lft" are different. If the "preferred_lft"
is expired the prefix should be avoided in source prefix selection.
However, the interface is allowed to still receive downstream traffic.
preferred_lfetime:
Limit for preferred lifetime of a prefix
If
On 1/2/21 9:31 PM, Hans Dedecker wrote:
Do we really need an extra config option to indicate a configured
preferred lifetime needs to be used ?
Thanks for your quick review!
I made the requested changes here (untested):
On Fri, Jan 1, 2021 at 9:15 PM wrote:
>
> From: Nick Hainke
>
> "valid_lft" and "preferred_lft" are different. If the "preferred_lft"
> is expired the prefix should be avoided in source prefix selection.
> However, the interface is allowed to still receive downstream traffic.
>
>
Hi David,
a few minor comments below.
> + {
> + status = "okay";
> +
> + flash@0 {
> + compatible = "mx25l25635f", "jedec,spi-nor";
> + reg = <0>;
> + spi-max-frequency = <5000>;
> +
> + partitions {
> + compatible =
Hardware
MediaTek MT7621AT
256M DDR3
32M SPI-NOR
MediaTek MT7603 2T2R 802.11n 2.4GHz
MediaTek MT7915 2T2R 802.11ax 5GHz
Not Working
---
- Bluetooth (connected to UART3)
UART
UART is located in the lower left corner of the board. Pinout is
0 - 3V3 (don't connect)
1 - RX
2
I figure that getting the starlink terminal working at all
was a greater challenge than tackling the bufferbloat issue. I've long
worried of
course, that the mac layer on this thing was going to be very weird,
and since they were working with qca they'd end up burying everything
in the network
On Sat, Jan 02, 2021 at 10:01:36PM +0800, yehol...@outlook.com wrote:
> From: Ye Holmes
>
> Output warning in case changing the ownership of ubus' home
> directory has failed. Besides, this avoids treating unused
> result warning as error by GCC (with glibc-2.31, version 10.2):
>
>
On Saturday, 2 January 2021 15:22:38 CET David Bauer wrote:
> sorry for the late reply.
>
> Firs to fall, there is no real policy on that one, as OpenWrt itself does not
> advertise support for cross-target upgrades. It might work, or it might not.
Thanks for the reply. But the option 3 was
Hi Sven,
sorry for the late reply.
Firs to fall, there is no real policy on that one, as OpenWrt itself does not
advertise support for cross-target upgrades. It might work, or it might not.
On 11/25/20 8:53 AM, Sven Eckelmann wrote:
> On Tuesday, 24 November 2020 08:58:04 CET Sven Eckelmann
From: Ye Holmes
Output warning in case changing the ownership of ubus' home
directory has failed. Besides, this avoids treating unused
result warning as error by GCC (with glibc-2.31, version 10.2):
procd-2020-12-12-7f12c89d/state.c: In function 'state_enter':
Paul Spooren kirjoitti 2.1.2021 klo 2.22:
The newly added `findrev` function does automatic versioning based on
Git commits of the package. Replace tedious to bump and merge conflict
causing `PKG_RELEASE` and replace it with `findrev`.
Sounds reasonable for me.
The PKG_RELEASE in base-files
14 matches
Mail list logo
