[OpenWrt-Devel] 回复： How to fix the unknown in the IWINFO

Oh, very sorry,  MT7620a_MT7610e, kmod-rt2800-soc John Crispin 于 2015年2月5日, 星期四, 下午 2:39 写道： On 05/02/2015 04:56, INYO L wrote: > Hi, > > How can I read the TX power, Signal, and others > > root@WirelessRouter:/etc# iwinfo wlan0    ESSID: "wifi" Access > Point: 00:0F:02:70:3C:20 M

Re: [OpenWrt-Devel] How to fix the unknown in the IWINFO

On 05/02/2015 04:56, INYO L wrote: > Hi, > > How can I read the TX power, Signal, and others > > root@WirelessRouter:/etc# iwinfo wlan0 ESSID: "wifi" Access > Point: 00:0F:02:70:3C:20 Mode: Master Channel: 11 (2.462 GHz) > Tx-Power: 20 dBm Link Quality: unknown/70 Signal: unknown Noise:

[OpenWrt-Devel] How to fix the unknown in the IWINFO

Hi,  How can I read the TX power, Signal, and others root@WirelessRouter:/etc# iwinfowlan0     ESSID: "wifi"          Access Point: 00:0F:02:70:3C:20          Mode: Master  Channel: 11 (2.462 GHz)          Tx-Power: 20 dBm  Link Quality: unknown/70          Signal: unknown  Noise: unknown       

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

Yes, the MAC is where expected. I've tried unloading and reloading the mt76pci module; the second line of the log passed unnoticed for me before. root@OpenWrt:/# rmmod mt76pci && modprobe mt76pci && dmesg [...] [ 73.62] pci device driver detached [ 73.63] mt76pci :01:00.0: no of_no

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

On 04/02/2015 22:11, Roger Pueyo Centelles wrote: > root@OpenWrt:/# hexdump -C /dev/mtd2 > 20 76 05 01 64 09 80 01 66 5d ff ff ff ff ff ff | > v..d...f]..| > 0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > || > 0020 ff ff ff ff ff ff ff ff 64 09

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

root@OpenWrt:/# hexdump -C /dev/mtd2 20 76 05 01 64 09 80 01 66 5d ff ff ff ff ff ff | v..d...f]..| 0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || 0020 ff ff ff ff ff ff ff ff 64 09 80 01 66 5c 00 d0 |d...f\..| 0030 59 60 00 04 22 0c

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

On 04/02/2015 20:18, Roger Pueyo Centelles wrote: > Hi, > > I tried with 0x8004 and I also got a random IP address. Actually, > I changed this block in in eeprom.c (line 571) [1]: can you do a "hexdump -C /dev/mtd2" and paste the output please ? ___ o

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

Hi, I tried with 0x8004 and I also got a random IP address. Actually, I changed this block in in eeprom.c (line 571) [1]: if (!is_valid_ether_addr(dev->macaddr)) { eth_random_addr(dev->macaddr); dev_printk(KERN_INFO, dev->dev, "Invalid MAC address, using random address %pM\n",

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

On 04/02/2015 17:08, Roger Pueyo Centelles wrote: > Hi, > > > > 2015-02-04 12:44 GMT+01:00 Chuanhong Guo >: > > From: 郭传鈜 mailto:gch981...@gmail.com>> > > 2ghz should be disabled on this router. > > > You're right. This should be patched. > > > A

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

Hi, 2015-02-04 12:44 GMT+01:00 Chuanhong Guo : > From: 郭传鈜 > > 2ghz should be disabled on this router. > You're right. This should be patched. > And I think 'mediatek,mtd-eeprom' should be defined as<&factory 32768> > instead of <&factory 0x8000> according to WHR-1166D.dts > Actually I didn

[OpenWrt-Devel] [PATCH v2 8/8] mvebu: Add Armada 385 DB AP support

The Armada 385 DB AP board is a reference design board for access points. Signed-off-by: Maxime Ripard --- target/linux/mvebu/image/Makefile | 1 + ...019-mtd-nand-pxa3xx-Fix-PIO-FIFO-draining.patch | 97 + ...M-mvebu-Add-a-number-of-pinctrl-functions.patch | 70

[OpenWrt-Devel] [PATCH v2 0/8] mvebu: Fix flash support and support for A38x

Hi, This serie aims at finally fixing the already supported mvebu boards images, since none of them actually work on the boards except for the WRT1900AC. This is the follow-up of two previous attempts at doing that: https://lists.openwrt.org/pipermail/openwrt-devel/2014-October/028593.html https:

[OpenWrt-Devel] [PATCH v2 7/8] mvebu: Add the Armada 385 Reference Design support

Signed-off-by: Maxime Ripard --- target/linux/mvebu/image/Makefile | 3 +++ .../207-armada-385-rd-mtd-partitions.patch| 19 +++ 2 files changed, 22 insertions(+) create mode 100644 target/linux/mvebu/patches-3.18/207-armada-385-rd-mtd-partitions.

[OpenWrt-Devel] [PATCH v2 6/8] mvebu: Fix NAND and NOR options

All the boards but Mamba had wrong UBI options so far, making it impossible to flash the built image on their respective storage medium. Fix all of the supported boards in order to make the generated images useful. Tested on a Mirabox, an Armada XP GP and an Openblocks AX3, and used the NAND chip

[OpenWrt-Devel] [PATCH v2 5/8] mvebu: Add a subprofile for boards based on a small NOR

Some boards only come with a small NOR on it, where UBI isn't a good solution because of its overhead. Add a new subprofile for such boards, that rely on the mtd split framework instead. Signed-off-by: Maxime Ripard --- target/linux/mvebu/image/Makefile | 25 + 1 file ch

[OpenWrt-Devel] [PATCH v2 4/8] mvebu: Add large NOR sub-profile implementation

While we supported only the NAND so far, some boards use a large enough NOR, where UBI is the only reasonable option. Create a new sub-profile template with a different set of UBI options. Signed-off-by: Maxime Ripard --- target/linux/mvebu/image/Makefile | 22 ++ 1 file chan

[OpenWrt-Devel] [PATCH v2 3/8] mvebu: Add sub-profiles

In order to support the various board NAND layout that we support, introduce a sub-profile similar to the one used by ar71xx. These subprofiles provide a default implementation for most of the building functions, while allowing each sub-profile to override any of these operations in order to have

[OpenWrt-Devel] [PATCH v2 2/8] kernel: Allow ubi autoattach to run on NOR flash

Some devices out there only have a NOR flash to store the rootfs on. While using UBI is arguable on this kind of NAND, this is something that should be supported. Signed-off-by: Maxime Ripard --- .../490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch | 5 +++-- .../490-ubi-auto-at

[OpenWrt-Devel] [PATCH v2 1/8] mvebu: 3.18: Add MTD split framework support

We're going to need the MTD split related options for our NOR support. Signed-off-by: Maxime Ripard --- target/linux/mvebu/config-3.18 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/target/linux/mvebu/config-3.18 b/target/linux/mvebu/config-3.18 index 096b5ed0180b..b4a372d7db72 100644 ---

[OpenWrt-Devel] Autonegotiation problem on RTL8168evl/8111evl

Hello, There is a problem with RTL8168evl/8111evl and driver to it r8169 on OpenWrt build for x86_64 device. The card is visible but link is not established.  I use Asus DSL-N10E as a gateway with dhcp server on it. Log: [   10.731939] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [   10.75

Re: [OpenWrt-Devel] byte counters for IP address using IPTABLES

Hi, please retry after "sysctl -w net.netfilter.nf_conntrack_skip_filter=0" ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/o

Re: [OpenWrt-Devel] byte counters for IP address using IPTABLES

Is this router doing SNAT? If so, these packets are likely being mangled by connection tracking before they get matched by the filter. Charlie On 04/02/15 13:48, INYO L wrote: hi, I have some trouble about the openwrt system, and the linux kernelver-3.10.49 , iptables version 1.4.21 (barrie

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

Ah.Sorry,I mean 2.4GHz support for MT7612E should be disabled. 2015-02-04 19:53 GMT+08:00 Gioacchino Mazzurco : > On Wednesday, February 04, 2015 06:44:44 AM Chuanhong Guo wrote: > > 2ghz should be disabled on this router. > > It doesn't have 2ghz wireless interface, or it is that we are not capa

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

This is a router with mt7620a soc for 2.4GHz wireless and mt7612e for 5.8GHz wireless. 2015-02-04 19:53 GMT+08:00 Gioacchino Mazzurco : > On Wednesday, February 04, 2015 06:44:44 AM Chuanhong Guo wrote: > > 2ghz should be disabled on this router. > > It doesn't have 2ghz wireless interface, or it

Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

On Wednesday, February 04, 2015 06:44:44 AM Chuanhong Guo wrote: > 2ghz should be disabled on this router. It doesn't have 2ghz wireless interface, or it is that we are not capable of supporting it at moment? ___ openwrt-devel mailing list openwrt-devel

[OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.

From: 郭传鈜 2ghz should be disabled on this router. And I think 'mediatek,mtd-eeprom' should be defined as<&factory 32768> instead of <&factory 0x8000> according to WHR-1166D.dts Actually I didn't have this router.But I think this is the reason that the MT7612E radio always gets a random MAC addr

[OpenWrt-Devel] [PATCH] ar71xx: dir-505: fix reset button gpio active_low value

Fix 'active_low' default value for the reset button on DIR-505. Signed-off-by: Rocco Folino --- target/linux/ar71xx/files/arch/mips/ath79/mach-dir-505-a1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-dir-505-a1.c b/target/li