Am 19.05.2015 um 05:45 schrieb nam228:
> Hi all,
>
> I have a board with a qca8334 eth switch chip.The chip is found by the ar8216
> phy as an ar8337.
>
> My board can not ping unless I remove the AR8337_PAD_MAC06_EXCHANGE_EN with a
> path file.
>
> The patch file is:
>
> --- a/drivers/net/ph
Hi all,
I have a board with a qca8334 eth switch chip.The chip is found by the
ar8216 phy as an ar8337.
My board can not ping unless I remove the AR8337_PAD_MAC06_EXCHANGE_EN
with a path file.
The patch file is:
--- a/drivers/net/phy/ar8327.c
+++ b/drivers/net/phy/ar8327.c
@@ -508,8 +508,8
I just realized I only replied to part of the question. They should also
probably be deleted from packages.git.
OpenWrt will ignore them anyway unless the override mechanism is used when
installing the feeds.
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.ope
Yeah; I actually wondered the same question. I’m not sure what we should happen
in this case.
I’ll let blogic replied as he’s the one who moved perf into openwrt.git.
If these packages are required by the OpenWrt core, then one of the openwrt.git
maintainer would probably own it. I’m not sure :s
elfutils is required by perf. So we'll move this package from
packages.git and make it part of the core distribution.
Signed-off-by: Mathieu Olivari
---
package/libs/elfutils/Makefile | 97 +
.../patches/001-elfutils-portability.patch | 1871
..
bzip2 is required by elfutils, itself required by perf. So we'll move
this package from packages.git and make it part of the core
distribution.
Signed-off-by: Mathieu Olivari
---
package/utils/bzip2/Makefile | 87
1 file changed, 87 insertions(+)
cre
perf in upstream Linux kernel 3.17 onwards expects STT_GNU_IFUNC
replicate it from glibc
Patch cherry-picked from:
http://lists.busybox.net/pipermail/uclibc/2015-February/048825.html
Signed-off-by: Mathieu Olivari
---
.../012-elf-Add-STT_GNU_IFUNC-from-glibc.patch | 37 +
EGLIBC dependency was required as libelf was not found. But we now fixed
the root cause, so we can remove it. perf works with uClibc again.
Signed-off-by: Mathieu Olivari
---
package/devel/perf/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/devel/perf/Makefi
Commit 9cddeba3a4eb00e85233f0b8ac84b8e8492822ef was removing uClibc
support from perf because it didn't build anymore.
The root cause of this failure was multiple:
*perf needs a uClibc patch to define STT_GNU_IFUNC. Patch has been done
already to the uClibc project, and just needs to be cherry-pic
argp-standalone is required by elfutils, itself required by perf. So
we'll move this package from packages.git and make it part of the core
distribution.
Signed-off-by: Mathieu Olivari
---
package/libs/argp-standalone/Makefile | 48 +
.../patches/001-throw-in-funcdef.pat
Hey everybody,
I'm trying to build a Barrier Breaker image with OpenVswitch 2.3.1. However,
it fails with
{standard input}:1116: Error: unknown pseudo-op: `.tprelword'
error. I found [a Stack Overflow
thread](http://stackoverflow.com/questions/8872517)
that suggests this is due to a too old
Hello, this is my first submission, please excuse me if I have the wrong
mailing list, or missed a mailing rule.
This patch is to add support for the Plusnet 2704N Router (BCM6318), on
the current trunk.
This will most possibly add support for the Sagem 2704N (Ver 1) and the
TP-Link-TD-W8960N
On 16 May 2015 at 12:53, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
With the previous patches nacked/rejected, it doesn't make sense to
apply this one.
I've commited workaround for RT-AC87U just to make it usable with the
upcoming CC release, see:
https://dev.openwrt.
On 16 May 2015 at 12:53, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
So I'll give a nack to this one too. The feature you proposed is
really nice, but should be implemented as some generic solution, see
Hauke's recent patch:
https://patchwork.ozlabs.org/patch/473208/
__
On 16 May 2015 at 12:53, Álvaro Fernández Rojas wrote:
> Signed-off-by: Álvaro Fernández Rojas
After discussion in this topic, I'll give a nack to this patch. We
should use different approach and we should probably focus on mainline
Broadcom NAND driver.
--
Rafał
__
On 16 May 2015 at 15:28, Rafał Miłecki wrote:
> On 16 May 2015 at 13:53, Álvaro Fernández Rojas wrote:
>> This patch splits firmware partition based on TRX header, while ofpart won't
>> be able to split firmware partition into kernel (linux) + rootfs.
>> It's very similar to bcm63xx code, where
To my knowledge theer has never been automatic building for the relase
branches. Developers have selectively built core packages (like openssl)
after security updates, but otherwise the updated package sources have been
compiled only for the .1 maintenance releases (like 10.03.1). But so far
th
Looks like iostat only tracks block devices so I can see change for
usb flash device but no change for internal flash partitions :(
# iostat
Linux 3.10.49 (Demo36_Muc (Base9)) 05/18/15 _mips_ (1 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
5.340.001.470.00
On 18 May 2015 at 12:12, Hante Meuleman wrote:
> Tested a clean checkout this morning and booted it. It is booting, but no
> packets are received. At least the ifconfig shows no RX packets, could be
> that the packets miss the vlan tag.
Can you see swconfig forcing port 8 state?
swconfig dev swit
Try iostat (selectable in busybox). Maybe is what are you looking for.
2015-05-17 0:40 GMT+02:00, valent.turko...@gmail.com
:
> Here is some interesting info I found using mtdinfo tool:
>
> # mtdinfo /dev/mtd5
> mtd5
> Name: rootfs_data
> Type: n
Hi Lars,
here's my conf:
/etc/config/firewall
config redirect
option target 'DNAT'
option src 'wan'
option dest 'lan'
option proto 'tcp'
option src_dport '22'
option dest_port '22'
option name 'ssh'
option dest_ip '192.168.100.200'
option reflection_src 'exter
Add 802.11r client support to wpa_supplicant. It's only enabled in
wpa_supplicant-full. hostapd gained 802.11r support in commit r45051.
Tested on a TP-Link TL-WR710N sta psk client with two 802.11r enabled
openwrt accesspoints (TP-Link TL-WDR3600).
Signed-off-by: Stefan Hellermann
---
package/
On 15 May 2015 at 20:25, Felix Fietkau wrote:
> On 2015-05-15 17:28, Cristian Morales Vega wrote:
>> Since a "wifi-iface" can only have one "network", how are you supposed
>> to link it to both the wan and wan6 interfaces?
> It can have multiple networks. Use 'list' instead of 'option'.
And it's
23 matches
Mail list logo
