[PATCH 0/2] determineable package name with ABIVersions

Hi, this set contains two patches which solve the same issues in two different ways, only one should be merged. ABIVersions of packages are simply attached to the package name, so package `foobar` with ABIVersion 32 becomes `foobar32`, literally the name to install via opkg. This information is s

[PATCH 2/2] include: store ABIVersion in Packages index

With the existence of ABI versions there is no clean way to determine the package name without an attached ABI version. The Packages index is stored on device to know what packages are installed. The ABIVersion was recently removed in c921650382 "build: drop ABI version from metadata", while ABI v

[PATCH 1/2] package: store SourceName in Packages index

With the existence of ABI versions there is no clean way to determine the package name without an attached ABI version. The Packages index is stored on device to know what packages are installed. As SourceName is filtered out the real package names are unknown to a running device. This becomes a p

[PATCH] ramips: move spi-nor-add-gd25q512 patch to generic

A SPI NOR flash should not be target-specific, so move it to generic in case another platform needs to use it. Signed-off-by: Ilya Lipnitskiy --- .../pending-5.10/483-mtd-spi-nor-add-gd25q512.patch} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename target/linux/{ramips/pa

Re: [PATCH procd] inittab: detect active console from kernel if no console= specified

Hi Mathew, On Fri, Mar 05, 2021 at 12:54:15AM +, Mathew McBride wrote: > The default serial console can be set in the device tree > using the linux,stdout-path parameter (or equivalent from ACPI). > > This is important for universal booting (EFI/EBBR) on ARM platforms > where the default con

[PATCH] ramips: mt7621: remove redundant lpj re-calibration

When the patch was originally introduced [0], it claimed that on mt7621, CPU core 1 came up with a bad BogoMIPS value because the clock needed time to stabilize. That is not the case today, at least on my Ubiquity EdgeRouter X device. As evident from messages below, the LPJ value is already correct

[sdwalker/sdwalker.github.io] e78484: This week's update

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 --- Branch: refs/heads/master Home

Re: [PATCH v1 1/2] libubox: fix test_base64.t for bash

On 07/03/2021 07:27, Petr Štetiar wrote: You've two options to test your changes from the CI perspective. [...] Can we have these very nice instructions added to a CONTRIBUTING.md file (or something to that effect) for libubox? -- Henrique de Moraes Holschuh Analista de Projetos Centro de E

Re: [PATCH v1 2/2] libubox: tests: add more blobmsg/json test cases

Peter Seiderer [2021-03-06 11:54:50]: Hi, nice, just a small nitpicks, these seems fine: > + int8_max: 127 > + int8_min: -128 ... but the outputs bellow looks suspicious: > + [*] blobmsg from json: ... > + int8_max: 1 > + int8_min: 1 ... > + [*] blobmsg from json/cast_u64: ... >

Re: [PATCH v1 1/2] libubox: fix test_base64.t for bash

Peter Seiderer [2021-03-06 11:54:49]: Hi, thanks a lot for your nice contribution! > My shell/bash seems to emit a more detailed failure message than > expected. Fix this by complete avoiding the failure message using > command substitution instead of direct command execution. This needs more