Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

@Alex Maclean and @Alberto Bursi Thank you for the recomendations! On Wed, 5 Dec 2018 at 14:39, Alberto Bursi wrote: > > > On 05/12/2018 15:08, Carlos Ferreira wrote: > > I still have a bunch of Old Foneras and some TP-Link 703N and TL-MR11U > > battery powered micro-rou

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

I still have a bunch of Old Foneras and some TP-Link 703N and TL-MR11U battery powered micro-routers. The foneras are kinda useless, but the TP-Links are somewhat usefull and I still use them with OpenWRT. What other inexpensive routers would you sugest to substitute the ones from TP-Link I just c

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

I understand that and I had no intention to restart such discussion. I'm sorry if what I wrote was misinterpreted as such. I didn't mean to. On 5 June 2017 at 02:08, David Lang wrote: > the vote on the name was held several months ago, please stop trying to > re-do the vote just because it didn

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

Julian, thank you for the correction. I truly thought that WRT was from Wireless Router. I stand corrected :) Bill, I understand that it would be a risk to change the name. I don't mind that the project continues to use the OpenWRT brand. I just was pointing out that it doesn't truly reflects what

[OpenWrt-Devel] Monitor Mode for Raspberry Pi 3

Hello to all. Can anyone tell me if the Raspberry Pi 3 wireless module is capable of entering in monitor mode? I have been reading some documentation related to the Broadcom 43430 fullmac firmware at https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 but I could not understand if monitor

Re: [OpenWrt-Devel] Project proposal: The GNUnet of autonomous Things

Hi Daniel, I would like to ask you if the Vehicular networks is something that could also be added in the future to this project of yours. I mean, there's already alot of development towards 802.11p / DSRC / WAVE. The linux kernel already supports OCB but despite the existent work towards providin

[OpenWrt-Devel] Dependency issues on custom packages and USE_MUSL visibility

Hello! I'm having some issues regarding the implementation of new package options, due to their peculiar dependencies. I'm trying to implement a configuration option, which should exist only if the package libbz2 is selected. I understand that to do this, I should have something like this: co

[OpenWrt-Devel] hostapd-wpad-mesh fails to build.

The output of "make ./package/network/services/hostapd/{clean,compile} V=s -j1" can be seen here: http://pastebin.com/KpcbNzmy hostapd-wpad-mesh is failing to build. -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - c...@av.it.pt Skype & GTal

Re: [OpenWrt-Devel] Introducing the LEDE project

I don't see the end of OpenWRT as a bad thing. If LEDE is basically a fork but without the development bottlenecks that seem to be affecting OpenwRT, then the change can be easily done by the industry segment that uses OpenWRT for their products. In fact, I see it as a good thing because it means t

Re: [OpenWrt-Devel] Introducing the LEDE project

>From times to times, a complete Refresh is needed to purge old habits. Let's face it. The name OpenWRT reflects the initial idea, an Open Wireless Router. I don't know about the main uses, but I have a router using OpenWRT which doesn't even has a wireless interface. I also have seen cases where

Re: [OpenWrt-Devel] Issues with Intel Wifi 7260 AC

Ok! Thanks for the info. I will run some tests with a new OpenWRT build for x86_64, with only the minimum required modules to see what happens. On 2 December 2015 at 16:15, Dirk Neukirchen wrote: > On 30.11.2015 19:35, Carlos Ferreira wrote: > > Direct firmware load for > >

[OpenWrt-Devel] Issues with Intel Wifi 7260 AC

Does anyone had any issues with the Intel 7260 AC Wi-Fi Mini-PCI Express card? After selecting the proper iwlwifi modules with support for the 7260 model, I'm plagued with this issue. After booting, I keep getting this output. I'm also unable to activate a regular configuration because the kernel

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

Nov 10, 2015 at 11:19:20AM +0000, Carlos Ferreira wrote: > > First of all, I fell the need to apologise for the 7MB attachment... > > Yeah, that wasn't appropriate to be sent to the ML... > > > I hope it can provide a little more info. > > Looks like you have "ha

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

These lines seem to be suspicious to me. A lot of "No such file or directory". What can you tell from them? [pid 3669] execve("/home/claymore/OpenWRT/trunk/staging_dir/host/bin/sh", ["sh", "-c", "if make V=s -f /home/claymore/OpenWRT/trunk/include/ prereq-build.mk check-working-gcc >/dev/null 2>/

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

GCC and G++ checks out but the tests implemented in prereq-build.mk (working-gcc and working-g++) seem to fail. I too believe this was triggered by a recent OS update. On 9 November 2015 at 17:14, Carlos Ferreira wrote: > For reference, I'm using Manjaro Linux (Arch Linux based). &

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

the > things have been normal again. > > Your situation pretty much matches what I would probably have seen if I > had not re-installed the prerequisities. > Just try reinstalling the ~20 prerequisities for Openwrt and see if that > helps. > > I don't think that

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

k> wrote: > > > On 09/11/15 13:43, Carlos Ferreira wrote: > > PS: Instead of "trunk repo", it's "15.05 repo". > > > > On 9 November 2015 at 13:42, Carlos Ferreira > <mailto:carlosmf...@gmail.com>> wrote: > > > > To

Re: [OpenWrt-Devel] OpenWRT broken for some reason in my system

PS: Instead of "trunk repo", it's "15.05 repo". On 9 November 2015 at 13:42, Carlos Ferreira wrote: > Today I updated my OpenWRT trunk repo and after making the usual > "./scripts/feeds install -a" this happened. > > [claymore@Claymore 15.05]$ ./sc

[OpenWrt-Devel] OpenWRT broken for some reason in my system

Today I updated my OpenWRT trunk repo and after making the usual "./scripts/feeds install -a" this happened. [claymore@Claymore 15.05]$ ./scripts/feeds install -a Checking 'working-make'... ok. Checking 'case-sensitive-fs'... ok. Checking 'gcc'... failed. Checking 'working-gcc'... failed. Checking

Re: [OpenWrt-Devel] [packages] broken package: procd is broken in 15.05 (#1879)

Sorry for that... Gmail must have added it for some reason. From my side, I cannot see it. On 22 October 2015 at 23:01, Daniel Gimpelevich < dan...@gimpelevich.san-francisco.ca.us> wrote: > On Thu, 2015-10-22 at 22:50 +0100, Carlos Ferreira wrote: > > Yes :S Sorry! > > Btw,

Re: [OpenWrt-Devel] [packages] broken package: procd is broken in 15.05 (#1879)

Yes :S Sorry! Btw, Caps lock day? Did my Gmail applied some weird format again ? :S On 22 October 2015 at 22:46, Daniel Gimpelevich < dan...@gimpelevich.san-francisco.ca.us> wrote: > On Thu, 2015-10-22 at 22:30 +0100, Carlos Ferreira wrote: > > Daniel > > Your patch did

Re: [OpenWrt-Devel] [packages] broken package: procd is broken in 15.05 (#1879)

l] Error 2 make[4]: Leaving directory '/home/ArkHDD/OpenWRT/15.05/build_dir/target-x86_64_glibc-2.21/rpcd' Makefile:116: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/home/ArkHDD/OpenWRT/15.05/build_dir/target-x86_64_glibc-2.21/rpcd&

Re: [OpenWrt-Devel] [packages] broken package: procd is broken in 15.05 (#1879)

Daniel Your patch did not work without some simple modifications. Instead of having *inline __attribute__((always_inline)) int ignore(int x) {return x;}* at procd.h, I had to add a *static inline __attribute__((always_inline)) int ignore(int x) {return x;}* at the begining of both coldplug.c and

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20473: Source lm_sensors-3.3.5.tar.bz2 for lm-sensors not available on mirror2.openwrt.org

Yes. At the time I also found mirrors. I never submitted a pull request to modify the lm-sensors makefile, because changing the URL to a mirror site did not sound very correct to me. Since the OpenWRT do not support mirror urls, I did not know what could actually be done, besides marking the packet

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20473: Source lm_sensors-3.3.5.tar.bz2 for lm-sensors not available on mirror2.openwrt.org

Forget it... I have just found it! On 21 September 2015 at 11:10, Carlos Ferreira wrote: > You did? > Can you send me those links? > I actually googled for it but most websites and links were mere redirects > to lm-sensors.org > > I'm more than willing to cache the proje

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20473: Source lm_sensors-3.3.5.tar.bz2 for lm-sensors not available on mirror2.openwrt.org

You did? Can you send me those links? I actually googled for it but most websites and links were mere redirects to lm-sensors.org I'm more than willing to cache the project at github or similar. On 21 September 2015 at 07:14, John Crispin wrote: > > On 20/09/2015 23:22, Carlos Fer

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20473: Source lm_sensors-3.3.5.tar.bz2 for lm-sensors not available on mirror2.openwrt.org

Still dead :S This is bad... This is why caching source files used by the packages Makefiles is important :S On 15 September 2015 at 13:10, OpenWrt wrote: > #20473: Source lm_sensors-3.3.5.tar.bz2 for lm-sensors not available on > mirror2.openwrt.org > +--

Re: [OpenWrt-Devel] x86-64: /proc is not being mounted

ific target for OpenWRT? On 13 September 2015 at 14:48, John Crispin wrote: > good decision let us know if you run into issues. one change at a time > is always best in these cases and tend to cost less time to get the > final result. > > > > On 13/09/2015 15:14, Carlos F

Re: [OpenWrt-Devel] x86-64: /proc is not being mounted

w out, I will use it instead of using the trunk. On 11 September 2015 at 11:02, Carlos Ferreira wrote: > I didn't. I copied the config value so that who read the mail, could > understand imediatly what I was talking about. > > I'm unable to see if the default config works,

Re: [OpenWrt-Devel] x86-64: /proc is not being mounted

It seems that preinit is not running after the first boot. I don't know why... On 11 September 2015 at 00:53, Carlos Ferreira wrote: > I have a custom build for x86_64 where CONFIG_PROC_FS is active (y) at the > kernel configuration. /etc/fstabs has nothing and is pointing into an e

[OpenWrt-Devel] x86-64: /proc is not being mounted

I have a custom build for x86_64 where CONFIG_PROC_FS is active (y) at the kernel configuration. /etc/fstabs has nothing and is pointing into an empty /tmp directory. Is there any reason that might prevent the /proc from being mounted? After booting for the first time, /proc is not mounted and bec

[OpenWrt-Devel] Macro for selected ABI

Hi everyone! Is there any Macro for the packages Makefiles that I can use, in order to know which ABI is selected, when a specific platform/profile is selected within the menuconfig? I need an automatic way to pass to my package the ABI that is being used by the CPU architecture. -- Carlos Migu

[OpenWrt-Devel] OpenWRT SDK and autotools + EclipseCDT development.

Hello to all! I'm trying to create a setup for a project using Eclipse-CDT with GNU autotools, from which I would be able to generate binaries for both my host platform and also for a OpenWRT platform, using the appropriate cross-compile. Now, I already know to to create an Eclipse Cross-Compile

Re: [OpenWrt-Devel] Symmetric MultiProcessing broken for IXP4xx arch.

Well, like I said, beyond Linux 3.14 kernel version, the field is defined if CONFIG_SYSFS is active. I will contact the netmap developers to see if they are available to update the source. On 12 July 2014 15:58, Felix Fietkau wrote: > On 2014-07-12 16:51, Carlos Ferreira wrote: > > Y

Re: [OpenWrt-Devel] Symmetric MultiProcessing broken for IXP4xx arch.

not active. Beyond 3.13 (I think), the real_num_rx_queues field is defined if CONFIG_SYSFS is defined. On 12 July 2014 15:40, Felix Fietkau wrote: > On 2014-07-12 16:29, Carlos Ferreira wrote: > > I'm having an issue with OpenWRT trunk where it seems > > that SMP (Symmetric

[OpenWrt-Devel] Symmetric MultiProcessing broken for IXP4xx arch.

I'm having an issue with OpenWRT trunk where it seems that SMP (Symmetric MultiProcessing) is marked as being Broken, for the IXP4xx arch and I'm trying to compile netmap for the Cambria SBC. Netmap requires the kernel to have SMP active. Can anyone tell me

Re: [OpenWrt-Devel] uClibc menuconfig

Ok, just ignore the question. I already noticed that libthread_db is only available at trunk. On 8 July 2014 17:50, Carlos Ferreira wrote: > Hello all! > > Can anyone tell me how can I enable the pthread debug mode in uClibc? > I followed the instructions as explained h

[OpenWrt-Devel] uClibc menuconfig

Hello all! Can anyone tell me how can I enable the pthread debug mode in uClibc? I followed the instructions as explained here with no luck in obtaining the libthread_db.so. In here

Re: [OpenWrt-Devel] CONFIG_RPS flag activation

Success! I was able to compile it and generate the kernel module. Now, I just need to test it and see if it works. On 13 June 2014 00:46, Carlos Ferreira wrote: > Ok, thanks for the assistance. I will try that! > Just to explain what are my actions here, I'm trying to compile

Re: [OpenWrt-Devel] CONFIG_RPS flag activation

2014 00:37, Florian Fainelli wrote: > 2014-06-12 16:22 GMT-07:00 Carlos Ferreira : > > Hello all! > > Can anyone tell me how can activate the CONFIG_RPS flag for the target > x86 > > generic? > > I have tried to add a CONFIG_RPS=y to the config-3.3 file in the > > t

Re: [OpenWrt-Devel] CONFIG_RPS flag activation

btw, just to be more accurate, its not a flag, its a kconfig symbol :) Sorry for the mistake. On 13 June 2014 00:22, Carlos Ferreira wrote: > Hello all! > Can anyone tell me how can activate the CONFIG_RPS flag for the target x86 > generic? > I have tried to add a CONFIG_RPS=y t

[OpenWrt-Devel] CONFIG_RPS flag activation

Hello all! Can anyone tell me how can activate the CONFIG_RPS flag for the target x86 generic? I have tried to add a CONFIG_RPS=y to the config-3.3 file in the target/linux/x86/generic dir and recompile, but i got no luck. In the kernel_menuconfig, RPS is still disabled. I need this active because

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #8627: mklibs fails with python3

Claymore here. It works well. I have been using it for quite some time. It works better than Python 2.7. On 25 June 2013 18:30, OpenWrt wrote: > #8627: mklibs fails with python3 > ---+-- > Reporter: tibor.vago@… | Owner: developers >