Re: [PATCH v3] fakeroot: fix to work with glibc 2.33

2021-02-14 Thread Philip Prindeville
Surprised (after what you said) that it was accepted that quickly. Had the impression that things were slow. Go ahead for now, unless you think the upstream release is imminent. > On Feb 14, 2021, at 3:26 PM, Ilya Lipnitskiy > wrote: > > Oh well, it is too late now - it's been merged

Re: Commit e95b1b23f1b6951318d6c6caf3803fb933f71a6c kernel: bump 5.4 to 5.4.97 kills mt7621/dir860l

2021-02-14 Thread Russell Senior
I rev'd up to 15785-g0fde111702 today (without my revert) and the freeze is gone, the dir860l-b1 boots normally again. I don't know why, but not knowing is made more tolerable by it working. -- Russell Senior russ...@personaltelco.net On Sun, Feb 14, 2021 at 4:51 AM Russell Senior wrote: > >

[PATCH] patchelf: bump to use latest master

2021-02-14 Thread Ilya Lipnitskiy
Recent ABI_VERSION commits make use of patchelf. It was discovered that with patchelf 0.10(and even 0.12) various big endian targets fail to link against libubox SO that was processed through patchelf. Using latest master patchelf fixes those link errors. Potential commits affecting big-endian

Re: New layerscape/aarch64 board

2021-02-14 Thread Mathew McBride
On Sat, Feb 13, 2021, at 2:13 AM, Michael Walle wrote: > Hi, > > I am looking into how to bring openwrt support for my board > (Kontron sl28) upstream. The board has upstream support in > both vanilla linux (since 5.8) and vanilla u-boot. Someone > in IRC told me there will be a new release based

Re: ath10k-ct iw missing rx stats

2021-02-14 Thread Ansuel Smith
> > On 2021-02-14 18:28, Ansuel Smith wrote: > > With recent mac80211 bump I notice that rx stats > > are no longer displayed. > > I ported the atk10-ct patches to the version 5.10 > > and I noticed this. It's only me? > > Also this is only to report that ath10k-ct patches can > > be ported with

Re: Installation error for libncursesw6

2021-02-14 Thread Ansuel Smith
> Collected errors: > * pkg_hash_fetch_best_installation_candidate: Packages for > libreadline8 found, but incompatible with the architectures configured > * opkg_install_cmd: Cannot install package libreadline8. > * satisfy_dependencies_for: Cannot satisfy the following dependencies > for

Installation error for libncursesw6

2021-02-14 Thread Ansuel Smith
Collected errors: * pkg_hash_fetch_best_installation_candidate: Packages for libreadline8 found, but incompatible with the architectures configured * opkg_install_cmd: Cannot install package libreadline8. * satisfy_dependencies_for: Cannot satisfy the following dependencies for

Re: Upcoming 19.07.7 release

2021-02-14 Thread Baptiste Jonglez
On 07-02-21, Jaap Buurman wrote: > Are we sure disabling TSO is the actual fix though? There are a few > reasons I am doubting that assessment: > > 1. Here is a user that is reporting he has always been running with > TSO disabled, yet he does experience the bug: >

RE: LICENSE move to LICENSES/ by 882e3014 causes buildbot breakage

2021-02-14 Thread Adrian Schmutzler
Hi, this should hopefully be fixed by https://github.com/openwrt/openwrt/commit/4894a3ff2870438cf812d88704c92c8d997a69db If not, please ping me again. Best Adrian > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Hannu Nyman >

Re: [PATCH v3] fakeroot: fix to work with glibc 2.33

2021-02-14 Thread Ilya Lipnitskiy
Oh well, it is too late now - it's been merged upstream: https://salsa.debian.org/clint/fakeroot/-/commits/upstream/ No release yet, though. Do you want me to do another patch, getting rid of the upstreamed patches and using PKG_SOURCE_VERSION? Ilya Ilya On Sun, Feb 14, 2021 at 12:25 PM

Re: OpenWrt add dependency to swig for U-Boot builds

2021-02-14 Thread Petr Štetiar
Hauke Mehrtens [2021-01-31 19:43:42]: Hi, > The U-Boot build for more and more SoCs is using binman by default to > combine the images (SPL, U-Boot, ...). Binman is build from the U-Boot > project and it needs swig to build. We have multiple patches in OpenWrt to > remove this dependency from

[no subject]

2021-02-14 Thread Stephen Walker 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 problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Branch: refs/heads/master

Re: [PATCH v3] fakeroot: fix to work with glibc 2.33

2021-02-14 Thread Philip Prindeville
Inline > On Feb 13, 2021, at 9:41 PM, Ilya Lipnitskiy > wrote: > > The following commit removed _STAT_VER definitions from glibc: > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8ed005daf0ab03e142500324a34087ce179ae78e > > That subsequently broke fakeroot: >

LICENSE move to LICENSES/ by 882e3014 causes buildbot breakage

2021-02-14 Thread Hannu Nyman
Looks like the LICENSE file move to LICENSES/ by 882e3014 causes buildbot breakage. The SDK Makefile still expects to find LICENSE file as |$(TOPDIR)/LICENSE| https://github.com/openwrt/openwrt/blob/master/target/sdk/Makefile#L133

[PATCH] mac80211: Update to version 5.10.16-1

2021-02-14 Thread Hauke Mehrtens
The removed patches were applied upstream. Signed-off-by: Hauke Mehrtens --- The refreshed patches are looking strange, it reverts many changes from this commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=ed1e234d87fc2fc1561b02dcc2f67a464721fc6f I refreshed the patches like

Re: ath10k-ct iw missing rx stats

2021-02-14 Thread Felix Fietkau
On 2021-02-14 18:28, Ansuel Smith wrote: > With recent mac80211 bump I notice that rx stats > are no longer displayed. > I ported the atk10-ct patches to the version 5.10 > and I noticed this. It's only me? > Also this is only to report that ath10k-ct patches can > be ported with minimal changes

ath10k-ct iw missing rx stats

2021-02-14 Thread Ansuel Smith
With recent mac80211 bump I notice that rx stats are no longer displayed. I ported the atk10-ct patches to the version 5.10 and I noticed this. It's only me? Also this is only to report that ath10k-ct patches can be ported with minimal changes and works normally (except this problem with ubus not

Re: Upcoming 19.07.7 release

2021-02-14 Thread Hauke Mehrtens
On 2/5/21 1:57 PM, Adrian Schmutzler wrote: HI, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Baptiste Jonglez Sent: Freitag, 5. Februar 2021 08:57 To: openwrt-devel@lists.openwrt.org Subject: Upcoming 19.07.7 release Hi, We are

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

2021-02-14 Thread Petr Štetiar
Bjørn Mork [2021-02-14 10:33:15]: Hi, > And it's already enabled for the ipq807x and rockchip targets, so you can't > really claim that it's not available in OpenWrt either. thanks to bringing this to my attention, but I tend to believe, that this is not intentional. > I do hope you don't

Re: [PATCHv3 2/3] busybox: update to 1.33

2021-02-14 Thread Hannu Nyman
Hauke Mehrtens kirjoitti 14.2.2021 klo 16.39: On 2/4/21 5:02 PM, Hannu Nyman wrote: Hauke Mehrtens kirjoitti 4.2.2021 klo 1.55: ... The commit message should probably extended with some content Hannu suggested. That would help a lot at the next version bump. I have done most the busybox

Re: [PATCHv3 2/3] busybox: update to 1.33

2021-02-14 Thread Hauke Mehrtens
On 2/4/21 5:02 PM, Hannu Nyman wrote: Hauke Mehrtens kirjoitti 4.2.2021 klo 1.55: On 2/1/21 1:15 AM, Rosen Penev wrote: Remove stime backport. Remove static libgcc patch as upstream fixed it with BUSYBOX_DEFAULT_STATIC_LIBGCC which defauls to off. Remove date -k patch as it no longer

Re: Commit e95b1b23f1b6951318d6c6caf3803fb933f71a6c kernel: bump 5.4 to 5.4.97 kills mt7621/dir860l

2021-02-14 Thread Russell Senior
Looks like this linux-stable commit might be the guilty party: e57d70c59bb7f6835ee47eb633e44efce4ab51b9 Reverting it in openwrt seems to fix the freezes. On Sun, Feb 14, 2021 at 4:07 AM Russell Senior wrote: > > I am stepping though the kernel patches (intially 10 at a whack) > between

RE: [PATCH] mvebu: cortexa9: fix missing wpad and iwinfo in images

2021-02-14 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Petr Štetiar > Sent: Sonntag, 14. Februar 2021 08:31 > To: Adrian Schmutzler > Cc: 'Tomasz Maciej Nowak' ; openwrt- > de...@lists.openwrt.org; 'Klaus Kudielka' > Subject: Re:

Re: Commit e95b1b23f1b6951318d6c6caf3803fb933f71a6c kernel: bump 5.4 to 5.4.97 kills mt7621/dir860l

2021-02-14 Thread Russell Senior
I am stepping though the kernel patches (intially 10 at a whack) between 5.4.96 and 5.4.97 to see if I can find what broke it. On Sat, Feb 13, 2021 at 2:51 PM Stijn Segers wrote: > > Hi, > > Op zaterdag 13 februari 2021 om 18u05 schreef Adrian Schmutzler > : > >> [1.176208] mt7621-pci

Re: [PATCH] mvebu: cortexa9: fix missing wpad and iwinfo in images

2021-02-14 Thread Bjørn Mork
Petr Štetiar writes: > Adrian Schmutzler [2021-02-13 15:49:17]: > >> > Seem like I need to prepare v2 as although I now have wpad/iwinfo in the >> > image, I'm still missing ath10 and ath9k wireless modules... >> >> Is this about initramfs or why does it have to be DEFAULT_PACKAGES here? > >

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

2021-02-14 Thread Christian Lamparter
On 14/02/2021 10:33, Bjørn Mork wrote: Petr Štetiar writes: I assume it's for some legacy reasons which don't apply in 2021 to OpenWrt. Not sure I understand what you mean here. There was a a request for this feature, so it obviously applies to OpenWrt. And it's already enabled for the

[PATCH] ramips: mt7621: add TP-Link EAP235-Wall support

2021-02-14 Thread Sander Vanheule
The TP-Link EAP235-Wall is a wall-mounted, PoE-powered AC1200 access point with four gigabit ethernet ports. When connecting to the device's serial port, it is strongly advised to use an isolated UART adapter. This prevents linking different power domains created by the PoE power supply, which

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

2021-02-14 Thread Bjørn Mork
Petr Štetiar writes: > I assume it's for some legacy reasons which don't apply in 2021 to OpenWrt. Not sure I understand what you mean here. There was a a request for this feature, so it obviously applies to OpenWrt. And it's already enabled for the ipq807x and rockchip targets, so you can't

[PATCH v2] ath79/nand: fix factory image generation for Netgear and Zyxel boards

2021-02-14 Thread Paul Fertser
The factory images need to embed specific IDs to pass verification with the OEM firmware (including TFTP recovery), so they need to be per-device variables. Fixes: ab1584a797 ("ath79: netgear: trim down uImage customisations") Reported-by: Marcin Juszkiewicz Signed-off-by: Paul Fertser --- v2:

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

2021-02-14 Thread Petr Štetiar
Tomasz Maciej Nowak [2021-02-09 18:02:13]: Hi, > Why do You need it enabled by default for OpenWrt provided images at > https://openwrt.org/downloads? answer to this question should be addressed in v2 of this patch. FYI it's very unlikely, that we would enable this feature in default images.

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

2021-02-14 Thread Petr Štetiar
Bjørn Mork [2021-02-10 12:33:44]: Hi, > DEVMEM is a standard feature, defaulting to Y in the kernel config: but it does not mean, that it's something you would like to have enabled by default. > and it's enabled in other distro kernels, like Debian (stable and > unstable) and RHEL (7 and 8).