[OpenWrt-Devel] [PATCH] ramips: Rework ramips_eth to not require irqsave locking anymore
Previously the tx housekeeping was done in a spin_lock_irqsave critical
section which causes irqs to be disabled during that time. Since the
housekeeping is already prepared to be scheduled as a tasklet process
the housekeeping only in softirq context and revise the locking between
the tx path and the housekeeping tasklet by using a normal spin_lock
which in most situations will be a NOP anyway.
This makes sure that interrupts are only disabled for a short time
since in the worst case the housekeeping might have to free up to 256
skbs.
Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com
---
target/linux/ramips/files/drivers/net/ramips.c | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/target/linux/ramips/files/drivers/net/ramips.c
b/target/linux/ramips/files/drivers/net/ramips.c
index 63570c7..0bc6c06 100644
--- a/target/linux/ramips/files/drivers/net/ramips.c
+++ b/target/linux/ramips/files/drivers/net/ramips.c
@@ -215,7 +215,6 @@ ramips_eth_hard_start_xmit(struct sk_buff *skb, struct
net_device *dev)
unsigned long tx;
unsigned int tx_next;
unsigned int mapped_addr;
- unsigned long flags;
if (priv-plat-min_pkt_len) {
if (skb-len priv-plat-min_pkt_len) {
@@ -233,7 +232,7 @@ ramips_eth_hard_start_xmit(struct sk_buff *skb, struct
net_device *dev)
mapped_addr = (unsigned int) dma_map_single(NULL, skb-data, skb-len,
DMA_TO_DEVICE);
dma_sync_single_for_device(NULL, mapped_addr, skb-len, DMA_TO_DEVICE);
- spin_lock_irqsave(priv-page_lock, flags);
+ spin_lock(priv-page_lock);
tx = ramips_fe_rr(RAMIPS_TX_CTX_IDX0);
tx_next = (tx + 1) % NUM_TX_DESC;
@@ -250,11 +249,11 @@ ramips_eth_hard_start_xmit(struct sk_buff *skb, struct
net_device *dev)
priv-tx_skb[tx] = skb;
wmb();
ramips_fe_wr(tx_next, RAMIPS_TX_CTX_IDX0);
- spin_unlock_irqrestore(priv-page_lock, flags);
+ spin_unlock(priv-page_lock);
return NETDEV_TX_OK;
out:
- spin_unlock_irqrestore(priv-page_lock, flags);
+ spin_unlock(priv-page_lock);
dev-stats.tx_dropped++;
kfree_skb(skb);
return NETDEV_TX_OK;
@@ -313,6 +312,7 @@ ramips_eth_tx_housekeeping(unsigned long ptr)
struct net_device *dev = (struct net_device*)ptr;
struct raeth_priv *priv = netdev_priv(dev);
+ spin_lock(priv-page_lock);
while ((priv-tx[priv-skb_free_idx].txd2 TX_DMA_DONE)
(priv-tx_skb[priv-skb_free_idx])) {
dev_kfree_skb_irq(priv-tx_skb[priv-skb_free_idx]);
@@ -321,6 +321,7 @@ ramips_eth_tx_housekeeping(unsigned long ptr)
if (priv-skb_free_idx = NUM_TX_DESC)
priv-skb_free_idx = 0;
}
+ spin_unlock(priv-page_lock);
ramips_fe_int_enable(RAMIPS_TX_DLY_INT);
}
@@ -346,8 +347,10 @@ ramips_eth_irq(int irq, void *dev)
tasklet_schedule(priv-rx_tasklet);
}
- if (fe_int RAMIPS_TX_DLY_INT)
- ramips_eth_tx_housekeeping((unsigned long)dev);
+ if (fe_int RAMIPS_TX_DLY_INT) {
+ ramips_fe_int_disable(RAMIPS_TX_DLY_INT);
+ tasklet_schedule(priv-tx_housekeeping_tasklet);
+ }
return IRQ_HANDLED;
}
--
1.7.7
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: Rework ramips_eth to not require irqsave locking anymore
Thx, applied in r29762 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] eth0 entry in /etc/config/network
I'm mounting the root file system via NFS. How can I stop the eth0 entry from getting added to /etc/config/network every time I build? -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] eth0 entry in /etc/config/network
On Tue, Jan 17, 2012 at 9:04 PM, jonsm...@gmail.com jonsm...@gmail.comwrote: I'm mounting the root file system via NFS. How can I stop the eth0 entry from getting added to /etc/config/network every time I build? openwrt/packages/basefiles/files/etc/config/network ?? this file remove your eth0 entry :) . and try it. Devendra. -- Jon Smirl jonsm...@gmail.com ___ 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] eth0 entry in /etc/config/network
On Tue, Jan 17, 2012 at 10:37 AM, devendra.aaru devendra.a...@gmail.com wrote: On Tue, Jan 17, 2012 at 9:04 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: I'm mounting the root file system via NFS. How can I stop the eth0 entry from getting added to /etc/config/network every time I build? openwrt/packages/basefiles/files/etc/config/network ?? editing package/base-files/files/etc/config/network does it. I thought it was being generated by the build system. this file remove your eth0 entry :) . and try it. Devendra. -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] eth0 entry in /etc/config/network
On Tue, Jan 17, 2012 at 9:09 PM, jonsm...@gmail.com jonsm...@gmail.comwrote: On Tue, Jan 17, 2012 at 10:37 AM, devendra.aaru devendra.a...@gmail.com wrote: On Tue, Jan 17, 2012 at 9:04 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: I'm mounting the root file system via NFS. How can I stop the eth0 entry from getting added to /etc/config/network every time I build? openwrt/packages/basefiles/files/etc/config/network ?? editing package/base-files/files/etc/config/network does it. I thought it was being generated by the build system. hmm, got your problem solved ? :) this file remove your eth0 entry :) . and try it. Devendra. -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] eth0 entry in /etc/config/network
On 17/01/12 10:41 AM, jonsm...@gmail.com wrote: On Tue, Jan 17, 2012 at 10:41 AM, devendra.aaru devendra.a...@gmail.com wrote: On Tue, Jan 17, 2012 at 9:09 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: On Tue, Jan 17, 2012 at 10:37 AM, devendra.aaru devendra.a...@gmail.com wrote: On Tue, Jan 17, 2012 at 9:04 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: I'm mounting the root file system via NFS. How can I stop the eth0 entry from getting added to /etc/config/network every time I build? openwrt/packages/basefiles/files/etc/config/network ?? editing package/base-files/files/etc/config/network does it. I thought it was being generated by the build system. hmm, got your problem solved ? :) it is solved. This is really what $TOPDIR/files/ is for. ie: mkdir -p $TOPDIR/files/etc/config/ cp -p $TOPDIR/packages/basefiles/files/etc/config/network $TOPDIR/files/etc/config/network vim $TOPDIR/files/etc/config/network ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] FTDI additional serial IDs
Add support for the Rainforest Automation Zigbee dongle.
This is against 2.6.39 only, however Linux 3.2 does not have this
ID either.
Signed-of-by: Peter Naulls pe...@chocky.org
Index: target/linux/generic/patches-2.6.39/823-usb_serial_ftdi_add_more_devices.patch
===
--- target/linux/generic/patches-2.6.39/823-usb_serial_ftdi_add_more_devices.patch (revision 0)
+++ target/linux/generic/patches-2.6.39/823-usb_serial_ftdi_add_more_devices.patch (revision 0)
@@ -0,0 +1,22 @@
+--- a/drivers/usb/serial/ftdi_sio_ids.h.orig 2012-01-16 15:05:19.479187251 -0800
b/drivers/usb/serial/ftdi_sio_ids.h 2012-01-16 15:09:36.059187291 -0800
+@@ -1159,4 +1159,8 @@
+ /* USB-Nano-485*/
+ #define FTDI_CTI_NANO_PID 0xF60B
+
+-
++/*
++ * Rainforest Automation
++ */
++/* ZigBee controller */
++#define FTDI_RF_R106 0x8A28
+--- a/drivers/usb/serial/ftdi_sio.c.orig 2012-01-16 15:05:27.727187253 -0800
b/drivers/usb/serial/ftdi_sio.c 2012-01-16 15:10:37.695187302 -0800
+@@ -828,6 +828,7 @@
+ .driver_info = (kernel_ulong_t)ftdi_jtag_quirk },
+ { USB_DEVICE(ST_VID, ST_STMCLT1030_PID),
+ .driver_info = (kernel_ulong_t)ftdi_stmclite_quirk },
++ { USB_DEVICE(FTDI_VID, FTDI_RF_R106) },
+ { }, /* Optional parameter entry */
+ { } /* Terminating entry */
+ };
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] FTDI additional serial IDs
Hello, On 01/17/12 17:15, Peter Naulls wrote: Add support for the Rainforest Automation Zigbee dongle. This is against 2.6.39 only, however Linux 3.2 does not have this ID either. Signed-of-by: Peter Naulls pe...@chocky.org Please make sure this makes it into next Linux 3.2 stable releases as well. Thanks. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Init Script to Foreground
Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? Pawel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Init Script to Foreground
On Tue, Jan 17, 2012 at 01:42:13PM -0500, Pawel Pastuszak wrote: Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? If your script is in the foreground and does not finish your openwrt will not boot completely. That is especialy the case when you boot openwrt for the first time after flashing it on the device. Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Init Script to Foreground
Why not add a pre-init hook? On 01/17/2012 02:02 PM, Pawel Pastuszak wrote: Ok, but i am looking for it to go into the foreground and i want to lock the console access till it finished running it then reboot. Pawel On Tue, Jan 17, 2012 at 1:52 PM, Luka Perkov open...@lukaperkov.net mailto:open...@lukaperkov.net wrote: On Tue, Jan 17, 2012 at 01:42:13PM -0500, Pawel Pastuszak wrote: Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? If your script is in the foreground and does not finish your openwrt will not boot completely. That is especialy the case when you boot openwrt for the first time after flashing it on the device. Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto: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] Init Script to Foreground
You can probably have a hook similar to the failsafe hook that does echo 1 /tmp/pawelhook and have your init script read it and do whatever you want. On 01/17/2012 02:10 PM, Pawel Pastuszak wrote: Need dhcp up first and everything mounted. So if there is an easy flag for that then i think pre-init would solve my issue. Pawel On Tue, Jan 17, 2012 at 2:05 PM, Jonathan Bither jonbit...@gmail.com mailto:jonbit...@gmail.com wrote: Why not add a pre-init hook? On 01/17/2012 02:02 PM, Pawel Pastuszak wrote: Ok, but i am looking for it to go into the foreground and i want to lock the console access till it finished running it then reboot. Pawel On Tue, Jan 17, 2012 at 1:52 PM, Luka Perkov open...@lukaperkov.net mailto:open...@lukaperkov.net mailto:open...@lukaperkov.net mailto:open...@lukaperkov.net__ wrote: On Tue, Jan 17, 2012 at 01:42:13PM -0500, Pawel Pastuszak wrote: Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? If your script is in the foreground and does not finish your openwrt will not boot completely. That is especialy the case when you boot openwrt for the first time after flashing it on the device. Luka _ openwrt-devel mailing list openwrt-devel@lists.openwrt.__org mailto:openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.__openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/__mailman/listinfo/openwrt-devel https://lists.openwrt.org/mailman/listinfo/openwrt-devel _ openwrt-devel mailing list openwrt-devel@lists.openwrt.__org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/__mailman/listinfo/openwrt-devel https://lists.openwrt.org/mailman/listinfo/openwrt-devel _ openwrt-devel mailing list openwrt-devel@lists.openwrt.__org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/__mailman/listinfo/openwrt-devel 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] Init Script to Foreground
Yes but i already have an flag from kernel arguments. So and have created rc.d init script which looks for this but what i wanted is to bring that script into the foreground. On Tue, Jan 17, 2012 at 2:15 PM, Jonathan Bither jonbit...@gmail.comwrote: You can probably have a hook similar to the failsafe hook that does echo 1 /tmp/pawelhook and have your init script read it and do whatever you want. On 01/17/2012 02:10 PM, Pawel Pastuszak wrote: Need dhcp up first and everything mounted. So if there is an easy flag for that then i think pre-init would solve my issue. Pawel On Tue, Jan 17, 2012 at 2:05 PM, Jonathan Bither jonbit...@gmail.com mailto:jonbit...@gmail.com wrote: Why not add a pre-init hook? On 01/17/2012 02:02 PM, Pawel Pastuszak wrote: Ok, but i am looking for it to go into the foreground and i want to lock the console access till it finished running it then reboot. Pawel On Tue, Jan 17, 2012 at 1:52 PM, Luka Perkov open...@lukaperkov.net mailto:open...@lukaperkov.net** mailto:open...@lukaperkov.net mailto:open...@lukaperkov.net**__ wrote: On Tue, Jan 17, 2012 at 01:42:13PM -0500, Pawel Pastuszak wrote: Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? If your script is in the foreground and does not finish your openwrt will not boot completely. That is especialy the case when you boot openwrt for the first time after flashing it on the device. Luka __**___ openwrt-devel mailing list openwrt-devel@lists.openwrt.__**org mailto:openwrt-devel@lists.**openwrt.orgopenwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.__**openwrt.org http://openwrt.org mailto:openwrt-devel@lists.**openwrt.orgopenwrt-devel@lists.openwrt.org https://lists.openwrt.org/__**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/__mailman/listinfo/openwrt-devel https://lists.openwrt.org/**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/mailman/listinfo/openwrt-devel ** __**___ openwrt-devel mailing list openwrt-devel@lists.openwrt.__**org mailto:openwrt-devel@lists.**openwrt.orgopenwrt-devel@lists.openwrt.org https://lists.openwrt.org/__**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/__mailman/listinfo/openwrt-devel https://lists.openwrt.org/**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/mailman/listinfo/openwrt-devel ** __**___ openwrt-devel mailing list openwrt-devel@lists.openwrt.__**org mailto:openwrt-devel@lists.**openwrt.orgopenwrt-devel@lists.openwrt.org https://lists.openwrt.org/__**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/__mailman/listinfo/openwrt-devel https://lists.openwrt.org/**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/mailman/listinfo/openwrt-devel ** __**_ openwrt-devel mailing list openwrt-devel@lists.openwrt.**org openwrt-devel@lists.openwrt.org https://lists.openwrt.org/**mailman/listinfo/openwrt-develhttps://lists.openwrt.org/mailman/listinfo/openwrt-devel __**_ openwrt-devel mailing list openwrt-devel@lists.openwrt.**org openwrt-devel@lists.openwrt.org https://lists.openwrt.org/**mailman/listinfo/openwrt-develhttps://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] target gdb - Symbol format `elf32-littlearm' unknown
Any ideas why the target ARM gdb doesn't work? run gdb ... This GDB was configured as arm-openwrt-linux... I'm sorry, Dave, I can't do that. Symbol format `elf32-littlearm' unknown. gdbremote works, but it doesn't support hardware breakpoints until the 7.x series and we're at 6.8. 7.2 won't build because it complains the C run-time is too old. Target gdb should support hardware breakpoints if I can get it running. -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Buying router SOC CPUs
This unfortunately a common attitude from parts vendors, especially when you are not buying in qty 10k+. You might try asking vendors for a tray of samples for testing purposes, e.g. a dozen chips. On Tue, Jan 17, 2012 at 7:16 PM, jonsm...@gmail.com jonsm...@gmail.comwrote: Are any of the router SOC CPUs easily available for purchase? We've tried to buy some buy nobody wants to talk to us. As a work around we are using a lpc3130 ($3.50) and an OEM USB wifi stick ($4.00 ralink). We have to go through FCC anyway because of the 2.4Ghz 802.15.4 radio. -- Ben West http://gowasabi.net b...@gowasabi.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Buying router SOC CPUs
On Tue, Jan 17, 2012 at 8:33 PM, Ben West b...@gowasabi.net wrote: This unfortunately a common attitude from parts vendors, especially when you are not buying in qty 10k+. We are in the 2-4K volume range which is too low for them to apparently care about. If they'd just put the chips into a distributor and give us an accurate manual we'd probably never call the chip manufacturer. What is pricing like for the SOC chips? Would it be less that our $8.00 combo of lpc3130/USB wifi? USB wifi is flexible in that we can put in 11g, 11b, 5Ghz, etc sticks. lpc3130 is a very good chip for this since it has the integrated 480Mb USB PHY. You might try asking vendors for a tray of samples for testing purposes, e.g. a dozen chips. On Tue, Jan 17, 2012 at 7:16 PM, jonsm...@gmail.com jonsm...@gmail.com wrote: Are any of the router SOC CPUs easily available for purchase? We've tried to buy some buy nobody wants to talk to us. As a work around we are using a lpc3130 ($3.50) and an OEM USB wifi stick ($4.00 ralink). We have to go through FCC anyway because of the 2.4Ghz 802.15.4 radio. -- Ben West http://gowasabi.net b...@gowasabi.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: support for kernel 3.1
On Thu, Dec 08, 2011 at 11:57:46PM +0100, Hartmut Knaack wrote: juhosg was working quite hard to get us out of sync, with decent support of nbd ;-) It took me a while, but we're finally back on the track. Minimum kernel version is probably still 3.1.1. Successfully tested with kernel 3.1.4 on a WR1043ND. Kernel version in the Makefile still needs to be adjusted manually. Any comments appreciated. Enjoy. Hi Harmut, do you have something for 3.2? I don't want to duplicate efforts :=) -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Init Script to Foreground
I'm confused. So in /etc/config/system: config system option foreground 1 doesn't work for you? -Philip On 1/17/12 11:42 AM, Pawel Pastuszak wrote: Hello everybody, I have an odd question i am trying to find an way to have my init script on power up to take over the console so the process can be interrupted. It's pretty much if an flag is set to x in kernel arguments then do y but i want y to be the foreground process. What i notice all Init script are executed in background. Any thoughts for any one? Pawel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: support for kernel 3.1
On Wed, Jan 18, 2012 at 4:42 AM, Otto Solares Cabrera so...@guug.org wrote: On Thu, Dec 08, 2011 at 11:57:46PM +0100, Hartmut Knaack wrote: juhosg was working quite hard to get us out of sync, with decent support of nbd ;-) It took me a while, but we're finally back on the track. Minimum kernel version is probably still 3.1.1. Successfully tested with kernel 3.1.4 on a WR1043ND. Kernel version in the Makefile still needs to be adjusted manually. Any comments appreciated. Enjoy. Hi Harmut, do you have something for 3.2? I don't want to duplicate efforts :=) Personally I feel that skipping 3.2 entirely and going to 3.3 is the right course, as that has byte queue limits, a fixed implementation of RED, aRED, multiple improvements to SFQ that make it scale up much better, and behave better in the general case, and a new combination of SFQ and RED that looks very promising. -- Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Dave Täht SKYPE: davetaht US Tel: 1-239-829-5608 FR Tel: 0638645374 http://www.bufferbloat.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
