Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp189570imn; Tue, 2 Aug 2022 23:19:21 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s6mSQBUFdfT1A2KEhPPZ9I12zoNymvoI01qobAc9vfirCxHWDw5k6lON430wgW50V81Ooe X-Received: by 2002:a63:5c22:0:b0:41a:56e8:27d with SMTP id q34-20020a635c22000000b0041a56e8027dmr19728404pgb.22.1659507561155; Tue, 02 Aug 2022 23:19:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659507561; cv=none; d=google.com; s=arc-20160816; b=hnx1r0C8FbViS3QQC6tAjyWhr6MdSrW0feOSALwWmqxSpqcnmn8V7mknQ975e6Oop1 8bBfedSDs58N9EJmV/1KYEIeOXi7N4JDsmLdF3h5G0coHuNwdoKgr7Io+baomm3pCaF1 MYdVgZV27bNWeE4+tko3M1s1cKtaE2bAvWVjWKlkw7U2sAd1K2tHlxukyNS0TgaJdeOh G5SluPMcCfrcsJgX8A9KP5atjEFCB/iGO/tkRME3YFy9/NxfCtN32/4pqa+KixemFmB6 zV8WrTafqNdbhLLpYnL0g+UPvegyFRarJe3uBYEDPuZEhE4mpEwZZf6I0YDtCCRLUMZW oGXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:to:from:date:dkim-signature; bh=REq99owLsoeMmTs+RoiqBlfYuDOwkJ/Fk991HAwfS7k=; b=oeNDdThCU511ESPgiC3XhIf3ulB9B4p32Rqh13Xdxi0XPy9yxgIWdNVKGu4fPcTvDe 0Q3kOk6y3dtymRXw60qZMwR1L8VgJB4N/c1FNaxDRI8P7cbb5MmAKt2xFMVpLabIaPGw 10JczvRlFxgixHyJcLaY24WNuPfG7vc+LmjYG9c6XIwQw47exevlVCQRg5D5733ZzKAj LIBsn+Xl1p5/9J/kO+H6b6c6Lg2ZNN/+zwVG6PVsVN70RydeGva/XOLo5lbQJKpHAfU3 fPKbwvXF+kMYsjgAVuWZbADhBldrGCcXhW+AFMWSwi8c35CfeMm5agdHh4dbFBOzrsEN 3JmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=msIDcyFy; 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=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w21-20020a631615000000b0041b698ead1asi3135620pgl.794.2022.08.02.23.19.02; Tue, 02 Aug 2022 23:19:21 -0700 (PDT) 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=@linuxfoundation.org header.s=korg header.b=msIDcyFy; 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=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234798AbiHCGIi (ORCPT + 99 others); Wed, 3 Aug 2022 02:08:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229789AbiHCGIh (ORCPT ); Wed, 3 Aug 2022 02:08:37 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AC7551A3A5 for ; Tue, 2 Aug 2022 23:08:36 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 5D43AB8217F for ; Wed, 3 Aug 2022 06:08:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A7247C433C1; Wed, 3 Aug 2022 06:08:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1659506914; bh=kfuk+0aXynx06c3o3pjaVWnK/rbUgbtj8vWQB25K0h4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=msIDcyFyyQTgdnwORVlVDKoZzClCZT4T7BgWa4BJukdoknUguA/1elFnmNMVKmb9u Bwd73X2uFBEvzefFQUlhf4cec64iCh2hIer2UqlUnBhAhwwovGYhi6ZU3n7CbHmugo t9XKL1KwaiPKRgXO2RgioVF2pGCbSAh/NcMwQOXM= Date: Wed, 3 Aug 2022 08:08:31 +0200 From: Greg KH To: Grzegorz Szymaszek , Larry Finger , Phillip Potter , linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev Subject: Re: [PATCH] staging: r8188eu: add firmware dependency Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, 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: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 02, 2022 at 07:18:44PM +0200, Grzegorz Szymaszek wrote: > The old rtl8188eu module, removed in commit 55dfa29b43d2 ("staging: > rtl8188eu: remove rtl8188eu driver from staging dir") (Linux kernel > v5.15-rc1), required (through a MODULE_FIRMWARE call()) the > rtlwifi/rtl8188eufw.bin firmware file, which the new r8188eu driver no > longer requires. > > I have tested a few RTL8188EUS-based Wi-Fi cards and, while supported by > both drivers, they do not work when using the new one and the firmware > wasn't manually loaded. According to Larry Finger, the module > maintainer, all such cards need the firmware and the driver should > depend on it (see the linked mails). > > Add a proper MODULE_FIRMWARE() call, like it was done in the old driver. > > Thanks to Greg Kroah-Hartman and Larry Finger for quick responses to my > questions. > > Link: https://answers.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+question/702611 > Link: https://lore.kernel.org/lkml/YukkBu3TNODO3or9@nx64de-df6d00/ > Signed-off-by: Grzegorz Szymaszek > --- > drivers/staging/r8188eu/os_dep/os_intfs.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/staging/r8188eu/os_dep/os_intfs.c b/drivers/staging/r8188eu/os_dep/os_intfs.c > index 891c85b088ca..5bd3022e4b40 100644 > --- a/drivers/staging/r8188eu/os_dep/os_intfs.c > +++ b/drivers/staging/r8188eu/os_dep/os_intfs.c > @@ -18,6 +18,7 @@ MODULE_LICENSE("GPL"); > MODULE_DESCRIPTION("Realtek Wireless Lan Driver"); > MODULE_AUTHOR("Realtek Semiconductor Corp."); > MODULE_VERSION(DRIVERVERSION); > +MODULE_FIRMWARE("rtlwifi/rtl8188eufw.bin"); This looks good, and I'll apply it after 5.20-rc1 is out, but you might want to send a follow-on patch that removes the hard-coded string in 2 places in the driver, and just puts it into a single define somewhere, to make it a bit easier over time. Most other drivers do this as well, so there are examples to look at. thanks, greg k-h