Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
This patch replaces a integer argument of SendConfigPkt function with
void type pointer and fix code that the function is called.
Because tstrWILC_WFIDrv structure is defined after SendConfigPkt function
is
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
Last argument of wilc_wlan_cfg_set function is actually structure's address.
This should be changed to be compatible with 64bit machine.
Because wilc_wlan_cfg_set function is mapped by function pointer later,
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
A argument of wilc_wlan_cfg_commit() is address of structure.
But because the size is restricted to 32bit, it is not correct
for 64bit machine.
So, this changes the interger value to obvious structure pointer.
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
Last argument of wilc_wlan_cfg_get function is actually structure's address.
This should be changed to be compatible with 64bit machine.
Because wilc_wlan_cfg_get function is mapped by function pointer later,
i2c_driver does not need to set an owner because i2c_register_driver()
will set it.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
---
The coccinelle script which generated the patch was sent here:
http://www.spinics.net/lists/kernel/msg2029903.html
---
drivers/nfc/nxp-nci/i2c.c |
Vasanthakumar Thiagarajan vthia...@qti.qualcomm.com writes:
It is observed that during cold reset pcie access right
after a write operation to SOC_GLOBAL_RESET_ADDRESS causes
Data Bus Error and system hard lockup. The reason
for bus error is that pcie needs some time to get
back to stable
It is observed that during cold reset pcie access right
after a write operation to SOC_GLOBAL_RESET_ADDRESS causes
Data Bus Error and system hard lockup. The reason
for bus error is that pcie needs some time to get
back to stable state for any transaction during cold reset. Add
delay of 20 msecs
On 07/10/2015 06:49 AM, Vineet Gupta wrote:
On Thursday 09 July 2015 11:55 PM, Arend van Spriel wrote:
On 07/09/2015 10:13 AM, Vineet Gupta wrote:
There's already a generic implementation so use that instead.
There is or there was? If there is now I am fine with this patch, but if
it already
On 07/09/2015 09:12 PM, Rafał Miłecki wrote:
On 9 July 2015 at 20:48, Arend van Spriel ar...@broadcom.com wrote:
On 07/09/2015 08:01 PM, Rafał Miłecki wrote:
After fixing user space - brcmfmac communication for using valid MACs:
[PATCH] brcmfmac: set wiphy's addresses to provide valid MACs
i
On 2015년 07월 10일 15:20, Julian Calaby wrote:
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
A argument of wilc_wlan_cfg_commit() is address of structure.
But because the size is restricted to 32bit, it is not correct
for 64bit machine.
So, this changes the
On 2015년 07월 10일 15:25, Julian Calaby wrote:
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
Last argument of wilc_wlan_cfg_get function is actually structure's address.
This should be changed to be compatible with 64bit machine.
Because wilc_wlan_cfg_get
Hi Johnny,
On Fri, Jul 10, 2015 at 5:58 PM, Johnny Kim johnny@atmel.com wrote:
On 2015년 07월 10일 15:20, Julian Calaby wrote:
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
A argument of wilc_wlan_cfg_commit() is address of structure.
But because the
Hi Johnny,
On Fri, Jul 10, 2015 at 6:11 PM, Johnny Kim johnny@atmel.com wrote:
On 2015년 07월 10일 15:25, Julian Calaby wrote:
Hi Johnny,
On Fri, Jul 10, 2015 at 3:55 PM, Johnny Kim johnny@atmel.com wrote:
Last argument of wilc_wlan_cfg_get function is actually structure's
address.
Hi,
Am 08.07.2015 um 17:28 schrieb Rolf Anderegg:
I am having trouble with the following setup using ath9k_htc (AR9271): I
would like to setup two virtual interfaces on a TP-Link Wireless USB
adapter (TL-WN722N).
ath0: AP (access point/master mode) with hostapd [1], on bridge br0
ath1: STA
On 07/09/2015 10:20 PM, Michal Kazior wrote:
On 10 July 2015 at 02:03, Ben Greear gree...@candelatech.com wrote:
Suppose one is doing heavy download (AP - peer traffic), and there are lots of
frames in the
NIC's tx buffers (ath10k firmware, in this case).
Then, peer sends a power-save pkt
From: Franky Lin fran...@broadcom.com
brcmf_flowring_block blocks the last active flowring under the same
interface instead of the one provided by caller. This could lead to a
dead lock of netif stop if there are more than one flowring under the
interface and the traffic is high enough so
In rx path the firmware provide an interface index which is used to
map to a struct brcmf_if instance. However, this involves some trick
that is done in two places. This is changed by having driver core
providing brcmf_get_ifp() function.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Use cfg80211_check_combinations() so we can bail out early when an
interface add or change results in an invalid combination.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
From: Hante Meuleman meule...@broadcom.com
Host platforms such as routers supported by OpenWRT can
support NVRAM reading directly from internal NVRAM store.
With this patch the nvram load routines will fall back to
this method when there is no nvram file and support is
available in the kernel.
The interface combination provided by brcmfmac did not truly reflect
the combinations supported by driver and/or firmware.
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Reviewed-by:
From: Franky Lin fran...@broadcom.com
Expose ring buffer read/write pointers and other useful statistics
through debugfs.
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by:
From: Hante Meuleman meule...@broadcom.com
Next generation devices will have firmware which will have more
than 256 flowrings. This patch increases the maximum number of
supported flowrings to 512.
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Franky (Zhenhui) Lin
This series comprises of following changes:
- support NVRAM loading for bcm47xx platform.
- revise announced interface combinations and validate against it.
- new debugfs entry for msgbuf protocol layer used with PCIe devices.
- couple of PCIe fixes.
- rework dealing with interface instances.
The
23 matches
Mail list logo
