Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Luka Perkov 
On Fri, Jun 08, 2012 at 08:50:46PM +0100, Tim Fletcher wrote:
 On 08/06/12 02:32, Luka Perkov wrote:
 Board owners please test this patch and give feedback for the boards:
 
   * sheevaplug
   * dockstar
   * iconnect
 
 You can use kwboot tool like this (run as root):
 
 ./bin/kirkwood/u-boot-kwboot/kwboot -b 
 bin/kirkwood/openwrt-kirkwood-ib62x0-u-boot.kwb -p /dev/ttyUSB0
 
 As soon as it is finished run your favorite terminal like usual. With
 kwboot you can not brick your boards. It sends bootloader via serial and
 does not touch the flash... You can recover board with no bootloader
 using this tool.
 
 My iConnect doesn't seem to do anything with this tool, all I get is
 
 Sending boot message. Please reboot the target...- and a spinning
 cursor, the iConnect doesn't boot.
 
 According to strace kwboot continues in a loop doing
 
 ioctl(3, TCFLSH, 0x2)   = 0
 write(3, \273\21\3DUfw, 8)   = 8
 ioctl(3, TCSBRK, 0x1)   = 0
 select(4, [3], NULL, NULL, {0, 5})  = 0 (Timeout)

Ok. On older kirkwood boards this does not work. Read about it here:

http://lists.denx.de/pipermail/u-boot/2012-May/123866.html

 If I try and tftpboot the bin file I get the following:
 
 Marvell tftp 0x80 iconnect/openwrt-kirkwood-iconnect-u-boot.bin
 Using egiga0 device
 TFTP from server 192.168.1.1; our IP address is 192.168.1.10
 Filename 'iconnect/openwrt-kirkwood-iconnect-u-boot.bin'.
 Load address: 0x80
 Loading: #
  ###
 done
 Bytes transferred = 364540 (58ffc hex)
 Marvell go 0x80
 ## Starting application at 0x0080 ...
 software interrupt
 pc : [00800dcc]  lr : [0060022c]
 sp : 0060  ip : c8012078 fp : 005ff25c
 r10:   r9 :  r8 : c8012000
 r7 : 005ff67f  r6 : 0002 r5 : 005ffe78  r4 : 
 r3 :   r2 :  r1 :   r0 : deadbeef
 Flags: nzcv  IRQs on  FIQs on  Mode USER_26
 Resetting CPU ...
 
 I have messed about with the iconnect a fair bit and I've never
 managed to get another uboot binary to chain boot in it.

This is normal if you try to run it that way. Plase test (and experiment)
with this values in package/uboot-kirkwood/files/include/configs/iconnect.h:

#define CONFIG_SYS_TEXT_BASE 0x80
#define CONFIG_SYS_RAMBOOT

Then try go 0x80

Luka
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Tim Fletcher 

On 09/06/12 12:00, Luka Perkov wrote:

On Fri, Jun 08, 2012 at 08:50:46PM +0100, Tim Fletcher wrote:

On 08/06/12 02:32, Luka Perkov wrote:

Board owners please test this patch and give feedback for the boards:

  * sheevaplug
  * dockstar
  * iconnect

You can use kwboot tool like this (run as root):

./bin/kirkwood/u-boot-kwboot/kwboot -b 
bin/kirkwood/openwrt-kirkwood-ib62x0-u-boot.kwb -p /dev/ttyUSB0

As soon as it is finished run your favorite terminal like usual. With
kwboot you can not brick your boards. It sends bootloader via serial and
does not touch the flash... You can recover board with no bootloader
using this tool.

My iConnect doesn't seem to do anything with this tool, all I get is

Sending boot message. Please reboot the target...- and a spinning
cursor, the iConnect doesn't boot.

According to strace kwboot continues in a loop doing

ioctl(3, TCFLSH, 0x2)   = 0
write(3, \273\21\3DUfw, 8)   = 8
ioctl(3, TCSBRK, 0x1)   = 0
select(4, [3], NULL, NULL, {0, 5})  = 0 (Timeout)

Ok. On older kirkwood boards this does not work. Read about it here:

http://lists.denx.de/pipermail/u-boot/2012-May/123866.html


If I try and tftpboot the bin file I get the following:

Marvell  tftp 0x80 iconnect/openwrt-kirkwood-iconnect-u-boot.bin
Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.10
Filename 'iconnect/openwrt-kirkwood-iconnect-u-boot.bin'.
Load address: 0x80
Loading: #
  ###
done
Bytes transferred = 364540 (58ffc hex)
Marvell  go 0x80
## Starting application at 0x0080 ...
software interrupt
pc : [00800dcc]  lr : [0060022c]
sp : 0060  ip : c8012078 fp : 005ff25c
r10:   r9 :  r8 : c8012000
r7 : 005ff67f  r6 : 0002 r5 : 005ffe78  r4 : 
r3 :   r2 :  r1 :   r0 : deadbeef
Flags: nzcv  IRQs on  FIQs on  Mode USER_26
Resetting CPU ...

I have messed about with the iconnect a fair bit and I've never
managed to get another uboot binary to chain boot in it.

This is normal if you try to run it that way. Plase test (and experiment)
with this values in package/uboot-kirkwood/files/include/configs/iconnect.h:

#define CONFIG_SYS_TEXT_BASE 0x80
#define CONFIG_SYS_RAMBOOT

Then try go 0x80


I've tried this and also the suggestion to load at 0x60 and neither 
seem to have helped but have produced different symptoms. Loading to 
0x60 causes a hang and changing the defines and then booting at 
0x80 produces the same CPU reset.


I have changed the PCIe wireless card from a ralink to an ath9k and I've 
also done a fair amount of changes to the uboot environment, I am going 
to try changing the wireless card back and also reset the environment to 
see if that helps.


--
Tim Fletchert...@night-shade.org.uk

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Tim Fletcher 

On 09/06/12 13:12, Tim Fletcher wrote:

On 09/06/12 12:00, Luka Perkov wrote:

On Fri, Jun 08, 2012 at 08:50:46PM +0100, Tim Fletcher wrote:

On 08/06/12 02:32, Luka Perkov wrote:

Board owners please test this patch and give feedback for the boards:

  * sheevaplug
  * dockstar
  * iconnect

You can use kwboot tool like this (run as root):

./bin/kirkwood/u-boot-kwboot/kwboot -b 
bin/kirkwood/openwrt-kirkwood-ib62x0-u-boot.kwb -p /dev/ttyUSB0


As soon as it is finished run your favorite terminal like usual. With
kwboot you can not brick your boards. It sends bootloader via 
serial and

does not touch the flash... You can recover board with no bootloader
using this tool.

My iConnect doesn't seem to do anything with this tool, all I get is

Sending boot message. Please reboot the target...- and a spinning
cursor, the iConnect doesn't boot.

According to strace kwboot continues in a loop doing

ioctl(3, TCFLSH, 0x2)   = 0
write(3, \273\21\3DUfw, 8)   = 8
ioctl(3, TCSBRK, 0x1)   = 0
select(4, [3], NULL, NULL, {0, 5})  = 0 (Timeout)

Ok. On older kirkwood boards this does not work. Read about it here:

http://lists.denx.de/pipermail/u-boot/2012-May/123866.html


If I try and tftpboot the bin file I get the following:

Marvell  tftp 0x80 iconnect/openwrt-kirkwood-iconnect-u-boot.bin
Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.10
Filename 'iconnect/openwrt-kirkwood-iconnect-u-boot.bin'.
Load address: 0x80
Loading: 
#

  ###
done
Bytes transferred = 364540 (58ffc hex)
Marvell  go 0x80
## Starting application at 0x0080 ...
software interrupt
pc : [00800dcc]  lr : [0060022c]
sp : 0060  ip : c8012078 fp : 005ff25c
r10:   r9 :  r8 : c8012000
r7 : 005ff67f  r6 : 0002 r5 : 005ffe78  r4 : 
r3 :   r2 :  r1 :   r0 : deadbeef
Flags: nzcv  IRQs on  FIQs on  Mode USER_26
Resetting CPU ...

I have messed about with the iconnect a fair bit and I've never
managed to get another uboot binary to chain boot in it.
This is normal if you try to run it that way. Plase test (and 
experiment)
with this values in 
package/uboot-kirkwood/files/include/configs/iconnect.h:


#define CONFIG_SYS_TEXT_BASE 0x80
#define CONFIG_SYS_RAMBOOT

Then try go 0x80


I've tried this and also the suggestion to load at 0x60 and 
neither seem to have helped but have produced different symptoms. 
Loading to 0x60 causes a hang and changing the defines and then 
booting at 0x80 produces the same CPU reset.


I have changed the PCIe wireless card from a ralink to an ath9k and 
I've also done a fair amount of changes to the uboot environment, I am 
going to try changing the wireless card back and also reset the 
environment to see if that helps.




Full envreset and without the ath9k pcie card still produce the same 
results, even with know good uboot binaries I guess either the iconnect 
is duff or I'm missing some obvious.


--
Tim Fletchert...@night-shade.org.uk

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Luka Perkov 
Hi,

On Sat, Jun 09, 2012 at 01:31:35PM +0100, Tim Fletcher wrote:
 Full envreset and without the ath9k pcie card still produce the same
 results, even with know good uboot binaries I guess either the
 iconnect is duff or I'm missing some obvious.

uboot has nothing to do what is connected to pcie (imho). Do you have
jtag? I found this:

http://hardsoftmix.blogspot.com/

I'll double check later the init values that he uses in his patch
(attached).

Luka
diff -Nur u-boot-2011.12-rc3/board/Marvell/iconnect/config.mk 
u-boot-2011.12-rc3.work/board/Marvell/iconnect/config.mk
--- u-boot-2011.12-rc3/board/Marvell/iconnect/config.mk 1969-12-31 
20:00:00.0 -0400
+++ u-boot-2011.12-rc3.work/board/Marvell/iconnect/config.mk2012-03-18 
06:28:41.0 -0400
@@ -0,0 +1,28 @@
+#
+# (C) Copyright 2009
+# Marvell Semiconductor www.marvell.com
+# Written-by: Prafulla Wadaskar prafu...@marvell.com
+#
+# See file CREDITS for list of people who contributed to this
+# project.
+#
+# This program is free software; you can redistribute it and/or
+# modify it under the terms of the GNU General Public License as
+# published by the Free Software Foundation; either version 2 of
+# the License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+# MA 02110-1301 USA
+#
+
+TEXT_BASE = 0x0060
+
+# Kirkwood Boot Image configuration file
+KWD_CONFIG = $(SRCTREE)/board/$(BOARDDIR)/kwbimage.cfg
diff -Nur u-boot-2011.12-rc3/board/Marvell/iconnect/iconnect.c 
u-boot-2011.12-rc3.work/board/Marvell/iconnect/iconnect.c
--- u-boot-2011.12-rc3/board/Marvell/iconnect/iconnect.c1969-12-31 
20:00:00.0 -0400
+++ u-boot-2011.12-rc3.work/board/Marvell/iconnect/iconnect.c   2012-03-18 
06:28:41.0 -0400
@@ -0,0 +1,149 @@
+/*
+ * (C) Copyright 2009
+ * Marvell Semiconductor www.marvell.com
+ * Written-by: Prafulla Wadaskar prafu...@marvell.com
+ *
+ * See file CREDITS for list of people who contributed to this
+ * project.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ */
+
+#include common.h
+#include miiphy.h
+#include asm/arch/kirkwood.h
+#include asm/arch/mpp.h
+#include iconnect.h
+
+DECLARE_GLOBAL_DATA_PTR;
+
+int board_early_init_f(void)
+{
+   /*
+* default gpio configuration
+* There are maximum 64 gpios controlled through 2 sets of registers
+* the  below configuration configures mainly initial LED status
+*/
+   kw_config_gpio(ICONNECT_OE_VAL_LOW,
+   ICONNECT_OE_VAL_HIGH,
+   ICONNECT_OE_LOW, ICONNECT_OE_HIGH);
+
+   /* Multi-Purpose Pins Functionality configuration */
+   u32 kwmpp_config[] = {
+   MPP0_NF_IO2,
+   MPP1_NF_IO3,
+   MPP2_NF_IO4,
+   MPP3_NF_IO5,
+   MPP4_NF_IO6,
+   MPP5_NF_IO7,
+   MPP6_SYSRST_OUTn,
+   MPP7_GPO,
+   MPP8_TW_SDA,
+   MPP9_TW_SCK,
+   MPP10_UART0_TXD,
+   MPP11_UART0_RXD,
+   MPP12_GPO,
+   MPP13_SD_CMD,
+   MPP14_SD_D0,
+   MPP15_SD_D1,
+   MPP16_SD_D2,
+   MPP17_SD_D3,
+   MPP18_NF_IO0,
+   MPP19_NF_IO1,
+   MPP20_GE1_0,
+   MPP21_GE1_1,
+   MPP22_GE1_2,
+   MPP23_GE1_3,
+   MPP24_GE1_4,
+   MPP25_GE1_5,
+   MPP26_GE1_6,
+   MPP27_GE1_7,
+   MPP28_GPIO,
+   MPP29_GPIO,
+   MPP30_GE1_10,
+   MPP31_GE1_11,
+   MPP32_GE1_12,
+   MPP33_GE1_13,
+   MPP34_GE1_14,
+   MPP35_GPIO,
+   MPP36_AUDIO_SPDIFI,
+   MPP37_AUDIO_SPDIFO,
+   MPP38_GPIO,
+   MPP39_TDM_SPI_CS0,
+   MPP40_TDM_SPI_SCK,
+

[OpenWrt-Devel] [PATCH] dnsmasq: update to 2.62

2012-06-09 Thread Dave Täht 
From: Dave Taht dave.t...@bufferbloat.net

---
 package/dnsmasq/Makefile |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/dnsmasq/Makefile b/package/dnsmasq/Makefile
index 10f1806..26f5a61 100644
--- a/package/dnsmasq/Makefile
+++ b/package/dnsmasq/Makefile
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=dnsmasq
-PKG_VERSION:=2.59
+PKG_VERSION:=2.62
 PKG_RELEASE:=4
 
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
 PKG_SOURCE_URL:=http://thekelleys.org.uk/dnsmasq
-PKG_MD5SUM:=b5757ef2d7b651748eeebb88af29d7d6
+PKG_MD5SUM:=f47e5cb8f5bac6343f24b2dbe317ab40
 
 PKG_INSTALL:=1
 
-- 
1.7.9.5

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 2/2] Switch openwrt default to TCP cubic from westwood

2012-06-09 Thread Dave Täht 
From: Dave Taht dave.t...@bufferbloat.net

Despite Westwood's theoretical advantages, in nearly
every benchmark we ran last year, TCP cubic won, whether it be
on correct RTT estimates, amount of buffering, responsiveness,
etc. on current hardware and software designs.

(both need timestamps on to work well, besides)

TCP cubic is better maintained and understood than westwood,
also.

While a scenario where westwood would win possibly exists,
there is too much buffering in the wifi stack in particular
at present, to see any improvement.

So this leaves westwood enabled, but no longer the default.

If you wish to exercise various TCPs under contention,
the current svn head of netperf (2.6) has options to switch
congestion control agorithms on the fly, as does iperf.
---
 target/linux/generic/config-3.3 |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/target/linux/generic/config-3.3 b/target/linux/generic/config-3.3
index f98ddd6..3c4843d 100644
--- a/target/linux/generic/config-3.3
+++ b/target/linux/generic/config-3.3
@@ -575,8 +575,8 @@ CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
 # CONFIG_DEFAULT_RENO is not set
 CONFIG_DEFAULT_SECURITY=
 CONFIG_DEFAULT_SECURITY_DAC=y
-CONFIG_DEFAULT_TCP_CONG=westwood
-CONFIG_DEFAULT_WESTWOOD=y
+CONFIG_DEFAULT_TCP_CONG=cubic
+CONFIG_DEFAULT_CUBIC=y
 CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
 # CONFIG_DEPRECATED_PARAM_STRUCT is not set
 # CONFIG_DETECT_HUNG_TASK is not set
@@ -2875,7 +2875,7 @@ CONFIG_SYSVIPC_SYSCTL=y
 # CONFIG_TCIC is not set
 CONFIG_TCP_CONG_ADVANCED=y
 # CONFIG_TCP_CONG_BIC is not set
-# CONFIG_TCP_CONG_CUBIC is not set
+CONFIG_TCP_CONG_CUBIC=y
 # CONFIG_TCP_CONG_HSTCP is not set
 # CONFIG_TCP_CONG_HTCP is not set
 # CONFIG_TCP_CONG_HYBLA is not set
-- 
1.7.9.5

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH 1/2] Enable TCP timestamps. Enable sack/dsack. Enable ECN if offered

2012-06-09 Thread Dave Täht 
From: Dave Taht dave.t...@bufferbloat.net

A year of testing in the cerowrt project shows not using timestamps
to be a very bad idea in nearly any TCP at speeds above a few Mbit.

As FQ_CODEL will actually assert ECT(3) on ECN streams, it is useful
to have ECN be negotiated when offered. In this day and age it
could also be hoped that ECN could merely be one by default, but...

Lastly sack/dsack help on recovery from larger amounts of packet
loss.
---
 package/base-files/files/etc/sysctl.conf |6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/package/base-files/files/etc/sysctl.conf 
b/package/base-files/files/etc/sysctl.conf
index 2d97000..0aa0588 100644
--- a/package/base-files/files/etc/sysctl.conf
+++ b/package/base-files/files/etc/sysctl.conf
@@ -4,11 +4,13 @@ net.ipv4.conf.all.arp_ignore=1
 net.ipv4.ip_forward=1
 net.ipv4.icmp_echo_ignore_broadcasts=1
 net.ipv4.icmp_ignore_bogus_error_responses=1
-net.ipv4.tcp_ecn=0
+net.ipv4.tcp_ecn=2
 net.ipv4.tcp_fin_timeout=30
 net.ipv4.tcp_keepalive_time=120
 net.ipv4.tcp_syncookies=1
-net.ipv4.tcp_timestamps=0
+net.ipv4.tcp_timestamps=1
+net.ipv4.tcp_sack=1
+net.ipv4.tcp_dsack=1
 
 net.ipv4.netfilter.ip_conntrack_checksum=0
 net.ipv4.netfilter.ip_conntrack_max=16384
-- 
1.7.9.5

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Luka Perkov 
On Sat, Jun 09, 2012 at 01:43:18PM +0100, Tim Fletcher wrote:
 Full envreset and without the ath9k pcie card still produce the same
 results, even with know good uboot binaries I guess either the
 iconnect is duff or I'm missing some obvious.
 uboot has nothing to do what is connected to pcie (imho). Do you have
 jtag? I found this:
 
 http://hardsoftmix.blogspot.com/
 
 I'll double check later the init values that he uses in his patch
 (attached).
 
 I've not got a jtag for the board but I understand how it works,
 I've tried his prebuild uboot binary but he has only put up a .kwb
 which as I understand it has a 200byte header on that you need to
 allow for with the go command?

Where did you see that?

 If I understood the process right you need to tftp it to 0x80
 and then go from 0x800200

No. I could try chainloading from my board later if you want.

 That binary also fails with the same CPU reset if I try and chain it.

His patch has all the same kwb values as mine does... I think that my
patch should work. There are now two options for testing this, you try
to flash this on your board and see if it works and if it does not work:

 1) you get jtag and reflash your original bootloader
 2) you send me your board and I make it work here (once I'm done I will
return the board)

Do you like any of this options? I dont see the third one...

Luka
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] IPv6: Add support for domain name distribution via RA messages

2012-06-09 Thread Dave Täht 
Backport from Kernel 3.5
---
 ...at-ND-option-31-as-userland-DNSSL-support.patch |   53 
 1 files changed, 53 insertions(+), 0 deletions(-)
 create mode 100644 
target/linux/generic/patches-3.3/050-Treat-ND-option-31-as-userland-DNSSL-support.patch

diff --git 
a/target/linux/generic/patches-3.3/050-Treat-ND-option-31-as-userland-DNSSL-support.patch
 
b/target/linux/generic/patches-3.3/050-Treat-ND-option-31-as-userland-DNSSL-support.patch
new file mode 100644
index 000..c2f68fc
--- /dev/null
+++ 
b/target/linux/generic/patches-3.3/050-Treat-ND-option-31-as-userland-DNSSL-support.patch
@@ -0,0 +1,53 @@
+From 86a53286bb9933244a86a684c68ee1ccb32bd53e Mon Sep 17 00:00:00 2001
+From: Alexey I. Froloff ra...@raorn.name
+Date: Fri, 6 Apr 2012 05:50:58 +
+Subject: [PATCH] Treat ND option 31 as userland (DNSSL support)
+
+As specified in RFC6106, DNSSL option contains one or more domain names
+of DNS suffixes.  8-bit identifier of the DNSSL option type as assigned
+by the IANA is 31.  This option should also be treated as userland.
+
+Signed-off-by: Alexey I. Froloff ra...@raorn.name
+Signed-off-by: David S. Miller da...@davemloft.net
+---
+ include/net/ndisc.h |1 +
+ net/ipv6/ndisc.c|4 +++-
+ 2 files changed, 4 insertions(+), 1 deletions(-)
+
+diff --git a/include/net/ndisc.h b/include/net/ndisc.h
+index e3133c2..a9d350e 100644
+--- a/include/net/ndisc.h
 b/include/net/ndisc.h
+@@ -34,6 +34,7 @@ enum {
+   __ND_OPT_ARRAY_MAX,
+   ND_OPT_ROUTE_INFO = 24, /* RFC4191 */
+   ND_OPT_RDNSS = 25,  /* RFC5006 */
++  ND_OPT_DNSSL = 31,  /* RFC6106 */
+   __ND_OPT_MAX
+ };
+ 
+diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
+index c964958..b103252 100644
+--- a/net/ipv6/ndisc.c
 b/net/ipv6/ndisc.c
+@@ -15,6 +15,7 @@
+ /*
+  *Changes:
+  *
++ *Alexey I. Froloff   :   RFC6106 (DNSSL) support
+  *Pierre Ynard:   export userland ND options
+  *through netlink (RDNSS support)
+  *Lars Fenneberg  :   fixed MTU setting on receipt
+@@ -228,7 +229,8 @@ static struct nd_opt_hdr *ndisc_next_option(struct 
nd_opt_hdr *cur,
+ 
+ static inline int ndisc_is_useropt(struct nd_opt_hdr *opt)
+ {
+-  return opt-nd_opt_type == ND_OPT_RDNSS;
++  return opt-nd_opt_type == ND_OPT_RDNSS ||
++  opt-nd_opt_type == ND_OPT_DNSSL;
+ }
+ 
+ static struct nd_opt_hdr *ndisc_next_useropt(struct nd_opt_hdr *cur,
+-- 
+1.7.1
+
-- 
1.7.1

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Tim Fletcher 

On 09/06/12 16:32, Luka Perkov wrote:

On Sat, Jun 09, 2012 at 01:43:18PM +0100, Tim Fletcher wrote:

Full envreset and without the ath9k pcie card still produce the same
results, even with know good uboot binaries I guess either the
iconnect is duff or I'm missing some obvious.

uboot has nothing to do what is connected to pcie (imho). Do you have
jtag? I found this:

http://hardsoftmix.blogspot.com/

I'll double check later the init values that he uses in his patch
(attached).

I've not got a jtag for the board but I understand how it works,
I've tried his prebuild uboot binary but he has only put up a .kwb
which as I understand it has a 200byte header on that you need to
allow for with the go command?

Where did you see that?


http://projects.doozan.com/uboot/build_uboot.htm

Under testing your uboot


That binary also fails with the same CPU reset if I try and chain it.

His patch has all the same kwb values as mine does... I think that my
patch should work. There are now two options for testing this, you try
to flash this on your board and see if it works and if it does not work:

  1) you get jtag and reflash your original bootloader
  2) you send me your board and I make it work here (once I'm done I will
 return the board)

Do you like any of this options? I dont see the third one...



I've been tempted to just try and flash the new uboot on and hope for 
the best, I brought the iconnect because it was cheap and interesting 
looking (it has a pcie slot for wireless etc) I've not got any further 
than installing various versions of Arch/Debian/Fedora/OpenWRT on it and 
tinkering with uboot.


The uboot on the iConnect is at least pretty function is has ext2/fat 
drivers as well as TFTP and usb.


I have a couple of bids on cheap iConnects on ebay atm so if I win one 
I'll ship it over to you so long as you keep supporting the iConnect :)


I suspect that in my fiddling I have broken something in the firmware or 
the iConnect I have is a very old version so if I win another I can see 
if that is the case as well.


--
Tim Fletchert...@night-shade.org.uk

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Daniel Golle 
On 09/06/12 15:43, Tim Fletcher wrote:
 If I understood the process right you need to tftp it to 0x80 and 
 then go from 0x800200
Again, loading it to 0x80 cannot work with that patch.
The address to tftp-load the u-boot bin (or kwb) depends on what is defined as
TEXT_BASE, either see mv-common.h, sometimes it's overwritten in config.mk or
the .h definitions file of the board in include/configs/. As both doesn't seem
to be the case for the iconnect, you should try loading it to 0x60 (and then
go 0x60 for the .bin or go 0x600200 for the .kwb)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2][RFC] uboot-kirkwood: upgrade to 2012.04.01

2012-06-09 Thread Tim Fletcher 

On 09/06/12 19:48, Daniel Golle wrote:

On 09/06/12 15:43, Tim Fletcher wrote:

If I understood the process right you need to tftp it to 0x80 and
then go from 0x800200

Again, loading it to 0x80 cannot work with that patch.
The address to tftp-load the u-boot bin (or kwb) depends on what is defined as
TEXT_BASE, either see mv-common.h, sometimes it's overwritten in config.mk or
the .h definitions file of the board in include/configs/. As both doesn't seem
to be the case for the iconnect, you should try loading it to 0x60 (and then
go 0x60 for the .bin or go 0x600200 for the .kwb)


Understood, I've both rebuilt the uboot binary with the TEXT_BASE set to 
0x80 in the iconnect.h file and also tried loading the plain 
binaries at 0x60.


Loading at 0x60 hangs the running uboot before completing the tftp 
transfer, compiling with the changed TEXT_BASE and loading at 0x80 
produces a cpu reset.


--
Tim Fletchert...@night-shade.org.uk

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] nodogsplash uses deprecated iptables syntax

2012-06-09 Thread Moritz Warning 
Starting nodogsplash there is the following warning on the console:

Using intrapositioned negation (`--option ! this`) is deprecated in
favor of extrapositioned (`! --option this`).

Attached is a trivial patch to fix the issue.

--- a/src/fw_iptables.c
+++ b/src/fw_iptables.c
@@ -449,7 +449,7 @@ iptables_fw_init(void) {
   /* CHAIN_TO_ROUTER, related and established packets  ACCEPT */
   rc |= iptables_do_command(-t filter -A  CHAIN_TO_ROUTER  -m state --state RELATED,ESTABLISHED -j ACCEPT);
   /* CHAIN_TO_ROUTER, bogus SYN packets  DROP */
-  rc |= iptables_do_command(-t filter -A  CHAIN_TO_ROUTER  -p tcp --tcp-flags SYN SYN --tcp-option \\! 2 -j  DROP);
+  rc |= iptables_do_command(-t filter -A  CHAIN_TO_ROUTER  -p tcp --tcp-flags SYN SYN \\! --tcp-option 2 -j  DROP);
 
   /* CHAIN_TO_ROUTER, packets to HTTP listening on gw_port on router ACCEPT */
   rc |= iptables_do_command(-t filter -A  CHAIN_TO_ROUTER  -p tcp --dport %d -j ACCEPT, gw_port);

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel