[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a657c02-b688-4f2f-bb0b-fd25d19a54be@broadcom.com>
Date: Mon, 28 Apr 2025 10:45:59 +0200
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Johannes Berg <johannes@...solutions.net>,
Artur Rojek <artur@...clusive.pl>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>
Cc: linux-wireless@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Jakub Klama <jakub@...clusive.pl>,
Wojciech Kloska <wojciech@...clusive.pl>,
Ulf Axelsson <ulf.axelsson@...dicsemi.no>, Josh Boyer <jwboyer@...nel.org>
Subject: Re: [RFC PATCH v2 0/2] wifi: Nordic nRF70 series
+ Josh
On 4/25/2025 8:11 PM, Johannes Berg wrote:
> On Tue, 2025-04-22 at 19:59 +0200, Artur Rojek wrote:
>> 1) Nordic gave us permission to upstream the firmware blob [1] required
>> to use this driver. As that needs to go through separate
>> linux-firmware repository and is subject to different licensing,
>> should I try to upstream it in parallel with this series, or does it
>> need to wait until the kernel driver gets in?
>
> I have no idea. Chicken and egg, I guess.
It used to be a check by the linux-firmware maintainer if the firmware
blob is referenced in kernel module info. I assume the main linux tree
is checked and not linux-next.
Regards,
Arend
Powered by blists - more mailing lists