Re: [OpenWrt-Devel] Current "OpenWrt Style Guide for DTS"?

Hi! I picked several things I could answer below :) On Wed, Jan 23, 2019 at 6:07 AM Jeff Kletsky wrote: ... > > Choice of Node Naming for Partitions > > > In some DTS files, the partitions are named using sequential integers. > In others, the offset of the

Re: [OpenWrt-Devel] MIPS stack security and other problems

On Tue, Jan 22, 2019 at 2:34 PM Hauke Mehrtens wrote: > > On 1/19/19 2:56 PM, Dave Taht wrote: > > Hauke Mehrtens writes: > > > >> On 12/18/18 12:46 PM, Hauke Mehrtens wrote: > >>> On 12/17/18 1:54 AM, Dave Taht wrote: > > A pretty deep look at home MIPS and arm routers, and a

Re: [OpenWrt-Devel] MIPS stack security and other problems

On 1/19/19 2:56 PM, Dave Taht wrote: > Hauke Mehrtens writes: > >> On 12/18/18 12:46 PM, Hauke Mehrtens wrote: >>> On 12/17/18 1:54 AM, Dave Taht wrote: A pretty deep look at home MIPS and arm routers, and a surprising bug in Linux/MIPS - by mudge and co:

Re: [OpenWrt-Devel] Current "OpenWrt Style Guide for DTS"?

On 1/21/19 9:26 PM, Rafał Miłecki wrote: > On Mon, 21 Jan 2019 at 20:06, Jeff Kletsky wrote: >> but I still have a few unanswered questions >> [around DTS "best practices" for OpenWrt]. > > Ask? > Style Questions === Choice of Node Naming for Partitions

Re: [OpenWrt-Devel] [PATCH 0/4] Update Gemini to kernel v4.19

On 1/22/19 7:26 AM, Petr Štetiar wrote: > Linus Walleij [2019-01-21 23:17:50]: > > Hi, > >> I pushed it to the branch "gemini-v4.19" (with some more patches, >> but shouldn't make a difference) here: >> https://github.com/linusw/openwrt > > thanks, so I've just tried following build config: >

[OpenWrt-Devel] [PATCH] lantiq: make AVM FRITZ!Box naming consistent

This commit changes the model string and device title of all AVM boards to fit the naming of the manufacturer. Drop all provider-specific titles as they are re-used for every device generation by 1&1. The original AVM model name is printed on the bottom of every devices. Exception applies for

Re: [OpenWrt-Devel] [PATCH] treewide: dts: Unify naming of gpio-keys nodes

Christian Lamparter [2019-01-22 17:54:13]: Hi, > The at91, apm821xx, ipq40xx, ipq806x, layerscape and oxnas are probably > ready to be merged. a lot of additional work, thanks! > The situation with ramips, ath79 and lantiq is a bit more complicated: >

Re: [OpenWrt-Devel] [PATCH] treewide: dts: Unify naming of gpio-keys nodes

On Thursday, January 3, 2019 10:39:08 PM CET Petr Štetiar wrote: > Christian Lamparter [2019-01-03 18:27:40]: > > > I would try to split up the patch into multiple patches so that > > each maintainer has the chance to act on just his own turf. > > I don't want to waste more of my time on such

Re: [OpenWrt-Devel] INSTALL_SUID macro

On 1/22/19 3:26 AM, Daniel Golle wrote: Hi Jo, Hi everyone, I was happy to see the addition of the INSTALL_SUID macro and now wonder if it'd make sense to use fakeroot in order to allow installing files for different users as well. For now, all files in rootfs are always owned by root:root,

Re: [OpenWrt-Devel] [PATCH] ath79: ag71xx: Fix tx queue timeouts during ifup

Hi! On Thu, Jan 3, 2019 at 10:25 AM Petr Štetiar wrote: > > On ath79 and UBNT Bullet M XW (ar9342) I was experiencing weird issues during > network setup[1] which I was able to reproduce easily with following commands: > > uci set network.lan.ipaddr='192.168.1.20' > uci commit network > ifup

[OpenWrt-Devel] [RFT] toolchain/musl: update to version 1.1.21

"This release makes improvements with respect to default thread stack size, including increasing the default from 80k to 128k, increasing the default guard size from 4k to 8k, and allowing the default to be increased via ELF headers so that

Re: [OpenWrt-Devel] [PATCH 1/2] mpc85xx: use generic diag.sh

On Thursday, January 17, 2019 12:43:12 AM CET David Bauer wrote: > This commit removes the target-specific diag.sh script. This way, the > generic one is used for the target, which uses DT-aliases to specify the > LEDs used. > > This way, we are also able to use different LEDs to indicate

Re: [OpenWrt-Devel] lantiq: Netgear DM200 kernel too large

Thomas Nixon writes: > On 1/21/19, Bjørn Mork wrote: > >> I wonder about those better options... What are they? > > In the UK at least BT OpenReach modems are available very cheaply second hand > and are in theory a bit better, for a few reasons. I only found this when googling:

Re: [OpenWrt-Devel] lantiq: Netgear DM200 kernel too large

I thought this was implied around here, but just to make it absolutely clear: OpenWrt support is required. Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] lantiq: Netgear DM200 kernel too large

On 22/01/19 01:11, Thomas Nixon wrote: On 1/21/19, Bjørn Mork wrote: Paul Oranje writes: Op 20 jan. 2019, om 17:52 heeft Thomas Nixon het volgende geschreven: I could add a new subtarget like xrx200 but with small_flash enabled, but this seems a bit excessive for a single board. The DM200

Re: [OpenWrt-Devel] [PATCH 0/4] Update Gemini to kernel v4.19

On Tue, Jan 22, 2019 at 12:15 PM Petr Štetiar wrote: > Ends with following: > > make[5]: Entering directory > '/openwrt/build_dir/target-arm_fa526_musl_eabi/linux-gemini/linux-4.19.16' > Makefile:600: include/config/auto.conf: No such file or directory >YACCscripts/kconfig/zconf.tab.c

Re: [OpenWrt-Devel] Invalid revision range

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 --- If Git fails with a "fatal"

Re: [OpenWrt-Devel] Invalid revision range

Hi! On Tue, Jan 22, 2019 at 3:16 AM R. Diez via openwrt-devel wrote: ... > If Git fails with a "fatal" error inside getver.sh, how come the build does > not stop at that point? Failed to calculate current revision isn't a "fatal error". As you can see in getver.sh it falls back to reporting an

Re: [OpenWrt-Devel] INSTALL_SUID macro

Hi Daniel, I am fine with adding a fakeroot solution. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] INSTALL_SUID macro

Hi Jo, Hi everyone, I was happy to see the addition of the INSTALL_SUID macro and now wonder if it'd make sense to use fakeroot in order to allow installing files for different users as well. For now, all files in rootfs are always owned by root:root, and sometimes this is not what we want. I'm

Re: [OpenWrt-Devel] [PATCH 0/4] Update Gemini to kernel v4.19

Linus Walleij [2019-01-21 23:17:50]: Hi, > I pushed it to the branch "gemini-v4.19" (with some more patches, > but shouldn't make a difference) here: > https://github.com/linusw/openwrt thanks, so I've just tried following build config: CONFIG_TARGET_gemini=y CONFIG_TARGET_MULTI_PROFILE=y