Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E04B5C61DA4 for ; Wed, 15 Mar 2023 09:59:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229720AbjCOJ7S (ORCPT ); Wed, 15 Mar 2023 05:59:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230491AbjCOJ6v (ORCPT ); Wed, 15 Mar 2023 05:58:51 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A34579B3D for ; Wed, 15 Mar 2023 02:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=95yfwrs7cwTHTJyhdBEndquZDdnynLTpS5h9w6xUWIE=; t=1678874245; x=1680083845; b=jFYkCQM7rzKEqhy0pPQ6LUGmPvVEeSKTffHrhe+lEQi/i8P uOSmCPDYPcb6Bqwoq/hrlM9lwiPcTtVgyvMejYeRPLTOJlo39JbG+EFfG9SFmxBgXwe5K2LmV0xo8 qNWDx4xh3u89fvFLmwOVo98Db7/xFp4j2dRI/uVYh+En6+f7GQ4RMfcJ+3fjbdjkqChU33E+lRXJZ mYs/C+C35KW3n67/Z8tjbPLka7houk8M4RsTtkbqNqzB28pJP/KiKqjnq+reQv2E1oRqkFctFjWHh ZhwYBGNPqaAfdnOBv95qI5x9ulSRQEGdwdoohNqEvLoDiQzqpXFTGK6mlV2YPWQA==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1pcNsl-0042mY-2x; Wed, 15 Mar 2023 10:57:20 +0100 Message-ID: Subject: Re: wifi breakage due to commit "wifi: brcmfmac: add support for vendor-specific firmware api" From: Johannes Berg To: Arend van Spriel , Michael Stapelberg Cc: Kalle Valo , Franky Lin , Pieter-Paul Giesberts , Hante Meuleman , linux-wireless@vger.kernel.org Date: Wed, 15 Mar 2023 10:57:18 +0100 In-Reply-To: <89262772-7358-77e8-8913-c459819d544a@broadcom.com> References: <186e23b5668.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> <186e26dc0a8.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> <186e4673718.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> <89262772-7358-77e8-8913-c459819d544a@broadcom.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 X-malware-bazaar: not-scanned Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, 2023-03-15 at 10:12 +0100, Arend van Spriel wrote: >=20 > I think it works pretty similar to firmware loading. These days firmware= =20 > loading does not rely on a user-space helper and I assumed the same is= =20 > true for module loading. Will look into it. >=20 As far as I know you still need the modprobe helper in /proc/sys/kernel/modprobe johannes