[OpenWrt-Devel] Freescale P1020 WLAN support
Hi, is there currently anybody working on OpenWRT P1020-WLAN (Freescale) support? It is because we at the FeM e.V. are working on it trying to port the freescale patches forward and would like to join forces with anybody already working on it. Regards, M. Braun -- http://www.fem.tu-ilmenau.de/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Freescale P1020 WLAN support
Hello, I have once got p1020 running with openwrt. It should basically work without any specific target patches. I had to only adapt image building script. I will give it a try with 3.3 kernel and let you know. Wojtek PS At the moment I am fighting with p1010 as I get some spurious interrupts on second pcie slot. Maybe somebody has experienced similar problems? - Original Message - Hi, is there currently anybody working on OpenWRT P1020-WLAN (Freescale) support? It is because we at the FeM e.V. are working on it trying to port the freescale patches forward and would like to join forces with anybody already working on it. Regards, M. Braun -- http://www.fem.tu-ilmenau.de/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] d-link dsl-2741b serial
Hello, I try to get the serial console on a d-link dsl-2741 wrong. There is a serial port on the board (with pins already). Does someone have the pin layout and the settings for it? I found that it should be 115200 (gpl source, kernel config: CONFIG_CMDLINE=console=ttyS0,115200 I got some output in some cases but the output is always garbled. I tried various speed settings but no success. With best regards Christoph -- Linux User Group Wernigerode http://www.lug-wr.de/ signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
Hello, Le 03/27/12 15:43, Otto Solares Cabrera a écrit : Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? You might want to revert changeset r30954 and see if that changes something for you. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Freescale P1020 WLAN support
I have just tried kernel 3.3 on p1020wlan and it seems to run with empty target patches folder. Only eth0 is working at the moment and most probably dts file has to be adapted slightly for eth1. What kind of other Freescale patches are you planning to port? Wojtek - Original Message - Hello, I have once got p1020 running with openwrt. It should basically work without any specific target patches. I had to only adapt image building script. I will give it a try with 3.3 kernel and let you know. Wojtek PS At the moment I am fighting with p1010 as I get some spurious interrupts on second pcie slot. Maybe somebody has experienced similar problems? - Original Message - Hi, is there currently anybody working on OpenWRT P1020-WLAN (Freescale) support? It is because we at the FeM e.V. are working on it trying to port the freescale patches forward and would like to join forces with anybody already working on it. Regards, M. Braun -- http://www.fem.tu-ilmenau.de/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
On 03/27/2012 04:14 PM, Wojciech Dubowik wrote: I have just tried kernel 3.3 on p1020wlan and it seems to run with empty target patches folder. Do you have any Makefile and scripts for this? Only eth0 is working at the moment and most probably dts file has to be adapted slightly for eth1. Do work the mPCIe ports and the serial console? What kind of other Freescale patches are you planning to port? We are planning to port almost all patches from the ltib build from freescale. Many of them are in the mainline kernel others don't. I wrote in the OpenWRT wiki a page for the P1020WLAN[0] board. Rainer [0] http://wiki.openwrt.org/hardware/freescale/p1020 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] BCMA - Enable use of IRQ6
Hi Nathan,
On 03/23/2012 08:50 PM, Nathan Hintz wrote:
Changes since v1: Patch file renamed (235-bcma-enable-irq6.patch).
Signed-off-by: Nathan Hintz nlhi...@hotmail.com
--- /dev/null
+++ target/linux/brcm47xx/patches-3.2/235-bcma-enable-irq6.patch
@@ -0,0 +1,29 @@
+--- a/drivers/bcma/driver_mips.c
b/drivers/bcma/driver_mips.c
+@@ -75,7 +75,7 @@
+ return dev-core_index;
+ flag = bcma_aread32(dev, BCMA_MIPS_OOBSELOUTA30);
+
+-return flag 0x1F;
++return (flag ? (flag 0x1F) : 0x3F);
Why do you want to that? This results in assiningning irq 8 to some
cores where the irq is never used by us.
The Broadcom SDK does the following for our chip:
si_setirq(sih, 1, D11_CORE_ID, 0);
si_setirq(sih, 2, GMAC_CORE_ID, 0);
si_setirq(sih, 3, USB20H_CORE_ID, 0);
si_setirq(sih, 4, PCIE_CORE_ID, 0);
si_setirq(sih, 0, CC_CORE_ID, 0);
si_setirq(sih, 0, I2S_CORE_ID, 0);
+ }
+
+ /* Get the MIPS IRQ assignment for a specified device.
+@@ -88,6 +88,8 @@
+ unsigned int irq;
+
+ irqflag = bcma_core_mips_irqflag(dev);
++if (irqflag == 0x3F)
++return 6;
+
+ for (irq = 1; irq = 4; irq++)
+ if (bcma_read32(mdev, BCMA_MIPS_MIPS74K_INTMASK(irq))
+@@ -244,7 +246,7 @@
+ core-irq = 0;
+ else
+ core-irq = mips_irq + 2;
+-if (core-irq 5)
++if (core-irq 6)
This looks good to me.
+ continue;
+ switch (core-id.id) {
+ case BCMA_CORE_PCI:
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
So I have cooked sth up based on latest trunk. I have made mistake in my setup and I accidentally used p1010rdb device tree instead of p1020rdb and got eth0 to work ;o) Device tree for 1020WLAN needs some more work to get physical addresses right. Anyway the current image should run on WAN interface. I don't have any older mpc85xx devices so I don't know whether they need patches with latest kernel or not. At the moment I have just removed them. I have used following command for booting: setenv fdtfile openwrt-mpc85xx-p1020rdb.fdt setenv bootfile openwrt-mpc85xx-uImage setenv bootcmd 'run ramboot2' setenv ramboot2 'setenv bootargs root=/dev/ram rw console=$consoledev, $baudrate $othbootargs ramdisk_size=12;tftp $loadaddr $bootfile; tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr' and the patch From bd32a8f6c3e64ba787ab3f2214ae35a12ea8ad30 Mon Sep 17 00:00:00 2001 From: Wojciech Dubowik wojciech.dubo...@neratec.com Date: Tue, 27 Mar 2012 17:18:04 +0200 Subject: [PATCH 1/1] mpc85xx: Experimental support for Feeescale P1010RDB and P1020WLAN Signed-off-by: Wojciech Dubowik wojciech.dubo...@neratec.com --- target/linux/mpc85xx/Makefile |2 +- target/linux/mpc85xx/config-3.3| 255 target/linux/mpc85xx/image/Makefile|8 +- .../patches-3.3/200-p1020-dts-eth0-hack.patch | 47 .../patches-3.3/201-p1010-dts-typo-fix.patch | 11 + 5 files changed, 318 insertions(+), 5 deletions(-) create mode 100644 target/linux/mpc85xx/config-3.3 create mode 100644 target/linux/mpc85xx/patches-3.3/200-p1020-dts-eth0-hack.patch create mode 100644 target/linux/mpc85xx/patches-3.3/201-p1010-dts-typo-fix.patch diff --git a/target/linux/mpc85xx/Makefile b/target/linux/mpc85xx/Makefile index 3543438..91d608c 100644 --- a/target/linux/mpc85xx/Makefile +++ b/target/linux/mpc85xx/Makefile @@ -13,7 +13,7 @@ CFLAGS:=-Os -pipe -fno-caller-saves -mcpu=8540 FEATURES:=spe_fpu ramdisk MAINTAINER:=Imre Kaloz ka...@openwrt.org -LINUX_VERSION:=2.6.38.8 +LINUX_VERSION:=3.3 include $(INCLUDE_DIR)/target.mk diff --git a/target/linux/mpc85xx/config-3.3 b/target/linux/mpc85xx/config-3.3 new file mode 100644 index 000..7c8adb6 --- /dev/null +++ b/target/linux/mpc85xx/config-3.3 @@ -0,0 +1,255 @@ +# CONFIG_40x is not set +# CONFIG_44x is not set +# CONFIG_ADVANCED_OPTIONS is not set +# CONFIG_ARCH_DMA_ADDR_T_64BIT is not set +CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y +CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y +CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_WALK_MEMORY=y +CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +# CONFIG_ARCH_NO_VIRT_TO_BUS is not set +# CONFIG_ARCH_PHYS_ADDR_T_64BIT is not set +CONFIG_ARCH_REQUIRE_GPIOLIB=y +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_MSI=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y +CONFIG_AUDIT_ARCH=y +CONFIG_BCMA_POSSIBLE=y +CONFIG_BOOKE=y +CONFIG_BOUNCE=y +CONFIG_CMDLINE=console=ttyS0,115200 +CONFIG_CMDLINE_BOOL=y +# CONFIG_CPM2 is not set +CONFIG_DEBUG_BUGVERBOSE=y +CONFIG_DECOMPRESS_LZMA=y +CONFIG_DEFAULT_UIMAGE=y +CONFIG_DEVKMEM=y +CONFIG_DNOTIFY=y +CONFIG_DTC=y +# CONFIG_E200 is not set +CONFIG_E500=y +CONFIG_EARLY_PRINTK=y +CONFIG_ELF_CORE=y +CONFIG_ENABLE_MUST_CHECK=y +# CONFIG_EPAPR_BOOT is not set +CONFIG_FREEZER=y +CONFIG_FSL_BOOKE=y +CONFIG_FSL_EMB_PERFMON=y +CONFIG_FSL_LBC=y +CONFIG_FSL_PCI=y +CONFIG_FSL_PMC=y +CONFIG_FSL_PQ_MDIO=y +CONFIG_FSL_SOC=y +CONFIG_FSL_SOC_BOOKE=y +CONFIG_FSL_ULI1575=y +CONFIG_GENERIC_ATOMIC64=y +CONFIG_GENERIC_BUG=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y +CONFIG_GENERIC_CMOS_UPDATE=y +# CONFIG_GENERIC_CPU_DEVICES is not set +CONFIG_GENERIC_GPIO=y +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_GENERIC_ISA_DMA=y +CONFIG_GENERIC_NVRAM=y +CONFIG_GENERIC_PCI_IOMAP=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_GENERIC_TIME_VSYSCALL=y +CONFIG_GEN_RTC=y +# CONFIG_GEN_RTC_X is not set +CONFIG_GIANFAR=y +CONFIG_GPIOLIB=y +CONFIG_GPIO_MPC8XXX=y +# CONFIG_HAMRADIO is not set +CONFIG_HAS_DMA=y +CONFIG_HAS_IOMEM=y +CONFIG_HAS_IOPORT=y +CONFIG_HAS_RAPIDIO=y +CONFIG_HAVE_ARCH_JUMP_LABEL=y +CONFIG_HAVE_ARCH_KGDB=y +CONFIG_HAVE_ARCH_TRACEHOOK=y +CONFIG_HAVE_DMA_API_DEBUG=y +CONFIG_HAVE_DMA_ATTRS=y +CONFIG_HAVE_DYNAMIC_FTRACE=y +CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y +CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y +CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y +CONFIG_HAVE_FUNCTION_TRACER=y +# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set +CONFIG_HAVE_GENERIC_HARDIRQS=y +CONFIG_HAVE_IDE=y +CONFIG_HAVE_IOREMAP_PROT=y +CONFIG_HAVE_IRQ_WORK=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_HAVE_MEMBLOCK=y +CONFIG_HAVE_MEMBLOCK_NODE_MAP=y +CONFIG_HAVE_OPROFILE=y +CONFIG_HAVE_PERF_EVENTS=y +CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y +# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set +CONFIG_HAVE_SPARSE_IRQ=y
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
On 03/27/2012 05:31 PM, Wojciech Dubowik wrote: Thank you, I would apply the patch and try to run OpenWRT on the P1020rdb. I let you know my experience. I don't have any older mpc85xx devices so I don't know whether they need patches with latest kernel or not. At the moment I have just removed them. The Freescale developer team make for the P1020rdb around 170 patches for the 2.6.32 Linux kernel. Many of them are meanwhile upstream but some are hardware hacks and driver changes. Its hard to say which patches really work and which don't without a working OS. Greetings, Rainer ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Commits] r31085 - trunk/package/hostapd/files
Minor comment...
On 3/27/12 7:29 AM, openwrt-comm...@openwrt.org wrote:
Author: nbd
Date: 2012-03-27 15:29:41 +0200 (Tue, 27 Mar 2012)
New Revision: 31085
Modified:
trunk/package/hostapd/files/wpa_supplicant.sh
Log:
wpa_supplicant: modify wpa_supplicant.sh in order to support IBSS-RSN/WPA-NONE
Based on patch by: Antonio Quartulli or...@autistici.org
Modified: trunk/package/hostapd/files/wpa_supplicant.sh
===
--- trunk/package/hostapd/files/wpa_supplicant.sh 2012-03-27 13:21:53 UTC
(rev 31084)
+++ trunk/package/hostapd/files/wpa_supplicant.sh 2012-03-27 13:29:41 UTC
(rev 31085)
@@ -3,6 +3,8 @@
local driver=$2
local key=$key
local options=$3
+ local freq
+ [ -n $4 ] freq=frequency=$4
I might have done this as:
local freq=$4
# wpa_supplicant should use wext for mac80211 cards
[ $driver = mac80211 ] driver='wext'
@@ -59,6 +61,7 @@
;;
*psk*)
key_mgmt='WPA-PSK'
+ [ $mode = adhoc -a $driver != nl80211 ]
key_mgmt='WPA-NONE'
config_get_bool usepassphrase $vif usepassphrase 1
if [ $usepassphrase = 1 ]; then
passphrase=psk=\${key}\
@@ -123,11 +126,13 @@
cat /var/run/wpa_supplicant-$ifname.conf EOF
ctrl_interface=/var/run/wpa_supplicant-$ifname
network={
+ $mode
scan_ssid=1
ssid=$ssid
$bssid
key_mgmt=$key_mgmt
$proto
+ $freq
and then:
${freq:+frequency=$freq}
instead.
$ieee80211w
$passphrase
$pairwise
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Have trunk snapshots been intentionally stopped?
I thought that trunk snapshots were done practically daily. Now it seems to me that there are no snapshots for any of the major platforms after March 14-16. It that intentional? http://downloads.openwrt.org/snapshots/trunk/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2 1/1] ppp: Fix high softirq utilization with pppoa
Users of the Geos platform are reporting high CPU utilization. This seems to be
rooted in a problem with the TX queue restart in PPP.
Redux: Add 3.3 version.
Signed-off-by: Philip Prindeville phil...@redfish-solutions.com
Index: target/linux/generic/patches-3.2/120-ppp_txqueue_restart.patch
===
--- target/linux/generic/patches-3.2/120-ppp_txqueue_restart.patch
(revision 0)
+++ target/linux/generic/patches-3.2/120-ppp_txqueue_restart.patch
(revision 0)
@@ -0,0 +1,82 @@
+For every transmitted packet, ppp_start_xmit() will stop the netdev
+queue and then, if appropriate, restart it. This causes the TX softirq
+to run, entirely gratuitously.
+
+This is only a waste of CPU time in the normal case, but it's actively
+harmful when the PPP device is a TEQL slave — the wakeup will cause the
+offending device to receive the next TX packet from the TEQL queue, when
+it *should* have gone to the next slave in the list. We end up seeing
+large bursts of packets on just *one* slave device, rather than using
+the full available bandwidth over all slaves.
+
+This patch fixes the problem by *not* unconditionally stopping the queue
+in ppp_start_xmit(). It adds a return value from ppp_xmit_process()
+which indicates whether the queue should be stopped or not.
+
+It *doesn't* remove the call to netif_wake_queue() from
+ppp_xmit_process(), because other code paths (especially from
+ppp_output_wakeup()) need it there and it's messy to push it out to the
+other callers to do it based on the return value. So we leave it in
+place — it's a no-op in the case where the queue wasn't stopped, so it's
+harmless in the TX path.
+
+Signed-off-by: David Woodhouse david.woodho...@intel.com
+
+--- a/drivers/net/ppp/ppp_generic.c~ 2012-01-26 00:39:32.0 +
b/drivers/net/ppp/ppp_generic.c2012-03-26 10:32:31.286744147 +0100
+@@ -235,7 +235,7 @@ struct ppp_net {
+ /* Prototypes. */
+ static int ppp_unattached_ioctl(struct net *net, struct ppp_file *pf,
+ struct file *file, unsigned int cmd, unsigned long arg);
+-static void ppp_xmit_process(struct ppp *ppp);
++static int ppp_xmit_process(struct ppp *ppp);
+ static void ppp_send_frame(struct ppp *ppp, struct sk_buff *skb);
+ static void ppp_push(struct ppp *ppp);
+ static void ppp_channel_push(struct channel *pch);
+@@ -968,9 +968,9 @@ ppp_start_xmit(struct sk_buff *skb, stru
+ proto = npindex_to_proto[npi];
+ put_unaligned_be16(proto, pp);
+
+- netif_stop_queue(dev);
+ skb_queue_tail(ppp-file.xq, skb);
+- ppp_xmit_process(ppp);
++ if (!ppp_xmit_process(ppp))
++ netif_stop_queue(dev);
+ return NETDEV_TX_OK;
+
+ outf:
+@@ -1048,10 +1048,11 @@ static void ppp_setup(struct net_device
+ * Called to do any work queued up on the transmit side
+ * that can now be done.
+ */
+-static void
++static int
+ ppp_xmit_process(struct ppp *ppp)
+ {
+ struct sk_buff *skb;
++ int ret = 0;
+
+ ppp_xmit_lock(ppp);
+ if (!ppp-closing) {
+@@ -1061,10 +1062,13 @@ ppp_xmit_process(struct ppp *ppp)
+ ppp_send_frame(ppp, skb);
+ /* If there's no work left to do, tell the core net
+ code that we can accept some more. */
+- if (!ppp-xmit_pending !skb_peek(ppp-file.xq))
++ if (!ppp-xmit_pending !skb_peek(ppp-file.xq)) {
+ netif_wake_queue(ppp-dev);
++ ret = 1;
++ }
+ }
+ ppp_xmit_unlock(ppp);
++ return ret;
+ }
+
+ static inline struct sk_buff *
+
+--
+David WoodhouseOpen Source Technology Centre
+david.woodho...@intel.com Intel Corporation
+
+
+
Index: target/linux/generic/patches-3.3/120-ppp_txqueue_restart.patch
===
--- target/linux/generic/patches-3.3/120-ppp_txqueue_restart.patch
(revision 0)
+++ target/linux/generic/patches-3.3/120-ppp_txqueue_restart.patch
(revision 0)
@@ -0,0 +1,82 @@
+For every transmitted packet, ppp_start_xmit() will stop the netdev
+queue and then, if appropriate, restart it. This causes the TX softirq
+to run, entirely gratuitously.
+
+This is only a waste of CPU time in the normal case, but it's actively
+harmful when the PPP device is a TEQL slave — the wakeup will cause the
+offending device to receive the next TX packet from the TEQL queue, when
+it *should* have gone to the next slave in the list. We end up seeing
+large bursts of packets on just *one* slave device, rather than using
+the full available bandwidth over all slaves.
+
+This patch fixes the problem by *not* unconditionally stopping the queue
+in ppp_start_xmit(). It adds a return value from ppp_xmit_process()
+which indicates whether the queue should be stopped or not.
+
+It *doesn't* remove the call to netif_wake_queue() from
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
Hey, On Tue, 27 Mar 2012 18:05:29 +0200, Rainer 'Rei' Schuth rainer.sch...@fem.tu-ilmenau.de wrote: On 03/27/2012 05:31 PM, Wojciech Dubowik wrote: Thank you, I would apply the patch and try to run OpenWRT on the P1020rdb. I let you know my experience. I don't have any older mpc85xx devices so I don't know whether they need patches with latest kernel or not. At the moment I have just removed them. The Freescale developer team make for the P1020rdb around 170 patches for the 2.6.32 Linux kernel. Many of them are meanwhile upstream but some are hardware hacks and driver changes. Its hard to say which patches really work and which don't without a working OS. If you have something basic up and running, I'm happy to review and (if needed) clean up the patches. Given how much I could nuke from the freescale patches previosly, you probably will be fine porting about 10 over from the 170 ;) Imre ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] enable ntpd server for busybox
I've now tested my trunk patch and it works fine But I still can't find were $PROG is defined (is this a mistake, or some sort of built in variable???) (I've made some grep and nothing) Le 23/03/2012 02:19, Philip Prindeville a écrit : Maybe: [ -n $PROG -a -x $PROG ] || return 1 instead? On 3/22/12 4:34 PM, Etienne Champetier wrote: Hi The 2 attached patchs (trunk bacfire) add busybox ntpd enable_server option, as busybox ntpd server is compiled by default. We only need 1 client/server daemon (olipro patch was launching 2 daemons) I've fully tested the bacfire patch, and as i don't have a running openwrt trunk i'm not sure for the trunk patch (i'm sure about my modifications, but i'm not sure about [ -x $PROG ] || return 1, as $PROG isn't defined ?!) Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr Le 16/01/2012 01:57, Philip Prindeville a écrit : On 1/14/12 11:37 AM, Olipro wrote: On Saturday 14 Jan 2012 02:45:59 Philip Prindeville wrote: Don't we already have a 'disabled' option? Now we're adding an 'enable_server' option? That seems confusing for no useful reason. have you bothered to read what I originally wrote? your response would make me inclined to believe that you didn't. currently the ntpd initscript only runs it as a CLIENT - this patch enables you to have one instance running as a client and another as a SERVER that other hosts can synchronise with. Or perhaps I'm misunderstanding, what would you propose for allowing the built-in busybox ntpd to be utilised as a server? a separate init script entirely perhaps? Or separate config sections... instead of 'config ntp' have 'config ntp-server' and 'config ntp-client'. -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix iptables when build as build-dependency
Hello Thomas,
On Wednesday 21 March 2012 19:19:00 thomas.lan...@lantiq.com wrote:
Hi,
this patch fixes the iptables build if no extensions are selected (e.g. when
building only as build-dependency)
Best regards,
Thomas
---
diff --git a/package/iptables/patches/210-fix-no-ext-install.patch
b/package/iptables/patches/210-fix-no-ext-install.patch new file mode
100644
--- /dev/null
+++ b/package/iptables/patches/210-fix-no-ext-install.patch
@@ -0,0 +1,15 @@
+--- a/extensions/GNUmakefile.in
b/extensions/GNUmakefile.in
+@@ -68,11 +68,10 @@ pf6_solibs:= $(patsubst %,libip6t_%.
+ #
+ targets := libext4.a libext6.a matches4.man matches6.man \
+targets4.man targets6.man
+-targets_install :=
+ libext4_objs := ${pfx_objs} ${pf4_objs}
+ libext6_objs := ${pfx_objs} ${pf6_objs}
+ targets += ${pfx_solibs} ${pf4_solibs} ${pf6_solibs}
+-targets_install += ${pfx_solibs} ${pf4_solibs} ${pf6_solibs}
++targets_install := $(strip ${pfx_solibs} ${pf4_solibs} ${pf6_solibs})
This breaks build when extensions are enabled for me:
make[5]: *** No rule to make target `extensions/libext4.a', needed by
`iptables-multi'. Stop.
make[5]: Leaving directory `/home/florian/dev/openwrt/trunk/build_dir/linux-
malta_le/iptables-1.4.10'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/florian/dev/openwrt/trunk/build_dir/linux-
malta_le/iptables-1.4.10'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/florian/dev/openwrt/trunk/build_dir/linux-
malta_le/iptables-1.4.10'
make[2]: *** [/home/florian/dev/openwrt/trunk/build_dir/linux-
malta_le/iptables-1.4.10/.built] Error 2
--
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 1/1] ppp: Fix high softirq utilization with pppoa
On Tuesday 27 March 2012 11:05:26 Philip Prindeville wrote: Users of the Geos platform are reporting high CPU utilization. This seems to be rooted in a problem with the TX queue restart in PPP. Redux: Add 3.3 version. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com Applied in r31096, thanks Philip! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/1] geos: Add 'tc' and kmod-sched for bonding
On Monday 26 March 2012 18:41:38 Philip Prindeville wrote: The Geos2 includes 2 ADSL+ interfaces, and as such it needs to have the TEQL scheduler for bonding. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com Applied in r31094, thanks Philip! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] wavemon: Bump to v0.7.4
On Monday 19 March 2012 00:41:05 Jonathan McCrohan wrote: Signed-off-by: Jonathan McCrohan jmccro...@gmail.com --- Applied in r31098, thanks Jonathan! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Update libmodbus to latest stable release 3.0.2
On Tuesday 06 March 2012 15:25:34 Simon G wrote: Patch against backfire branch. Trunk is probably the same. This patch updates libmodbus from version 2.0.3 to the latest stable release 3.0.2 I needed modbus RTU and that seemed to be missing in the older version ? Patch is also attached in case it is corrupt inline here! Signed-off-by: Simon Gaynor open...@simong.net Applied in r31099, thanks! Next time, please do not hijack the thread ;) -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/1] v1: configure lighttpd with OpenSSL support only if the user asks for it
On Tuesday 28 February 2012 13:05:51 Emmanuel Deloget wrote: SSL support adds a quite large dependency to lighttpd when compiled in. On a 32 bit platform, libcrypto is roughly 1MB, to which one must add the size of libssl (roughly 250KB). This is 2 to 5 times the size of a typical lighttpd embedded installation. SSL support is only needed if one enables the SSL engine in the lighttpd.conf configuration file. This patch introduces a configuration option that allows the user to choose whether or not he wants to compile SSL support in. It defaults to 'y' only if libopenssl is already selected (either by active selection or because libopenssl is a dependency of another package). Signed-off-by: Emmanuel Deloget log...@free.fr Applied in r31097, thanks Emmanuel! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] packages: upgrade libconfig to 1.4.8
On Saturday 18 February 2012 16:38:04 Michael Heimpold wrote: Signed-off-by: Michael Heimpold m...@heimpold.de --- For the record, swalker applied this patch in r30635. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: rt305x: add profile for the Asus WL-330N board
2012.03.20. 11:35 keltezéssel, Frédéric Leroy írta: Signed-off-by: Frédéric Leroy fr...@starox.org Applied with some changes. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: add ath9k support to netgear dgn3500 platform
This patch adds support for the AR9223 wifi chip on the Netgear DGN3500 ADSL2
router. Originally the chip was identified with PCI product ID 0xff1d. This was
fixed by using ltq_pci_ath_fixup similair to other implementations with the
AR9223. The eeprom data is extracted from the original firmware located in
/etc/ath/eeprom.
I've tested this by manually scanning other networks and creating a simple
access-point.
Signed-off-by: Pieter Voorthuijsen p.voorthuijsen at gmail.com
---
Index: target/linux/lantiq/files-3.2/arch/mips/lantiq/xway/mach-netgear.h
===
--- target/linux/lantiq/files-3.2/arch/mips/lantiq/xway/mach-netgear.h
(revision 0)
+++ target/linux/lantiq/files-3.2/arch/mips/lantiq/xway/mach-netgear.h
(revision 0)
@@ -0,0 +1,271 @@
+/*
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ *
+ * Copyright (C) 2012 Pieter Voorthuijsen
+ *
+ */
+
+#ifndef _MACH_NETGEAR_H__
+#define _MACH_NETGEAR_H__
+
+static u16 dgn3500_eeprom_data[] = {
+ 0xa55a, 0x, 0x0003, 0x6000, 0x168c, 0x0029, 0x6008, 0x0001,
+ 0x0280, 0x602c, 0x168c, 0x2093, 0x5000, 0x168c, 0x002a, 0x5008,
+ 0x0001, 0x0280, 0x502c, 0x168c, 0x2093, 0x5064, 0x0cc0, 0x0504,
+ 0x506c, 0x3811, 0x0003, 0x4004, 0x073b, 0x0040, 0x4074, 0x0003,
+ 0x, 0x4000, 0x, 0x01c2, 0x6034, 0x0044, 0x, 0x,
+ 0xc01a, 0x1aac, 0x612a, 0x9e3c, 0xf29a, 0x0ebc, 0x5fbd, 0x46c3,
+ 0xc1fe, 0x8b93, 0x9ed8, 0xd4c8, 0xcfbb, 0x99f6, 0xb094, 0x7cbf,
+ 0x52a2, 0x5a3b, 0xedde, 0x97cf, 0x5928, 0xe314, 0xb947, 0xb4c1,
+ 0x5ac8, 0x80d5, 0x892b, 0x6053, 0xc9b5, 0xb4e5, 0xf242, 0x0ef1,
+ 0xb947, 0xc159, 0x22d1, 0x0cd9, 0xf77d, 0x2845, 0x6f35, 0x05a2,
+ 0x0d74, 0x0d1f, 0x7ee6, 0x1002, 0xc682, 0xe94d, 0x0f2e, 0x4d8e,
+ 0x869b, 0x74df, 0x1240, 0x2c9f, 0xd680, 0x62d6, 0xea70, 0xfa50,
+ 0xa53e, 0xebb0, 0xc96a, 0xfaac, 0x13f9, 0x45f7, 0xe6a4, 0xada6,
+ 0x114e, 0x2c8e, 0x305e, 0x76ba, 0xd2d5, 0xd6ad, 0x69f0, 0x03a0,
+ 0xd6bb, 0x8063, 0x7c8d, 0x7fee, 0x83d4, 0x3888, 0x1460, 0xbd4c,
+ 0x7104, 0xad78, 0xe57f, 0xddb6, 0x5910, 0x87a0, 0xb725, 0x29be,
+ 0x81b5, 0x2ffe, 0x269e, 0x55f4, 0xb5f1, 0xc447, 0x23aa, 0x5f1a,
+ 0x7eda, 0x091b, 0x7c76, 0xd018, 0xd69e, 0xb521, 0x1975, 0x5910,
+ 0xd162, 0xb75c, 0xeba0, 0x7a0a, 0x1973, 0x28aa, 0x6721, 0x20cb,
+ 0x8415, 0xcde5, 0x0fe9, 0x6e66, 0x8600, 0x9aff, 0xc370, 0x33eb,
+ 0x3ba8, 0x5e64, 0x6d6c, 0xe0d8, 0x98e5, 0xff91, 0x17db, 0xa722,
+ 0xfbe5, 0x251c, 0x7a2b, 0x4d84, 0xaf8d, 0x2ef7, 0x714e, 0xe055,
+ 0xe90d, 0xbcc4, 0x81eb, 0xfe75, 0xc386, 0xe836, 0x5cb0, 0x9748,
+ 0x6a9c, 0x5df2, 0xbe32, 0x9320, 0xe5e2, 0x345b, 0x11e2, 0x5165,
+ 0x452d, 0x1500, 0x2cd1, 0x6e60, 0xfffe, 0x7ab4, 0xb3fa, 0x9a07,
+ 0xeb13, 0x65ae, 0x6cfd, 0x8ec6, 0x81c8, 0x6fd5, 0x2025, 0x022f,
+ 0x783e, 0x01ea, 0x55d3, 0x1163, 0xfa51, 0x7eb9, 0xdbd2, 0xdc45,
+ 0x28bf, 0x226d, 0x9535, 0x4340, 0x9267, 0x86e5, 0xb20b, 0x692c,
+ 0xb6a5, 0xf6ee, 0x101b, 0xb882, 0x428f, 0xe4b4, 0x0f1d, 0x2bd6,
+ 0x29f4, 0xdb1f, 0x0618, 0xe5d3, 0x211f, 0xbef0, 0x3207, 0x8271,
+ 0xee38, 0x328c, 0x1766, 0xe3b0, 0x5612, 0x5c36, 0x54dd, 0xb685,
+ 0x15f0, 0x15be, 0xac6a, 0x6b38, 0x0944, 0xde4a, 0x85e0, 0xbce3,
+ 0x0cb8, 0xd437, 0xe015, 0x0002, 0x, 0x001f, 0x0300, 0xbe7f,
+ 0x3cf1, 0x0303, 0x, 0x, 0x, 0x1b00, 0x0007, 0x0003,
+ 0x, 0x0002, 0x0100, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x2d00, 0x0b0b, 0x0b0b, 0x0b0b, 0x00e0, 0x0e0e, 0x000e,
+ 0x0e02, 0xca00, 0xcaca, 0x0109, 0x, 0x, 0x, 0x0206,
+ 0x0002, 0x, 0x0e0e, 0x0002, 0x, 0x, 0x2c00, 0x,
+ 0x, 0x, 0x0202, 0x098d, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x8000, 0x, 0x, 0x, 0x, 0x,
+ 0x, 0x, 0x, 0x, 0x0010, 0x, 0x0010, 0x,
+ 0x, 0x, 0x05a0, 0x0960, 0x, 0x2d00, 0x2020, 0x000b,
+ 0x1000, 0x00e2, 0x0d0d, 0x000d, 0x0e02, 0xff1c, 0x, 0x0106,
+ 0x, 0x, 0x, 0x0306, 0x0303, 0x, 0x0e0e, 0x1b00,
+ 0x001b, 0x1919, 0x2d00, 0x, 0x, 0x, 0x0303, 0x098d,
+ 0x, 0x, 0x, 0x0092, 0x9200, 0x, 0x8000, 0x,
+ 0x, 0x, 0x, 0x, 0x, 0x, 0x, 0x,
+
Re: [OpenWrt-Devel] [PATCH] lantiq: add ath9k support to netgear dgn3500 platform
On 27/03/12 22:53, Pieter Voorthuijsen wrote: This patch adds support for the AR9223 wifi chip on the Netgear DGN3500 ADSL2 router. Originally the chip was identified with PCI product ID 0xff1d. This was fixed by using ltq_pci_ath_fixup similair to other implementations with the AR9223. The eeprom data is extracted from the original firmware located in /etc/ath/eeprom. I've tested this by manually scanning other networks and creating a simple access-point. Signed-off-by: Pieter Voorthuijsen p.voorthuijsen at gmail.com --- Thank you, i will go over it tomorrow. i was told today that there is a spi driver coming up that makes irq work on ar9. so dont invest too much time on that one please ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On 03/27/2012 06:05 PM, Rainer 'Rei' Schuth wrote: I would apply the patch and try to run OpenWRT on the P1020rdb. I let you know my experience. I managed to boot a standard ramfs image with default out of the box configuration. Developer enviromet settings: - OpenWRT SVN trunk rev 31088 - Target System Freescale MPC85xx - with the patch from Wojtek u-boot: setenv gatewayip 10.26.254.16 setenv netmask 255.255.0.0 setenv ipaddr 10.26.1.6 setenv serverip 10.26.254.16 setenv fdtfile [full-path-to-file]/openwrt-mpc85xx-p1020rdb.fdt setenv bootfile [full-path-to-file]/openwrt-mpc85xx-uImage setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs ramdisk_size=12; tftp $loadaddr $bootfile; tftp $fdtaddr $fdtfile; bootm $loadaddr - $fdtaddr It then boots OpenWRT :) But, there are some problems: 1. Bug with the missing eth1 (second ethernet interface) confirmed Kernel says: [ 418.361439] net eth1: PHY already attached [ 418.365566] net eth1: could not attach to PHY 2. the kernel only sees one of two processors grep cpu /proc/cpuinfo | wc -l 1 3. the kernel only sees 776892 kB of the available (1048576 kB) memory 4. no working watchdog It's a good start ;) Rainer -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPcjRKAAoJEPizOL253ODVXF0IAJzWsofTgMhljAekQB+u5pL9 SFaHjbNvgl3K1qAJkojgl7YM4PAFn9jzzL8ZB8EDf/ljA4pSBdBmv9t80qnHSFbA nmMMnzRAgv+059mWVnAEL5xQNr4558/Ys8clYYfN8rFlzaNPMo2/j2qLqxtGkDY6 PGwPnw9oEBubAXBMefXs6T4dxxX33EOLj7c3FIDEtIl0Cqy55FVaknvtQtJp6z0v /XS9x6+2+VGQGzOkjl8XAh2myvvzO7JRNb1I062rNywzR8FKFHnrgaglaMg8nDtX LP/9u/gjU7hnahXGElgfkvQ1cHY2SWnUHg9ynJivBzllgD+H/tSVBD9D1LvXJj0= =WNVM -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Projekt-wlan] Freescale P1020 WLAN support
Hello, On 03/27/2012 08:41 PM, Imre Kaloz wrote: If you have something basic up and running, I'm happy to review and (if needed) clean up the patches. Given how much I could nuke from the freescale patches previosly, you probably will be fine porting about 10 over from the 170 ;) What do you need exactly? I applied the patch from Wojtek and worked. But we need some kernel patches. Greetings, Rainer ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: add ath9k support to netgear dgn3500 platform
On 27 March 2012 22:53, Pieter Voorthuijsen p.voorthuij...@gmail.comwrote: The eeprom data is extracted from the original firmware located in /etc/ath/eeprom. Hi Are you sure that /etc/ath/eeprom isn't created from some flash partition in boot time, because usually every device should have it's own eeprom calibration data to make wifi performance best. Gigaset sx763 has one eeprom for all devices, and i think some device had wireless problems. Bye ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 25/03/12 19:01, En/na Luca Olivetti ha escrit: Al 29/03/11 18:30, En/na John Crispin ha escrit: On 29/03/11 18:06, Luca Olivetti wrote: Al 29/03/11 10:32, En/na John Crispin ha escrit: AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. yes, the proposed patch rewrites the eep on the fly upon a read and fakes a ES reg. this is the patch we can accept as is into owrt Can or can't? Bye cannot And now, a year later, after constantly ignoring my patches that made the modification to the regdomain optional (with a command line switch), you go and check in a patch that does exactly what you said wasn't acceptable. Unbelievable. I'm still waiting for you to revert such an unacceptable commit. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Bridge filtering on WRT160NL (ar71xx) not working
On Tue, Mar 27, 2012 at 03:49:04PM +0200, Florian Fainelli wrote: Hello, Le 03/27/12 15:43, Otto Solares Cabrera a écrit : Hi! I have a WRT160NL with the 3 interfaces (eth0, eth1, wlan0) on a single bridge (br-lan) and I was normally doing filtering between them but now all the packets are unconditionally bridged to all the interfaces despite the ebtables rules. ebtables doesn't report hits on rules. My last working image was based on r30676 with 3.2.7 kernel, I'm pretty sure is not an upstream kernel problem as I tried latest trunk with kernels 3.2.7, 3.2.12, 3.2.13 and 3.3 and the same problem. Does some default changed recently? You might want to revert changeset r30954 and see if that changes something for you. Reverting that changeset fixes my problem, thank you! -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
On 28/03/12 00:25, Luca Olivetti wrote: Al 25/03/12 19:01, En/na Luca Olivetti ha escrit: Al 29/03/11 18:30, En/na John Crispin ha escrit: On 29/03/11 18:06, Luca Olivetti wrote: Al 29/03/11 10:32, En/na John Crispin ha escrit: AFAIS, the current in-kernel driver relies on regulatory domain for frequency restrictions. It could solve your current problem. yes, the proposed patch rewrites the eep on the fly upon a read and fakes a ES reg. this is the patch we can accept as is into owrt Can or can't? Bye cannot And now, a year later, after constantly ignoring my patches that made the modification to the regdomain optional (with a command line switch), you go and check in a patch that does exactly what you said wasn't acceptable. Unbelievable. I'm still waiting for you to revert such an unacceptable commit. Bye Hi Luca, you were right, i was wrong, i am terribly sorry if the delay caused any inconvenience to you thanks for your understanding, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
Al 28/03/12 00:49, En/na John Crispin ha escrit: Hi Luca, you were right, i was wrong, i am terribly sorry if the delay caused any inconvenience to you thanks for your understanding, Don't worry, I waited for one year, I can wait a few days longer. Bye -- Luca ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] hostapd issue maybe between 30952 - 31118
after freezing at 30952 for the last two(ish) weeks... I updated to 31118 this morning and built against my formerly working 3.3 kernel... I see hostapd, ar71xx, ath9k, 3.3, etc all had updates over this period. Despite replacing my mac80211.sh with the new one and trying a more open-wrt-y build... I see earlier advice today about reverting a bridging related commit, which I will try. (as everything is routed in cerowrt, not bridged)... however my issue is that hostapd isn't coming up for ap mode. I can get adhoc interfaces to come up, but they don't get a ssid. ifup sw00 Configuration file: /var/run/hostapd-phy0.conf nl80211: Failed to set interface sw00 into AP mode nl80211 driver initialization failed. Failed to start hostapd for phy0 cat hostapd-phy0.conf ctrl_interface=/var/run/hostapd-phy0 driver=nl80211 wmm_ac_bk_cwmin=4 wmm_ac_bk_cwmax=10 wmm_ac_bk_aifs=7 wmm_ac_bk_txop_limit=0 wmm_ac_bk_acm=0 wmm_ac_be_aifs=3 wmm_ac_be_cwmin=4 wmm_ac_be_cwmax=10 wmm_ac_be_txop_limit=0 wmm_ac_be_acm=0 wmm_ac_vi_aifs=2 wmm_ac_vi_cwmin=3 wmm_ac_vi_cwmax=4 wmm_ac_vi_txop_limit=94 wmm_ac_vi_acm=0 wmm_ac_vo_aifs=2 wmm_ac_vo_cwmin=2 wmm_ac_vo_cwmax=3 wmm_ac_vo_txop_limit=47 wmm_ac_vo_acm=0 tx_queue_data3_aifs=7 tx_queue_data3_cwmin=15 tx_queue_data3_cwmax=1023 tx_queue_data3_burst=0 tx_queue_data2_aifs=3 tx_queue_data2_cwmin=15 tx_queue_data2_cwmax=63 tx_queue_data2_burst=0 tx_queue_data1_aifs=1 tx_queue_data1_cwmin=7 tx_queue_data1_cwmax=15 tx_queue_data1_burst=3.0 tx_queue_data0_aifs=1 tx_queue_data0_cwmin=3 tx_queue_data0_cwmax=7 tx_queue_data0_burst=1.5 hw_mode=g channel=11 country_code=US logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 ieee80211n=1 ht_capab=[HT20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40] ieee80211d=1 preamble=0 interface=sw00 ctrl_interface=/var/run/hostapd-phy0 auth_algs=1 wpa=0 ssid=OpenWrt wmm_enabled=1 bssid=e0:46:9a:34:30:d2 ignore_broadcast_ssid=0 -- Dave Täht SKYPE: davetaht US Tel: 1-239-829-5608 http://www.bufferbloat.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd issue maybe between 30952 - 31118
On Tue, Mar 27, 2012 at 05:03:24PM -0700, Dave Taht wrote: however my issue is that hostapd isn't coming up for ap mode. Yeah in 3.3 the mon.wlan0 i/f is not being setup but I didn't investigate further. OTOH is just me or do you note too that the compressed firmware image with the 3.3 kernel is like 0.25MB bigger than 3.2? It seems too much kernelbloat* to me :( *any similarity with bufferbloat is pure coincidence... :) -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq cumulative patch
On 28/03/12 01:42, Luca Olivetti wrote: I can wait a few days longer. what are you waiting for now ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
