From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: "Marek Behún" <kabel@kernel.org>,
davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] net: phy: marvell10g: Support firmware loading on 88X3310
Date: Tue, 2 Jan 2024 10:12:26 +0000 [thread overview]
Message-ID: <ZZPhiuyvEepIcbKm@shell.armlinux.org.uk> (raw)
In-Reply-To: <87sf3y7b1u.fsf@waldekranz.com>
On Tue, Dec 19, 2023 at 11:15:41AM +0100, Tobias Waldekranz wrote:
> On tis, dec 19, 2023 at 10:22, Marek Behún <kabel@kernel.org> wrote:
> > On Thu, 14 Dec 2023 21:14:39 +0100
> > Tobias Waldekranz <tobias@waldekranz.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?
Without the firmware being published, what use is having this code in
mainline kernels?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-01-02 10:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 20:14 [PATCH net-next 0/4] net: phy: marvell10g: Firmware loading and LED support for 88X3310 Tobias Waldekranz
2023-12-14 20:14 ` [PATCH net-next 1/4] net: phy: marvell10g: Support firmware loading on 88X3310 Tobias Waldekranz
2023-12-15 14:30 ` Andrew Lunn
2023-12-15 14:34 ` Russell King (Oracle)
2023-12-18 17:11 ` Tobias Waldekranz
2023-12-15 14:33 ` Andrew Lunn
2023-12-15 15:52 ` Russell King (Oracle)
2023-12-16 14:35 ` kernel test robot
2023-12-19 9:22 ` Marek Behún
2023-12-19 10:15 ` Tobias Waldekranz
2023-12-19 10:49 ` Marek Behún
2023-12-19 13:15 ` Tobias Waldekranz
2024-01-02 10:12 ` Russell King (Oracle) [this message]
2024-01-02 13:09 ` Tobias Waldekranz
2024-10-06 16:15 ` Daniel Golle
2024-10-06 21:32 ` Tobias Waldekranz
2023-12-14 20:14 ` [PATCH net-next 2/4] net: phy: marvell10g: Fix power-up when strapped to start powered down Tobias Waldekranz
2023-12-15 15:44 ` Russell King (Oracle)
2023-12-18 18:02 ` Tobias Waldekranz
2023-12-14 20:14 ` [PATCH net-next 3/4] net: phy: marvell10g: Add LED support for 88X3310 Tobias Waldekranz
2023-12-15 14:44 ` Andrew Lunn
2023-12-15 15:12 ` Russell King (Oracle)
2023-12-18 15:55 ` Simon Horman
2023-12-14 20:14 ` [PATCH net-next 4/4] dt-bindings: net: marvell10g: Document LED polarity Tobias Waldekranz
2023-12-15 8:47 ` Krzysztof Kozlowski
2023-12-15 11:19 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZZPhiuyvEepIcbKm@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tobias@waldekranz.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.