Search Linux Wireless

Re: [PATCH v2 1/5] brcmfmac: Drop all the RAW device IDs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



- stale Cypress emails

On February 5, 2023 3:50:41 AM Hector Martin <marcan@xxxxxxxxx> wrote:

On 03/02/2023 02.19, Arend Van Spriel wrote:
On February 2, 2023 6:25:28 AM "'Hector Martin' via BRCM80211-DEV-LIST,PDL"
<brcm80211-dev-list.pdl@xxxxxxxxxxxx> wrote:

On 31/01/2023 23.17, Jonas Gorski wrote:
On Tue, 31 Jan 2023 at 12:36, Hector Martin <marcan@xxxxxxxxx> wrote:

These device IDs are only supposed to be visible internally, in devices
without a proper OTP. They should never be seen in devices in the wild,
so drop them to avoid confusion.

I think these can still show up in embedded platforms where the
OTP/SPROM is provided on-flash.

E.g. https://forum.archive.openwrt.org/viewtopic.php?id=55367&p=4
shows this bootlog on an BCM4709A0 router with two BCM43602 wifis:

[    3.237132] pci 0000:01:00.0: [14e4:aa52] type 00 class 0x028000
[    3.237174] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
[    3.237199] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
[    3.237302] pci 0000:01:00.0: supports D1 D2
...
[    3.782384] pci 0001:03:00.0: [14e4:aa52] type 00 class 0x028000
[    3.782440] pci 0001:03:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
[    3.782474] pci 0001:03:00.0: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
[    3.782649] pci 0001:03:00.0: supports D1 D2

0xaa52 == 43602 (BRCM_PCIE_43602_RAW_DEVICE_ID)

Rafał can probably provide more info there.

Regards
Jonas

Arend, any comments on these platforms?

Huh? I already replied to that couple of days ago or did I only imagine
doing that.

I don't see any replies from you on the lists (or my inbox) to Jonas' email.

Accidentally sent that reply to internal mailing list. So quoting myself here:

"""
Shaking the tree helps ;-) What is meant by "OTP/SPROM is provided on-flash"? I assume you mean that it is on the host side and the wifi PCIe device can not access it when it gets powered up. Maybe for this scenario we should have a devicetree compatible to configure the device id, but that does not help any current users of these platforms. Thanks for providing this info.
"""

Regards,
Arend



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux