Message ID | 20230214080034.3828-1-marcan@marcan.st |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp2830206wrn; Tue, 14 Feb 2023 00:04:08 -0800 (PST) X-Google-Smtp-Source: AK7set8zKDLs/Pt2sd8E7vk40n3ArB0IakAj0fALKG2que6R2ih7Tw1STHknOSlL78/b68Rt8OpJ X-Received: by 2002:a17:90b:4a88:b0:234:409:9752 with SMTP id lp8-20020a17090b4a8800b0023404099752mr1408674pjb.25.1676361847961; Tue, 14 Feb 2023 00:04:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1676361847; cv=none; d=google.com; s=arc-20160816; b=Pq8RWzQ7yj/pMVdtU99wtbJTGDi37wJOv/VKrH/HjB81B/1DQePa8vDvpDdAEoc/qm s+fQtGjAkrXa7pmsXDQPrGMRNfSHZfHEBN+9LhBpgpGCoakhKFdVNtLxofJFRmabIVX5 8Y7HHfNq7pmjTdwnSP/rcxKM4Vei42kI3ShfJnrvCv2VApOpcRfrGG8iKXZgNULJQT5S UKzPIlkLVaUqIHiYoSpmKAz4fAswoeSteeiBW7hjZtORLa7qFN+cMRF/P8S6boRJPMNE nLte02fj0Nwah+CrM9KFZThvVyJuPbCyCjdcZ6/VjOONv1Y6UUGH1bcgfBxrAmowi4hn WmZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=zFHx2WF36YPc4claIb5IXNrIA3yYk5BbWI99JLlbn4E=; b=bj1cSwm5sOX/6UA5B39ayjOOfSpIeXWSpimWfyWSwoW/ZlEN+vhNFn4RP6txl05cXf 0N6qv3oif+In+EkmgogbP+Bad2FEQ2zivMlmDuWyON3HunGqVxjNGbBujZsd3B6AVUHp aI7/wYnwOWl755vA0RbS4rwHzu0cFVSx+vKelZRZLiyb7H1PCGhYNsK9MjeuGoCbf5/D FYA9OtMh/VTr2fafvt9LzKfHR0rp/Nkaqa44FVRIoDgoG0h+FhPCm9BywASfn/xoqlYP dD9xUT5FcEDIR70lgPzt08L5VFnFqZxFGrVC4ZcLf9yjy7SmtP8ulSKAiZBaFXnoN8aM cuLw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b=AWRsTTF3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f19-20020a17090aa79300b00230d70ab759si17506237pjq.93.2023.02.14.00.03.42; Tue, 14 Feb 2023 00:04:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@marcan.st header.s=default header.b=AWRsTTF3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=marcan.st Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231579AbjBNICR (ORCPT <rfc822;tebrre53rla2o@gmail.com> + 99 others); Tue, 14 Feb 2023 03:02:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34408 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229936AbjBNIBl (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 14 Feb 2023 03:01:41 -0500 Received: from mail.marcansoft.com (marcansoft.com [212.63.210.85]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6B9C73C33; Tue, 14 Feb 2023 00:01:39 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: sendonly@marcansoft.com) by mail.marcansoft.com (Postfix) with ESMTPSA id 6A1EC4262F; Tue, 14 Feb 2023 08:01:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=marcan.st; s=default; t=1676361697; bh=LulywthSgoMY00ciMXgI8pcvl/7Qitv9bYFn/FgF6PQ=; h=From:To:Cc:Subject:Date; b=AWRsTTF3+iGzsWXu17baKH3m5EzkQMdg/dFeHRKwed3zbqu/SqjC9QyPuo2D4aRyK O12+cLq/8xgBc25us+dltD9mtkUPIEhNyM/qCgM4yFMSS/pIpvesaEeI7az/wLgCPl kHFJf+0wI4eLTdUwS/QigUUbRTgVRtjrlo9gLCjf3cGv6Tb2Igli500PMROPkukrAH vn+ret+pep8fCWogjKUabyp51SaKdpc8tkAH4l8hVEpHujYYO4SqVkkg50agOn99dC RqD7W6XuBoTUlYSLOtejM5qrkGme47AyHcpEcR9YfxzY2UjNhTkQD26JOwhI6j6FsY ZADQXS7v5ERNw== From: Hector Martin <marcan@marcan.st> To: Arend van Spriel <aspriel@gmail.com>, Franky Lin <franky.lin@broadcom.com>, Hante Meuleman <hante.meuleman@broadcom.com>, Kalle Valo <kvalo@kernel.org>, "David S. Miller" <davem@davemloft.net>, Eric Dumazet <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com> Cc: Sven Peter <sven@svenpeter.dev>, Alyssa Rosenzweig <alyssa@rosenzweig.io>, Linus Walleij <linus.walleij@linaro.org>, asahi@lists.linux.dev, linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Hector Martin <marcan@marcan.st> Subject: [PATCH 0/2] Apple T2 platform support Date: Tue, 14 Feb 2023 17:00:32 +0900 Message-Id: <20230214080034.3828-1-marcan@marcan.st> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1757792801213086591?= X-GMAIL-MSGID: =?utf-8?q?1757792801213086591?= |
Series | Apple T2 platform support | |
Message
Hector Martin
Feb. 14, 2023, 8 a.m. UTC
Hi all, This short series adds the missing bits to support Apple T2 platforms. There are two quirks: these devices have firmware that requires the host to provide a blob of randomness as a seed (presumably because the chipsets lack a proper RNG), and the module/antenna information that is used for Apple firmware selection and comes from the Device Tree on ARM64 systems (already upstream) needs to come from ACPI on these instead. Changes since the megaseries from a ~year ago: made the ACPI code bail if there is no module-instance, so we don't try to get the antenna info at all in that case (as suggested by Arend). Made the randomness conditional on an Apple OTP being present, since it's not known to be needed on non-Apple firmware. Hector Martin (2): brcmfmac: acpi: Add support for fetching Apple ACPI properties brcmfmac: pcie: Provide a buffer of random bytes to the device .../broadcom/brcm80211/brcmfmac/Makefile | 2 + .../broadcom/brcm80211/brcmfmac/acpi.c | 51 +++++++++++++++++++ .../broadcom/brcm80211/brcmfmac/common.c | 1 + .../broadcom/brcm80211/brcmfmac/common.h | 9 ++++ .../broadcom/brcm80211/brcmfmac/pcie.c | 32 ++++++++++++ 5 files changed, 95 insertions(+) create mode 100644 drivers/net/wireless/broadcom/brcm80211/brcmfmac/acpi.c
Comments
Hi Hector I’ve applied the following patchset (arranged in chronological order) to linux 6.2, and wifi seems to have broken on MacBookPro16,1 (brcmfmac4364b3) https://lore.kernel.org/asahi/20230212063813.27622-1-marcan@marcan.st/T/#t (BCM4355/4364/4377 support & identification fixes) https://lore.kernel.org/asahi/20230214080034.3828-1-marcan@marcan.st/T/#t (Apple T2 platform support) https://lore.kernel.org/asahi/20230214091651.10178-1-marcan@marcan.st/T/#t (BCM4387 / Apple M1 platform support) https://lore.kernel.org/asahi/b4489e24-e226-4f99-1322-cab6c1269f09@broadcom.com/T/#t (brcmfmac: cfg80211: Use WSEC to set SAE password) The logs show: Feb 23 20:08:57 MacBook kernel: usbcore: registered new interface driver brcmfmac Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: enabling device (0000 -> 0002) Feb 23 20:08:57 MacBook kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4 Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.Apple Inc.-MacBookPro16,1.bin failed with error -2 Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.bin failed with error -2 Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_setup: Dongle setup failed I also tested the patchiest in the following link, and wifi mostly worked there (occasionally it complained about some pic error, I’ll save the logs next time I encounter that) : https://github.com/t2linux/linux-t2-patches/blob/main/8001-asahilinux-wifi-patchset.patch Thanks Aditya > On 14-Feb-2023, at 1:30 PM, Hector Martin <marcan@marcan.st> wrote: > > Hi all, > > This short series adds the missing bits to support Apple T2 platforms. > > There are two quirks: these devices have firmware that requires the > host to provide a blob of randomness as a seed (presumably because the > chipsets lack a proper RNG), and the module/antenna information that > is used for Apple firmware selection and comes from the Device Tree > on ARM64 systems (already upstream) needs to come from ACPI on these > instead. > > Changes since the megaseries from a ~year ago: made the ACPI code bail > if there is no module-instance, so we don't try to get the antenna > info at all in that case (as suggested by Arend). Made the randomness > conditional on an Apple OTP being present, since it's not known to be > needed on non-Apple firmware. > > Hector Martin (2): > brcmfmac: acpi: Add support for fetching Apple ACPI properties > brcmfmac: pcie: Provide a buffer of random bytes to the device > > .../broadcom/brcm80211/brcmfmac/Makefile | 2 + > .../broadcom/brcm80211/brcmfmac/acpi.c | 51 +++++++++++++++++++ > .../broadcom/brcm80211/brcmfmac/common.c | 1 + > .../broadcom/brcm80211/brcmfmac/common.h | 9 ++++ > .../broadcom/brcm80211/brcmfmac/pcie.c | 32 ++++++++++++ > 5 files changed, 95 insertions(+) > create mode 100644 drivers/net/wireless/broadcom/brcm80211/brcmfmac/acpi.c > > -- > 2.35.1 > >
> On 23-Feb-2023, at 8:31 PM, Aditya Garg <gargaditya08@live.com> wrote: > > Hi Hector > > I’ve applied the following patchset (arranged in chronological order) to linux 6.2, > and wifi seems to have broken on MacBookPro16,1 (brcmfmac4364b3) > > https://lore.kernel.org/asahi/20230212063813.27622-1-marcan@marcan.st/T/#t (BCM4355/4364/4377 support & identification fixes) > > https://lore.kernel.org/asahi/20230214080034.3828-1-marcan@marcan.st/T/#t (Apple T2 platform support) > > https://lore.kernel.org/asahi/20230214091651.10178-1-marcan@marcan.st/T/#t (BCM4387 / Apple M1 platform support) > > https://lore.kernel.org/asahi/b4489e24-e226-4f99-1322-cab6c1269f09@broadcom.com/T/#t (brcmfmac: cfg80211: Use WSEC to set SAE password) > > > The logs show: > > Feb 23 20:08:57 MacBook kernel: usbcore: registered new interface driver brcmfmac > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: enabling device (0000 -> 0002) > Feb 23 20:08:57 MacBook kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.Apple Inc.-MacBookPro16,1.bin failed with error -2 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.bin failed with error -2 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_setup: Dongle setup failed > > I also tested the patchiest in the following link, and wifi mostly worked there (occasionally it complained about some pic error, I’ll save the logs next time I encounter that) : > Sorry for the typos here (thanks to autocorrect) It says I also tested the *patchset* in the following link, and wifi mostly worked there (occasionally it complained about some *pci* error, I’ll save the logs next time I encounter that) : > > https://github.com/t2linux/linux-t2-patches/blob/main/8001-asahilinux-wifi-patchset.patch > > Thanks > Aditya > >> On 14-Feb-2023, at 1:30 PM, Hector Martin <marcan@marcan.st> wrote: >> >> Hi all, >> >> This short series adds the missing bits to support Apple T2 platforms. >> >> There are two quirks: these devices have firmware that requires the >> host to provide a blob of randomness as a seed (presumably because the >> chipsets lack a proper RNG), and the module/antenna information that >> is used for Apple firmware selection and comes from the Device Tree >> on ARM64 systems (already upstream) needs to come from ACPI on these >> instead. >> >> Changes since the megaseries from a ~year ago: made the ACPI code bail >> if there is no module-instance, so we don't try to get the antenna >> info at all in that case (as suggested by Arend). Made the randomness >> conditional on an Apple OTP being present, since it's not known to be >> needed on non-Apple firmware. >> >> Hector Martin (2): >> brcmfmac: acpi: Add support for fetching Apple ACPI properties >> brcmfmac: pcie: Provide a buffer of random bytes to the device >> >> .../broadcom/brcm80211/brcmfmac/Makefile | 2 + >> .../broadcom/brcm80211/brcmfmac/acpi.c | 51 +++++++++++++++++++ >> .../broadcom/brcm80211/brcmfmac/common.c | 1 + >> .../broadcom/brcm80211/brcmfmac/common.h | 9 ++++ >> .../broadcom/brcm80211/brcmfmac/pcie.c | 32 ++++++++++++ >> 5 files changed, 95 insertions(+) >> create mode 100644 drivers/net/wireless/broadcom/brcm80211/brcmfmac/acpi.c >> >> -- >> 2.35.1 >> >> >
> > I also tested the *patchset* in the following link, and wifi mostly worked there (occasionally it complained about some *pci* error, I’ll save the logs next time I encounter that) : I got the logs as follows: Feb 24 12:04:50 MacBook kernel: usbcore: registered new interface driver brcmfmac Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: enabling device (0000 -> 0002) Feb 24 12:04:50 MacBook kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4364b3-pcie for chip BCM4364/4 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,bali-HRPN-u-7.7-X3.bin failed with error -2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,bali-HRPN-u-7.7.bin failed with error -2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,bali-HRPN-u.bin failed with error -2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,bali-HRPN.bin failed with error -2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for brcm/brcmfmac4364b3-pcie.apple,bali-X3.bin failed with error -2 Feb 24 12:04:50 MacBook kernel: brcmfmac_bca: brcmf_bca_attach: executing Feb 24 12:04:50 MacBook kernel: brcmfmac_bca: brcmf_bca_detach: executing Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_setup: Dongle setup failed Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 0000.853 EL: 30 3e84 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.853 Thread: wlan_thread(ID:0x54485244) run cnt:2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.854 Thread: Stack:0029ff34 Start Addr:0029e000 End Addr:0029ffdf Size:8160 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.854 Thread: Entry func:0016f819 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.854 Thread: Timer:001ca70c Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.854 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: FWID 01-23419ed2 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: flags 78010007 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.854 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: TRAP 4(29fef8): pc 16e218, lr 16e205, sp 29ff50, cpsr 60000193, spsr 60000033 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.855 dfsr 80d, dfar 0 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.855 r0 1, r1 0, r2 160988, r3 0, r4 167f35, r5 1, r6 167f35 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.855 r7 0, r8 0, r9 0, r10 29e000, r11 80d, r12 0 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.855 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: sp+0 00280648 00019783 00000000 00167f35 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+10 00280648 00168301 00236ec4 00000002 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+4 00019783 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+c 00167f35 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+14 00168301 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+2c 00019783 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.856 sp+34 0003910f Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.857 sp+44 0016f8e7 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.857 sp+4c 0003d1c5 Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.857 sp+60 0000c02b Feb 24 12:04:50 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_bus_console_read: CONSOLE: 000000.857 sp+6c 0003dfcd
Aditya Garg <gargaditya08@live.com> writes: > On 23-Feb-2023, at 8:31 PM, Aditya Garg <gargaditya08@live.com> wrote: > > Hi Hector > > I’ve applied the following patchset (arranged in chronological order) to linux 6.2, > and wifi seems to have broken on MacBookPro16,1 (brcmfmac4364b3) > > https://lore.kernel.org/asahi/20230212063813.27622-1-marcan@marcan.st/T/#t > (BCM4355/4364/4377 support & identification fixes) > > https://lore.kernel.org/asahi/20230214080034.3828-1-marcan@marcan.st/T/#t (Apple T2 > platform support) > > https://lore.kernel.org/asahi/20230214091651.10178-1-marcan@marcan.st/T/#t (BCM4387 > / Apple M1 platform support) > > https://lore.kernel.org/asahi/b4489e24-e226-4f99-1322-cab6c1269f09@broadcom.com/T/#t > (brcmfmac: cfg80211: Use WSEC to set SAE password) > > The logs show: > > Feb 23 20:08:57 MacBook kernel: usbcore: registered new interface driver brcmfmac > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: enabling device (0000 -> 0002) > Feb 23 20:08:57 MacBook kernel: brcmfmac: brcmf_fw_alloc_request: using > brcm/brcmfmac4364b3-pcie for chip BCM4364/4 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for > brcm/brcmfmac4364b3-pcie.Apple Inc.-MacBookPro16,1.bin failed with error -2 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for > brcm/brcmfmac4364b3-pcie.bin failed with error -2 > Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_setup: Dongle setup > failed > > I also tested the patchiest in the following link, and wifi mostly worked there (occasionally it > complained about some pic error, I’ll save the logs next time I encounter that) : > > https://github.com/t2linux/linux-t2-patches/blob/main/8001-asahilinux-wifi-patchset.patch > > Thanks > Aditya > > I just noticed that the patch to ACPI was missing. Adding that fixed the issue. > > https://github.com/t2linux/linux-t2-patches/blob/main/8005-ACPI-property-Support-strings-in-Apple-_DSM-props.patch Please don't use HTML, our lists drop those. I'll reply in text/plain so that is info is archived.
> On 24-Feb-2023, at 6:42 PM, Kalle Valo <kvalo@kernel.org> wrote: > > Aditya Garg <gargaditya08@live.com> writes: > >> On 23-Feb-2023, at 8:31 PM, Aditya Garg <gargaditya08@live.com> wrote: >> >> Hi Hector >> >> I’ve applied the following patchset (arranged in chronological order) to linux 6.2, >> and wifi seems to have broken on MacBookPro16,1 (brcmfmac4364b3) >> >> https://lore.kernel.org/asahi/20230212063813.27622-1-marcan@marcan.st/T/#t >> (BCM4355/4364/4377 support & identification fixes) >> >> https://lore.kernel.org/asahi/20230214080034.3828-1-marcan@marcan.st/T/#t (Apple T2 >> platform support) >> >> https://lore.kernel.org/asahi/20230214091651.10178-1-marcan@marcan.st/T/#t (BCM4387 >> / Apple M1 platform support) >> >> https://lore.kernel.org/asahi/b4489e24-e226-4f99-1322-cab6c1269f09@broadcom.com/T/#t >> (brcmfmac: cfg80211: Use WSEC to set SAE password) >> >> The logs show: >> >> Feb 23 20:08:57 MacBook kernel: usbcore: registered new interface driver brcmfmac >> Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: enabling device (0000 -> 0002) >> Feb 23 20:08:57 MacBook kernel: brcmfmac: brcmf_fw_alloc_request: using >> brcm/brcmfmac4364b3-pcie for chip BCM4364/4 >> Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for >> brcm/brcmfmac4364b3-pcie.Apple Inc.-MacBookPro16,1.bin failed with error -2 >> Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: Direct firmware load for >> brcm/brcmfmac4364b3-pcie.bin failed with error -2 >> Feb 23 20:08:57 MacBook kernel: brcmfmac 0000:05:00.0: brcmf_pcie_setup: Dongle setup >> failed >> >> I also tested the patchiest in the following link, and wifi mostly worked there (occasionally it >> complained about some pic error, I’ll save the logs next time I encounter that) : >> >> https://github.com/t2linux/linux-t2-patches/blob/main/8001-asahilinux-wifi-patchset.patch >> >> Thanks >> Aditya >> >> I just noticed that the patch to ACPI was missing. Adding that fixed the issue. >> >> https://github.com/t2linux/linux-t2-patches/blob/main/8005-ACPI-property-Support-strings-in-Apple-_DSM-props.patch > > Please don't use HTML, our lists drop those. I'll reply in text/plain so > that is info is archived. > Hi Sorry for that. I actually forgot to format that email as plain text. > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches