Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W

Hi Arend, Am 26.07.2017 um 10:50 schrieb Arend van Spriel: > On 7/26/2017 8:19 AM, Stefan Wahren wrote: >> Hi, >> >> >> what are the plans to fix this regression? > > I am a bit in doubt about this one. We can avoid the firmware config > above for bcm4343x dev

Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W

Hi, > Stefan Wahren <stefan.wah...@i2se.com> hat am 28. Juni 2017 um 21:33 > geschrieben: > > > Hi, > > i'm currently working on Raspberry Pi Zero W for Mainline. Here is my first > patch series [1]. > > Unfortunately i didn't get brcmfmac (connected

Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W

Hi, > Franky Lin <franky@broadcom.com> hat am 17. Juli 2017 um 21:50 > geschrieben: > > > On Mon, Jul 17, 2017 at 6:10 AM, Stefan Wahren <stefan.wah...@i2se.com> wrote: > > Hi, > > > >> Stefan Wahren <stefan.wah...@i2se.c

Re: brcmfmac: Possible memleak brcmf_sdiod_sgtable_alloc

> Arend van Spriel <arend.vanspr...@broadcom.com> hat am 22. Juli 2017 um 21:40 > geschrieben: > > > On 22-07-17 15:18, Stefan Wahren wrote: > > Hi, > > > > with enabled memleak detector on 4.13-rc1 (Raspberry Pi Zero W) i get the > > following

Re: brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W

Hi, > Stefan Wahren <stefan.wah...@i2se.com> hat am 17. Juli 2017 um 22:31 > geschrieben: > > > Hi, > > > Franky Lin <franky@broadcom.com> hat am 17. Juli 2017 um 21:50 > > geschrieben: > > > > > > On Mon, Jul 17, 2017 a

Re: brcmfmac: Possible memleak brcmf_sdiod_sgtable_alloc

Hi Arend, > Stefan Wahren <stefan.wah...@i2se.com> hat am 23. Juli 2017 um 02:24 > geschrieben: > > > > > Arend van Spriel <arend.vanspr...@broadcom.com> hat am 22. Juli 2017 um > > 21:40 geschrieben: > > > > > > On 22-07-17 15:18,

brcmfmac: Possible memleak brcmf_sdiod_sgtable_alloc

Hi, with enabled memleak detector on 4.13-rc1 (Raspberry Pi Zero W) i get the following: root@raspberrypi:/sys/kernel/debug# cat kmemleak unreferenced object 0xd824e400 (size 1024): comm "kworker/0:0", pid 3, jiffies 4294939822 (age 873.420s) hex dump (first 32 bytes): 00 00 00 00 00 00

brcmfmac: BCM43431 won't get probed on Raspberry Pi Zero W

Hi, i'm currently working on Raspberry Pi Zero W for Mainline. Here is my first patch series [1]. Unfortunately i didn't get brcmfmac (connected via SDIO) probed with this patch series against 4.12.0-rc5-next-20170616+ [8.389167] brcmfmac: F1 signature read @0x1800=0x1541a9a6 [

Re: [PATCH v2] brcmfmac: add CLM download support

Hi, > Wright Feng hat am 17. August 2017 um 12:22 > geschrieben: > > > From: Chung-Hsien Hsu > > The firmware for brcmfmac devices includes information regarding > regulatory constraints. For certain devices this information is kept >

Re: CVE-2017-9417 and brcmfmac

Hi Ben, > Ben Hutchings hat am 27. August 2017 um 17:14 > geschrieben: > > > The CVE-2017-9417 aka "Broadpwn" vulnerability is said to affect the > firmware for various Broadcom BCM43xx wifi chips, some of which are > supported by the in-tree brcmfmac driver and firmware

Re: brcmfmac: Unable to handle kernel paging request at virtual address 726f6674616cd8

Hi Arend, > Arend van Spriel <arend.vanspr...@broadcom.com> hat am 22. November 2017 um > 19:23 geschrieben: > > > On 22-11-17 17:20, Stefan Wahren wrote: > > Hi, > > > >> Stefan Wahren <stefan.wah...@i2se.com> hat am 12. November 2017 um 17

Re: brcmfmac: Unable to handle kernel paging request at virtual address 726f6674616cd8

Hi Arend, > Arend van Spriel hat am 24. November 2017 um > 13:52 geschrieben: > > > ... > > I just realized the remove of sdio func #1 removes everything so we must > first remove sdio func #2. Can you try the patch below. > > Regards, > Arend > --- > diff

Re: brcmfmac: Unable to handle kernel paging request at virtual address 726f6674616cd8

Hi, > Stefan Wahren <stefan.wah...@i2se.com> hat am 12. November 2017 um 17:50 > geschrieben: > > > Hi, > i discovered a random oops during probe of brcmfmac on Raspberry Pi 3 in > yesterdays kernelci run for net-next [1]. I need to point out there is no DT

brcmfmac: Unable to handle kernel paging request at virtual address 726f6674616cd8

Hi, i discovered a random oops during probe of brcmfmac on Raspberry Pi 3 in yesterdays kernelci run for net-next [1]. I need to point out there is no DT entry for the wifi chip on Raspberry Pi 3 in the lack of a driver for the necessary GPIO expander. So the "HT Avail timeout" is expected. I

Re: [PATCH] brcmfmac: add support for external 32khz clock

Hi Simon, > Simon Shields hat am 4. November 2017 um 14:24 > geschrieben: > > > Some boards use an external 32khz clock for low-power > mode timing. Make sure the clock is powered on while the chipset > is active. > > Signed-off-by: Simon Shields >

Re: [PATCH] brcmfmac: add support for external 32khz clock

Hi, > Kalle Valo <kv...@codeaurora.org> hat am 7. November 2017 um 03:18 > geschrieben: > > > Stefan Wahren <stefan.wah...@i2se.com> writes: > > >> Simon Shields <si...@lineageos.org> hat am 4. November 2017 um 14:24 > >> geschrieben: &g

Re: brcmfmac: Updating Broadcom/Cypress Wifi/BT firmware

Hi Arend, Am 14.05.2018 um 10:15 schrieb Arend van Spriel: On 5/2/2018 8:05 PM, Stefan Wahren wrote: Hi, i wanted to know, if there are any plans to update the Broadcom/Cypress firmware under: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git As BCM2835

brcmfmac: Updating Broadcom/Cypress Wifi/BT firmware

Hi, i wanted to know, if there are any plans to update the Broadcom/Cypress firmware under: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git As BCM2835 maintainer i'm interested in the following files: brcm/brcmfmac43430-sdio.bin brcm/brcmfmac43455-sdio.bin

Re: [PATCH] wireless: brcmfmac: cfg80211: Fix check for ISO3166 code

Am 15.03.2018 um 07:27 schrieb Rafał Miłecki: On 14 March 2018 at 20:02, Stefan Wahren <stefan.wah...@i2se.com> wrote: The commit "regulatory: add NUL to request alpha2" increases the length of alpha2 to 3. This causes a regression on brcmfmac, because brcmf_cfg80211_reg_notifie

Re: [Regression] brcmfmac: brcmf_cfg80211_reg_notifier: not an ISO3166 code

Hi, > Stefan Wahren <stefan.wah...@i2se.com> hat am 4. März 2018 um 18:26 > geschrieben: > > > Hi, > > the commit "regulatory: add NUL to request alpha2" in linux-next-20180302 > causes a regression with brcmfmac (Platform: Raspberry Pi 3 B). Duri

[PATCH] wireless: brcmfmac: cfg80211: Fix check for ISO3166 code

The commit "regulatory: add NUL to request alpha2" increases the length of alpha2 to 3. This causes a regression on brcmfmac, because brcmf_cfg80211_reg_notifier() expect valid ISO3166 codes in the complete array. So fix this accordingly. Signed-off-by: Stefan Wahren <stefan.wa

[Regression] brcmfmac: brcmf_cfg80211_reg_notifier: not an ISO3166 code

Hi, the commit "regulatory: add NUL to request alpha2" in linux-next-20180302 causes a regression with brcmfmac (Platform: Raspberry Pi 3 B). During driver probe i will get this error: brcmfmac: brcmf_cfg80211_reg_notifier: not an ISO3166 code (0x44 0x45) But 0x44 0x45 ( = DE ) is a valid

Re: brcmfmac: regression using AP mode

Hi, Am 26.11.18 um 11:11 schrieb Arend van Spriel: > On 11/25/2018 2:14 PM, Stefan Wahren wrote: >> Hi Rafał, >> >>> Rafał Miłecki hat am 24. November 2018 um 22:23 >>> geschrieben: >>> >>> >>> Possibly you can just update hostapd to

brcmfmac: regression using AP mode

Hi guys, today i wanted to setup an access point on my Raspberry Pi 3 A+ (BCM43455). Unfortunately the hostapd 2.4 shipped with Raspbian failed with recent Linux kernel: rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0 rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0 nl80211: Using

Re: brcmfmac: regression using AP mode

Hi Rafał, > Rafał Miłecki hat am 24. November 2018 um 22:23 > geschrieben: > > > Possibly you can just update hostapd to anything more recent? I'm afraid > the version you're using may suffer from a lot of security issues anyway thanks for your quick reply. I updated hostapd to 2.6.18 from

Re: brcmfmac: regression using AP mode

Hi, > Stefan Wahren hat am 26. November 2018 um 19:14 > geschrieben: > > > Hi Arend, > > > Arend van Spriel hat am 26. November 2018 um > > 11:11 geschrieben: > > > > So no AP listed here. I suspect Rafał was focusing on "device_ap_sme=1 >

Re: brcmfmac: regression using AP mode

Hi Arend, > Arend van Spriel hat am 26. November 2018 um > 11:11 geschrieben: > > So no AP listed here. I suspect Rafał was focusing on "device_ap_sme=1 > use_monitor=1" scenario. You can try adding AP entry with similar rx > bits as P2P_GO above. thanks this make all driver errors like