* Re: [PATCH] brcm: provide new firmwares for BCM4366 chipset [not found] <1541622996-16181-1-git-send-email-arend.vanspriel@broadcom.com> @ 2018-12-14 13:02 ` Josh Boyer 2018-12-15 11:02 ` Arend Van Spriel 0 siblings, 1 reply; 5+ messages in thread From: Josh Boyer @ 2018-12-14 13:02 UTC (permalink / raw) To: Arend van Spriel; +Cc: Linux Firmware, Linux Wireless On Wed, Nov 7, 2018 at 3:45 PM Arend van Spriel <arend.vanspriel@broadcom.com> wrote: > > These firmwares are for the BCM4366 3x3 802.11 ac chipsets, which also comprise of BCM4366E or BCM43664 devices. Signed-off-by: Arend van Spriel This didn't add brcm/brcmfmac4366c-pcie.bin to WHENCE. I'm assuming it's under the same license as the rest of the brcmfmac files? If so, I can just amend the patch. josh ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] brcm: provide new firmwares for BCM4366 chipset 2018-12-14 13:02 ` [PATCH] brcm: provide new firmwares for BCM4366 chipset Josh Boyer @ 2018-12-15 11:02 ` Arend Van Spriel 2018-12-16 1:52 ` Josh Boyer 2018-12-17 10:34 ` Rafał Miłecki 0 siblings, 2 replies; 5+ messages in thread From: Arend Van Spriel @ 2018-12-15 11:02 UTC (permalink / raw) To: Josh Boyer; +Cc: Linux Firmware, Linux Wireless On 12/14/2018 2:02 PM, Josh Boyer wrote: > On Wed, Nov 7, 2018 at 3:45 PM Arend van Spriel > <arend.vanspriel@broadcom.com> wrote: >> >> These firmwares are for the BCM4366 3x3 802.11 ac chipsets, which also comprise of BCM4366E or BCM43664 devices. Signed-off-by: Arend van Spriel > > This didn't add brcm/brcmfmac4366c-pcie.bin to WHENCE. I'm assuming > it's under the same license as the rest of the brcmfmac files? If so, > I can just amend the patch. Hi Josh, I was not sure this patch ever made it through. It did not appear on linux-wireless list probably due to exceeding a size limit. So I resend it as two patches on December 10th. However, I indeed forgot to update the WHENCE file in that series as well. Indeed there is no license change. Regards, Arend ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] brcm: provide new firmwares for BCM4366 chipset 2018-12-15 11:02 ` Arend Van Spriel @ 2018-12-16 1:52 ` Josh Boyer 2018-12-17 10:34 ` Rafał Miłecki 1 sibling, 0 replies; 5+ messages in thread From: Josh Boyer @ 2018-12-16 1:52 UTC (permalink / raw) To: Arend van Spriel; +Cc: Linux Firmware, Linux Wireless On Sat, Dec 15, 2018 at 6:02 AM Arend Van Spriel <arend.vanspriel@broadcom.com> wrote: > > > > On 12/14/2018 2:02 PM, Josh Boyer wrote: > > On Wed, Nov 7, 2018 at 3:45 PM Arend van Spriel > > <arend.vanspriel@broadcom.com> wrote: > >> > >> These firmwares are for the BCM4366 3x3 802.11 ac chipsets, which also comprise of BCM4366E or BCM43664 devices. Signed-off-by: Arend van Spriel > > > > This didn't add brcm/brcmfmac4366c-pcie.bin to WHENCE. I'm assuming > > it's under the same license as the rest of the brcmfmac files? If so, > > I can just amend the patch. > > Hi Josh, > > I was not sure this patch ever made it through. It did not appear on > linux-wireless list probably due to exceeding a size limit. So I resend > it as two patches on December 10th. However, I indeed forgot to update > the WHENCE file in that series as well. Indeed there is no license change. OK. Amended and pushed out. josh ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] brcm: provide new firmwares for BCM4366 chipset 2018-12-15 11:02 ` Arend Van Spriel 2018-12-16 1:52 ` Josh Boyer @ 2018-12-17 10:34 ` Rafał Miłecki 2018-12-17 12:37 ` Arend Van Spriel 1 sibling, 1 reply; 5+ messages in thread From: Rafał Miłecki @ 2018-12-17 10:34 UTC (permalink / raw) To: Arend Van Spriel Cc: Josh Boyer, Linux Firmware, Linux Wireless, Hauke Mehrtens On Sat, 15 Dec 2018 at 12:03, Arend Van Spriel <arend.vanspriel@broadcom.com> wrote: > On 12/14/2018 2:02 PM, Josh Boyer wrote: > > On Wed, Nov 7, 2018 at 3:45 PM Arend van Spriel > > <arend.vanspriel@broadcom.com> wrote: > >> > >> These firmwares are for the BCM4366 3x3 802.11 ac chipsets, which also comprise of BCM4366E or BCM43664 devices. Signed-off-by: Arend van Spriel > > > > This didn't add brcm/brcmfmac4366c-pcie.bin to WHENCE. I'm assuming > > it's under the same license as the rest of the brcmfmac files? If so, > > I can just amend the patch. > > Hi Josh, > > I was not sure this patch ever made it through. It did not appear on > linux-wireless list probably due to exceeding a size limit. So I resend > it as two patches on December 10th. However, I indeed forgot to update > the WHENCE file in that series as well. Indeed there is no license change. Unfortunately I have only 1 device with 4366B1 (D-Link DIR-885L) and it seems to have dummy NVRAM restored from the bootloader's copy: 1:ccode=ALL 0:regrev=0 0:ccode=ALL 1:regrev=0 1) Old fw 10.10.69.3309 (r610991) FWID 01-c47a91a4 2 GHz: very weak signal (about -79 dBm) 5 GHz: good signal & works stable (this also matches vendor firmware behavior) 2) New fw 10.28.2 (r769115) FWID 01-801fb449 2 GHz: very weak signal (about -79 dBm) 5 GHz: good signal but huge packet loss So the new firmware introduces 5 GHz regression for me, but I guess I should not complain since my device seems to come with a missing NVRAM regulatory info. Is there any chance you know a correct ccode + regrev for D-Link DIR-885L for any region? -- Rafał ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] brcm: provide new firmwares for BCM4366 chipset 2018-12-17 10:34 ` Rafał Miłecki @ 2018-12-17 12:37 ` Arend Van Spriel 0 siblings, 0 replies; 5+ messages in thread From: Arend Van Spriel @ 2018-12-17 12:37 UTC (permalink / raw) To: Rafał Miłecki Cc: Josh Boyer, Linux Firmware, Linux Wireless, Hauke Mehrtens On 12/17/2018 11:34 AM, Rafał Miłecki wrote: > On Sat, 15 Dec 2018 at 12:03, Arend Van Spriel > <arend.vanspriel@broadcom.com> wrote: >> On 12/14/2018 2:02 PM, Josh Boyer wrote: >>> On Wed, Nov 7, 2018 at 3:45 PM Arend van Spriel >>> <arend.vanspriel@broadcom.com> wrote: >>>> >>>> These firmwares are for the BCM4366 3x3 802.11 ac chipsets, which also comprise of BCM4366E or BCM43664 devices. Signed-off-by: Arend van Spriel >>> >>> This didn't add brcm/brcmfmac4366c-pcie.bin to WHENCE. I'm assuming >>> it's under the same license as the rest of the brcmfmac files? If so, >>> I can just amend the patch. >> >> Hi Josh, >> >> I was not sure this patch ever made it through. It did not appear on >> linux-wireless list probably due to exceeding a size limit. So I resend >> it as two patches on December 10th. However, I indeed forgot to update >> the WHENCE file in that series as well. Indeed there is no license change. > > Unfortunately I have only 1 device with 4366B1 (D-Link DIR-885L) and > it seems to have dummy NVRAM restored from the bootloader's copy: > 1:ccode=ALL > 0:regrev=0 > 0:ccode=ALL > 1:regrev=0 > > 1) Old fw 10.10.69.3309 (r610991) FWID 01-c47a91a4 > 2 GHz: very weak signal (about -79 dBm) > 5 GHz: good signal & works stable > (this also matches vendor firmware behavior) > > 2) New fw 10.28.2 (r769115) FWID 01-801fb449 > 2 GHz: very weak signal (about -79 dBm) > 5 GHz: good signal but huge packet loss > > So the new firmware introduces 5 GHz regression for me, but I guess I > should not complain since my device seems to come with a missing NVRAM > regulatory info. > > Is there any chance you know a correct ccode + regrev for D-Link > DIR-885L for any region? Hi Rafał, That is bad news. Is the packet loss in receive or transmit direction? How do you obtain the info? Regards, Arend ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-12-17 12:37 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <1541622996-16181-1-git-send-email-arend.vanspriel@broadcom.com> 2018-12-14 13:02 ` [PATCH] brcm: provide new firmwares for BCM4366 chipset Josh Boyer 2018-12-15 11:02 ` Arend Van Spriel 2018-12-16 1:52 ` Josh Boyer 2018-12-17 10:34 ` Rafał Miłecki 2018-12-17 12:37 ` Arend Van Spriel
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).