[PATCH V4] brcmfmac: print errors if creating interface fails

This is helpful for debugging. Without this all I was getting from "iw" command on failed creating of P2P interface was: > command failed: Too many open files in system (-23) Signed-off-by: Rafał Miłecki --- V2: s/in/if/ in commit message V3: Add one more error message as

Re: [RFC] brcmfmac: Add tracepoints for bcmdhd-dissector tool

On 26 May 2016 at 12:59, Mikael Kanstrup wrote: > Add hexdump tracepoints to be used to dissect firmware > protocol data with bcmdhd-dissector: > https://github.com/kanstrup/bcmdhd-dissector I think it'd be worth describing it a bit more. What kind of tool is it, is

Re: [PATCH v1 1/1] rtl8xxxu: tuse %*ph to dump buffers

Andy Shevchenko writes: > On Thu, 2016-05-26 at 09:02 -0700, Joe Perches wrote: >> On Thu, 2016-05-26 at 17:52 +0300, Andy Shevchenko wrote: >> > Use %*ph specifier to dump small buffers in hex format instead of >> > doing this >> > byte-by-byte. >> [] >> > diff

Re: [PATCH 0/2] ath10k: Add support for QCA9887

Sven Eckelmann writes: > the QCA9887 chip is similar to the QCA988x chips. But it requires a special > firmware and uses a different calibration data source. Unfortunately, no > working firmware currently exists. But it is possible to create a semi working > one by

Re: [PATCH v1 1/1] rtl8xxxu: tuse %*ph to dump buffers

On Thu, 2016-05-26 at 09:02 -0700, Joe Perches wrote: > On Thu, 2016-05-26 at 17:52 +0300, Andy Shevchenko wrote: > > Use %*ph specifier to dump small buffers in hex format instead of > > doing this > > byte-by-byte. > [] > > diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192c.c > >

Re: [PATCH v1 1/1] rtl8xxxu: tuse %*ph to dump buffers

On Thu, 2016-05-26 at 17:52 +0300, Andy Shevchenko wrote: > Use %*ph specifier to dump small buffers in hex format instead of doing this > byte-by-byte. [] > diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192c.c > b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192c.c [] > @@

[PATCH v1 1/1] rtl8xxxu: tuse %*ph to dump buffers

Use %*ph specifier to dump small buffers in hex format instead of doing this byte-by-byte. Signed-off-by: Andy Shevchenko --- drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192c.c | 9 ++--- drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_8192e.c | 9

[RFC] ath9k: Measure per-station airtime usage

This is my attempt to add per-station airtime usage accounting to ath9k. For now I just export it to a new debugfs entry, but my plan is to use it to make (station) scheduling decisions. However, before attempting that I would like some feedback from someone more familiar with the ath9k than me as

Re: BCM4331 reset leads to wl lockup

On Thu, 26 May 2016 14:12:10 +0200 Lukas Wunner wrote: > + mmio = early_ioremap(addr, BCM4331_MMIO_SIZE); > + if (!mmio) { > + pr_err("Cannot iomap Apple AirPort card\n"); > + return; > + } > + pr_info("Resetting Apple AirPort card\n"); >

BCM4331 reset leads to wl lockup

Dear Broadcom support, on Macs equipped with a BCM4331, a reset of the wireless core is needed early in the boot process to prevent spurious IRQs and memory corruption. This is achieved by the below patch. Unfortunately the patch seems to cause a lockup with wl depending on the amount of traffic

[RFC] brcmfmac: Add tracepoints for bcmdhd-dissector tool

Add hexdump tracepoints to be used to dissect firmware protocol data with bcmdhd-dissector: https://github.com/kanstrup/bcmdhd-dissector Signed-off-by: Mikael Kanstrup --- I've been using a simple Wireshark lua plugin to sniff the host to chip firmware communication

[PATCH] ath10k: Fix error while writing 'simulate_fw_crash' debugfs

From: Mohammed Shafi Shajakhan Fix invalid argument error while writing 'simulate_fw_crash', though the funcionality is working fine we get an error 'invalid argument' because 'count' value is not returned properly (no reason to reduce the count value for removing the

Re: [PATCH V3] brcmfmac: print error if p2p_ifadd firmware command fails

On 26-5-2016 0:44, Rafał Miłecki wrote: > This is helpful for debugging, without this all I was getting from "iw" > command on device with BCM43602 was: >> command failed: Too many open files in system (-23) > > Signed-off-by: Rafał Miłecki > --- > V2: s/in/if/ in commit

[PATCH] wext: Fix 32 bit iwpriv compatibility issue with 64 bit Kernel

iwpriv app uses iw_point structure to send data to Kernel. The iw_point structure holds a pointer. For compatibility Kernel converts the pointer as required for WEXT IOCTLs (SIOCIWFIRST to SIOCIWLAST). Some drivers may use iw_handler_def.private_args to populate iwpriv commands instead of