On Sat, Nov 10, 2012 at 03:52:37AM +0100, Mike Belopuhov wrote:
On Tue, Nov 06, 2012 at 12:15 +0100, Stefan Sperling wrote:
It seems more appropriate to handle this problem entirely within
the USB-specific layer of the driver, rather than within dev/ic/athn.c.
If loading the firmware
Since we all seem to be playing with cwm these days, here's a patch
that renames iter to i used in for-loops. conf.c used both, while
the rest of the code used i so I chose to use i.
Index: conf.c
===
RCS file:
On Thu, 8 Nov 2012, Mark Kettenis wrote:
On Tuesday 21 August 2012, Stefan Fritsch wrote:
On x86, the xchg operation between reg and mem has an implicit lock
prefix, i.e. it is a relatively expensive atomic operation. This is
not needed here.
OKs, anyone?
What you say makes sense, although
On Sat, Nov 10, 2012 at 03:38:15PM +0100, Claudio Jeker wrote:
In some cases it helps to be able to restrict nexthops from pathes
received. E.g. at IXP where only routes originating from the neighbor
should be accepted.
This diff implements this for bgpd.
Updated diff that fixes a missing
On Sat, Nov 10, 2012 at 06:52:17PM +0100, Claudio Jeker wrote:
On Sat, Nov 10, 2012 at 03:38:15PM +0100, Claudio Jeker wrote:
In some cases it helps to be able to restrict nexthops from pathes
received. E.g. at IXP where only routes originating from the neighbor
should be accepted.
Date: Sat, 10 Nov 2012 18:10:53 +0100 (CET)
From: Stefan Fritsch s...@sfritsch.de
On Thu, 8 Nov 2012, Mark Kettenis wrote:
On Tuesday 21 August 2012, Stefan Fritsch wrote:
On x86, the xchg operation between reg and mem has an implicit lock
prefix, i.e. it is a relatively expensive
Add support for Intel 6235 WiFi:
iwn0 at pci2 dev 0 function 0 Intel Centrino Advanced-N 6235 rev 0x24: msi,
MIMO 2T2R, AGN, address c4:85:08:35:55:f7
Requires newer iwn-6030 firmware that I recently added to the
iwn-firmware package. Trying to configure Bluetooth coexistence
kills the device
