Re: [OpenWrt-Devel] [PATCH] explicitely ignore return value of symlink(3) call

On 2015-10-22 23:15, Daniel Golle wrote: > glibc sets __attribute_warn_unused_result__ on symlink(3) if > FORTIFY_SOURCE is set. This breaks procd which deliberately ignores > the result of the symlink(3) call early during init as there wouldn't > be anything better to do in that case other than

[OpenWrt-Devel] [PATCH 4/5] malta: convert to router type target.

There is currently no relevant definition for developerboard device type in include/target.mk, thus packages like iptables, firewall, dnsmasq etc. are missing in the default images, rendering it almost useless for regular testing or normal use. Signed-off-by: Yousong Zhou

[OpenWrt-Devel] [PATCH 3/5] malta: set CPU_TYPE:=24kc.

There are instructions (e.g. wsbh) only available in MIPS32R2 which is the isa level used by many MIPS targets in OpenWrt. As we use the malta target mostly for development and testing purposes, setting the CPU_TYPE to 24Kc will make the emulation more real. The following is output from

[OpenWrt-Devel] [PATCH 2/5] target.mk: add optimization flags for MIPS 24Kc.

Signed-off-by: Yousong Zhou --- include/target.mk |1 + 1 file changed, 1 insertion(+) diff --git a/include/target.mk b/include/target.mk index 3e7f17d..119f88c 100644 --- a/include/target.mk +++ b/include/target.mk @@ -212,6 +212,7 @@ ifeq ($(DUMP),1)

[OpenWrt-Devel] [PATCH 0/5] malta: changes for better testing environment

The series is a refreshed version of a previous mixed one in September [1]. With many kind advices from linux-mips, the kernel patch was merged in upstream since release 4.3-rc5. It was run-tested with 3.18 kernel and only compile-tested with 4.0 and 4.1. [1]

Re: [OpenWrt-Devel] [PATCH 2/5] target.mk: add optimization flags for MIPS 24Kc.

On 28 October 2015 at 12:55, Yousong Zhou wrote: > --- a/include/target.mk > +++ b/include/target.mk > @@ -212,6 +212,7 @@ ifeq ($(DUMP),1) > CPU_CFLAGS_mips32 = -mips32 -mtune=mips32 > CPU_CFLAGS_mips32r2 = -mips32r2 -mtune=mips32r2 > CPU_CFLAGS_mips64 =

Re: [OpenWrt-Devel] AR9344 Openwrt - LAN and WAN interface link issue

Hi Jow, Thank you so much for the reply. Below is my /etc/config/network file config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config interface 'lan' option ifname 'eth0.1 eth1' option type 'bridge' option proto 'static'

Re: [OpenWrt-Devel] AR9344 Openwrt - LAN and WAN interface link issue

Hi Afkar, WAN: swconfig dev switch0 port 1 get link LAN: swconfig dev switch0 port 1 get link swconfig dev switch0 port 2 get link swconfig dev switch0 port 3 get link swconfig dev switch0 port 4 get link ~ Jow ___ openwrt-devel mailing list

[OpenWrt-Devel] [PATCH] ar71xx: Add support for wdr7500v3

Fixed the commit message to make it more descriptive. Sorry for the noise. Srdjan Rosic (1): ar71xx: Add support for wdr7500v3 target/linux/ar71xx/image/Makefile | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) -- 2.6.1 ___

Re: [OpenWrt-Devel] [PATCH] Add initial support for wdr7500v3

Fixed the commit messages and resent. Please ignore this thread, and look for one prefixed with ar71xx Srdjan Rosic On Tue, Oct 27, 2015 at 10:12 PM, Srdjan Rosic wrote: > Ooops, it's my first patch to openwrt and I didn't know :( > I'm fine with resending, but I'd

Re: [OpenWrt-Devel] backport 46936 (procd: rework makefile, split ujail/seccomp)

if you send a patch it would be faster :) i just got into the office and will be here all day so i can merge it promptly. John On 28/10/2015 00:10, Etienne Champetier wrote: > Hi John, > > since 47268, we need -DUTRACE_SUPPORT=1 to compile utrace >

[OpenWrt-Devel] [PATCH] ar71xx: Add support for wdr7500v3

The device is similar to Archer C7 v2, but with 8M of flash, and 6 external antennas. Reason for breaking the naming pattern is that sticker on the back mentions "WDR7500" and has no mention of "Archer". Signed-off-by: Srdjan Rosic --- target/linux/ar71xx/image/Makefile | 9

Re: [OpenWrt-Devel] [PATCH 5/5] malta: use "static" proto for lan interface

On Oct 28, 2015 5:56 AM, "Yousong Zhou" wrote: > > This is almost the default config of OpenWrt targets (currently even > those sunxi boards with only one ethernet interface use static IP > address for its lan interface). And this is intend intended, because Malta is

Re: [OpenWrt-Devel] [PATCH 4/5] malta: convert to router type target.

On Oct 28, 2015 5:56 AM, "Yousong Zhou" wrote: > > There is currently no relevant definition for developerboard device type > in include/target.mk, thus packages like iptables, firewall, dnsmasq > etc. are missing in the default images, rendering it almost useless > for

[OpenWrt-Devel] [PATCH] ramips: add support for the Asus RP-N53 in the "02_network" boot script

This patch adds a case for the Asus RP-N53 in the "02_network" boot script. Without this, the lan interface does not get configured on startup, effectively bricking the device. Signed-off-by: Alberto Mattea --- diff -uN

[OpenWrt-Devel] Fwd: [OpenWrt-Commits] r47262 - trunk/target/linux/ar71xx/patches-4.1

Uhm, is there any chance for the wr841n v10 full support by Mr. Matthias Schiffer to be back ported to Chaos Calmer? After all it is not a "new device" but a subversion of an existing supported equipment.. Thanks! Forwarded Message Subject: [OpenWrt-Commits] r47262 -

Re: [OpenWrt-Devel] [PATCH] ramips: add support for the Asus RP-N53 in the "02_network" boot script

Hello Alberto, Two comments: 1. Your patch breaks alphabetical order. 2. If you look more deeply into the file, you will easily find there other boards with exactly the same configuration: asl26555 and re6500. Please, don't add unnecessary code and use what's already there. Cheers, Piotr

Re: [OpenWrt-Devel] [PATCH] ramips: add support for the Asus RP-N53 in the "02_network" boot script

Hey, thanks for the quick review. To be honest I hadn't noticed they were in alphabetical order :) I'll fix and resubmit Cheers Alberto In data mer 28 ottobre 2015 19:46:50, Piotr Dymacz ha scritto: > Hello Alberto, > > Two comments: > 1. Your patch breaks alphabetical order. > 2. If you look

[OpenWrt-Devel] [PATCH v2] ramips: add support for the Asus RP-N53 in the "02_network" boot script

This patch adds a case for the Asus RP-N53 in the "02_network" boot script. Without this, the lan interface does not get configured on startup, effectively bricking the device. Signed-off-by: Alberto Mattea --- diff -uN

Re: [OpenWrt-Devel] [PATCH] ramips: add support for the Asus RP-N53 in the "02_network" boot script

Hey, Thanks for fast fix! Cheers, Piotr 2015-10-28 19:56 GMT+01:00 Alberto Mattea : > Hey, > > thanks for the quick review. To be honest I hadn't noticed they were in > alphabetical order :) I'll fix and resubmit > > Cheers > Alberto > > In data mer 28 ottobre 2015

Re: [OpenWrt-Devel] AR9344 Openwrt - LAN and WAN interface link issue

Hi Jow, Thanks a lot for the reply. I have tried the switch command but getting failed response as below: root@openwrt:/# swconfig dev switch0 port 1 get link failed root@openwrt:/# swconfig dev switch0 port 2 get link failed root@openwrt:/# swconfig dev switch0 port 3 get link failed

Re: [OpenWrt-Devel] [PATCH 5/5] malta: use "static" proto for lan interface

On 29 October 2015 at 00:19, Florian Fainelli wrote: > On Oct 28, 2015 5:56 AM, "Yousong Zhou" wrote: >> >> This is almost the default config of OpenWrt targets (currently even >> those sunxi boards with only one ethernet interface use static IP >>

[OpenWrt-Devel] Fwd: [PATCH 2/5] target.mk: add optimization flags for MIPS 24Kc.

Fwd to openwrt-devel list. -- Forwarded message -- From: Yousong Zhou Date: 29 October 2015 at 09:59 Subject: Re: [OpenWrt-Devel] [PATCH 2/5] target.mk: add optimization flags for MIPS 24Kc. To: Cristian Morales Vega On 28 October

Re: [OpenWrt-Devel] [PATCH 1/3] ramips: mt7620 add icplus phy driver kernel config symbol

Hi, On 29/10/2015 02:26, Andrej Vlasic wrote: > Add missing icplus phy driver kernel config symbol to mt7620 subtarget. > This is needed since some mt7620 devices have icplus ip1001 ethernet > transceiver > > Signed-off-by: Andrej Vlasic are you sure this is needed ?

[OpenWrt-Devel] [PATCH 1/3] ramips: mt7620 add icplus phy driver kernel config symbol

Add missing icplus phy driver kernel config symbol to mt7620 subtarget. This is needed since some mt7620 devices have icplus ip1001 ethernet transceiver Signed-off-by: Andrej Vlasic --- target/linux/ramips/mt7620/config-3.18 | 1 + 1 file changed, 1 insertion(+) diff

[OpenWrt-Devel] [PATCH 2/3] ramips: add function to change rt2x00 wifi eeprom mac

Some boards like dovado tiny ac have generic ralink mac in onflash wifi eeprom. Add eeprom_set_macaddr function to rt2x00 eeprom extract script which changes mac addr insde eeprom dump. Signed-off-by: Andrej Vlasic ---

[OpenWrt-Devel] [PATCH 3/3] ramips: add support for Dovado tiny AC

Add support for Dovado tiny AC wifi router. Soc: mt7620a ram: 64MB flash: 8MB 1x usb 2.0 two gigabit lan ports 5ghz wlan is not supported on this board since there is no gpl driverfor mt7610e wifi chip. Signed-off-by: Andrej Vlasic ---

Re: [OpenWrt-Devel] [PATCH 4/5] malta: convert to router type target.

On 29 October 2015 at 00:20, Florian Fainelli wrote: > On Oct 28, 2015 5:56 AM, "Yousong Zhou" wrote: >> >> There is currently no relevant definition for developerboard device type >> in include/target.mk, thus packages like iptables, firewall, dnsmasq

[OpenWrt-Devel] [PATCH] tools/cmake: update to 3.3.2

Update cmake to 3.3.2 and refresh patches. Add a secondary download location. Signed-off-by: Hannu Nyman --- Release notes 3.0-3.3: https://cmake.org/cmake/help/v3.3/release/3.0.html https://cmake.org/cmake/help/v3.3/release/3.1.html

[OpenWrt-Devel] AR9344 Openwrt - LAN and WAN interface link issue

Hi, When I connect only LAN cable and check below command on console "cat /sys/class/net/eth0.1/carrier" will get "1" its correct but when we check "cat /sys/class/net/eth0.2/carrier" even the only LAN cable is connected it returns "1" but i didn't connect the WAN cable. The same thing if we

Re: [OpenWrt-Devel] AR9344 Openwrt - LAN and WAN interface link issue

Hi Afkar, > The same thing if we connect only WAN cable and check "cat > /sys/class/net/eth0.1/carrier" and "cat /sys/class/net/eth0.2/carrier" > both returns "1" . But it should not be like this. This is expected since both eth0.1 and eth0.2 are actually SoC connection to the external switch