[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sf3y7b1u.fsf@waldekranz.com>
Date: Tue, 19 Dec 2023 11:15:41 +0100
From: Tobias Waldekranz <tobias@...dekranz.com>
To: Marek BehĂșn <kabel@...nel.org>
Cc: davem@...emloft.net, kuba@...nel.org, linux@...linux.org.uk,
andrew@...n.ch, hkallweit1@...il.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
netdev@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next 1/4] net: phy: marvell10g: Support firmware
loading on 88X3310
On tis, dec 19, 2023 at 10:22, Marek BehĂșn <kabel@...nel.org> wrote:
> On Thu, 14 Dec 2023 21:14:39 +0100
> Tobias Waldekranz <tobias@...dekranz.com> wrote:
>
>> +MODULE_FIRMWARE("mrvl/x3310fw.hdr");
>
> And do you have permission to publish this firmware into linux-firmware?
No, I do not.
> Because when we tried this with Marvell, their lawyer guy said we can't
> do that...
I don't even have good enough access to ask the question, much less get
rejected by Marvell :) I just used that path so that it would line up
with linux-firmware if Marvell was to publish it in the future.
Should MODULE_FIRMWARE be avoided for things that are not in
linux-firmware?
Powered by blists - more mailing lists