On 08.11.2014 08:51, Pomidora Belisima wrote:
On Fri, Nov 7, 2014 at 10:30 PM, Bob Marcan bob.mar...@lnx.no-ip.org
wrote:
Obviously we should avoid this chip.
BR, Bob
Begin forwarded message:
Date: Fri, 07 Nov 2014 11:21:40 -0600
From: Larry Finger larry.fin...@lwfinger.net
To: Bob
phy_read and phy_write are not set for every phy any more sine this:
commit d342b95dd735014a590f9051b1ba227eb54ca8f6
Author: Rafał Miłecki zaj...@gmail.com
Date: Thu Jul 31 21:59:43 2014 +0200
b43: don't duplicate common PHY read/write ops
b43_phy_copy() accesses phy_read and phy_write
On 11/07/14 20:37, Luca Coelho wrote:
On November 7, 2014 9:15:21 PM EET, Johannes Bergjohan...@sipsolutions.net
wrote:
On Fri, 2014-11-07 at 14:37 +0200, Luca Coelho wrote:
+#if 0
+ struct ieee80211_vendor_radiotap *rtap;
+
+ rtap = (void *)skb_push(skb, sizeof(*rtap) + 8 + 4);
On 11/07/14 20:05, Greg Kroah-Hartman wrote:
On Tue, Oct 28, 2014 at 01:19:11PM +0100, Arend van Spriel wrote:
The debugfs files that are defined in debug.c which are read-only
and using a simple_open as .open file operation have been modified
to use the single_open seq_file API. This
On 11/08/14 14:44, Arend van Spriel wrote:
On 11/07/14 20:05, Greg Kroah-Hartman wrote:
On Tue, Oct 28, 2014 at 01:19:11PM +0100, Arend van Spriel wrote:
The debugfs files that are defined in debug.c which are read-only
and using a simple_open as .open file operation have been modified
to use
On Sat, Nov 08, 2014 at 03:07:50PM +0100, Arend van Spriel wrote:
On 11/08/14 14:44, Arend van Spriel wrote:
On 11/07/14 20:05, Greg Kroah-Hartman wrote:
On Tue, Oct 28, 2014 at 01:19:11PM +0100, Arend van Spriel wrote:
The debugfs files that are defined in debug.c which are read-only
and
On 8 November 2014 13:59, Hauke Mehrtens ha...@hauke-m.de wrote:
phy_read and phy_write are not set for every phy any more sine this:
commit d342b95dd735014a590f9051b1ba227eb54ca8f6
Looks OK, thanks for your patch!
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
Hi,
right. The default NIC EEPROM setup doesn't include those channels
because they haven't tested them out.
If you have an 802.11p regulatory compliant NIC then it should have
the 11p frequencies show up in the EEPROM channel range.
So you should definitely first check that the NIC EEPROM has
Dear all,
I’m trying to get the 7260 to act as an AP on the 5G band. Unfortunately it
seems to be impossible due to the „no IR“ reg domain restriction done by the
Intel firmware internally (this is what I’ve googled so far..).
Could someone explain to me the technical background of this. As
On Fri, Nov 7, 2014 at 4:58 PM, Uwe Brauer o...@mat.ucm.es wrote:
Hello
I am running Kubuntu 10.04 with either the 2.6.32 or the 3.0.0 kernels
on both laptops and wireless works fine. Firmware is installed.
I just compiled a vanilla 3.7.0 kernel and booted it and wireless does
not work:
Hi,
I just got an ECS LIVA and I haven't been able to get the wireless
working. First I got the error that the brcmfmac43241b4-sdio.txt file
was missing. I got the file from the ECS's beta drivers [1], but it's
still not working.
brcmfmac: brcmf_sdio_drivestrengthinit: No SDIO Drive strength
On Sat, Nov 8, 2014 at 7:42 PM, Emmanuel Grumbach egrumb...@gmail.com wrote:
On Sat, Nov 8, 2014 at 6:33 PM, ef...@me.com wrote:
Dear all,
I’m trying to get the 7260 to act as an AP on the 5G band. Unfortunately it
seems to be impossible due to the „no IR“ reg domain restriction done by the
12 matches
Mail list logo
