[OpenWrt-Devel] [PATCH] uml: fix mac80211 hwim for uml

A duplicate include guard prevents inclusion of barrier.h in UML build and this prevents mac80211 from building. This patch re-enables mac80211 hwsim and renames the include guard. See https://lists.openwrt.org/pipermail/openwrt-devel/2015-June/033614.html for details. Signed-off-by: Martin

[OpenWrt-Devel] Possible Fix for broken hwsim on UML target

Hi, there is also a ticket about the problem here[1]. The problem is a missing include for barrier.h that is caused by a duplicate header guard - I guess it might be this commit that introduced the problem: [2] The problem seems to be that both barrier.h header files are included when

Re: [OpenWrt-Devel] alternatives to TDMA

2015-07-14 17:50 GMT+02:00 Bill Moffitt bmoff...@ayrstone.com: My understanding is that UBNT has an ASIC in their devices to help with the timing of the TDMA mode. My suspicion is that, without that ASIC, software only TDMA would probably not be precise enough to bring benefit. Does anyone

Re: [OpenWrt-Devel] Alternatives do TDMA

2015-07-14 18:45 GMT+02:00 Martin Tippmann martin.tippm...@gmail.com: 2015-07-14 11:34 GMT+02:00 John Crispin blo...@openwrt.org: On 14/07/2015 11:18, valent.turko...@gmail.com wrote: I have your found out that NETSHe offers some of their firmwares for free download and testing with TDMA

Re: [OpenWrt-Devel] Alternatives do TDMA

2015-07-14 11:34 GMT+02:00 John Crispin blo...@openwrt.org: On 14/07/2015 11:18, valent.turko...@gmail.com wrote: I have your found out that NETSHe offers some of their firmwares for free download and testing with TDMA enbled driver: http://netshe.ru/files/NETSHe-3.0/ looks like it is

Re: [OpenWrt-Devel] UML not working in master

2015-09-26 20:48 GMT+02:00 Javier Domingo Cansino : > Hi Bastian, > > I have patched, compiled correctly, and working alright! =) > > You should really send that patch upstream! Hi, it's already fixed in the Kernel since June:

Re: [OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

>> Not entirely. It (r48456) segfaults on receiving a 301 redirect for >> http->https: >> >> # /bin/uclient-fetch -O- 'http://de-korte.org/robots.txt' >> Downloading 'http://de-korte.org/robots.txt' >> Connecting to 2001:470:7ad2::10:80 >> Segmentation fault > That's an error handling bug - the

Re: [OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-23 14:36 GMT+01:00 Bastian Bittorf <bitt...@bluebottle.com>: > * Martin Tippmann <martin.tippm...@gmail.com> [23.01.2016 14:23]: >> The daemon should work fine, at least curl and wget on Ubuntu handle it fine. > > i cannot reproduce this here: Sorry if I was

[OpenWrt-Devel] Bug Report: zram corrupts memory / misbehaves on ar71xx

Hi, are here any other users of zram? We see some serious issues: - application segfaults on memory pressure, without zram the OOM killer is invoked but with zram random SIGSEVs starting to happen. This happens also with light memory pressure e.g. when using luci. Unfortunately I'm at loss how

Re: [OpenWrt-Devel] Using kdump... persistent logs, etc. (Syrone Wong)

On Thu, Feb 23, 2017 at 12:13 PM, Bernie McIntosh wrote: >> Hi, >> >> Has anyone managed to use kdump with OpenWRT/LEDE? >> >> I have a box which periodically panics, and since /var is a link to /tmp/ >> there are no persistent logs. Which reminds me: is it

Re: [OpenWrt-Devel] [LEDE-DEV] Any interest in adding runit to OpenWRT?

On Tue, Dec 27, 2016 at 9:43 AM, John Crispin wrote: > Hi, > > currently procd service restart/reload can be triggered by config > changes and network interface changes. from what i understand you are > missing the following features > > * an option to simply run a script to

Re: [OpenWrt-Devel] Any interest in adding runit to OpenWRT?

On Mon, Dec 26, 2016 at 5:32 PM, Rob Landley <r...@landley.net> wrote: > On 12/26/2016 08:05 AM, Martin Tippmann wrote: >> On Sun, Dec 25, 2016 at 9:01 PM, Denys Vlasenko >> So TL;DR: procd is fine for init but having runit/runsvdir easily >> usable woul

Re: [OpenWrt-Devel] Any interest in adding runit to OpenWRT?

On Sun, Dec 25, 2016 at 9:01 PM, Denys Vlasenko wrote: > I decided to try to do what I can, and put together a draft > of the proposal how daemontools-like supervision > should be used by a distro in a way which makes > developers/packagers life easier - they will not

Re: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas

On Mon, May 29, 2017 at 12:11 PM, Jamie Stuart wrote: > Hi, > First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is > moving forward. > For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and > not tied to the name of an old

Re: [OpenWrt-Devel] LEDE 17.01.5 release planning

On Thu, May 24, 2018 at 9:06 PM, Hauke Mehrtens wrote: > Please do not hesitate to re report some request that something should > be backported from master or some regression compared to lede-17.01, if > it looks like they got ignored and didn't got a response. Hi, would be

Re: [OpenWrt-Devel] [PATCH] config: extend small_flash feature

On Wed, May 30, 2018 at 3:21 PM, Alex Maclean wrote: > change the squashfs block size to 1024KiB. This might cause a problem with memory. You might also want to change CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE from 3 to 1 in the kernel config.

Re: [OpenWrt-Devel] [PATCH] config: extend small_flash feature

On Fri, Jun 1, 2018 at 8:05 PM, Alex Maclean wrote: > On 01/06/18 12:34, Lucian Cristian wrote: > >> On 30.05.2018 20:22, Martin Tippmann wrote: >>> find /usr | >>> xargs md5sum >> >> I made the test on tl-wr841n-v9 with luci selected >> >>

Re: [OpenWrt-Devel] openwrt-imagebuilder-18.06.0-rc1-ar71xx-generic.Linux-x86_64

On Mon, Jun 25, 2018 at 3:56 PM, Mikael Bak wrote: > Build dependency: Please install GNU 'time' or BusyBox 'time' > > Prerequisite check failed. Use FORCE=1 to override. > make[1]: *** [Makefile:76: staging_dir/host/.prereq-build] Error 1 > make: *** [Makefile:175: image] Error 2 >

[OpenWrt-Devel] netifd: DEVICE= always empty for ACTION=ifdown for scripts in /etc/hotplug.d/iface

Hi, I'm calling some iptables rules from a scripts in /etc/hotplug.d/iface and these failed because there seems to be no $DEVICE variable for ACTION=ifdown events. It's not really obvious that the device is not populated for ifdown events, is there a reason for this? I guess the data about the

Re: [OpenWrt-Devel] netifd: DEVICE= always empty for ACTION=ifdown for scripts in /etc/hotplug.d/iface

On Fri, Feb 22, 2019 at 9:17 AM Martin Tippmann wrote: > > Hi, > > I'm calling some iptables rules from a scripts in /etc/hotplug.d/iface > and these failed because there seems to be no $DEVICE variable for > ACTION=ifdown events. > > It's not really obvious that the

[OpenWrt-Devel] Hang on setting $PROMPT in master

We are using a shell-function to set the prompt based on return code - it works fine in 17.01 / 18.06 / 19.07, however in current master when the function is run the terminal/ssh session hangs. how to reproduce: <--- hang.sh: #!/bin/sh prompt_set() { face() { local rc=$? case "$rc"